BSOD waking from sleep mode

GaffOz · 08 Jun 2011

I just built a new computer:
Since first fired up it blue screens every time it comes out of sleep mode.
I've checked all my drivers and all report being up to date.
Currently I have sleep mode turned off and the computer is running reliably.
I've attached the required files.
Thanks for any assistance.
GaffOz

usasma · 08 Jun 2011

Perfmon shows a problem with the Cyberlink Power Control component - please uninstall the Cyberlink software from your system.

Error
Symptom:[IMG]res://wdc.dll/error.gif[/IMG]
Device is not present, not working properly, or does not have all of its drivers installed.Cause:A device has a configuration problem that prevents it from working properly.Details:The device, Power Control [2011/06/06 09:33:15], is reporting "tv_ConfigMgrErr24". This device will not be available until the issue is resolved. The Plug and Play ID for this device is ROOT\LEGACY_{B154377D-700F-42CC-9474-23858FBDF4BD}\0000.Resolution:1. Verify the correct driver is installed.
2. Try updating the drivers using Windows Update.
3. Check with the manufacturer for an updated driver.
4. Attempt to uninstall and then reinstall the device using Device Manager.Related:Explanation of Error Codes Generated by Device Manager
Manage Devices in Windows

Your GigaByte ET6 (EasyTune6) driver dates from 2006 - and that's a known BSOD cause in Win7 systems.
Please uninstall the program and see if that stops the BSOD's

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

Code:


iaStorV.sys       Thu Jun 10 20:46:19 2010 (4C11875B)
iaStor.sys        Sat Nov 06 03:44:52 2010 (4CD50774)
SYMDS64.SYS       Tue Dec 07 19:16:58 2010 (4CFECE7A)
Ironx64.SYS       Fri Nov 12 18:06:50 2010 (4CDDC88A)
CLBStor.sys       Wed Oct 07 02:42:27 2009 (4ACC3853)
dump_iaStor.sys   Sat Nov 06 03:44:52 2010 (4CD50774)
SRTSPX64.SYS      Tue Mar 29 22:46:18 2011 (4D92997A)
AppleCharger.sys  Mon Apr 26 23:54:05 2010 (4BD65FDD)
Rt64win7.sys      Thu Nov 11 01:35:36 2010 (4CDB8EB8)
HECIx64.sys       Tue Sep 21 12:59:04 2010 (4C98E458)
ctoss2k.sys       Wed Jul 07 09:38:24 2010 (4C348350)
ctprxy2k.sys      Wed Jul 07 09:42:17 2010 (4C348439)
nusb3xhc.sys      Thu Nov 18 20:34:25 2010 (4CE5D421)
ctaud2k.sys       Wed Jul 07 09:42:14 2010 (4C348436)
ctsfm2k.sys       Wed Jul 07 09:38:10 2010 (4C348342)
CTHWIUT.SYS       Wed Jul 07 09:44:19 2010 (4C3484B3)
CT20XUT.SYS       Wed Jul 07 09:44:15 2010 (4C3484AF)
000.fcl           Fri Sep 26 09:11:22 2008 (48DCDF7A)
emupia2k.sys      Wed Jul 07 09:38:03 2010 (4C34833B)
nusb3hub.sys      Thu Nov 18 20:34:24 2010 (4CE5D420)
ha20x22k.sys      Wed Jul 07 09:41:25 2010 (4C348405)
gdrv.sys          Thu Mar 12 23:22:29 2009 (49B9D175)
CTEXFIFX.SYS      Wed Jul 07 09:44:03 2010 (4C3484A3)
CLBUDF.SYS        Wed Oct 07 02:42:23 2009 (4ACC384F)
RTKVHD64.sys      Fri Sep 03 04:02:27 2010 (4C80AB93)
GVTDrv64.sys      Tue Sep 05 03:10:02 2006 (44FD22CA)
hiber_iaStor.sys  Sat Nov 06 03:44:52 2010 (4CD50774)
hiber_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
ENG64.SYS         Thu May 12 17:20:34 2011 (4DCC4F22)
atikmpag.sys      Tue Apr 19 21:22:32 2011 (4DAE3558)
IDSvia64.sys      Fri Mar 11 21:15:42 2011 (4D7AD74E)
eeCtrl64.sys      Tue May 03 00:23:25 2011 (4DBF833D)
atikmdag.sys      Tue Apr 19 21:53:29 2011 (4DAE3C99)
SYMEFA64.SYS      Sun Mar 13 23:20:58 2011 (4D7D899A)
SYMNETS.SYS       Thu Mar 17 23:24:33 2011 (4D82D071)
RzSynapse.sys     Wed Apr 06 05:29:13 2011 (4D9C3269)
wdcsam64.sys      Wed Apr 16 04:39:08 2008 (4805BB2C)

