Constant Restarts X670E

[Anthony_Kinson]

I know a few other people have mentioned this in various threads, and I can't for the life of me find a solution in the forums. I have the CROSSHAIR x670E Hero board and I am constantly being hard reset randomly throughout the day.

It's become unbearable, 6 hours into my work day and I have 32 hard restarts while I'm working, not even putting the system under any heavy load. It will restart while in chrome or while writing code in VSCode, if I leave the PC on the windows login screen it will hard restart after a few minutes of just sitting on the login screen.

I get the "early adopter" thing, but this board cost almost as much as a 7950X and I kind of expect a high-end product to work out of the box. i have no overclocks, i even have EXPO disabled and run everything at stock, and still issues. I'm running the latest 0750 bios (i couldn't even get into Windows with earlier bios versions that shipped!)

Weirdly, if I fire up a game, the hard resets don't seem to occur, putting the system under load seems to stabilize it to some degree. I've been using these crosshair boards since the 1800X CPU and never had these kinds of problems and I'm out of ideas on how to get this thing stable enough to work.

It's really disheartening when you spend thousands of £'s on a system upgrade for it to be so much worse than your old machine.

If anyone else has experienced this and found a fix I'd love to hear your solutions.

my pc info should be in my profile, but i'm running the 7950X, RTX 4090 and 64GB DDR5 (2x 32GB) @ 5200 (although recently disabled EXPO)

UPDATE: If you're having this issue I found setting the windows power plan to "High Performance" prevented the random restarts. It's not a "fix" but it should at least stop the reset until a proper fix is implemented.

[MikeAce420]

Day 2 and no resets when idle. For me the fix was setting the power plan to performance. In addition, I optimized the PBO and am sitting comfortably with a negative 30 on a 7700x. I also set the thermal cap at 85C. Again the issue I was having was not BSOD's, but instead the system was doing random hard resets with no errors being reported when the system was idle. I have no idea why changing the power plan to performance would make a difference compared to the balanced or Ryzen balanced plan. The only significant difference I could see on the Ryzen plan was the minimum processor state was 90% vs the normal balanced and performance plans are set at 0%. The weird thing is that I still had the issue on the normal balanced plan as well.

[Anthony_Kinson]

MikeAce420 wrote:
Day 2 and no resets when idle. For me the fix was setting the power plan to performance. In addition, I optimized the PBO and am sitting comfortably with a negative 30 on a 7700x. I also set the thermal cap at 85C. Again the issue I was having was not BSOD's, but instead the system was doing random hard resets with no errors being reported when the system was idle. I have no idea why changing the power plan to performance would make a difference compared to the balanced or Ryzen balanced plan. The only significant difference I could see on the Ryzen plan was the minimum processor state was 90% vs the normal balanced and performance plans are set at 0%. The weird thing is that I still had the issue on the normal balanced plan as well.

Glad that worked for you. Yeah, it's a weird one for sure. Hopefully, somebody can figure it out and a bios update will resolve it.

[fredepf]

I get the same problem whit my X670E Hero + 7950X .
Each time it's Hard reboot + QCODE 00 . I have to shut down the PSU because nothing work .
I somebody find the way to fix this it would be very appreciate .

[validusername]

fredepf wrote:
I get the same problem whit my X670E Hero + 7950X .
Each time it's Hard reboot + QCODE 00 . I have to shut down the PSU because nothing work .
I somebody find the way to fix this it would be very appreciate .

I've been having the same issue, the only solution I've found is setting the performance power profile in Windows, then editing it to set the 'Minimum Processor State' to 100%.

[planetbeing]

Random reboots are probably overly optimistic Curve Optimizer settings. It's very hard to suss those out because a lot of work-loads (particularly all-core ones) do not actually exercise those settings effectively. I tried all the Windows settings and such in the past and that didn't really help for me.

I recommend using OCCT with AVX2 (not AVX512 or anything else), Small, Extreme, exercising both Virtual and Physical cores, selecting cores 0 and 1 initially, and cycling the cores every 10 seconds. You should see random reboots and/or BSODs if your settings aren't stable. You want enough cores to be exercised simultaneously to generate heat, but not enough for the CPU to reach 95 degrees and the frequency starts being limited by thermals, or enough power draw for the CPU to switch to the all core OC mode, which won't strain some individual cores enough. Small AVX2 is the toughest single core test OCCT has to offer. That sussed out a lot of the "idle" reboot issues for me.

