Need help with computer randomly crashing

Toggle sidebar Toggle sidebar
C

ClutchAutomatic

Member
Nov 14, 2013
37
0
0
Computer specs
CPU: Intel i7 3930k at 4.5 @ 1.325
Motherboard: ASUS Rampage IV Gene
Ram: 16 GB CORSAIR Vengeance Pro @ 1600mhz
Graphics Card: MSI GTX 780 Lighting
Hard Drive :2 Samsung 840 Pro 256 in Raid 0 and 3TB Seagate Barracuda
Power Supply: Corsair AX 860i Modular
Case: Corsair 350D
Case Fans: Noctua NF-S12A PWM Exhaust fan and 2 Noctua NF-A14 PWM Intake fans
CPU cooling: Corsair H100i with 2 Noctua NF-F12 PWM fans
OS: Windows 8.1 Pro 64 bit

Every once in a while my computer will crash either if I am browsing the internet or playing a game. When it crashes, it shuts off and then tries to reboot then after 2 seconds it cuts off, then tries again. It goes in an endless cycle until I turn off the psu switch and let it cool off a few minutes and clear cmos. Then I turn it back on and load bios profile and it is good to go.

I thought it was the graphics card but I changed to a new one and then I thought it was the overclock so I ran it at default and these events started to occur again. I cleaned up and rewired the cables and it ran fine, didn't have any crashes so I was thinking maybe there was a short in the wires somewhere.

Next I changed out all the fans and used the resistor to quiet up the fans even on the h100i. I am not using corsair link because it isn't really compatible with windows 8.1 yet. But just now I was in Diablo 3 for about 4 minutes I saw a little bit of smoothness issues about 3 seconds before it crashed again. I took the side panel off and turned off the psu switch and then back on. I was still getting the crash before post. I waited another 2 minutes with the psu switch off and tried it again. I was able to get into bios and reload my profile.

Do I have bad ram, a faulty psu or motherboard?
The bios default runs the ram at 1333mhz and cpu at 3.8 and I was still getting those random crashes. On the overclock profile I have the ram at the correct timings and rated speed.
 
C

ClutchAutomatic

Member
Nov 14, 2013
37
0
0
Yeah after it crashed, the psu did feel warm. Do you think I need to RMA the ax860i?
I also unplugged the psu cables and ran the self test and it was fine.
 
Last edited:
Virgorising

Virgorising

Diamond Member
Apr 9, 2013
4,470
0
0
ClutchAutomatic said:
Yeah after it crashed, the psu did feel warm. Do you think I need to RMA the ax860i?
I also unplugged the psu cables and ran the self test and it was fine.
Click to expand...

I am not qualified to answer that, but one of the real geniuses here will soon arrive and help you decide.:)

But really good you at least have the RMA option.:thumbsup:
 
Ketchup

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
Run a temp-monitoring program and give us your temps under load. Wouldn't be a bad idea to use one that monitors voltages as well. I would be really interested in seeing each core and video card temp under load.
 
C

ClutchAutomatic

Member
Nov 14, 2013
37
0
0
I just ran sleeping dogs for over an hour straight max gpu temp was 73, memory max at 64 and vram at 68 degrees, gpu usage hit 99%, power was 94%, did see a cpu 3 @ 100% at 58 degrees.
 
B

Boondox

Member
Nov 14, 2013
46
0
0
Back off the overclocking and see if the stability improves.

Edit: I see that you ran at stock settings as well, but it looks like the Rampage isn't picking up the XMP profiles on the Corsair Vengeance modules. What BIOS version are you using at the moment?

And according to this link at Asus ROG Forums: http://rog.asus.com/forum/showthread.php?25510-Rampage-IV-Extreme-RAM-Guide - It appears that the Vengeance modules are causing a lot of issues with the Rampage IV. I can't say for certain if it's a problem with the X79 chipset itself or the Rampage IV.
 
Last edited:
Ketchup

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
Temps look good. If you backoff the overclock and the problems persist, it sounds like a power suppy problem.

Edit: the power supply looks more than adequate, and Corsair is a good brand, but that doesn't mean that every one that comes out of the factory is perfect.
 
Last edited:
C

ClutchAutomatic

Member
Nov 14, 2013
37
0
0
Boondox said:
Back off the overclocking and see if the stability improves.

Edit: I see that you ran at stock settings as well, but it looks like the Rampage isn't picking up the XMP profiles on the Corsair Vengeance modules. What BIOS version are you using at the moment?

And according to this link at Asus ROG Forums: http://rog.asus.com/forum/showthread.php?25510-Rampage-IV-Extreme-RAM-Guide - It appears that the Vengeance modules are causing a lot of issues with the Rampage IV. I can't say for certain if it's a problem with the X79 chipset itself or the Rampage IV.
Click to expand...

I am running the latest bios, just built this about 2 weeks ago. That is really disappointing to hear about the vengeance ram granted this is the new pro series.
 
Ketchup

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
ClutchAutomatic said:
I just ran sleeping dogs for over an hour straight max gpu temp was 73, memory max at 64 and vram at 68 degrees, gpu usage hit 99%, power was 94%, did see a cpu 3 @ 100% at 58 degrees.
Click to expand...

