Win7 64-bit BSODs...please help

mhowie · 19 Feb 2011

I returned from a business trip last week and upon powering on my PC noticed a strange looking screen...my computer had booted into its D: drive and found my old XP build to run from. I went into the BIOS and the boot sequence order had changed (weird). I changed it back, did a little research, and determined my CMOS battery might need swapped out. I made a note to pick up a battery later in the week. Soon after getting the computer to boot into the correct HDD, I installed the new IE9 RC and began getting BSODs. I wound up uninstalling IE9 RC, rolling back to IE8, and all was well until this past evening.

Last evening I swapped out the CMOS battery and restarted my rig. All was well. I then decided to give IE9 RC another shot so I redownloaded and installed. Yep, BSOD soon thereafter. Unfortunately, this time, upon uninstalling and reverting back to IE8, the BSODs continue. Of note is the fact that after one of the BSODs last night the "boot into the D: drive" phenomenon occurred once again. So...ruling out the CMOS battery...perhaps my motherboard is on the fritz? Could the HDD be a culprit? Video drivers which have gone nutty?

I am attaching the Minidumps from last night as well as from a week ago and would appreciate your review and subsequent counsel/direction. Perhaps the whole IE9 RC correlation is oddly coincidental and I have some hardware item going bad...but before I commence that level of troubleshooting I thought there would be benefit in understanding what the Minidumps reveal.

Unfortunately as is often the case with the Windows System Restore function, mine is flaky and never completes a restore when attempted...so I can not simply roll back to an earlier time.

Thanks in advance for your help,

mhowie · 20 Feb 2011

Any thoughts on what might be the culprit(s)?

usasma · 20 Feb 2011

Often times we find answers in other reports - rather than just running dump analysis'
Please provide the info from this post: https://www.sevenforums.com/crashes-d...tructions.html

usasma · 20 Feb 2011

8 memory dumps over a period of 7 days
7 different BSOD error codes
6 different causes blamed
Most likely this is a hardware problem, but they can also be caused by compatibility or other low-level issues (such as rootkits and other malware).

So, I'd first suggest these free diagnostics:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Scanners (read the details at the link)

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Windows Update exceptions may be noted below for Windows drivers:

Code:


amdxata.sys      Tue May 19 13:56:59 2009 (4A12F2EB)
AtiPcie.sys      Mon Nov 06 11:59:54 2006 (454F6A0A)
MpFilter.sys     Tue Sep 14 20:19:28 2010 (4C901110)
tifsfilt.sys     Wed Aug 29 08:37:29 2007 (46D56889)
cpuz132_x64.sys  Thu Mar 26 19:17:23 2009 (49CC0D03)
VBoxDrv.sys      Sun Dec 06 15:58:16 2009 (4B1C1AE8)
vpcnfltr.sys     Tue Sep 22 21:32:30 2009 (4AB97AAE)
vpcvmm.sys       Tue Sep 22 21:32:38 2009 (4AB97AB6)
vmlitedrv.sys    Sun Dec 06 16:14:15 2009 (4B1C1EA7)
Rt64win7.sys     Wed Jun 23 05:10:45 2010 (4C21CF95)
GEARAspiWDM.sys  Mon May 18 08:17:04 2009 (4A1151C0)
vpcusb.sys       Tue Sep 22 21:32:39 2009 (4AB97AB7)
usbrpm.sys       Mon Jul 13 20:35:14 2009 (4A5BD2C2)
vpchbus.sys      Tue Sep 22 21:32:32 2009 (4AB97AB0)
VBoxNetAdp.sys   Sun Dec 06 15:58:19 2009 (4B1C1AEB)
vmlitediskmp.sys Mon Jan 11 14:52:02 2010 (4B4B8162)
VBoxNetFlt.sys   Sun Dec 06 15:58:08 2009 (4B1C1AE0)
MpNWMon.sys      Tue Sep 14 20:19:30 2010 (4C901112)
NisDrvWFP.sys    Tue Sep 14 20:20:25 2010 (4C901149)
usbaapl64.sys    Thu Sep 16 22:19:05 2010 (4C92D019)
WinUSB.SYS       Mon Jul 13 20:06:28 2009 (4A5BCC04)
LHidFilt.Sys     Wed Jun 17 12:49:39 2009 (4A391EA3)
LMouFilt.Sys     Wed Jun 17 12:49:43 2009 (4A391EA7)
nvlddmkm.sys     Tue Mar 16 03:57:48 2010 (4B9F39FC)
nvBridge.kmd     Tue Mar 16 03:26:37 2010 (4B9F32AD)
nvBridge.kmd     Fri Jul 09 17:07:54 2010 (4C378FAA)
nvlddmkm.sys     Fri Jul 09 17:15:58 2010 (4C37918E)

