all stuff running at or below stock GIGABYTE GA-X79-UD3 MB Intel Core i7-3930K Sandy Bridge-E 3.2GHz G.SKILL Ripjaws Z Series 32GB (4 x 8GB) 240-Pin DDR3 SDRAM DDR3 1600 Desktop Memory Model F3-12800CL10Q-32GBZL OCZ Agility 3 AGT3-25SAT3-240G 2.5" 240GB SATA III MLC Internal Solid State Drive (SSD) BFG Geforce 8800 GTS 512 MB (haven't upgraded this part of the rig yet) Thermaltake 850 watt PSU Running Microsoft Windows 7 Professional SP1 64-bit Any luck with this?I have a similar setup with similar issue, brand new build.

updating drivers in sandisk flash drives-74

I started with newer Bios version F8 GIGABYTE GA-X79-UD3 MB Intel Core i7-3930K Sandy Bridge-E 3.2GHz G.

SKILL Ripjaws Z Series 16GB (4 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 Desktop Memory Old 80GB Seagate SATA for OS until prices come down a bit Gigabyte GTX580 Corsair 650 watt PSU Running Microsoft Windows 7 Home Premium SP1 64-bit Thanks, John Even if the two hardrives i keep in raid array are both disconnected- it makes no difference.

I haven't switched them to other ports- as i dont see what difference it would make if they are in 1 port v.s.

another if when they aren't even connected the problem persists.

I also have the problem you mentioned (jdroflet), that after it reboots when it crashed it gets into this 10 second cycle where it repeatedly reboots with different beeps.

I found a website that went over the basics of how to interpret those beeps- but life got busy and i didn't ever get around to looking into it more.

Start ≠ 0; Start = 3 = IDE and the wrong drivers are being used.

I bought a new rig, and everything seemed to be going great and i was about to start overclocking it, but i found that whenever i suspended my computer in any state of sleep- it would appear to resume and show me the log on screen for about thirty seconds, and then BSOD with error 0x000000f4 "process of thread crucial to system operation has unexpectedly exited or been terminated." if during that thirty seconds where it seems like everything is OK- if i log in to windows, the busy cursor comes up on a new background (not yet the desktop), and then it will BSOD as if no difference.

After messing around with many variables and reinstalls it appears that the one variable that is able to change things is that if i boot the intel chipset in ahci rather than raid- it will work.