Windows 8 Windows 8 Pro x64 - BSOD with Driver Verifier after waking from sleep

[gifyku]

Hi all,

This is my first post. Please excuse any failings therefore.

Recently, over the last three days, I have been experiencing random BSOD's, atleast once a day. I have not added any new hardware or any new software that I am aware of apart from Windows Updates. I an running Driver Verifier and it crashed on startup today morning. I believe all the crashes came quickly after startup.

Your help would be much appreciated. I looked at the dumps and they seem to indicate USB but I am not sure since the cause changes each time.

I have the Diagnostics attached! Thanks

 

[usasma]

Windows 8 was installed on 25 Oct 2012 - the day before it was released to the public. Is this a TechNet/MSDN/other legitimate copy? If not, please be advised that we may not be able to fix it (as the hacks that were done to activate it will cause the OS to behave differently than we expect it to). If that's the case, our efforts to help may just waste your time. Secondly, the forum rules prohibit assisting with pirated software - so the topic would be closed if that is the case.

Corsair Vengeance Mouse is blamed in the stack text of one of the memory dumps. Please:
- Uninstall the current software/drivers
- Download and install a fresh copy of the latest, Win8 compatible version
- monitor for BSOD's

MSI Afterburner/Riva Tuner/EVGA Precision are known to cause BSOD's on some Windows systems. Please uninstall it immediately. If overclocking, please stop while we are troubleshooting. Feel free to resume the overclock once the system is stabilized.

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

In this case it appears that your SSD is connected to your Marvell Controller. Please switch it to another controller (specifications will be listed in your motherboard's manual).



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

mv_process.sys Tue Feb 22 04:22:20 2011 (4D63804C)

mv_process.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.

speedfan.sys Fri Mar 18 12:08:46 2011 (4D83838E)
SpeedFan
Link Removed



Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Tue Jan 29 06:33:22.467 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012913-11546-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16461.amd64fre.win8_gdr.121119-1606
System Uptime:[B]0 days 23:32:19.824[/B]
*** ERROR: Module load completed but symbols could not be loaded for usbccgp.sys
*** WARNING: Unable to verify timestamp for dot4usb.sys
*** ERROR: Module load completed but symbols could not be loaded for dot4usb.sys
*** WARNING: Unable to verify timestamp for Dot4.sys
*** ERROR: Module load completed but symbols could not be loaded for Dot4.sys
Probably caused by :[B]dot4usb.sys ( dot4usb+2b94 )[/B]
BugCheck [B]C9, {228, fffff88008395b94, fffff98028f8caf0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000228, A driver's completion routine has not marked the IRP pending if the
	PendingReturned field was set in the IRP passed to it. This may cause the OS
	to hang, especially if an error is returned by the stack.
Arg2: fffff88008395b94, The address in the driver's code where the error was detected.
Arg3: fffff98028f8caf0, IRP address.
Arg4: 0000000000000000
BUGCHECK_STR:  0xc9_228
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0xc9_228_VRF_dot4usb+2b94[/B]
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3303[/B]
  BIOS Version                  U1g
  BIOS Release Date             07/15/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 28 06:09:59.035 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012813-9984-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16461.amd64fre.win8_gdr.121119-1606
System Uptime:[B]0 days 23:00:33.402[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!RealSuccessor+37 )[/B]
BugCheck [B]3B, {c0000005, fffff800b109a877, fffff8800c88aa30, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800b109a877, Address of the instruction which caused the bugcheck
Arg3: fffff8800c88aa30, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID: [B]0x3B_nt!RealSuccessor[/B]
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3303[/B]
  BIOS Version                  U1g
  BIOS Release Date             07/15/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jan 27 06:43:13.850 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012713-9765-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16461.amd64fre.win8_gdr.121119-1606
System Uptime:[B]0 days 14:22:37.515[/B]
*** WARNING: Unable to verify timestamp for WIMBLEMS.sys
*** ERROR: Module load completed but symbols could not be loaded for WIMBLEMS.sys
Probably caused by :[B]WIMBLEMS.sys ( WIMBLEMS+1abe )[/B]
BugCheck [B]1E, {ffffffffc0000047, fffff8001ef5f008, fffff80020906060, fffffa80ffffffff}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffffc0000047, The exception code that was not handled
Arg2: fffff8001ef5f008, The address that the exception occurred at
Arg3: fffff80020906060, Parameter 0 of the exception
Arg4: fffffa80ffffffff, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000047
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x1E_c0000047_WIMBLEMS+1abe[/B]
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3303[/B]
  BIOS Version                  U1g
  BIOS Release Date             07/15/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/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.

[font=lucida console]**************************Tue Jan 29 06:33:22.467 2013 (UTC - 5:00)**************************
[COLOR=RED][B]mv_process.sys              Tue Feb 22 04:22:20 2011 (4D63804C)[/B][/COLOR]
[COLOR=RED][B]speedfan.sys                Fri Mar 18 12:08:46 2011 (4D83838E)[/B][/COLOR]
[COLOR=RED][B]RTCore64.sys                Tue Sep  6 08:24:50 2011 (4E661112)[/B][/COLOR]
[COLOR=RED][B]WIMBLEMS.sys                Sat Oct  8 02:08:24 2011 (4E8FE8D8)[/B][/COLOR]
mvxxmm.sys                  Thu Jan 19 01:50:44 2012 (4F17BD44)
mvs91xx.sys                 Thu Jan 19 01:51:00 2012 (4F17BD54)
Rt630x64.sys                Tue Jun 12 09:37:53 2012 (4FD74631)
RTKVHD64.sys                Tue Jun 19 04:50:56 2012 (4FE03D70)
HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
nvhda64v.sys                Tue Jul  3 11:25:04 2012 (4FF30ED0)
EtronXHCI.sys               Fri Jul 20 03:15:46 2012 (500905A2)
EtronHub3.sys               Fri Jul 20 03:15:52 2012 (500905A8)
dump_iaStorA.sys            Thu Aug 16 16:32:56 2012 (502D58F8)
hiber_iaStorA.sys           Thu Aug 16 16:32:56 2012 (502D58F8)
iaStorA.sys                 Thu Aug 16 16:32:56 2012 (502D58F8)
intelppm.sys                Mon Nov  5 22:55:02 2012 (50988A16)
nvlddmkm.sys                Sat Dec 29 01:47:52 2012 (50DE9218)
[/font]

mv_process.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
hiber_iaStorA.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

 

[gifyku]

Thanks usasma for the comprehensive analysis.

I bought Windows 8 the first day it was released (9 PM EST in Canada, the day before official release using the Windows Updater tool).

I will take a look at these drivers. I do believe all my crashes are when waking the machine from a long sleep.

Fingers crossed

 

[usasma]

Most common cause of sleep/hibernate crashes are either drivers or incompatibilities.
Please ensure that the following are updated:
- chipset
- storage
- video
- audio
- any other Intel drivers related to the chipset/storage drivers (like the Intel Management Engine, etc).

We've noticed that SSD's on Marvell controllers with 2011 or earlier drivers are usually problematic.
Switch to another controller and ensure the drivers for that controller date from 2012 or later.