Recall, we are pushing above the vendor's rated specs here. And as such, one shouldn't judge the platform for stability.

-- Craig

[QUOTE=nucleon;356916]Recall, we are pushing above the vendor's rated specs here. And as such, one shouldn't judge the platform for stability.[/QUOTE]
I wonder if people with stock cooler can run Linpack or latest Prime95 without the CPU throttling down. I bet they can't. Of course it could be argued it's not a stability issue, but given how Haswell behaves, I have decided not to OC it and regret to have picked a castrated 4770K instead of a 4770 or a 4771.

IVR + AVX + OC'd mem + highly optimized code, sends the temp thru the roof.

Running any other code is fine.

I pulled the CPU out again, looked at removing the locking mech, but need star screwdriver. Going to have to find one.

Gave me a chance to redo the paste. Not much difference, except core #2 is now the hottest, previously it was core #0. :)

-- Craig

[QUOTE=nucleon;356938]IVR + AVX + OC'd mem + highly optimized code, sends the temp thru the roof.[/QUOTE]

My Haswells (4GHz, DDR3-2400) are running in the mid-70s and mid-80s doing normal LL testing. I doubt temps are the source of my crash-once-every-few-days instability.

[QUOTE=Prime95;356946]My Haswells (4GHz, DDR3-2400) are running in the mid-70s and mid-80s doing normal LL testing. I doubt temps are the source of my crash-once-every-few-days instability.[/QUOTE]

Ah, you have that too? I was assuming that it was a driver issue, to be expected from running a Linux distribution older than the CPU, and would magically fix itself when I went to Ubuntu-13.10.

I'm running Kubuntu 13.04 on a Haswell 3770 at stock clocks without issue (Hyper 212 Evo keeping it < 86°C).

[QUOTE=fivemack;356965]Ah, you have that too? I was assuming that it was a driver issue, to be expected from running a Linux distribution.[/QUOTE]

Crap. I was going to try running Linux to see if my problem was a Windows-only issue.

[QUOTE=Prime95;356946]My Haswells (4GHz, DDR3-2400) are running in the mid-70s and mid-80s doing normal LL testing. I doubt temps are the source of my crash-once-every-few-days instability.[/QUOTE]

Is this running v27 or 28? Tried reverting the CPU to stock speed? [I realize that would be annoying, after your time+money investment in high-end cooling.]

[QUOTE=ewmayer;356987]Is this running v27 or 28? Tried reverting the CPU to stock speed? [I realize that would be annoying, after your time+money investment in high-end cooling.][/QUOTE]

Running v28. I'm slowly increasing voltage to see if the problem goes away. It is a very slow process as it can take 3+ days before you realize that didn't solve the problem.

[QUOTE=Prime95;356946]My Haswells (4GHz, DDR3-2400) are running in the mid-70s and mid-80s doing normal LL testing. I doubt temps are the source of my crash-once-every-few-days instability.[/QUOTE]

Cool. My thinking is that if there was a invalid voltage - you'd be hitting that with invalid results rather than system reboot.

System reboots generally occur when all the auto-down clocking/voltages are turned off and it's the last course of action for the CPU to save itself.

If it isn't temperature, than it could be the power/amps failsafes.

There's an option in the bios to modify the allowed power/amps to the CPU. By default it's 84W/95amps.

Why it happens every few days - it's probably due to the probability of hitting high usage stuff all at once. All 4 cores sync with high power consumption at same time - then boom, reboot.

-- Craig

[QUOTE=nucleon;357010]
There's an option in the bios to modify the allowed power/amps to the CPU. By default it's 84W/95amps.

Why it happens every few days - it's probably due to the probability of hitting high usage stuff all at once. All 4 cores sync with high power consumption at same time - then boom, reboot.[/QUOTE]

I'm running at ~120W, so I suspect the power/amps failsafes are disabled.
If it were a high power spike problem, then the voltage increases I've been applying the last few weeks would be making the problem worse.

Can memory timings or overheating cause a kernel panic? Any other ideas as to the cause?