Windows 7 1 week of BSOD Please help!!

Wooshna · Aug 9, 2012

Hi,

I've been having really weird BSOD's with my system lately. Googled all the error codes and still came up with nothing. Most of the suggested fix was to just strip the system and test 1 peice of hardware at a time, but i know that my system is stable, 5passes with memtest showed 0 errors, prime95 ran for 12 hours no errors, cpu idles at 20c and never gets hotter then 37c, video card temps idle at 38c and never over 58c. Tested my PSU (PCP&C 760w silencer MKII) unit is stable and works on my other pc. For cooling i use a Corsair H80 in push/pull config. Using a NZXT M59 PC case with 3 Scythe slipstream fans (110.31 CFM) and 1 stock case fan. All other system information is in the attachment. Just recently cleaned out my components with compressed air so dust is not an issue. Please if anyone could give me some help or point me in the right direction to fix the issue it would be greatly appreciated.

Wooshna · Aug 11, 2012

Just a few updates:

1) tried updating my SSD but the crucial updater says i already have the most recent firmware.
2) uninstalled demon tools and tried looking for sptd.sys driver and it looks like its gone from my system.
3) uninstalled AMD Overdrive.

system has been stable for 2 days now with prime95 running for 18 hours. I have tried everything i could think of to make the computer BSOD like multi screening and running massive amounts of programs but it seems like everything is running just fine now.

Thank you usasma for the help!!!

usasma · Aug 9, 2012

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.

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 Link Removed - Invalid URL (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 "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): [DEL] Link Removed [/DEL] Link broken as of 21 Jul 2012
Alternate link: Disc-Tools.com
Manual procedure here: Link Removed - Invalid URL

If the above steps don't stop the BSOD's, please zip up and upload any new memory dumps with your next post - and we'll see what we can figure out from there.

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: Link Removed
- Info on how to troubleshoot BSOD's (DRAFT): Link Removed
- How I do it: Link Removed

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:

[FONT=lucida console]
AODDriver2.sys              Mon Jan 16 02:42:46 2012 (4F13D4F6)
AtihdW76.sys                Thu Feb 23 07:30:12 2012 (4F463154)
GEARAspiWDM.sys             Mon May 18 08:17:04 2009 (4A1151C0)
RTKVHD64.sys                Tue Nov 23 05:14:08 2010 (4CEB93F0)
Rt64win7.sys                Mon Mar 21 09:20:32 2011 (4D8750A0)
SaiKF622.sys                Tue Jun  2 08:38:08 2009 (4A251D30)
_                             2009  2009 
amd_sata.sys                Fri Mar  4 15:45:41 2011 (4D714F75)
amd_xata.sys                Fri Mar  4 15:45:44 2011 (4D714F78)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
asmthub3.sys                Wed Feb 23 21:25:56 2011 (4D65C1B4)
asmtxhci.sys                Wed Feb 23 21:25:47 2011 (4D65C1AB)
atikmdag.sys                Mon Jun 11 12:59:31 2012 (4FD623F3)
atikmpag.sys                Mon Jun 11 12:26:14 2012 (4FD61C26)
avgidsdrivera.sys           Fri Dec 23 07:05:21 2011 (4EF46E81)
avgidsfiltera.sys           Fri Dec 23 07:05:40 2011 (4EF46E94)
avgidsha.sys                Wed Apr 18 22:19:15 2012 (4F8F7623)
avgldx64.sys                Tue Feb 21 22:57:53 2012 (4F4467C1)
avgmfx64.sys                Fri Dec 23 07:08:12 2011 (4EF46F2C)
avgrkx64.sys                Mon Jan 30 22:11:41 2012 (4F275BED)
avgtdia.sys                 Sun Mar 18 23:53:32 2012 (4F66ADBC)
dtsoftbus01.sys             Fri Jan 13 08:45:46 2012 (4F10358A)
jraid.sys                   Wed Nov 24 22:27:17 2010 (4CEDD795)
mcupdate.dll                Mon Jul 13 21:29:09 2009 (4A5BDF65)
usbfilter.sys               Wed Dec 15 05:34:49 2010 (4D0899C9)
[/FONT]

Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed - Invalid URL

BSOD BUGCHECK SUMMARY

Code:

[FONT=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080812-12823-02.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Aug  8 19:35:48.249 2012 (UTC - 4:00)
System Uptime: 0 days 0:37:32.373
BugCheck 101, {19, 0, fffff88002fd7180, 3}
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000019 00000000`00000000 fffff880`02fd7180 00000000`00000003
BiosVersion = 1102
BiosReleaseDate = 03/12/2012
SystemManufacturer = To be filled by O.E.M.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080812-12823-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Aug  8 18:58:20.276 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:04.400
BugCheck 124, {0, fffffa800d56d8f8, 0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : AuthenticAMD
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`0d56d8f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080812-11403-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Aug  8 14:37:00.216 2012 (UTC - 4:00)
System Uptime: 0 days 3:44:25.340
BugCheck 101, {19, 0, fffff88002f65180, 2}
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000019 00000000`00000000 fffff880`02f65180 00000000`00000002
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080712-15054-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Tue Aug  7 03:58:06.514 2012 (UTC - 4:00)
System Uptime: 0 days 2:49:55.622
BugCheck 124, {0, fffffa800d7e8028, b4800000, 20e0f}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : AuthenticAMD
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`0d7e8028 00000000`b4800000 00000000`00020e0f
BiosVersion = 1102
BiosReleaseDate = 03/12/2012
SystemManufacturer = To be filled by O.E.M.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\080312-12948-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Aug  3 04:03:49.370 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:04.478
BugCheck 124, {0, fffffa800d5408f8, 0, 0}
Probably caused by : AuthenticAMD
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`0d5408f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\072212-12792-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jul 22 06:24:50.271 2012 (UTC - 4:00)
System Uptime: 0 days 17:39:07.881
BugCheck 101, {19, 0, fffff88002f65180, 2}
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000019 00000000`00000000 fffff880`02f65180 00000000`00000002
BiosVersion = 1102
BiosReleaseDate = 03/12/2012
SystemManufacturer = To be filled by O.E.M.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071712-12760-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Tue Jul 17 15:31:05.354 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:04.494
BugCheck 124, {0, fffffa800d5588f8, 0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : AuthenticAMD
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`0d5588f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

usasma · Aug 9, 2012

Duplicate post

usasma · Aug 9, 2012

I've replied to this several times, but the post doesn't seem to take (probably has something to do with the 10 post limit and to the number of links in my posts (I have a ton of them).

I identified possible issues with:
-SSD firmware or storage controller drivers
-AMD OverDrive
-Daemon Tools

Wooshna · Aug 9, 2012

Alright thanks i'll work on all those and report back when i'm done.

Wooshna · Aug 11, 2012

Just a few updates:

1) tried updating my SSD but the crucial updater says i already have the most recent firmware.
2) uninstalled demon tools and tried looking for sptd.sys driver and it looks like its gone from my system.
3) uninstalled AMD Overdrive.

system has been stable for 2 days now with prime95 running for 18 hours. I have tried everything i could think of to make the computer BSOD like multi screening and running massive amounts of programs but it seems like everything is running just fine now.

Thank you usasma for the help!!!

Windows 7 1 week of BSOD Please help!!

Wooshna

New Member

Wooshna

usasma

Fantastic Member

usasma

Fantastic Member

usasma

Fantastic Member

Wooshna

New Member

Wooshna

New Member

Similar threads