Random BSODs and Reboots

Please provide the information from this post: https://www.sevenforums.com/crashes-d...tructions.html These reports are needed to see what's going on inside your system (in addition to the BSOD memory dump files.

The BSOD's seem to point towards either an issue with your Western Digital USB device/software, or with your nVidia video card - but this is not certain. I would suggest uninstalling the Western Digital software and then unplugging the Western Digital device while we're troubleshooting.

Try this free stress test for your video card:
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit[/quote]

Beyond that, try these free bootable hardware diagnostics:

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: Malware (read the details at the link)

Run the hard drive diagnostics with the Western Digital device plugged into the USB port - and see if the test detects the drive and runs a test on it (in addition to testing your installed hard drive).

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 22 01:35:37.813 2010 (UTC - 4:00)
System Uptime: 1 days 6:39:07.000
*** 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+1830f2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`05393450 00000000`00000002 00000000`00000001 fffff800`02ea4c7c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 20 19:06:58.966 2010 (UTC - 4:00)
System Uptime: 0 days 11:32:52.154
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+157 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`00000082 00000000`00000002 00000000`00000000 fffff800`02e9a167
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 20 07:33:07.028 2010 (UTC - 4:00)
System Uptime: 3 days 14:46:06.000
Probably caused by : usbhub.sys ( usbhub!UsbhHubWorker+70 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`00000ae8 00000000`00000002 00000000`00000001 fffff800`02e7e365
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep 16 16:46:54.530 2010 (UTC - 4:00)
System Uptime: 0 days 6:02:28.702
*** 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+74a1d )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep 16 10:43:09.949 2010 (UTC - 4:00)
System Uptime: 4 days 8:04:27.265
*** WARNING: Unable to verify timestamp for wdcsam64.sys
*** ERROR: Module load completed but symbols could not be loaded for wdcsam64.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a56 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WDDMService.ex
Bugcheck code 00000019
Arguments 00000000`00000003 fffff800`03010dc0 fffff800`03010dc0 fffff880`03010dc0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Aug 21 07:25:40.352 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:29.524
BugCheck D1, {fffffa0005c69aa8, 2, 1, fffff880040100a4}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 000000D1
Arguments fffffa00`05c69aa8 00000000`00000002 00000000`00000001 fffff880`040100a4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  

Try the Hitachi Drive Fitness Test to see if it gets different results.
But the upshot here is that the drive is spitting out errors - so it's probably bad.
Backup your stuff IMMEDIATELY as there's no telling when it's gonna die for good.

Memtest should be run for a minimum of 3 passes (my experience), with overnight being the best.

USB drive? Unplug it and see if that stops the BSOD's. If it does, then you've found the cause.

Most memory has a lifetime warranty, so I'd exchange it for new stuff.

Disk check can fix stuff (as can other tools) - but my view of this is:
- why did it fail?
- is it gonna fail again soon?

So, I just go ahead and replace the drive. As for Western Digital external drives, I've had many issues with them. The connectors and circuitry go bad on my, but when I pull the drive out it has all my data and the drive works fine.