BSOD After PSU Failure

thickas · 10 Mar 2011

I'm getting periodic BSODs after PSU failed while machine was running unattended.

WIN7 Ult 64
Original OS
Retail Version
Both Hardware and OS 3 Months old

The required zip file is attached.

Thanks in advance for any help in getting this sorted.

Cheers-t

usasma · 12 Mar 2011

MSINFO32 shows issues with these 3 devices:

WAN Miniport (Network Monitor) ROOT\MS_NDISWANBH\0000 This device is not working properly because Windows cannot load the drivers required for this device.

WAN Miniport (IP) ROOT\MS_NDISWANIP\0000 39

WAN Miniport (IPv6) ROOT\MS_NDISWANIPV6\0000 39

Go to Device Manager and right click on each device and select "Uninstall"
Reboot the system and Windows will reinstall the devices if they are needed.
Check in Device Manager to be sure that the devices are functioning properly (after the reboot)

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system. Reference links included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

Code:


vmbus.sys        Sat Nov 20 04:57:29 2010 (4CE79B89)
winhv.sys        Sat Nov 20 04:20:02 2010 (4CE792C2)
mv91xx.sys       Fri Dec 25 01:45:39 2009 (4B345F93)
mvxxmm.sys       Fri Dec 25 01:45:15 2009 (4B345F7B)
amdxata.sys      Fri Mar 19 12:18:18 2010 (4BA3A3CA)
MpFilter.sys     Tue Sep 14 20:19:28 2010 (4C901110)
hotcore3.sys     Tue Jul 29 17:58:17 2008 (488F9279)
vmm.sys          Tue Apr 07 09:25:54 2009 (49DB5462)
uimx64.sys       Fri Sep 26 09:28:33 2008 (48DCE381)
SASKUTIL64.SYS   Tue Feb 09 17:27:34 2010 (4B71E156)
SASDIFSV64.SYS   Mon Feb 08 19:11:52 2010 (4B70A848)
yk62x64.sys      Wed May 20 04:14:06 2009 (4A13BBCE)
AsIO.sys         Mon Aug 03 03:03:16 2009 (4A768BB4)
nusb3xhc.sys     Thu Jan 21 22:22:21 2010 (4B5919ED)
NDISTAPI.SYS     Mon Jul 13 20:10:00 2009 (4A5BCCD8)
ASACPI.sys       Wed Jul 15 23:31:29 2009 (4A5E9F11)
VMNetSrv.sys     Wed Jan 16 06:52:01 2008 (478DEFE1)
nvlddmkm.sys     Sat Jul 31 09:43:08 2010 (4C54286C)
nvBridge.kmd     Sat Jul 31 09:41:19 2010 (4C5427FF)
WmBEnum.sys      Fri Sep 11 15:40:09 2009 (4AAAA799)
WmXlCore.sys     Fri Sep 11 15:40:07 2009 (4AAAA797)
vmnetadapter.sys Thu May 22 06:33:57 2008 (48354C15)
VMNET.SYS        Thu May 22 06:33:54 2008 (48354C12)
nusb3hub.sys     Thu Jan 21 22:22:18 2010 (4B5919EA)
nvhda64v.sys     Mon Jun 21 18:07:25 2010 (4C1FE29D)
LMouFilt.Sys     Tue Aug 24 13:21:43 2010 (4C73FFA7)
WmFilter.sys     Fri Sep 11 15:40:09 2009 (4AAAA799)
RTKVHD64.sys     Fri Jan 29 01:48:35 2010 (4B6284C3)
SbieDrv.sys      Sun Oct 17 18:42:23 2010 (4CBB7BCF)
vmnetbridge.sys  Thu May 22 06:34:05 2008 (48354C1D)
LHidFilt.Sys     Tue Aug 24 13:21:36 2010 (4C73FFA0)
hcmon.sys        Thu Mar 26 21:52:03 2009 (49CC3143)
vmci.sys         Thu Mar 26 21:21:48 2009 (49CC2A2C)
vmnetuserif.sys  Thu Mar 26 22:06:58 2009 (49CC34C2)
vmx86.sys        Fri Mar 27 00:28:08 2009 (49CC55D8)
VMkbd.sys        Thu Mar 26 23:59:55 2009 (49CC4F3B)
vstor2-ws60.sys  Mon Dec 01 14:26:32 2008 (49343A68)
WmVirHid.sys     Fri Sep 11 15:40:05 2009 (4AAAA795)
MpNWMon.sys      Tue Sep 14 20:19:30 2010 (4C901112)
NisDrvWFP.sys    Tue Sep 14 20:20:25 2010 (4C901149)
kerneld.x64      Thu Dec 16 18:50:30 2010 (4D0AA5C6)
mbam.sys         Thu Dec 16 15:53:16 2010 (4D0A7C3C)

If that doesn't fix it, then I'd run Driver Verifier according to the following directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Mar 10 13:44:53.893 2011 (UTC - 5:00)
System Uptime: 0 days 0:26:40.815
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME:  rundll32.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 00000050
Arguments ffffffff`ffffffa3 00000000`00000001 fffff800`035d7f8f 00000000`00000000
BiosVersion = 0303   
BiosReleaseDate = 05/25/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Mar 10 06:11:03.100 2011 (UTC - 5:00)
System Uptime: 0 days 0:04:46.021
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME:  WMIADAP.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 00000050
Arguments ffffbda0`3949ca70 00000000`00000000 fffff800`0355ff88 00000000`00000007
BiosVersion = 0303   
BiosReleaseDate = 05/25/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Mar 10 02:25:13.704 2011 (UTC - 5:00)
System Uptime: 0 days 0:05:06.625
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x50
PROCESS_NAME:  WMIADAP.exe
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Bugcheck code 00000050
Arguments ffffbda0`42de3140 00000000`00000000 fffff800`0355ff88 00000000`00000007
BiosVersion = 0303   
BiosReleaseDate = 05/25/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Mar 10 02:19:30.664 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:34.585
Probably caused by : cng.sys ( cng!BCryptResolveProviders+2bd )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_cng!BCryptResolveProviders+2bd
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`034dd3e5 00000000`00000000 00000000`00000000
BiosVersion = 0303   
BiosReleaseDate = 05/25/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Mar 10 02:15:20.404 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:12.325
BugCheck D1, {0, 2, 0, fffff880075dc2b2}
*** WARNING: Unable to verify timestamp for MpNWMon.sys
*** ERROR: Module load completed but symbols could not be loaded for MpNWMon.sys
Probably caused by : MpNWMon.sys ( MpNWMon+32b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_MpNWMon+32b2
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff880`075dc2b2
BiosVersion = 0303   
BiosReleaseDate = 05/25/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

thickas · 12 Mar 2011

Hi u-

Thanks for your time and effort in responding to my post. After going round in circles (probably the same one repeatedly) I found that the PSU failure reset the BIOS to default settings and in my haste to get the system back up I misconfigured the RAM timings. Have reconfigured this properly and all is well. PEBKAC lives! Thanks again.

Cheers-t