Overclock.net banner

Random hard crash

529 views 11 replies 3 participants last post by  Thiefofspades 
#1 · (Edited)
Desktop.zip 1571k .zip file
Happened once when i wasn't in the room, and once while i was looking at twin turbos on youtube. Crashes with a blue screen for .5 seconds then shuts off and powers back on.

· Windows 7
· x64
· Windows 7
· Had a friend install os for me at his work.
· Less than a year old
· Have not re installed before.

· i5-2500k
· Evga Gtx 680 4gb
· Gigabyte G1. Sniper M3
· Seasonic X-series 1050w
 
#3 ·
Quote:
Originally Posted by ripsaw View Post

Need more info
Download this, http://www.nirsoft.net/utils/blue_screen_view.html
Google error code(s)
and/or post here
He's attached the needed information already (which, if you bothered to look, contains A LOT of info, around 100x more than BlueScreenView, which is not useful).
smile.gif


@OP I'll take a look at your files
smile.gif


--

OK your BSODs are mostly 0x124 (there was one that was 0xF4 - but we'll treat that as a red herring for now). 0x124 are of type WHEA_UNCORRECTABLE_ERROR and are always a hardware fault. Though in your scenario, it appears as if you are overclocking and so I would advise to revert to stock for the time being to diagnose the issue, or increase vcore (a common solution for 0x124 BSODs).
 
#5 ·
Quote:
Originally Posted by Thiefofspades View Post

I reset bios to defaults for now. It was worse when i was using the nvidia 313.96 beta driver. I'm thinking its the ram because its supposed to be 1.35v and i got it stable at 1.54v. Lots of stop blue screens with those drivers.
Just drop your ram back to defaults, or set to 1866, mine is rock solid stable at 1866 @ 1.35v, although it should handle 1.54v as well.....

Quote:
Originally Posted by tompsonn View Post

He's attached the needed information already (which, if you bothered to look, contains A LOT of info, around 100x more than BlueScreenView, which is not useful).
smile.gif
Thanks didn't see that
thumb.gif


100x more useful than not useful is still useless.....100000000000000000000000000000000000000000000000000000000000001 x 0 = 0
tongue.gif
 
#6 ·
Quote:
Originally Posted by ripsaw View Post

Just drop your ram back to defaults, or set to 1866, mine is rock solid stable at 1866 @ 1.35v, although it should handle 1.54v as well.....

Thanks didn't see that
thumb.gif


100x more useful than not useful is still useless.....100000000000000000000000000000000000000000000000000000000000001 x 0 = 0
tongue.gif
LOL good catch!
 
#8 ·
Quote:
Originally Posted by Thiefofspades View Post

Think its just vcore? Windows seems to jump my vcore almost .200v higher than what i set it at.
.2v higher? thats a huge jump.
What is your vcore at? Personally, i would go to bios, save all your settings for now, then revert back to stock
Quote:
Originally Posted by tompsonn View Post

OK your BSODs are mostly 0x124 (there was one that was 0xF4 - but we'll treat that as a red herring for now). 0x124 are of type WHEA_UNCORRECTABLE_ERROR and are always a hardware fault. Though in your scenario, it appears as if you are overclocking and so I would advise to revert to stock for the time being to diagnose the issue, or increase vcore (a common solution for 0x124 BSODs).
 
#11 ·
Quote:
Originally Posted by Thiefofspades View Post

I have it set to 1.295v now for 4.4ghz and under load it likes to go 1.44v with intel burn test using hwinfo to monitor.
Quote:
Originally Posted by ripsaw View Post

thats fubar. Some setting in bios is doing this, perhaps Load Line Calibration or something similar.
I've got a pretty crappy 3770k, and it ONLY wants 1.36v for 4.5ghz....
rolleyes.gif
Yeah what's your LLC setting? vdroop should be going the other way (i.e. down), so that's pretty weird...
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top