Hey ClutchAutomatic, where did you get your memory temps? I assume that is the 64, but the software I am using won't tell me which readings those are (I am looking at CPUID Hardware Monitor and HWiNFO64). Could be my system just doesn't have the needed sensor for it.

Also, do you ever get a blue screen, or does the screen just go blank?
 
Last edited:
Ketchup

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
B

Boondox

Member
Nov 14, 2013
46
0
0
http://rog.asus.com/forum/search.php?searchid=2412495

That's pretty much what turns up when you go to search for Corsair Vengeance. Problems are based on BSOD, unable to boot, etc. The OP is experiencing a no-boot issue until he clears the CMOS, so that could be the issue. I haven't played with Corsair RAM since the DDR1 days (come to avoid their QC mishaps), so I can't say for certain.
 
C

ClutchAutomatic

Member
Nov 14, 2013
37
0
0
ketchup79 said:
Hey ClutchAutomatic, where did you get your memory temps? I assume that is the 64, but the software I am using won't tell me which readings those are (I am looking at CPUID Hardware Monitor and HWiNFO64). Could be my system just doesn't have the needed sensor for it.

Also, do you ever get a blue screen, or does the screen just go blank?
Click to expand...

I use MSI Afterburner, This is my overclock settings

I am not getting any BSOD recently from this issue, but I did before I had the overclock settings just right. The X.M.P. mode wasn't very friendly with my ram.

Since the first post my computer hasn't crashed yet, it's been on the whole time. I played another 40 minutes of sleeping dogs and it was fine.
 
Last edited:
C

ClutchAutomatic

Member
Nov 14, 2013
37
0
0
This morning it crashed but I don't know what the fault was. I left the computer running ever since the first post. And I went to check on it today and the computer was off. I hit the power button and it clicked off after 2 seconds then came back about 5 seconds later and booted normally.
 
Virgorising

Virgorising

Diamond Member
Apr 9, 2013
4,470
0
0
ClutchAutomatic said:
This morning it crashed but I don't know what the fault was. I left the computer running ever since the first post. And I went to check on it today and the computer was off. I hit the power button and it clicked off after 2 seconds then came back about 5 seconds later and booted normally.
Click to expand...

Sorry it happened again. If I might ask: why do U leave the system on 24/7?

What is the upside of that?

Again, feels as if this might be shutdowns when the system overheats. If so, they are GOOD and protective. Tho it's also not happening under load, it's happening at idle.

Goal is to determine if it is overheating and what is causing it?

Are yr fans working normally? I think you said you already went there.

Did you, as Ketchup79 suggested unhook one of yr SSDs?
 
Ketchup

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
That latest incident sounds like a BIOS setting that the system isn't happy with.
 
C

ClutchAutomatic

Member
Nov 14, 2013
37
0
0
The ssd is running in raid 0 so I cannot unplug one of them. Also the computer crashed at idle 5 minutes after I posted. So the computer was maybe running less than 10 minutes. All my noctua fans are working properly. I am trying to see if I can boot it without clearing cmos. Right now it keeps cutting out after I try to boot it.
 
Virgorising

Virgorising

Diamond Member
Apr 9, 2013
4,470
0
0
ClutchAutomatic said:
The ssd is running in raid 0 so I cannot unplug one of them. Also the computer crashed at idle 5 minutes after I posted. So the computer was maybe running less than 10 minutes. All my noctua fans are working properly. I am trying to see if I can boot it without clearing cmos. Right now it keeps cutting out after I try to boot it.
Click to expand...

O! I din know you had RAID setup. Would U be willing to, however briefly, change that to test the system with one SDD removed?

I think, at this point, I would. This is a new and uber build, after all! If, as Ketchup79 just suggested it might B, it's not a bios issue (might be if he said), we may still be left with overload/heat, and that system don deserve to put up with that. U don't want any hardware damaged.

I wouldn't regard the shutdowns as the problem, but rather, maybe something being triggered normally to protect yr hardware. Could still be that way impressive to me, PSU.
 
Last edited:
Virgorising

Virgorising

Diamond Member
Apr 9, 2013
4,470
0
0
ketchup79 said:
How far are we getting?
Click to expand...


Yes, frustrating!:| U think he should undo his RAID setup and pull one of the SDDs as U suggested?

I don't know enuff to know how to do that without his loosing data, given, system the two SDDs both drives as one drive.

I dunno, maybe use an external drive to clone them to? This is over my head, so form ow on I will be watching the progress.

One more: how about unhooking the Seagate from the PSU and seeing if that makes a difference? I mean, no harm, right?
 
Last edited:
C

ClutchAutomatic

Member
Nov 14, 2013
37
0
0
I am at the same 2 seconds of power then cut off and wait 5 seconds for it to try again. I cleared cmos three times and let the psu switch stay off for some time between each session. So I don't think it could be ssd if it won't even let me into bios.
 
Ketchup

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
Ah, so we are not even getting into the BIOS.

Probably time to start unplugging anything that isn't necessary to get your into the BIOS: hard drives (SSD and spinners), CD drives, anything USB except the keyboard, perhaps even going down to one stick or RAM.

So if it you get it down to where it will let you access the BIOS, hopefully you can add items and see what the culprit is.
 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom