Constant BSOD: SYSTEM_SERVICE_EXCEPTION, BAD_POOL_HEADER

fabian5003 · 15 Jun 2012

Hello everyone,

My computer has been suffering this last year. These horrible BSOD keep happening, I thought it was dust on the board, so I cleaned it, it was good for a while but then it kept happening again. Normally the BSOD occurs while playing a YouTube video, playing a videogame, or simply just doing something else, but most of the times it happens with videos or videogames. Could it be video card related? Maybe, or maybe a RAM issue. I really wish it was a software issue, like a driver or something.

The board is an Asus m4a78lt. It has a built-in videocard, AMD 760g (drivers up to date).

Any help will be greatly appreciated. If you need any other info, just let me know!

I excuse myself if some of the logs are in Spanish. This is a family computer and I'm the only one who sort of speak English.

Thanks.

usasma · 16 Jun 2012

Running the last 10 memory dumps (there's more than 40, but the 40 are from 09 May to the present)

SP1 isn't installed, please do the following:

Installing Windows 7 Service Pack 1
1. Visit the PC manufacturer's website and update ALL drivers. DO NOT use Windows Update or the "Update drivers" function of Device Manager.
2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
3. Visit Windows Update and get all updates (may take repeated visits)
4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
NOTE: For Vista, read these notes:

Read these notes for installing Vista SP1: Learn how to install Windows Vista Service Pack 1 (SP1)
Read these notes for installing Vista SP2: Learn how to install Windows Vista Service Pack 2 (SP2)

5. Visit Windows Update and get any other available updates. May take repeated visits, but keep it up until you get several "Windows is updated" results.
If you're having difficulties with installing a Service Pack, please use the SURTool from this link: What is the System Update Readiness Tool?
Also, check out this troubleshooting link from Microsoft: Troubleshoot problems installing Service Pack 1 (SP1) for Windows 7 and Windows Server 2008 R2

I have had limited success in installing updates/Service Packs when using a "clean boot". I suspect that I'm just bypassing the problem - and that it can come back to bite me in the butt later on.

The MSINFO32 report is missing, please do the following:

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.

Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

Some free alternatives (I don't use them, so I can't comment on them)

MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor

LogMeIn/Hamachi drivers date from 2007 through 2009. Please uninstall it.

One suggestion (to try if all the stuff above doesn't work) is to set the memory settings manually in the BIOS. Use the recommended settings from the RAM manufacturer. If you need assistance with this, please post a separate topic over in this forum: Hardware & Devices - Windows 7 Forums

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


AODDriver2.sys   Tue Mar 06 04:55:00 2012 (4F55DEF4)
ASACPI.sys       Wed Jul 15 23:31:29 2009 (4A5E9F11)
AtiPcie.sys      Tue May 05 11:00:22 2009 (4A005486)
L1C62x64.sys     Wed Apr 01 01:09:17 2009 (49D2F6FD)
LMIRfsDriver.sys Mon Jul 14 12:26:56 2008 (487B7E50)
MpFilter.sys     Wed Apr 06 16:07:29 2011 (4D9CC801)
MpNWMon.sys      Wed Apr 06 16:07:23 2011 (4D9CC7FB)
NisDrvWFP.sys    Wed Apr 06 16:08:53 2011 (4D9CC855)
PxHlpa64.sys     Tue Oct 20 14:08:42 2009 (4ADDFCAA)
RaInfo.sys       Fri Jan 04 13:57:14 2008 (477E818A)
SCDEmu.SYS       Mon Apr 09 23:37:52 2007 (461B0690)
a0b9slkd.SYS     Tue Jul 14 17:12:55 2009 (4A5CF4D7)
a1ky1xrz.SYS     Tue Jul 14 17:12:55 2009 (4A5CF4D7)
a20zqlwu.SYS     Tue Jul 14 17:12:55 2009 (4A5CF4D7)
a5zvbqqm.SYS     Tue Jul 14 17:12:55 2009 (4A5CF4D7)
adfs.SYS         Thu Jun 26 16:52:37 2008 (48640195)
ag5ztj4a.SYS     Tue Jul 14 17:12:55 2009 (4A5CF4D7)
ajsry28t.SYS     Tue Jul 14 17:12:55 2009 (4A5CF4D7)
alc5fjyy.SYS     Tue Jul 14 17:12:55 2009 (4A5CF4D7)
amdiox64.sys     Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys      Fri Mar 19 12:18:18 2010 (4BA3A3CA)
aopvd53j.SYS     Tue Jul 14 17:12:55 2009 (4A5CF4D7)
at165ilg.SYS     Tue Jul 14 17:12:55 2009 (4A5CF4D7)
atikmdag.sys     Wed Aug 25 21:47:22 2010 (4C75C7AA)
atikmpag.sys     Wed Aug 25 21:20:56 2010 (4C75C178)
aui7nxhx.SYS     Tue Jul 14 17:12:55 2009 (4A5CF4D7)
hamachi.sys      Thu Feb 19 05:36:41 2009 (499D3639)
lmimirr.sys      Tue Apr 10 18:32:45 2007 (461C108D)
nvBridge.kmd     Wed Feb 23 02:34:23 2011 (4D64B87F)
nvlddmkm.sys     Thu Feb 09 21:02:58 2012 (4F347AD2)
nvlddmkm.sys     Wed Feb 23 02:46:52 2011 (4D64BB6C)
sphr.sys         Sun Oct 11 16:55:14 2009 (4AD24632)
spjo.sys         Sun Oct 11 16:55:14 2009 (4AD24632)
splr.sys         Sun Oct 11 16:55:14 2009 (4AD24632)
spmk.sys         Sun Oct 11 16:55:14 2009 (4AD24632)
spmw.sys         Sun Oct 11 16:55:14 2009 (4AD24632)
spow.sys         Sun Oct 11 16:55:14 2009 (4AD24632)
spsc.sys         Sun Oct 11 16:55:14 2009 (4AD24632)
spvf.sys         Sun Oct 11 16:55:14 2009 (4AD24632)
spya.sys         Sun Oct 11 16:55:14 2009 (4AD24632)
spyr.sys         Sun Oct 11 16:55:14 2009 (4AD24632)
viahduaa.sys     Tue Sep 28 05:53:08 2010 (4CA1BB04)

Code:


Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061212-30888-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Jun 12 14:33:08.121 2012 (UTC - 4:00)
System Uptime: 0 days 0:42:48.542
BugCheck 19, {3, fffffa80021b3200, fffffa80021b3200, 42526354005a0006}
*** WARNING: Unable to verify timestamp for spjo.sys
*** ERROR: Module load completed but symbols could not be loaded for spjo.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c7b )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+c7b
Bugcheck code 00000019
Arguments 00000000`00000003 fffffa80`021b3200 fffffa80`021b3200 42526354`005a0006
BiosVersion = 0606   
BiosReleaseDate = 04/14/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061212-33930-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Tue Jun 12 21:58:26.024 2012 (UTC - 4:00)
System Uptime: 0 days 0:06:04.320
BugCheck 3B, {c0000005, fffff8800125a5e0, fffff880070ba050, 0}
Probably caused by : hardware ( fltmgr!FltpFastIoRead+1c0 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  calibre.exe
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0125a5e0 fffff880`070ba050 00000000`00000000
BiosVersion = 0606   
BiosReleaseDate = 04/14/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061312-18938-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Jun 13 17:09:38.119 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:52.430
BugCheck 19, {20, fffff8a003e51be0, fffff8a003e52a30, 5e51bf0}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGDEVICE::DestroyAllocations+248 )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x19_20_dxgkrnl!DXGDEVICE::DestroyAllocations+248
Bugcheck code 00000019
Arguments 00000000`00000020 fffff8a0`03e51be0 fffff8a0`03e52a30 00000000`05e51bf0
BiosVersion = 0606   
BiosReleaseDate = 04/14/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061312-20404-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Jun 13 17:07:17.568 2012 (UTC - 4:00)
System Uptime: 0 days 1:06:25.004
BugCheck 19, {3, fffffa800153d6b0, fffffa800153d6a0, fffffa800153d6b0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a56 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  services.exe
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a56
Bugcheck code 00000019
Arguments 00000000`00000003 fffffa80`0153d6b0 fffffa80`0153d6a0 fffffa80`0153d6b0
BiosVersion = 0606   
BiosReleaseDate = 04/14/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061312-23790-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Jun 13 17:31:34.231 2012 (UTC - 4:00)
System Uptime: 0 days 0:14:55.667
BugCheck D1, {fffffffffffffffc, 2, 0, fffff880016e5b3b}
Probably caused by : ndis.sys ( ndis!NdisReturnPackets+4b )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  LogMeIn.exe
FAILURE_BUCKET_ID:  X64_0xD1_ndis!NdisReturnPackets+4b
Bugcheck code 000000D1
Arguments ffffffff`fffffffc 00000000`00000002 00000000`00000000 fffff880`016e5b3b
BiosVersion = 0606   
BiosReleaseDate = 04/14/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061312-25537-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Jun 13 17:37:02.600 2012 (UTC - 4:00)
System Uptime: 0 days 0:05:04.036
BugCheck 3B, {c0000005, fffff800035b5f11, fffff8800666aac0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+186 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpWaitForMultipleObjects+186
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`035b5f11 fffff880`0666aac0 00000000`00000000
BiosVersion = 0606   
BiosReleaseDate = 04/14/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061312-33181-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Jun 13 17:11:59.522 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:44.958
BugCheck 3B, {c0000005, fffff80003037587, fffff88002983e60, 0}
Probably caused by : NETIO.SYS ( NETIO! ?? ::FNODOBFM::`string'+f89 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_NETIO!_??_::FNODOBFM::_string_+f89
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`03037587 fffff880`02983e60 00000000`00000000
BiosVersion = 0606   
BiosReleaseDate = 04/14/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061412-23930-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Jun 14 17:48:59.809 2012 (UTC - 4:00)
System Uptime: 0 days 0:05:18.104
BugCheck A, {d7d05bc6, 2, 0, fffff800032ce01d}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+18d )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiInsertTimerTable+18d
Bugcheck code 0000000A
Arguments 00000000`d7d05bc6 00000000`00000002 00000000`00000000 fffff800`032ce01d
BiosVersion = 0606   
BiosReleaseDate = 04/14/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061512-29187-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Jun 15 18:31:04.065 2012 (UTC - 4:00)
System Uptime: 0 days 0:29:33.376
BugCheck 3B, {c0000005, fffff800032d71ec, fffff88002485000, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectSafe+c )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  lsass.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ObReferenceObjectSafe+c
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`032d71ec fffff880`02485000 00000000`00000000
BiosVersion = 0606   
BiosReleaseDate = 04/14/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061512-38672-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Jun 15 16:12:44.817 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:36.128
BugCheck 19, {3, fffff80003455a50, ffffffffffffffff, fffff80003455a50}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a56 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  ramaint.exe
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a56
Bugcheck code 00000019
Arguments 00000000`00000003 fffff800`03455a50 ffffffff`ffffffff fffff800`03455a50
BiosVersion = 0606   
BiosReleaseDate = 04/14/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

fabian5003 · 30 Jul 2012

I'm sorry usasma for taking so long. It's just that after following some of your steps I found out the BSOD are being caused by dust on the board. As soon as I clean it, it works OK for about 15 days, then the next two weeks BSOD start to show up every other day, by the fifth week, the BSOD are daily or twice a day, and as soon as I remove the CPU's fan and blow the dust and motes and also clean the RAM slots, it starts working smooth for another two weeks. You can see the improvement immediately, so I have deduced it's actually a physical issue. If only I knew... I mean, I've used PCs with a lot more dust and motes than this one.

Thanks for your help, you are doing a great labor here.

Greetings.