I have to suspect hardware. Here is a summary of all your BSODs to date:
BSOD BUGCHECK SUMMARY
Try this free stress test: Free Software - GIMPS
Test your hard drive too. See this page: HD Diagnostic
BSOD BUGCHECK SUMMARY
Code:
[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 6 20:16:54.120 2010 (GMT-4)
System Uptime: 0 days 0:01:24.774
BugCheck C9, {224, fffff880011692d8, fffff98017234d30, 3}
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
Probably caused by : PxHlpa64.sys ( PxHlpa64+82d8 )
BUGCHECK_STR: 0xc9_224
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 6 15:11:32.547 2010 (GMT-4)
System Uptime: 0 days 1:10:43.061
BugCheck F4, {3, fffffa8005b7a760, fffffa8005b7aa40, fffff80002fcd540}
Probably caused by : hardware_disk
PROCESS_NAME: csrss.exe
BUGCHECK_STR: 0xF4_IOERR_C000000E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 13:37:50.046 2010 (GMT-4)
System Uptime: 0 days 0:12:46.560
BugCheck F4, {3, fffffa8005a83600, fffffa8005a838e0, fffff80002fc8540}
Probably caused by : csrss.exe
PROCESS_NAME: csrss.exe
BUGCHECK_STR: 0xF4_C0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 30 11:17:37.236 2010 (GMT-4)
System Uptime: 0 days 0:11:52.015
BugCheck F4, {3, fffffa800534ab30, fffffa800534ae10, fffff80002d83540}
Probably caused by : hardware_disk
PROCESS_NAME: csrss.exe
BUGCHECK_STR: 0xF4_IOERR_C000000E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 30 07:03:32.859 2010 (GMT-4)
System Uptime: 13 days 22:29:16.073
BugCheck 7A, {fffff6fc50045600, ffffffffc000000e, 74fb9880, fffff8a008ac0bc8}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34c4e )
BUGCHECK_STR: 0x7a_c000000e
PROCESS_NAME: OUTLOOK.EXE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 30 11:01:40.238 2010 (GMT-4)
System Uptime: 0 days 3:56:55.017
BugCheck F4, {3, fffffa80050d3b30, fffffa80050d3e10, fffff80002de2540}
Probably caused by : csrss.exe
PROCESS_NAME: csrss.exe
BUGCHECK_STR: 0xF4_C0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun 4 19:49:29.442 2010 (GMT-4)
System Uptime: 0 days 4:21:46.081
BugCheck F4, {3, fffffa80052f34a0, fffffa80052f3780, fffff80002fdf540}
Probably caused by : csrss.exe
PROCESS_NAME: csrss.exe
BUGCHECK_STR: 0xF4_C0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun 3 19:05:14.317 2010 (GMT-4)
System Uptime: 0 days 14:01:40.956
BugCheck 7A, {fffff6fc400097a0, ffffffffc000000e, 11743f860, fffff880012f402c}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR: 0x7a_c000000e
PROCESS_NAME: System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 07:53:54.026 2010 (GMT-4)
System Uptime: 0 days 19:45:45.680
BugCheck 7A, {fffff6fc40009860, ffffffffc000000e, 7a52860, fffff8800130c69c}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR: 0x7a_c000000e
PROCESS_NAME: svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 08:01:43.275 2010 (GMT-4)
System Uptime: 0 days 0:06:48.055
BugCheck F4, {3, fffffa80061c4b30, fffffa80061c4e10, fffff80002d85540}
Probably caused by : hardware_disk
PROCESS_NAME: wininit.exe
BUGCHECK_STR: 0xF4_IOERR_C000000E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 13:23:50.431 2010 (GMT-4)
System Uptime: 0 days 1:18:14.070
BugCheck F4, {3, fffffa8005a9eb30, fffffa8005a9ee10, fffff80002fe1540}
Probably caused by : hardware_disk
PROCESS_NAME: csrss.exe
BUGCHECK_STR: 0xF4_IOERR_C00000C0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 6 21:59:53.225 2010 (GMT-4)
System Uptime: 0 days 0:02:30.880
BugCheck F4, {3, fffffa8006609680, fffffa8006609960, fffff80002f7d540}
Probably caused by : csrss.exe
PROCESS_NAME: csrss.exe
BUGCHECK_STR: 0xF4_IOERR
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/font]
Try this free stress test: Free Software - GIMPS
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.
- "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).
The Test selection box and the stress.txt file describes what components that the program stresses.
Test your hard drive too. See this page: HD Diagnostic
My Computer
- Computer Manufacturer/Model Number
- Custom
- OS
- Windows 7 Professional x64
- CPU
- Intel i7 2600K OC'd @ 4620 MHz
- Motherboard
- Asus P8Z68-V Pro
- Memory
- 16GB GSkill Sniper 2133 Mhz (4x4GB)
- Graphics Card(s)
- EVGA GeForce GTX 480 SuperClocked+
- Sound Card
- Realtek High Definition Audio
- Monitor(s) Displays
- 2x Acer S273HLbmii 27"
- Screen Resolution
- 2 x 1920x1080
- Hard Drives
- 64GB Crucial M4 SSD
Storage: Hitachi 1TB 5400RPM, Samsung 1.5TB 5400RPM
- PSU
- Corsair HW Series 750w (modular)
- Case
- Cooler Master HAF 932 Advanced Blue Edition
- Cooling
- CM Hyper 212+ CPU cooler, 3x 230mm + 1x 140mm case fans
- Keyboard
- Logitech MK320 (wireless)
- Mouse
- Logitech MK320 (wireless)
- Internet Speed
- 30 Mb/s : 2 Mb/s