Other than that, there's no firm eveidence of anything else wrong. Let's try the above stuff and see if it helps> If not, post back and we'll work on other tests.

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060711-28594-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jun  6 13:00:51.688 2011 (UTC - 4:00)
System Uptime: 0 days 4:41:01.485
BugCheck F4, {3, fffffa800bc26630, fffffa800bc26910, fffff8000319af40}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`0bc26630 fffffa80`0bc26910 fffff800`0319af40
BiosVersion = F1
BiosReleaseDate = 02/14/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060611-129980-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun  5 22:35:21.311 2011 (UTC - 4:00)
System Uptime: 0 days 3:32:14.108
BugCheck F4, {3, fffffa800b57fa70, fffffa800b57fd50, fffff800031ccf40}
Probably caused by : wininit.exe
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0xF4_svchost.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_svchost.exe_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`0b57fa70 fffffa80`0b57fd50 fffff800`031ccf40
BiosVersion = F1
BiosReleaseDate = 02/14/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060611-93226-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun  5 18:58:36.358 2011 (UTC - 4:00)
System Uptime: 0 days 9:44:22.064
BugCheck F4, {3, fffffa800b735060, fffffa800b735340, fffff8000318af40}
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_IOERR
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`0b735060 fffffa80`0b735340 fffff800`0318af40
BiosVersion = F1
BiosReleaseDate = 02/14/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060511-89684-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun  5 09:10:34.259 2011 (UTC - 4:00)
System Uptime: 0 days 10:22:36.056
BugCheck F4, {3, fffffa800b446b30, fffffa800b446e10, fffff800031d0f40}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`0b446b30 fffffa80`0b446e10 fffff800`031d0f40
BiosVersion = F1
BiosReleaseDate = 02/14/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060511-23836-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun  4 22:45:00.752 2011 (UTC - 4:00)
System Uptime: 0 days 1:37:25.353
BugCheck F4, {3, fffffa800b6cdb30, fffffa800b6cde10, fffff80003194f40}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`0b6cdb30 fffffa80`0b6cde10 fffff800`03194f40
BiosVersion = F1
BiosReleaseDate = 02/14/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060511-24211-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun  4 19:12:04.262 2011 (UTC - 4:00)
System Uptime: 0 days 23:17:22.058
BugCheck F4, {3, fffffa8008ab0550, fffffa8008ab0830, fffff800031e2f40}
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`08ab0550 fffffa80`08ab0830 fffff800`031e2f40
BiosVersion = F1
BiosReleaseDate = 02/14/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060411-20280-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jun  3 19:40:22.254 2011 (UTC - 4:00)
System Uptime: 0 days 7:38:54.050
BugCheck F4, {3, fffffa8008b07950, fffffa8008b07c30, fffff8000318ef40}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`08b07950 fffffa80`08b07c30 fffff800`0318ef40
BiosVersion = F1
BiosReleaseDate = 02/14/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060411-17425-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jun  3 11:57:22.218 2011 (UTC - 4:00)
System Uptime: 0 days 1:27:10.015
BugCheck F4, {3, fffffa800b442920, fffffa800b442c00, fffff800031ccf40}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`0b442920 fffffa80`0b442c00 fffff800`031ccf40
BiosVersion = F1
BiosReleaseDate = 02/14/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060311-125393-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jun  3 09:15:05.611 2011 (UTC - 4:00)
System Uptime: 0 days 9:43:47.407
BugCheck D1, {8, 2, 1, fffff8800145f723}
Probably caused by : NETIO.SYS ( NETIO!WfppIncrementIndexAndPurgeEntries+93 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_NETIO!WfppIncrementIndexAndPurgeEntries+93
Bugcheck code 000000D1
Arguments 00000000`00000008 00000000`00000002 00000000`00000001 fffff880`0145f723
BiosVersion = F1
BiosReleaseDate = 02/14/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

There's a lot of "hardware_disk" errors in MSINFO32 - please run these free hardware 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 Resources (read the details at the link)

GaffOz · 09 Jun 2011

Hi usasma, Thanks for all your help. I uninstalled GigaByte ET6 (EasyTune6) but it made no difference. Forgive me but the the rest of your advice is a little beyond me. I go to the links you supplied but don't really know what to look for, download or install. I don't understand why all brand new, high end, name brand equipment, running the latest version of windows 7 and only the driver disks that came with the gear installed, is full of redundant drivers that are 5 years old! There's really nothing much on the machine, steam and a couple of games, would a reinstall help? Or could you please give a little more detail on what to do with the links you supplied?
Thanks again for your time.
GaffOz

usasma · 09 Jun 2011

The driver problems are primarily due to distribution issues. For example, the motherboard manufacturer makes the CD/DVD with the drivers on it for their motherboard. Then they manufacture and package the motherboard with the CD/DVD. They sit on a shelf until someone orders them. Then they sit on the shelf of the orderer until someone buys them (there may be more steps if there are several resellers involved). Finally, by the time that you get them, they're significantly outdated.

Now, throw a new OS into the equation. Were there even drivers for the OS when the board was manufactured? Had they been thoroughly tested by millions of users for a couple of years to work out all the bugs?

Finally, please understand that OLD is not the same as BAD. Old drivers are more likely to cause a problem - but that doesn't mean that they will cause a problem (especially if they're well designed and then submitted to Microsoft for WHQL certification).

