BSOD - various random 0x000000 codes, even when idle.

Robbyo · 08 Apr 2014

Hi, I have been experiencing multiple BSOD for a few weeks now. They are not triggered by a specific action, as they occur even when idle from first being turned on. They can occur after a matter of minutes or hours after use. They are also not consistently the same 0x000000 error code. Please see the attached

I believe they may be linked to a driver issue, or perhaps hardware. Additional symptoms relate to USB ports including peripheral hardware freezing from idle (e.g. network adapter, keyboard, mouse) and the network adapter needing to be reset upon reboot - windows auto update has had some problem updating the optional automatic update driver for this recently.

Specs are within the attached as well.
Any help identifying what the problem is and how to fix would be really appreciated.

Thank

koolkat77 · 08 Apr 2014

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!:-

ASACPI.sys Tue Oct 31 08:09:12 2006 (4546B048)
Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities (Win8 versions available from Windows Update as an Optional Update - but check Asus first!)
Driver Reference Table - ASACPI.sys

scmndisp.sys Wed Jan 17 13:48:03 2007 (45ADD4B3)
Netgear Neutral Wireless Solution
Driver Reference Table - scmndisp.sys

BdFileSpy.sys Thu Jan 22 17:43:27 2009 (49785BDF)
BullGuard File Scan
Driver Reference Table - BdFileSpy.sys

viahduaa.sys Fri Jul 10 09:07:01 2009 (4A56B055)
VIA High Definition Audio Function Driver
Driver Reference Table - viahduaa.sys

bcmwlhigh664.sys Tue Apr 19 13:13:08 2011 (4DAD3604)
Broadcom 802.11 USB Network Adapter Driver
Driver Reference Table - bcmwlhigh664.sys

Rt64win7.sys Fri Jun 10 12:33:15 2011 (4DF1BAAB)
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
Driver Reference Table - Rt64win7.sys

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Perform a clean install of a driver following: How to Clean Left Over Driver Files with Driver Sweeper

AODDriver2.sys Thu Sep 12 09:36:40 2013 (523136C8)
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7[br][br]Part of AMD Fuel[br][br]Location: C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys
Driver Reference Table - AODDriver2.sys

AMD OverDrive Removal - Step 1:
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 http://ati.amd.com (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

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.

Reduce items at start-up: Startup Programs - Change

Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: Screenshots and Files - Upload and Post in Seven Forums

Run Disk Check on your Hard Drive(s): Disk Check

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try

Keep us posted.

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Tue Apr  8 22:28:48.535 2014 (UTC + 6:00)
System Uptime: 0 days 0:06:40.706
BugCheck D1, {d6, 2, 8, d6}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Mon Apr  7 00:30:08.937 2014 (UTC + 6:00)
System Uptime: 0 days 0:19:37.483
BugCheck FC, {fffff88002d8b5c2, 800000007abf8963, fffff88002d8b3d0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+433ac )
BUGCHECK_STR:  0xFC
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Sun Apr  6 22:02:17.707 2014 (UTC + 6:00)
System Uptime: 0 days 0:24:26.269
BugCheck 124, {0, fffffa800404f028, f6002000, 82000136}
*** WARNING: Unable to verify timestamp for afwcore.sys
*** ERROR: Module load completed but symbols could not be loaded for afwcore.sys
Probably caused by : AuthenticAMD
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Sun Apr  6 13:14:13.908 2014 (UTC + 6:00)
System Uptime: 0 days 0:05:00.318
BugCheck 101, {31, 0, fffff88002f63180, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Robbyo · 09 Apr 2014

Thanks Yussi, very comprehensive reply! I have updated all drivers with the exception of the Broadcom 802.11 USB Network Adapter Driver as I simply could not find a suitable update or that I was actually using it?! Today is the first day without a BSOD! Will keep you posted if I experience any more and continue on with the AMD overdrive suggestion and stop 0x0124 advice if necessary. Or if none is experienced in next week or so, mark as solved.

Thanks again

Rob

Robbyo · 16 Apr 2014

hey again,

All drivers now updated and BSOD's have decreased but still take place. Latest debug files and minidump attached. They seem to all be around USB related problems bug e.g. 0x0FE, Bugcode_usb_driver and when restarting the first restart has unresponsive keyboard and mouse (which are plugged into USB).

Continued help is appreciated.

Rob

koolkat77 · 16 Apr 2014

Bump the thread if I don't respond in 24 hours.

koolkat77 · 16 Apr 2014

What except keyboard and mice do you have plugged into the USB ports? You might want to unplug the rest and see if it helps.

A tutorial that also might help: USB Driver - General Fix for Problems

Code:

Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Wed Apr 16 22:52:55.145 2014 (UTC + 6:00)
System Uptime: 0 days 0:06:41.691
BugCheck FE, {8, 6, 6, fffffa800523db20}
Probably caused by : usbhub.sys ( usbhub+17fa )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Robbyo · 23 Apr 2014

I only have keyboard mouse and wifi adapter connected via usb - Nothing else. I completed the USB driver general fix guidance but experienced two BSOD's since that time on 21st April. These were new codes to me, 101 and 124 from memory.

I have also run memtest86 to be thorough and in 15 passes had 0 errors.

Latest files attached.

Thedoctor44 · 23 Apr 2014

The 0x101 bugcheck indicates the CPU has not responded to an interrupt within the time interval, generally this is caused by a faulty CPU but software (Mainly drivers) can cause this bugcheck.
Similar principles apply for the 0x124 bugcheck in terms of the cause.

Minidumps are pretty much useless when analyzing 0x101 bugchecks because they only contain the context for the processor that was awake and called the KeBugCheckEx routine.
I think for the time being we shall leave that and test the CPU with Prime95 if you already haven't done so.
Please follow these instructions.

Hardware - Stress Test With Prime95

Run Prime95 for around 2 hours and let us know the results.

Code:

===============================================================================
Common Platform Error Record @ fffffa8004001028
-------------------------------------------------------------------------------
Record Id     : 01cf5d27236bba23
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/21/2014 10:57:05
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80040010a8
Section       @ fffffa8004001180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Data Read
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000100f42
Processor ID  : 0x0000000000000002

A machine check exception is caused when the CPU finds a fault and reports it, the CPU generally gets the blame but it doesn't mean it's the cause.
However if we look at the WHEA record we can see the error is in the cache of the CPU which mostly means the CPU is at fault.

EDIT: By the way if Prime95 crashes during the test please try it in safe mode as it should rule out the driver problem.

essenbe · 23 Apr 2014

In addition to what Thedoctor44 said, I would strongly suggest you use a CPU temp monitoring program. Prime 95 will cause your CPU temps to climb rapidly. If it gets close to your max CPU temp, stop the test. If you do not have a CPU temp program, I use either Core Temp or Real Temp. Both are free, but as always, opt out of any add ons they offer. If you are overclocking, stop and set everything to default values.

Robbyo · 23 Apr 2014

Thanks to you both, I have speedfan 4.49 already installed and I assume this is also sufficient? I ran Prime95 for a few minutes and the CPU and core temperatures jumped up to 63 and 65 respectively. From my rudimentary understanding I thought 62 degrees C was the upper limit? Sitting idle / low usage they are both usually below 40 degrees C, which they returned back to after 5 minutes or so when stopping.

Can I ask what is the safe limit for me to continue running the prime95 test at before I should be stopping it for fear of over heating?

Thanks Rob.