Rampage IV Extreme - Intermittent Shutdown Problems

[mikeblunt2020]

Hi all, I was wondering if you could offer me any insight. I just recently obtained a R4E board. I'm running a 3960X @ 4.7 on it, with some slight adjustments to VCore, VCCSA, clockgen filter, etc. All the standard tweaks that most people seem to be making on this board.

The system is rock solid stable with one exception. Intermittently, it fails to shudown gracefully (it effectively hangs at a black screen without actually powering down). After this occurs, when it comes back up it gives the "overclocking failed" message. Note that this does not always happen, as it frequently shuts down properly. It seems to happen more frequently when I bring the system up from sleep mode and then power it down quickly thereafter. Also note that the system always goes to sleep and wakes up properly - the intermittent shutdown hang is the only problem I am currently experiencing.

Has anyone else experienced anything similar? Any suggested tweaks that I can make?

I should note that I do have all the CPU power saving options on (speedstep, C1E) and would prefer to leave them on if I can find a solution that enables me to.

Thanks for your assistance.

[mikeblunt2020]

Turbo Mode is set to By All Cores (set in BIOS)

[HiVizMan]

OK I am stumped as to why your system is getting so hot (or at least being reported as so hot) when waking.

Things we have checked and know.

Your CPU is cool when asleep
Your cooler fans spin up when you wake
Your system feels cool to the touch when you wake
The system reports high heat

I am starting to think that the system readings are incorrect.

[Arne_Saknussemm]

Could this be an SSD waking from sleep issue?

[HiVizMan]

Arne I would welcome any ideas or thoughts right now mate, would you like to expand a bit more about the wake SSD side of things please. 🙂

[Arne_Saknussemm]

HiVizMan wrote:
expand a bit more about the wake SSD side of things please. 🙂

It was just a thought. The OP didn't put up system specs so I have no idea if he even has an SSD.....it's just I know that there are quite a few problems with Sandforce controllers hanging and not liking sleep states etc. My vertex 3s only stopped this kind of thing after the latest firmware update. I've seen people fixing Sandforce drives hanging up with Intel drivers (RST and RSTe) by doing everything from disabling sleep to registry edits to enabling hot-plugging in the BIOS....

The temperature thing is odd. But looking round a few other threads people are having similar problems and those cases are pointing to memory...so i don't mean to draw attention entirely from that.

[HiVizMan]

Like I said I am getting to the point where I just don't know what to do next. So anything constructive I will like to give a try to. Let me speak to Praz he has heaps of experience with SSD's and if anyone would know he is the man.

[mikeblunt2020]

The 91C readings definitely are incorrect. I am using two SSDs: an Intel 520 240GB and a Samsung 830 256GB. I installed the Samsung at a later date and I believe the problem was happening with only the Intel in the system. Both are running the latest firmware.

I see other posts around (on this and other forums) with people complaining of waking from sleep with all core temps reading 91C and CPU multiplier locked at 12x, but I can't seem to find anyone who says they have definitively solved the issue.

At this point, I'm not quite sure what to do next.

[mdzcpa]

Just for giggles, go into your control panel, Power Options, select Balanced Change Plan Settings, then choose Set Default Settings for This Plan. Leave your power plan on Balanced and reboot. See if that helps.

Make sure you leave all your C States in the BIOS as you want them (enabled) before doing this.

[mikeblunt2020]

Just tried that. No luck. Followed the instructions above, rebooted, initiated sleep mode, woke back up, and all cores reporting 91C. CPU multiplier also locked at 12x (even under load).

[Shamino]

try this bios
http://www.datafilehost.com/download-31bc4f1a.html
manually set clockgen filter to disabled (as opposed to auto)