To make it a bit easier on you (normally I'd go to each individual manufacturer's website), please go to this page: GIGABYTE - Motherboard - Socket 1155 - GA-P67A-UD5-B3 (rev. 1.0) and click on the DOWNLOADS tab about ½ way down the page. Enter your OS in the dropdown box and install all the drivers from there.

Next, please uninstall all ATI stuff from Control Panel...Programs...Uninstall a program
Then visit this link: ATI Radeon and download the DISPLAY DRIVER ONLY.
- then install the new, DISPLAY DRIVER ONLY

GaffOz · 11 Jun 2011

Hi usasma,

Stability has been achieved! I installed all the mobo drivers you directed me to and stability tested successfully before having to reduce the video card support to driver only.
Thanks again for your patient assistance and walking me through the process.
GaffOz

spoke to soon.... intermittent now...
I'll go back and do the ATI drivers

GaffOz · 14 Jun 2011

OK, I updated all the drivers you directed me to, removed the video card drivers and associated programs and replaced with the latest driver only. I ran memtest for 3 passes without logging any errors.

Still crashing on waking, seems the longer it's asleep the more likely it is to crash. I'll upload an up to date crash log and health report.

I did have 2x 1TB HHD installed but removed them as they, or one thereof, seemed problematic in spite of being less than 2 months old. So now the only storage is the 420gig OCZ Vortex 2 SSD.

The more I speak to people the more common this problem appears to be, most of them just turn off the sleep function.

Any further thoughts? Maybe it's time for those high explosives? :)

Thanks again,

GaffOz

usasma · 14 Jun 2011

First, a story....

Back when Win7 was in beta, I built a new system just to test it on. It had RAID 5 and a hardware RAID card on an Asus P6T Deluxe v1 mobo. It had BSOD's when sleeping.