Code:


Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 21:23:30.151 2011 (UTC - 5:00)
System Uptime: 0 days 0:27:30.010
Probably caused by : ntkrnlmp.exe ( nt!CcAcquireByteRangeForWrite+5e2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!CcAcquireByteRangeForWrite+5e2
Bugcheck code 00000050
Arguments ffffffff`ffffffef 00000000`00000000 fffff800`02cbc771 00000000`00000000
SystemManufacturer = MICRO-STAR INTERANTIONAL CO.,LTD
SystemProductName = MS-7368
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 20:48:30.476 2011 (UTC - 5:00)
System Uptime: 0 days 0:18:43.335
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`98fb36dd 00000000`00000000 155cd3bf`0a86561f 00000000`00000101
SystemManufacturer = MICRO-STAR INTERANTIONAL CO.,LTD
SystemProductName = MS-7368
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Feb 18 20:26:41.642 2011 (UTC - 5:00)
System Uptime: 0 days 0:09:32.402
Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2cc9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x24
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!_??_::FNODOBFM::_string_+2cc9
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`022faed8 fffff880`022fa740 fffff880`00000610
SystemManufacturer = MICRO-STAR INTERANTIONAL CO.,LTD
SystemProductName = MS-7368
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 12 09:59:39.337 2011 (UTC - 5:00)
System Uptime: 0 days 0:24:21.197
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31 )
BUGCHECK_STR:  0x4E_9a
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x4E_9a_dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31
Bugcheck code 0000004E
Arguments 00000000`0000009a 00000000`0000c50c 00000000`00000000 00000000`00000000
SystemManufacturer = MICRO-STAR INTERANTIONAL CO.,LTD
SystemProductName = MS-7368
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 12 09:25:33.203 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:23.062
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+ca0 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+ca0
Bugcheck code 00000019
Arguments 00000000`00000003 fffff8a0`01e013e0 fffff8a0`01e013e0 00300030`00300030
SystemManufacturer = MICRO-STAR INTERANTIONAL CO.,LTD
SystemProductName = MS-7368
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 12 09:09:18.559 2011 (UTC - 5:00)
System Uptime: 0 days 8:32:51.418
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+83b0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WerFault.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!_??_::NNGAKEGL::_string_+83b0
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02fd7b6c fffff880`072f7020 00000000`00000000
SystemManufacturer = MICRO-STAR INTERANTIONAL CO.,LTD
SystemProductName = MS-7368
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 12 00:34:50.972 2011 (UTC - 5:00)
System Uptime: 0 days 0:22:54.832
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`98fe86c6 00000000`00000000 1ca378f4`b16df9d2 00000000`00000101
SystemManufacturer = MICRO-STAR INTERANTIONAL CO.,LTD
SystemProductName = MS-7368
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Feb 12 00:10:36.688 2011 (UTC - 5:00)
System Uptime: 0 days 0:02:22.547
Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e )
BUGCHECK_STR:  0x1a_1238
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_1238_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e
Bugcheck code 0000001A
Arguments 00000000`00001238 fffffa80`0732f3d0 00000000`00000802 00000000`00000000
SystemManufacturer = MICRO-STAR INTERANTIONAL CO.,LTD
SystemProductName = MS-7368
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``