Solved Windows freezing randomly

I recently made my first custom build computer but my computer freezing randomly on windows. I have tested all my hardware on other OS (Mac OS X test=prime 95 and memtest 86). Yes, it is a hackintosh but windows 8 is install on a other drive. It has been 2 months and I still did not find the problem. I even tried windows 7 and had the same issue(note after the installation I could not go in safe mode it would crash). the bios is on default setting but with wake on LAN disable. I have tried install and running windows without my other drive plug in but had no luck. My system specs are:

500r
h100i
3770k
z77x-ud5h
2 tb seagate hdd(windows)
3 tb seagate hdd(backup)
240 gb ssd ( Mac )
gtx 660 ti

thanks in advance.

Please provide this information so we can provide a complete analysis (even though you're not reporting BSOD's): https://www.eightforums.com/bsod-cr...e-screen-death-bsod-posting-instructions.html

At work we run diagnostics on every system that we take in for repair (before we even start working on it). At a minimum, please run the free diagnostics here: Initial Hardware Diagnostics. For more in-depth diagnostics, please run those listed here: Hardware Diagnostics

Click to expand...

You only have one drive (2tB) - but 3 disks?
Is the SSD formatted in the MAC filesystem?
Is one of the others (the 3tB) not formatted?

This device isn't installed:

Not Available USB\VID_045E&PID_0291\7&2A42A4B7&0&3 The drivers for this device are not installed.

Click to expand...

This looks to be a wireless USB XBox controller. These devices are known to cause issues in Win7 and should be physically removed from your system while we're troubleshooting. Then test to see if the problems stop.

Numerous unexplained shutdowns.
If these are caused by you holding the power button down - then we don't worry about them.
If it's not that, then we worry about it (probably a hardware problem)
Which is it?

Found a pile of errors related to Virtual Disk/Hard Disk stuff.

Event[490]:
Log Name: System
Source: VDS Basic Provider
Date: 2012-12-16T09:25:13.000
Event ID: 1
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: vincent
Description:
Unexpected failure. Error code: 2@01010013

Click to expand...

Finally I also saw this error (which concerns me because there are no memory dumps in the upload, no record of BSOD's in the WER section of MSINFO32, and yet the system is trying to create crash (memory) dumps and failing):

Event[13]:
Log Name: System
Source: volmgr
Date: 2012-12-15T17:29:50.667
Event ID: 46
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: windows-uj49s6b
Description:
Crash dump initialization failed!

Click to expand...

So, there's a lot of issues related to the storage subsystem.
A couple of suggestions:
- update the firmware on your SSD to the latest available version
- update Intel Rapid Storage Technology (RST) driver from Intel - NOT from Gigabyte: Intel Download Center
- update Marvell controller storage drivers through Gigabyte (GIGABYTE - Motherboard - Socket 1155 - GA-Z77X-UD5H (rev. 1.0))
- do not use the Marvell controller for the SSD - the latest drivers for these date from 2011 and have issues with SSD's

Remove the 3 tB drive and test the system without it.
Then (if problems persist) remove the SSD and test the system without it.

Also test ALL hard drives to see if any are having problems: Hard Drive Diagnostic Procedure

This appears to be (IMO) a hardware problem - so the hardware diagnostics and low-level drivers are very important.
Please post back if this doesn't help out.

Still have the problem.

Have you run the diagnostics that I suggested in my first post? If so, what were the results?

Have you done the things that I suggested in my second post? If so, what were the results?

I found the problem. I fell so stupid. I guess this kinda stuff only happens on the first build. The bios default vcore was wrong so I just changed it to 1.14 voltes and now everything works(9 hours on prime 95). I will do some more testing then if everything is good I will change the status to solved. Thanks for your time.

I've built PC's since the late 1980's and never had one work on the first boot for over 20 years!
My Win7 PC (built in 2009) was the first!