So, I reported the bug to Microsoft. And they pointed at my RAID drivers and said that that was the problem.
So I contacted the RAID device manufacturer and got them to generate new drivers.

By the time that this was done, Win7 had been released. And I had the new RAID drivers and the system still BSOD'd when sleeping. So, I ripped out the RAID and reinstalled Windows - and guess what? Yep, still had BSOD's when sleeping.

After trying everything under the sun (and asking a whole lot of very smart people about this) I wondered...."Why does Asus have a v2 of my mobo?" So I took the plunge and purchased v2.

Reinstalled Windows and reset everyting once again. And, viola! No more BSOD's!!! Hundreds of hours and hundreds of dollars spent - just to find out it was the mobo!

The perfmon report still shows an issue with your Power Control device - which, I suspect, it associated with the Cyberlink software on your system. Please remove this software so that we can see if it impacts the BSOD's when sleeping.

[IMG]res://wdc.dll/open.gif[/IMG]

Win32_PnPEntity.DeviceID="ROOT\\LEGACY_{B154377D-700F-42CC-9474-23858FBDF4BD}\\0000"
PropertyValueConfigManagerErrorCode[IMG]res://wdc.dll/flag.gif[/IMG]

Device is not present, not working properly, or does not have all of its drivers installed.ConfigManagerUserConfig0DescriptionPower Control [2011/06/06 09:33:15]NamePower Control [2011/06/06 09:33:15]Service{B154377D-700F-42cc-9474-23858FBDF4BD}StatusError

Also, one of the drivers for this program dates from 2009 (Cyberlink Storage Helper Driver)

Loads of BSOD's in the MSINFO32 report:
2 blame the file system (ntfs.sys) - a Windows driver
3 blame networking (NETIO.sys) - a Windows driver
8 blame Client/Server Runtime Server Subsystem (csrss.exe) - a critical Windows component
4 blame the Windows Startup Application (wininit.exe)
14 blame hardware_disk

I'm just being cautious with this one:
Please uninstall the Gigabyte Easy Saver - mobo power utility driver - it's driver dates from 2009

These have caused BSOD's in other systems (there's no indication that they are doing it in yours, but I mention it for the sake of mentioning everything):
Norton Internet Security
Razer drivers
2009 versions of the USB 3.0 drivers

I strongly suspect that your SSD is the culprit here - but there's nothing firm other than the hardware_disk errors.
If it's not that, then it's the motherboard and how it deals with the SSD.
Either way it's a hardware problem (IMO). If you can RMA one or the other - that would save you some money.

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061311-12558-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jun 13 04:45:46.357 2011 (UTC - 4:00)
System Uptime: 0 days 0:59:21.027
BugCheck F4, {3, fffffa800becd920, fffffa800becdc00, fffff8000319ef40}
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`0becd920 fffffa80`0becdc00 fffff800`0319ef40
BiosVersion = F1
BiosReleaseDate = 02/14/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061211-12573-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun 12 02:05:51.306 2011 (UTC - 4:00)
System Uptime: 0 days 0:12:19.102
BugCheck F4, {3, fffffa800befbb30, fffffa800befbe10, fffff80003182f40}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`0befbb30 fffffa80`0befbe10 fffff800`03182f40
BiosVersion = F1
BiosReleaseDate = 02/14/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061211-12979-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun 12 01:44:12.503 2011 (UTC - 4:00)
System Uptime: 0 days 0:29:04.300
BugCheck F4, {3, fffffa800bf0db30, fffffa800bf0de10, fffff8000319cf40}
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`0bf0db30 fffffa80`0bf0de10 fffff800`0319cf40
BiosVersion = F1
BiosReleaseDate = 02/14/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061211-13182-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 11 10:00:31.188 2011 (UTC - 4:00)
System Uptime: 0 days 9:00:48.984
BugCheck F4, {3, fffffa800be51b30, fffffa800be51e10, fffff8000318cf40}
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_IOERR
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`0be51b30 fffffa80`0be51e10 fffff800`0318cf40
BiosVersion = F1
BiosReleaseDate = 02/14/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``