Showing results for 
Search instead for 
Did you mean: 

Random Freezing No BSOD

Level 7
Hi all,

For the past few days been really struggling to find out the cause of my computer randomly freezing i have checked everything i can think of but still its still happening. These are my specs:

Operating System
Windows 8.1 Pro 64-bit
Intel Core i7 4930K @ 3.40GHz 27 °C
Corsair CMY32GX3M4A1866C9 32.0GB DDR3 (9-9-9-24)
BIOS ver 0701
2048MB ATI AMD Radeon R9 270 Series Powercolor 46 °C
Power Supply
Corsair RM1000
465GB Seagate ST500DM002-1BC142 (SATA) 28 °C
2794GB Seagate ST3000DM001-1CH166 (SATA) 29 °C
931GB Western Digital WDC WD10EZEX-07M2NA0 (SATA) 29 °C
Cooler Master HAF-X
CORSAIR Hydro Series™ H105 240mm Extreme Performance Liquid CPU Cooler

And i have done the following tests:
- Originally was using a SSD, but swapped out for brand new HDD, even though SMART was fine on SSD
- re-installed windows multiple times
- reset overclocking to standard with no XMP profile (was using watercooling O.C. profile and XMP )
- checked mobo voltages all seem fine:
+5V 5.080 V
+3.3V 3.328 V
+12V 12.096 V
VIN3 0.184 V
VIN4 0.368 V
VCORE 1.408 V
- checked mobo LED's no problems
- Checked mobo Q-CODE showing AA
- visually checked mobo cant see anything wrong
- triple checked all connections in PC
- memtest86 - no problems
- SMART test all HDD's - Good
- CHDSK /f - no problems on any hard drive
- ran Passmark BurnInTest multiple times no errors or freezing during test
- ran Passmark Benchmark no problems

I am currently using the PC now however i dunno when its next going to freeze, the only odd thing that i have noticed is when the PC is forcefully shutdown the bios says "Overclocking failed" even though no overclocking is applied at this time. Any thoughts or ideas that could solve this i would greatly appreciate it as i have a lot of university work for my masters to do before Christmas and i cant keep loosing reports all the time even though i am saving after every sentence, and more importantly i want to find out why its doing this.


Level 13
Hi wolfgang959 and Welcome to ROG

Well you have indeed been pretty thorough in assessing the problem. Only thing I can think of is to clear your CMOS to default or flash your Bios to latest 0701 or Beta version for IM support, (if you haven't already) and see how you go.
Use a USB stick and utilize the Flashback port on your IO panel.
If not sure how to go about this, I can help guide you, for best and safest method.

We owe our existence to the scum of the earth, Cyanobacteria

My System Specs:

MB:ASUS ROG Crosshair VII Hero/WiFi GPU:EVGA GTX 1080 sc PSU:Corsair AX-1200i
AMD R7 2700X Cooler: Corsair Hydro H115i Case: Corsair Carbide 780t

Memory:G.Skill TridentZ F4-3200C14D-16GTZR SSD:Samsung 500GB 960 EVO M.2


Level 10
Before you clear the CMOS, try to unplug your power supply for at least 10 seconds. See if that helps.

Rampage IV Extreme BIOS 4206
Intel I7-3820
32 GB Quad Channel Kingston Hyper X Genesis
2 x Nvidia GTX 690
2 x WD Velociraptor 250 GB RAID0
Intel 120GB 320 SSD
Noctua NH-D14 SE2011
CM Silent Pro Hybrid - 1300W

Level 7
Hi all sorry for the late reply been extremely busy and didn't get an email though that there were replies even though i subscribed to the thread. anyways, things have been going okay so far, but there's still something not quiet right though. I did unplugging power supply for a few hours whilst i was at uni and after that i cleared the CMOS at next boot.

I installed the beta BIOS 0801 yesterday and nothing much has changed in terms of that from the 0701 to this one, i have only had one freeze like before but normal crashing with BSOD has started happening i think this may be related to the drivers because when i was going through driver settings it BSOD twice, and then mobo stated that overclocking failed and to press f1 to set it up again.

Although installing the BIOS took some time because a) the bios flashback didn't want to work at all started flashing green once released flashed a few more times and stopped, b) the EZ Flash 2 didnt want to see the file even though it was named correctly and in right place after a few restarts decided to work.