Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Multiple Random BSODs, Please help me


10 Mar 2014   #1

UEFI Windows 7 Pro x64
 
 
Multiple Random BSODs, Please help me

I've been having a random BSOD on a daily basis, occasionally in small outbursts of 2-3 in a 30min period. All I've been doing is browsing the web, no games or intense production aside from a couple 30sec Adobe Premier files. There is no consistent factor to why the BSODs are being caused that I can see.

I bought a new gold+ rated 850w power supply to be sure that wasn't the issue. I tried reinstalling this machine twice from an image I've used on countless other machines without any problems. I even updated my 840 Pro FW and tried booting from an HDD instead, still had the random BSOD's. I feel like it's either my GPU or my MoBo's memory controller fussing about 32Gb of RAM, but I don't know how to confirm that using these logs. I attached everything the forum guide asked for so that those of you who know how can read my logs and find the issue.

If you solve it I wouldn't even know how to begin to thank you for restoring stability and Zen to my work and playspace.




Attached Files
File Type: zip SF_08-03-2014.zip (1.26 MB, 1 views)
My System SpecsSystem Spec
.

10 Mar 2014   #2

Microsoft Community Contributor Award Recipient

Windows 7 Pro 64 SP1
 
 

I might be jumping in over my head here (Hardware) but this is your second thread with no response yet.

Have you run and installed all updates through Windows Update? A few of your dumps are pointing to drivers available only through windows update.

Code:
Unable to load image \SystemRoot\system32\DRIVERS\prl_strg.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for prl_strg.sys
*** ERROR: Module load completed but symbols could not be loaded for prl_strg.sys
Probably caused by : USBSTOR.SYS ( USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+121 )

Followup: MachineOwner
Driver Reference Table - USBSTOR.SYS

There's a few of these,

Code:
BugCheck F7, {fffff880084d5f5c, f88000e841cb, ffff077fff17be34, 0}

Probably caused by : volmgr.sys ( volmgr!_report_gsfailure+26 )

Followup: MachineOwner
Driver Reference Table - volmgr.sys

One is a memory corruption,

Code:
BugCheck A, {fffffa80029a9338, 2, 1, fffff800037803bc}

Probably caused by : memory_corruption ( nt!MiRemoveLowestPriorityStandbyPage+1bc )

Followup: MachineOwner
That could be from a driver as well, try enabling driver verifier,

information   Information
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode


Running a SFC scan wouldn't hurt either, try that before enabling the driver verifier.

SFC /SCANNOW Command - System File Checker

And there was also a display driver in one,

Code:
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b192e )

Followup: MachineOwner
That's a pretty recent driver, you could try a clean install of that,

