BSOD - Yippee

Try this first:

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)

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 21:41:56.302 2010 (UTC - 4:00)
System Uptime: 0 days 8:50:06.001
BugCheck 1A, {411, fffff6fc50001b10, d6700001a32ba882, fffff6fc50001511}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6051 )
BUGCHECK_STR:  0x1a_411
PROCESS_NAME:  avgrsa.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 11:36:23.319 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:36.379
BugCheck DE, {2, fffff8a0005720a0, fffff8a0005700a1, 19e1f28c0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2d260 )
BUGCHECK_STR:  0xDE
PROCESS_NAME:  autochk.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 08:51:05.326 2010 (UTC - 4:00)
System Uptime: 0 days 11:07:10.386
BugCheck 1A, {411, fffff6fc8060fa70, e34000011e3a2882, fffff6fc80600071}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+18223 )
BUGCHECK_STR:  0x1a_411
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep  5 19:25:23.198 2010 (UTC - 4:00)
System Uptime: 0 days 7:25:52.883
BugCheck 1A, {411, fffff6fc50030b28, 4f54a820, fffff6fc50030029}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6051 )
BUGCHECK_STR:  0x1a_411
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep  5 11:58:28.816 2010 (UTC - 4:00)
System Uptime: 0 days 2:12:24.712
BugCheck 1A, {403, fffff6800000b640, f34000017185f867, fffff68000000040}
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )
BUGCHECK_STR:  0x1a_403
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep  5 09:45:28.054 2010 (UTC - 4:00)
System Uptime: 0 days 8:39:39.114
BugCheck 1000007E, {ffffffffc0000005, fffff80002f742cd, fffff880031a8988, fffff880031a81f0}
Probably caused by : ntkrnlmp.exe ( nt!CmpLockTableRemove+1d )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep  2 22:06:29.578 2010 (UTC - 4:00)
System Uptime: 0 days 4:07:13.411
BugCheck 4E, {99, 13d461, 3, 56a41}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu May  6 20:30:08.419 2010 (UTC - 4:00)
System Uptime: 2 days 21:36:58.479
BugCheck FE, {8, 6, 5, fffffa8007aa5640}
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 

Sorry I was rushed when I last replied.
In general, if you have multiple crashes and there are a number of different BSOD error codes and causes involved - then it's likely that there is a hardware problem. You have 8 crashes with 5 different BSOD error codes and 5 different causes - that makes it likely that this is a hardware problem.

There are repeated STOP 0x1A errors. These are Memory Management errors (info here: BSOD Index ). So, if you have a hardware problem and you're getting memory errors - the most likely cause is bad memory (RAM). It can be many other things, but this is the most likely.

If the hardware diagnostics come back clean, then we'll try other tests.

FWIW - I work in a PC repair shop and these are the first tests we run on any system that comes in.

In general, there's no need to mess with a properly functioning system. But in this case I'd have to wonder what caused it to stop malfunctioning. Broken hardware doesn't fix itself (and it could be something other than broken hardware).

There are only a couple of reasons that computers get BSOD's:
- 3rd party driver issues (most common)
- broken/malfunctioning hardware
- compatibility issues (mostly associated with Win7)
- Windows problems (least common)

Windows does have some self-healing properties - so I'd wonder if that's what's happened. I'd tentatively suggest leaving it alone for now. Should it start BSOD'ing again, please try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
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

Prime95 download site: http://www.mersenne.org/freesoft/
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.

Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - http://nvworld.ru/utilities/vmt/
Artifact Locator - http://nvworld.ru/utilities/alocator/
Sorry, but I don't read the language that this website is made in.