Constant BSOD - ntoskrnl.exe

bryanonbass · Apr 10, 2012

I've been getting tons of BSOD's since October, and eventually, busted up my hard disk in December. I've replaced it and re-installed new windows (windows 7 ultimate x64) retail, yet, I'm still having BSOD's pointing-out ntoskrnl.exe as cause. :cry:

I've tried reseating my processor, re-aligned my RAM, yet the problem still persists. It would really mean a lot if someone can help me address this recurring dilemma I'm having

. My PC is 1.5 years old. It has never been overclocked, no modifications.

P.S. The dumps attached are the ones left after I've accidentally "cleaned" it using CCleaner

. Also, the dumps dated 010402, are actually just new dumps, i forgot to re-calibrate my system clock (i took out the motherboard battery to check it, thus, resetting the clock).

usasma · Apr 10, 2012

MSI Afterburner (along with Riva Tuner and EVGA Precision) are known to cause BSOD's on some Win7 systems. Please uninstall it immediately. The driver dates from 2005.

The memory dumps in MSINFO32 are suggestive of a hardware problem.
This includes:
- hardware problems
- overclocking
- compatibility issues (such as MSI Afterburner)
- low-level driver problems (such as Daemon Tools and AMD OverDrive)
- malware

The memory dumps agree with this
11 memory dumps
7 different BSOD error codes
6 different causes blamed.

One blames you hard drive (010602-17097-01.dmp), so I'd suggest starting with this free hard drive diagnostic: HD Diagnostic

If that doesn't reveal anything, then run the rest of the free hardware diagnostics here: Hardware Diags

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

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 and 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)
- Select the "Custom" installation option and don't let it install AMD OverDrive or the VISION Engine Control Center (if present)
Then use the ATI uninstall manager to uninstall the Catalyst Control Center (CCC). This is a separate issue and isn't required for the AMD OverDrive removal.

If the device (AODDriver or AODDriver4.01) remains a problem in perfmon /report, 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.

Please make sure that you turn Driver Verifier off.

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:

