- Bsod error de pool corruption in file area drivers#
- Bsod error de pool corruption in file area update#
- Bsod error de pool corruption in file area driver#
This was probably caused by the following module: ntkrpamp.exe (nt+0x27E33) Google query: ntkrpamp.exe POOL_CORRUPTION_IN_FILE_AREA On Sun 5:11:32 PM GMT your computer crashed
Bsod error de pool corruption in file area update#
It is suggested you look for an update for the following driver: ntkrpamp.exe.
Bsod error de pool corruption in file area driver#
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1B)īugcheck code: 0xDE (0x2, 0xFFFFFFFFEB1181B8, 0xFFFFFFFFFB1181B8, 0xFFFFFFFFE413B8C0)īug check description: This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk.Ī third party driver was identified as the probable root cause of this system error. O n Sun 5:11:32 PM GMT your computer crashedĬrash dump file: C:\WINDOWS\Minidump\Mini081912-01.dmp
Bsod error de pool corruption in file area drivers#
The server has passed two different memory tests on several passes, and all possible third-party drivers that could have been the probable cause have been fixed. What can anyone deduct from these BSODs? Keep in mind that After fixing those drivers, I have pretty much limited the BSODs to the following logs. I have been running Driver Verifier on all drivers for the past couple of days, and a few drivers (hotcore3.sys, ser2pl.sys) seem to have caused Driver Verifier to trip andīSOD, but I have since removed/updated those drivers and no new BSODs have stemmed from them. The server is still having issues crashing with 0xA and 0xDE bugcheck errors. It's been quite a while, but I wanted to update on what's going on. XG20GRV.DLL |XGI Technology|6.14:10.1130 ||XGI Compatible Super VGA Driverĭave Guenthner This posting is provided "AS IS" with no warranties, and confers no rights. XG20GRP.SYS |XGI Technology|6.14:10.1130 ||XGI Compatible Super VGA Driver SER2PL.SYS |Prolific Techn|2.0:0.24 ||USB-to-Serial Cable Driver PTILINK.SYS |Parallel Techn|1.1:0.0 ||Parallel Technologies DirectParallel IO Library HOTCORE3.SYS |Paragon Softwa|9.0:99.9293 ||A part of Paragon System Utilities KAPFA.SYS |Kaseya |6.1:0.0 ||Kaseya Agent Protected File Access Driver REVFS.SYS |Iomega Corpora|2.0:0.21 ||Iomega REV System Software IMDRVFSF.SYS |Iomega Corpora|1.0:3.5 ||Iomega Filter Driver |4.1:1.7043 ||DELL CERC SATA1.5/6ch Miniport DriverĪTMFD.DLL |Adobe Systems |5.2:2.232 ||Windows NT OpenType/Type 1 Font Driverī57XP32.SYS |Broadcom Corpo|12.4:1.1 ||Broadcom NetXtreme Gigabit Ethernet NDIS5.1 Driver.ĪCFSDK32.SYS |Conexant |1.0:2.14 ||Diagnostic Interface x86 DriverĭCDBAS32.SYS |Dell Inc. |4.1:1.7043 ||Dell Management DriverĬERCSR6.SYS |Adaptec, Inc.
Name- |-Company- |-Version- |-Date- |-DESCRIPTION- PstatVer3ĪFAMGT.SYS |Adaptec, Inc. OS Name Microsoft(R) Windows(R) Server 2003 for Small Business Server I would also review what drivers can be safely removed and which ones 3rd party vendor have proided updates. Since memory is cheap and you only have 4 GB, I would replace it. Since server is Windows 2003 and likely has been in serviceįor a long time you may have a hardware problem with RAM. What you can see is that its occuring several times a day at random times.
The system event log only goes back 09:28:20 AM so we can't see *when* this problem started happening.
0 kommentar(er)
