Windows 7 Frequent BSODs Caused by ntoskrnl.exe: Seeking Help with Hardware or Driver Issues

ilku · Jan 5, 2013

Well, I've got a BSOD a couple of times now and it's really starting to annoy me.It comes a couple of times a week so not every day.I've googled abit and what I've found out was that it's a hardware that's faulty or it's driver.I'll attach probably all the files you will need to help me out.
My current "known" Specs are:
Asus Crosshair Formula IV MB
2 HDD 256gb/1tb
1 sdd 60gb
Amd radeon 7970 sapphire
Corsair vengeance rams 16 gb, dont know the speed but think atleast 1333mhz
Creative x-fi Fatality titanium sound card non-integrated.

usasma · Jan 5, 2013

C and D drives are very short of free space. Please free up enough space so that 15% of the drive is free (that way Windows has room to do stuff in the background).

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller...

usasma · Jan 5, 2013

C and D drives are very short of free space. Please free up enough space so that 15% of the drive is free (that way Windows has room to do stuff in the background).

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.
10 Nov 2012 - I'm seeing an upswing in SSD errors - but most appear due to older storage controller drivers. I strongly suggest NOT using storage controller drivers that don't date from 2012 (if none are available, don't connect an SSD to that controller)
05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: https://www.eightforums.com/bsod-cr...-pc-reboots-when-waking-sleep.html#post169956

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). I strongly suspect that this hold true for Win8 systems also.

Please un-install 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): ~~[DEL] Link Removed [/DEL]~~ Link broken as of 21 Jul 2012
New link (15 Aug 2012): Link Removed (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

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 un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Link Removed (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: Link Removed

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 "Un-install". 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 update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

AsUpIO.sys Sun Jul 5 22:21:38 2009 (4A515FB2)
ASUS hardware monitoring software related
Link Removed

nusb3hub.sys Thu Jan 21 22:22:18 2010 (4B5919EA)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 version)
Link Removed

nusb3xhc.sys Thu Jan 21 22:22:21 2010 (4B5919ED)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 version)
Link Removed

dtsoftbus01.sys Fri Jan 13 08:45:46 2012 (4F10358A)
Daemon Tools driver [br] Possible BSOD issues in Win7
Link Removed

sptd.sys Sat Mar 3 11:45:52 2012 (4F524AC0)
SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win7)
Link Removed

AODDriver2.sys Thu Apr 5 05:23:37 2012 (4F7D6499)
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
Link Removed

Analysis:
The following is for informational purposes only.

Code:

[FONT=lucida console]**************************Tue Jan  1 13:02:35.590 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010113-63601-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]2 days 4:54:42.714[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+e7 )[/B]
BugCheck [B]3B, {c000001d, fffff80003384172, fffff8800d1adab0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff80003384172, Address of the instruction which caused the bugcheck
Arg3: fffff8800d1adab0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]uTorrent.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_nt!ObpWaitForMultipleObjects+e7[/B]
  BIOS Version                  1902   
  BIOS Release Date             02/17/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec 22 01:18:51.140 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122212-62150-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]3 days 17:14:39.233[/B]
Probably caused by :[B]hardware ( nt!KiInsertTimerTable+b9 )[/B]
BugCheck [B]3B, {c000001d, fffff8000308c059, fffff8800c3478e0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff8000308c059, Address of the instruction which caused the bugcheck
Arg3: fffff8800c3478e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]uTorrent.exe[/B]
FAILURE_BUCKET_ID: [B]X64_IP_MISALIGNED[/B]
  BIOS Version                  1902   
  BIOS Release Date             02/17/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[FONT=lucida console]**************************Tue Jan  1 13:02:35.590 2013 (UTC - 5:00)**************************