[font=lucida console]
AtihdW76.sys                Tue Dec 06 04:14:25 2011 (4EDDDCF1)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
sptd.sys                    Sun Feb 27 14:29:52 2011 (4D6AA630)
aswTdi.SYS                  Tue Mar 06 19:01:56 2012 (4F56A574)
aswSnx.SYS                  Tue Mar 06 19:04:05 2012 (4F56A5F5)
AtiPcie.sys                 Mon Aug 24 04:25:26 2009 (4A924E76)
aswrdr2.sys                 Tue Mar 06 19:02:19 2012 (4F56A58B)
aswSP.SYS                   Tue Mar 06 19:04:03 2012 (4F56A5F3)
AsIO.sys                    Mon Aug 03 03:03:16 2009 (4A768BB4)
atikmpag.sys                Tue Feb 14 21:13:12 2012 (4F3B14B8)
nusb3xhc.sys                Thu Jan 21 22:22:21 2010 (4B5919ED)
ASACPI.sys                  Wed Jul 15 23:31:29 2009 (4A5E9F11)
Rt64win7.sys                Fri Jun 10 02:33:15 2011 (4DF1BAAB)
atikmdag.sys                Tue Feb 14 21:51:52 2012 (4F3B1DC8)
mcdbus.sys                  Tue Feb 24 05:34:07 2009 (49A3CD1F)
amdiox64.sys                Thu Feb 18 10:17:53 2010 (4B7D5A21)
nusb3hub.sys                Thu Jan 21 22:22:18 2010 (4B5919EA)
AODDriver2.sys              Mon Dec 19 02:30:03 2011 (4EEEE7FB)
cpuz133_x64.sys             Tue May 11 05:58:57 2010 (4BE92A61)
idmwfp.sys                  Wed Jul 06 10:37:41 2011 (4E147335)
RTKVHD64.sys                Wed Mar 17 04:49:15 2010 (4BA0978B)
aswMonFlt.sys               Tue Mar 06 19:01:51 2012 (4F56A56F)
aswFsBlk.SYS                Tue Mar 06 19:01:31 2012 (4F56A55B)
GEARAspiWDM.sys             Mon May 18 08:17:04 2009 (4A1151C0)
[Color=Red]RTCore64.sys                Wed May 25 02:39:12 2005 (42941D90)[/Color]
TuneUpUtilitiesDriver64.sys Thu Sep 17 07:54:52 2009 (4AB2238C)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\041012-17565-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Tue Apr 10 04:04:00.910 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:22.471
Probably caused by : cng.sys ( cng!GatherRandomKey+294 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_VRF_cng!GatherRandomKey+294
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02e58e82 fffff880`033cafc8 fffff880`033ca820
BiosVersion = 1404   
BiosReleaseDate = 05/28/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\041012-17440-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Tue Apr 10 02:37:58.306 2012 (UTC - 4:00)
System Uptime: 0 days 0:04:43.851
Probably caused by : ntkrnlmp.exe ( nt!CmpAllocateKeyControlBlock+72 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!CmpAllocateKeyControlBlock+72
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`031a7542 fffff880`02cf8a80 00000000`00000000
BiosVersion = 1404   
BiosReleaseDate = 05/28/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\041012-17206-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Tue Apr 10 02:29:49.728 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:51.273
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+464bd )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  USBGuard.exe
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+464bd
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`00000cbc 00000c9d`00000078
BiosVersion = 1404   
BiosReleaseDate = 05/28/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010702-18798-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Mon Jan  7 09:47:58.934 2002 (UTC - 4:00)
System Uptime: 0 days 0:00:12.480
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  smss.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!ExFreePoolWithTag+43
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02fabdd3 00000000`00000000 00000000`100000f8
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010702-17534-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan  6 23:56:13.478 2002 (UTC - 4:00)
System Uptime: 0 days 0:00:24.649
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
Probably caused by : aswSP.SYS ( aswSP+cbd7 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_aswSP+cbd7
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff880`0415cbd7 00000000`00000000 00000000`000001df
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010702-23665-01.dmp]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010602-21699-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan  6 11:51:56.002 2002 (UTC - 4:00)
System Uptime: 0 days 1:39:10.547
Probably caused by : atikmpag.sys ( atikmpag+a9d3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Reckoning.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmpag+a9d3
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0440a9d3 fffff880`0b3078e0 00000000`00000000
BiosVersion = 1404   
BiosReleaseDate = 05/28/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010602-17097-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Jan  6 01:58:35.229 2002 (UTC - 4:00)
System Uptime: 0 days 0:00:24.400
Probably caused by : hardware_disk
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk
Bugcheck code 1000007E
Arguments ffffffff`c0000006 fffff800`02f2e31a fffff880`009a9808 fffff880`009a9060
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010502-18049-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Jan  5 03:54:36.059 2002 (UTC - 4:00)
System Uptime: 0 days 0:02:25.604
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x19_20_nt!PoIdle+52a
Bugcheck code 00000019
Arguments 00000000`00000020 fffff900`c0c20090 fffff900`c0c20090 00000000`25000152
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010502-18470-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Jan  5 03:49:21.956 2002 (UTC - 4:00)
System Uptime: 0 days 0:02:41.502
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+2aa )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  AvastSvc.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiCommitThreadWait+2aa
Bugcheck code 0000000A
Arguments fffff880`031d1388 00000000`00000002 00000000`00000001 fffff800`02e8d79a
BiosVersion = 1404   
BiosReleaseDate = 05/28/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010502-17612-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Jan  5 00:13:01.392 2002 (UTC - 4:00)
System Uptime: 0 days 0:06:00.563
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+4d208f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xBE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xBE_atikmdag+4d208f
Bugcheck code 000000BE
Arguments fffff880`040320c7 00000001`28186121 fffff880`067e6a90 00000000`0000000b
BiosVersion = 1404   
BiosReleaseDate = 05/28/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010402-16816-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan  4 00:10:34.372 2002 (UTC - 4:00)
System Uptime: 0 days 0:02:35.917
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+249 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExDeferredFreePool+249
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02ff9b05 fffff880`0715cfc0 00000000`00000000
BiosVersion = 1404   
BiosReleaseDate = 05/28/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

bryanonbass · Apr 11, 2012

Thanks, usasma. I'll try to do the suggestions you have provided. It may take some time, I might have to read it a few more times. Hahahaha! I'm really grateful. I'll post any updates as soon as I have performed everything.

usasma · Apr 11, 2012

Not a problem. Just take your time.
I generally post similar stuff in a paragraph - so just do each paragraph and then move on to the next one.
One-by-one.

Good Luck!

Constant BSOD - ntoskrnl.exe

bryanonbass

New member

Attachments

My Computer

usasma

Mr. Cranky Pants

My Computer

bryanonbass

New member

My Computer

usasma

Mr. Cranky Pants

My Computer

Similar threads