If you're posting about random reboots, you should share any BIOS settings you modified from stock along with your report, including automatic overclocking, PBO settings, RAM settings, etc.

[zoobzone]

planetbeing wrote:
Random reboots are probably overly optimistic Curve Optimizer settings. It's very hard to suss those out because a lot of work-loads (particularly all-core ones) do not actually exercise those settings effectively. I tried all the Windows settings and such in the past and that didn't really help for me.

I recommend using OCCT with AVX2 (not AVX512 or anything else), Small, Extreme, exercising both Virtual and Physical cores, selecting cores 0 and 1 initially, and cycling the cores every 10 seconds. You should see random reboots and/or BSODs if your settings aren't stable. You want enough cores to be exercised simultaneously to generate heat, but not enough for the CPU to reach 95 degrees and the frequency starts being limited by thermals, or enough power draw for the CPU to switch to the all core OC mode, which won't strain some individual cores enough. Small AVX2 is the toughest single core test OCCT has to offer. That sussed out a lot of the "idle" reboot issues for me.

If you're posting about random reboots, you should share any BIOS settings you modified from stock along with your report, including automatic overclocking, PBO settings, RAM settings, etc.

I use PBO with negative voltage curve 20 magnitutde on my 7700X and a +200MHz offset. The temperatures are fine while gaming on load its usually at 60-70s. Sometimes I even crash on desktop doing nothing. I have also tried reverting everything back to stock it doesn't seem to help either.

The error message I get from eventviewer is "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

[planetbeing]

zoobzone wrote:
I use PBO with negative voltage curve 20 magnitutde on my 7700X and a +200MHz offset. The temperatures are fine while gaming on load its usually at 60-70s. Sometimes I even crash on desktop doing nothing. I have also tried reverting everything back to stock it doesn't seem to help either.

The error message I get from eventviewer is "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

Yeah, that's what happens to me when my overclock isn't stable as well. The system just reboots all of a sudden with no BSOD and that message appears in the Event Viewer. Those kinds of random reboots while idle stopped happening to me after I dialed in my CO offsets.

It's strange that it happens to you even with completely stock settings. I hate to say it, but are you absolutely sure that they happen to you on stock? That means no DOCP/EXPO and no even auto overclocking? Even then, I still would do what I recommended with OCCT. You get more BSODs with more information that way and it can maybe help you find the problematic cores and perhaps even add a positive CO offset for them.

[zoobzone]

planetbeing wrote:
Yeah, that's what happens to me when my overclock isn't stable as well. The system just reboots all of a sudden with no BSOD and that message appears in the Event Viewer. Those kinds of random reboots while idle stopped happening to me after I dialed in my CO offsets.

It's strange that it happens to you even with completely stock settings. I hate to say it, but are you absolutely sure that they happen to you on stock? That means no DOCP/EXPO and no even auto overclocking? Even then, I still would do what I recommended with OCCT. You get more BSODs with more information that way and it can maybe help you find the problematic cores and perhaps even add a positive CO offset for them.

Those errors were with +200 frequency offset and -20 curve. I did 0 frequency offset (stock frequency) and -18 frequency and no longer have any error messages in OCCT. Although I've only ran it for around 50 minutes before I had to leave for work.

I run DOCP with 6000MHz, CL30-36-36-39 (those were the DOCP settings for my ram)

I would've expected to get BSOD/hard lockup or some other error message if it was due to frequency instabilities (thats my experience on Intel platforms), this is new to me.

[kempa]

I also have irregular reboots with my Asus B650E-F, in combination with 32GB Skill Ram (EXPO) and a 7600x.
I had EXPO II loaded all the time (UCLK=MEMCLK) and the PBO Level 1 profile. Ran so actually quite stable, however, I have since about a week in the middle of the game reboots without warning.
I will now try it without PBO, which I actually do not want (the temperatures with PBO Level 1 were much better). If this doesn't help, I will try it without the EXPO-Profile.

[Maikal]

The only time I've had this is when I enabled the medium load boost. Any time that the machine was idle for a period and I went to say open a browser it would reset. I've replicated this multiple times on my personal machine and across multiple bios versions. However, for me this wasn't happening as often as others have mentioned.