Computer freezes, nothing in logs

[Johan_V]

I have a strange problem with my linux computer. During heavy computation, computer sometimes freezes totally.
The most peculiar symptom is that during halt, the computer is slow to respond to the reset button (the actual separate reset pin on the motherboard, not the power button). To recap,

1) Total system halt, but picture still on screen.
2) Nothing unordinary in the logs.
3) Totally random halt, appears during heavy( 100% utilization all cores) computation but not often
4) Reset button working with a few seconds lag

My question is, does the badly functioning reset button point to power supply fault, or could these problems be caused by something else?

Hardware: i7 4770k, Asus p87-pro, gtx titan and Corsair hx 650 power supply.

 

[Bardock]

Do a memory test, usually located in BIOS. I bet something fried.

 

[denis280]

Hardware: i7 4770k, Asus p87-pro, gtx titan and Corsair hx 650 power supply.

what are the all the system spec.specially hdd.

 

[sm625]

Can you force your clock speed to a significantly lower value? That might tell you something if it doesnt freeze at the slower clocks.

As for the reset button lag, that could just be a byproduct of it being frozen inside some kind of hardware interrupt state. I'm not exactly sure how the reset gets handled, but I dont think it goes directly into the power supply. I think it goes through the bios which puts it at the mercy of any sort of lockup. There is probably some sort of watchdog timer on the reset line which allows it to eventually function even in a locked up state.

 

[Smoove910]

are you overclocking?

 

[Johan_V]

Thank you for suggestions. Memory seems fine, at least after a few hours testing. I will run more extensive tests when I get back.
Computer is running at stock freq. There has been three freezes in two week period, so debugging is a bit frustating. Each computation run takes a couple of hours, so a freeze won't cause significant losses, but it is annoying.
I just noticed from the logs that at least two freezes apparently happened after resuming from S3 sleep (but not immediately) so it could actually be a some kind glitch in hardware caused by the S3 state.

 

[phis6]

You might try disabling the Intel C State option in your BIOS if it has that option.

 

[NewYorksFinest]

Either you are Overclocking or your PSU died. But what else is in the computer? But what is your ram type? Is it the cheapest, shittiest kind around? I am making an assumption that is what happened.

 

[Smoove910]

if you are running 1600mhz ram, what voltage are you running at? I believe it'll default to 1.5v, but alot of 1600mhz ram requires 1.65v (since it's essentially overclocked ddr800 stuff).

Worth a shot!

 

[Johan_V]

Update: There have not been any freezes in four days, so it appears that the freezes are connected to S3 sleep. Probably some buggy firmware/driver cannot handle resume correctly and locks up randomly after some time.