GEARAspiWDM.sys             Mon May 18 08:17:04 2009 (4A1151C0)
[B]AsUpIO.sys                  Sun Jul  5 22:21:38 2009 (4A515FB2)[/B]
ASACPI.sys                  Wed Jul 15 23:31:29 2009 (4A5E9F11)
usbfilter.sys               Wed Oct  7 03:44:08 2009 (4ACC46C8)
jraid.sys                   Thu Oct 29 04:14:20 2009 (4AE94EDC)
LGBusEnum.sys               Mon Nov 23 20:36:48 2009 (4B0B38B0)
[B]nusb3hub.sys                Thu Jan 21 22:22:18 2010 (4B5919EA)[/B]
[B]nusb3xhc.sys                Thu Jan 21 22:22:21 2010 (4B5919ED)[/B]
yk62x64.sys                 Mon Feb 15 10:46:41 2010 (4B796C61)
amdiox64.sys                Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
AsIO.sys                    Thu Apr 22 07:18:03 2010 (4BD0306B)
npf.sys                     Fri Jun 25 12:50:58 2010 (4C24DE72)
emupia2k.sys                Wed Jul  7 09:38:03 2010 (4C34833B)
ctsfm2k.sys                 Wed Jul  7 09:38:10 2010 (4C348342)
ctoss2k.sys                 Wed Jul  7 09:38:24 2010 (4C348350)
ha20x22k.sys                Wed Jul  7 09:41:25 2010 (4C348405)
ctaud2k.sys                 Wed Jul  7 09:42:14 2010 (4C348436)
ctprxy2k.sys                Wed Jul  7 09:42:17 2010 (4C348439)
CTEXFIFX.SYS                Wed Jul  7 09:44:03 2010 (4C3484A3)
CT20XUT.SYS                 Wed Jul  7 09:44:15 2010 (4C3484AF)
CTHWIUT.SYS                 Wed Jul  7 09:44:19 2010 (4C3484B3)
ESLWireACD.sys              Wed Oct 26 07:14:34 2011 (4EA7EB9A)
tap0901.sys                 Thu Nov 24 13:50:27 2011 (4ECE91F3)
aowvtbzj.SYS                Tue Dec 27 17:30:45 2011 (4EFA4715)
[B]dtsoftbus01.sys             Fri Jan 13 08:45:46 2012 (4F10358A)[/B]
[B]sptd.sys                    Sat Mar  3 11:45:52 2012 (4F524AC0)[/B]
aswKbd.SYS                  Tue Mar  6 19:02:44 2012 (4F56A5A4)
TPLINKUDSMBus.sys           Thu Mar  8 03:28:11 2012 (4F586D9B)
[B]AODDriver2.sys              Thu Apr  5 05:23:37 2012 (4F7D6499)[/B]
AtihdW76.sys                Fri May 11 04:25:40 2012 (4FACCD04)
aswFsBlk.SYS                Tue Aug 21 05:04:55 2012 (50334F37)
aswMonFlt.sys               Tue Aug 21 05:05:00 2012 (50334F3C)
aswTdi.SYS                  Tue Aug 21 05:05:01 2012 (50334F3D)
aswrdr2.sys                 Tue Aug 21 05:05:16 2012 (50334F4C)
aswSP.SYS                   Tue Aug 21 05:05:54 2012 (50334F72)
aswSnx.SYS                  Tue Aug 21 05:05:56 2012 (50334F74)
atikmpag.sys                Thu Sep 27 21:12:52 2012 (5064F994)
atikmdag.sys                Thu Sep 27 22:14:57 2012 (50650821)
rzendpt.sys                 Wed Nov  7 02:49:46 2012 (509A129A)
rzudd.sys                   Wed Nov  7 02:49:47 2012 (509A129B)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Dec 22 01:18:51.140 2012 (UTC - 5:00)**************************
a3t6l70d.SYS                Tue Dec 27 17:30:45 2011 (4EFA4715)
[/FONT]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
aowvtbzj.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
TPLINKUDSMBus.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
a3t6l70d.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

ilku · Jan 5, 2013

Okay! Thanks for the rather quick response! I will start to fixing the issues you've told me about and I'll return here if no BSOD happens for another week!
Really appreciate the great amount of effort you've put in to this!
Thanks alot!

Windows 7 Frequent BSODs Caused by ntoskrnl.exe: Seeking Help with Hardware or Driver Issues

ilku

New Member

Attachments

usasma

usasma

Fantastic Member

ilku

New Member