Do a clean install of the display driver.
  • Uninstall All nvidia items in Control Panel > Programs and features
    • 3D Vision Control Driver
    • 3D Vision Driver
    • Graphics Driver
    • HD Audio Driver
    • PhysX
    • nvidia Update
    (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
  • Now follow Drivers - Clean Left over Files after Uninstalling
  • Install the driver again. While installing, Select Custom (Advanced) install. In the next page, follow this settings:


I also noticed a few items that don't seem to have drivers installed.

Have you checked device manager?

Code:
PCI Simple Communications Controller	PCI\VEN_8086&DEV_1D3A&SUBSYS_1C3A1458&REV_05\3&11583659&0&B0	The drivers for this device are not installed.
Code:
Unknown Device	USB\VID_0000&PID_0000\6&D66F1F7&0&4	43
Code:
Universal Serial Bus (USB) Controller	PCI\VEN_1B73&DEV_1009&SUBSYS_50071458&REV_02\4&26B9FA6B&0&00E6	The drivers for this device are not installed.
Code:
Universal Serial Bus (USB) Controller	PCI\VEN_1B73&DEV_1009&SUBSYS_50071458&REV_02\4&36515ACB&0&00E5	The drivers for this device are not installed.
It's possible that chipset drivers may fix those.
My System SpecsSystem Spec
10 Mar 2014   #3

Microsoft Community Contributor Award Recipient

Windows 7 Pro 64 SP1
 
 

These are quite interesting too, the date is 2006...

Code:
12/2/2006 9:31 AM	Windows Error Reporting	Fault bucket 3021759633, type 5
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_0ad01dfb

Analysis symbol: 
Rechecking for solution: 0
Report Id: d8032138-81e7-11db-b272-0019d1258734
Report Status: 0
12/2/2006 9:31 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_cab_03fc1229

Analysis symbol: 
Rechecking for solution: 0
Report Id: d8032138-81e7-11db-b272-0019d1258734
Report Status: 4
12/2/2006 9:31 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: d8032138-81e7-11db-b272-0019d1258734
Report Status: 0
12/2/2006 9:22 AM	Windows Error Reporting	Fault bucket 3021759633, type 5
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_074ff0d3

Analysis symbol: 
Rechecking for solution: 0
Report Id: 989d3d34-81e6-11db-b272-0019d1258734
Report Status: 0
12/2/2006 9:22 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_cab_03d3e4f1

Analysis symbol: 
Rechecking for solution: 0
Report Id: 989d3d34-81e6-11db-b272-0019d1258734
Report Status: 4
12/2/2006 9:22 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: 989d3d34-81e6-11db-b272-0019d1258734
Report Status: 0
12/2/2006 9:20 AM	Windows Error Reporting	Fault bucket 3021759633, type 5
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_0b6a2e21

Analysis symbol: 
Rechecking for solution: 0
Report Id: 53c75227-81e6-11db-b272-0019d1258734
Report Status: 0
12/2/2006 9:20 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_cab_0b5e2210

Analysis symbol: 
Rechecking for solution: 0
Report Id: 53c75227-81e6-11db-b272-0019d1258734
Report Status: 4
12/2/2006 9:20 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: 53c75227-81e6-11db-b272-0019d1258734
Report Status: 0
12/2/2006 9:17 AM	Windows Error Reporting	Fault bucket 3021759633, type 5
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_074b4d54

Analysis symbol: 
Rechecking for solution: 0
Report Id: eaed9d34-81e5-11db-a91e-0019d1258734
Report Status: 0
12/2/2006 9:17 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_cab_069341ef

Analysis symbol: 
Rechecking for solution: 0
Report Id: eaed9d34-81e5-11db-a91e-0019d1258734
Report Status: 4
12/2/2006 9:17 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: eaed9d34-81e5-11db-a91e-0019d1258734
Report Status: 0
12/2/2006 9:17 AM	Windows Error Reporting	Fault bucket 3021759633, type 5
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_0342f45c

Analysis symbol: 
Rechecking for solution: 0
Report Id: dd368f7b-81e5-11db-a91e-0019d1258734
Report Status: 0
12/2/2006 9:17 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_cab_09b2e80d

Analysis symbol: 
Rechecking for solution: 0
Report Id: dd368f7b-81e5-11db-a91e-0019d1258734
Report Status: 4
12/2/2006 9:17 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: dd368f7b-81e5-11db-a91e-0019d1258734
Report Status: 0
12/2/2006 9:13 AM	Windows Error Reporting	Fault bucket 3021759633, type 5
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_06b7b099

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5dd57e8d-81e5-11db-a91e-0019d1258734
Report Status: 0
12/2/2006 9:13 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_cab_045ba543

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5dd57e8d-81e5-11db-a91e-0019d1258734
Report Status: 4
12/2/2006 9:13 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: 5dd57e8d-81e5-11db-a91e-0019d1258734
Report Status: 0
12/2/2006 9:13 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:
P1: 80072f8f
P2: EndSearch
P3: Search
P4: 6.1.7600.16385
P5: MpSigDwn.dll
P6: 6.1.7600.16385
P7: Windows Defender
P8: 
P9: 
P10: 

Attached files:
C:\Windows\Temp\MPTelemetrySubmit\client_manifest.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_80072f8f_2599d8d460db8dc3c94d1c833fae74b92d2c9094_cab_012b9c7d

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5adbc635-81e5-11db-a91e-0019d1258734
Report Status: 4
12/2/2006 8:59 AM	Windows Error Reporting	Fault bucket 3021759633, type 5
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_04e26e5b

Analysis symbol: 
Rechecking for solution: 0
Report Id: 57d0c5d7-81e3-11db-a91e-0019d1258734
Report Status: 0
12/2/2006 8:58 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_cab_099e6279

Analysis symbol: 
Rechecking for solution: 0
Report Id: 57d0c5d7-81e3-11db-a91e-0019d1258734
Report Status: 4
My System SpecsSystem Spec
.


11 Mar 2014   #4

UEFI Windows 7 Pro x64
 
 

Quote   Quote: Originally Posted by derekimo View Post
These are quite interesting too, the date is 2006...

Code:
12/2/2006 9:31 AM	Windows Error Reporting	Fault bucket 3021759633, type 5
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_0ad01dfb

Analysis symbol: 
Rechecking for solution: 0
Report Id: d8032138-81e7-11db-b272-0019d1258734
Report Status: 0
12/2/2006 9:31 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_cab_03fc1229

Analysis symbol: 
Rechecking for solution: 0
Report Id: d8032138-81e7-11db-b272-0019d1258734
Report Status: 4
12/2/2006 9:31 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: d8032138-81e7-11db-b272-0019d1258734
Report Status: 0
12/2/2006 9:22 AM	Windows Error Reporting	Fault bucket 3021759633, type 5
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_074ff0d3

Analysis symbol: 
Rechecking for solution: 0
Report Id: 989d3d34-81e6-11db-b272-0019d1258734
Report Status: 0
12/2/2006 9:22 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_cab_03d3e4f1

Analysis symbol: 
Rechecking for solution: 0
Report Id: 989d3d34-81e6-11db-b272-0019d1258734
Report Status: 4
12/2/2006 9:22 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: 989d3d34-81e6-11db-b272-0019d1258734
Report Status: 0
12/2/2006 9:20 AM	Windows Error Reporting	Fault bucket 3021759633, type 5
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_0b6a2e21

Analysis symbol: 
Rechecking for solution: 0
Report Id: 53c75227-81e6-11db-b272-0019d1258734
Report Status: 0
12/2/2006 9:20 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_cab_0b5e2210

Analysis symbol: 
Rechecking for solution: 0
Report Id: 53c75227-81e6-11db-b272-0019d1258734
Report Status: 4
12/2/2006 9:20 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: 53c75227-81e6-11db-b272-0019d1258734
Report Status: 0
12/2/2006 9:17 AM	Windows Error Reporting	Fault bucket 3021759633, type 5
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.6.7600.256_deb4168eeb93fe3c14b57021d781f060476bf126_074b4d54

Analysis symbol: 
Rechecking for solution: 0
Report Id: eaed9d34-81e5-11db-a91e-0019d1258734
Report Status: 0
12/2/2006 9:17 AM	Windows Error Reporting	Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: 7.6.7600.256
P2: 80072f8f
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available
Thank you so much for starting the ball rolling

I don't know what this interesting code means that you've snipped out, would you be able to explain why it's of interest?

I've been getting these BSOD messages for a month now. I also had just performed my third fresh reinstall of the PC a few days ago, so the nVidia drivers were clean installed. I just updated them after reading your responses to the version that was released yesterday and installed the missing drivers for USB3 and Intel Management. I also just installed a firmware update to my Samsung 840 Pro SSD while reviewing this message.

I'll zip up the next BSOD it has to see if these tweaks changed anything.

I'm a little afraid to run Driver Verifier because last time I told it to run I was left with eternal bootloops. Is there a way to deactivate Verifier pre-boot if it doesn't work out?

The reinstall before that was inspired by activating the RAPID Mode of my 840 Pro and also resulted in eternal bootloops, so now I'm afraid of that too...and it's supposed to give me near 1Gb/s data transfer T.T
My System SpecsSystem Spec
11 Mar 2014   #5

Microsoft Community Contributor Award Recipient

Windows 7 Pro 64 SP1
 
 

I just found the date to be odd, 2006, when Windows 7 didn't come out till 2009. They are all related to Windows update though.

Here's another tidbit that fits with the date above,

Code:
Original Install Date:     12/2/2006, 3:56:57 AM
That is from your system info, it is obviously wrong since windows 7 didn't come out until 2009.

You said you did a clean install, but this in your first post,

Quote:
I tried reinstalling this machine twice from an image I've used on countless other machines without any problems.
Does not match. Technically, that is not a clean install.

The SFC scan I mentioned above would be the next place to start, there has to be something going on to have incorrect dates like that.

The last sentence in that green box above tells you how to disable driver verifier in safe mode.
My System SpecsSystem Spec
11 Mar 2014   #6

UEFI Windows 7 Pro x64
 
 

Technically, maybe not, but the image is one I update monthly and use to restore countless other systems without any BSOD's. I'm not ruling it out as a possibility, but I feel it's not the cause. I hadn't noticed the date, but I think it was probably because I installed the first image on an old offline system and hadn't changed the BIOS date since replacing the battery.

I'll perform a fresh install if this new BSOD doesn't show anything new. The memory corruption you mentioned has me nervous, there's 8 sticks to test in there...that'll take forever @_@


Attached Files
File Type: zip SF_11-03-2014.zip (1.36 MB, 1 views)
My System SpecsSystem Spec
11 Mar 2014   #7

Microsoft Community Contributor Award Recipient

Windows 7 Pro 64 SP1
 
 

Your latest dump blames the display driver,

Code:
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xc8354
I can see it's the latest driver too.

You mentioned you thought it might be GPU related, have you tested it at all?

We have this tutorial,

Video Card - Stress Test with Furmark
My System SpecsSystem Spec
12 Mar 2014   #8

UEFI Windows 7 Pro x64
 
 

Soo...uhmm...an occasional white streak every four seconds across the Furmark screen from a GTX 570 wouldn't happen to mean failing card, would it? T.T

Here's yet another BSOD log with 2 BSOD's, one from between the time I responded and you suggested Furmark. Then, after running Furmark and seeing streaks, I decided to enable verifier as the tutorial suggested. I got bluescreened at the windows logo as well before disabling verifier and making this log.

Is my card definitely trash? Would be most depressing as I had hoped to sell it soon for $150 and upgrade...

Again, thank you so much for helping me out. Depressing news or no, whatever you find will finally return stability to the machine that I've put so much of my life into.


Attached Files
File Type: zip SF_12-03-2014.zip (1.41 MB, 1 views)
My System SpecsSystem Spec
16 Mar 2014   #9

UEFI Windows 7 Pro x64
 
 

Quote   Quote: Originally Posted by derekimo View Post
Your latest dump blames the display driver,

Code:
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xc8354
I can see it's the latest driver too.

You mentioned you thought it might be GPU related, have you tested it at all?

We have this tutorial,

Video Card - Stress Test with Furmark
I tested it again, still getting artifacts within 2 seconds of starting the test. I got 3 BSOD's today from completely different causes than the usual ones, hopefully these 3 and the furmark test might finally provide the evidence we need to close the case. Thanks again for all your help. Please take a look and tell me what you find.


Attached Files
File Type: zip SF_16-03-2014.zip (1.51 MB, 2 views)
My System SpecsSystem Spec
16 Mar 2014   #10
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Two different bugcheck codes saying the same thing.
Code:
BugCheck F7, {fffff880093c8d30, f88000ddd1c9, ffff077fff222e36, 0}

Probably caused by : volmgr.sys ( volmgr!_report_gsfailure+26 )

Followup: MachineOwner
---------
Code:
BugCheck 44, {fffffa801a98de20, eae, 0, 0}

Probably caused by : volmgr.sys ( volmgr! ?? ::FNODOBFM::`string'+6f0 )

Followup: MachineOwner
---------
Also, Parallels is hugely failing. Almost at every instance. Does it have any relations to the BSODs? Apparently (I may be wrong) the age of Parallels and the age of the issue is almost the same. Can you uninstall it, just as a test? (Feeling bad to say it, as I am not 100% sure that parallels is causing the issue; but it is causing problems for sure).

If parallels is not the issue, make it sure that your SSDs are running with the latest firmware.
How to Upgrade Samsung SSD Firmware | StorageReview.com - Storage Reviews

Test the HDDs using Seatools.

Scan the system for possible virus infection with the following programs (a precausion for the stop 0xF7 BSOD).
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.

Edit: Before uninstalling Parallels, dont let it start at its own alongwith windows, and see how the situation goes.
  1. Click on the Start button
  2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
  3. Select the “Startup” tab.
  4. Deselect all items other than the antivirus.
  5. Apply > OK
  6. Click on "services" tab. Check the "Hide all Microsoft Services"; Click "Disable all" > Apply > OK
  7. Accept then restart.
Let us know the results.
My System SpecsSystem Spec
Reply

 Multiple Random BSODs, Please help me




Thread Tools



Similar help and support threads for2: Multiple Random BSODs, Please help me
Thread Forum
Solved Multiple random BSODs BSOD Help and Support
Multiple BSODs, Random Occurences, Multiple Error Codes BSOD Help and Support
Multiple BSODs at random moments BSOD Help and Support
Multiple BSODs, random errors BSOD Help and Support
Multiple random BSODs BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 05:13 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33