F5F Stay Refreshed Hardware Desktop Power surge causing immediate shutdown without blue screen.

Power surge causing immediate shutdown without blue screen.

Power surge causing immediate shutdown without blue screen.

M
mennogerben
Member
199
05-02-2020, 02:15 PM
#1
Hello everyone, here’s what I’ve tried so far. About a month ago I upgraded my CPU to a 5900X and since then I’ve experienced frequent hard power resets and Event IDs 18 and 41. (Attached screenshot) Adding a positive offset of 2 to the curve optimizer didn’t help much, though it reduced crashes somewhat. Just before my vacation, I upgraded to a 1000W EVGA PSU, a 360mm Corsair AIO, and a new 5000T case. After finishing the rebuild, all cables were properly seated and I added an extra 4 PIN CPU cable with this PSU for more power. I undervolted by a factor of 10 yesterday just to test the situation, but crashes continued. I reverted the undervolt to a positive 3 in the curve optimizer. Despite all this investment, I’m still facing hard power crashes with the same Event IDs. I’m unsure what to do next. Any advice would be greatly appreciated—I’d rather not lose my computer again but am open to suggestions.
M
mennogerben
05-02-2020, 02:15 PM #1

Hello everyone, here’s what I’ve tried so far. About a month ago I upgraded my CPU to a 5900X and since then I’ve experienced frequent hard power resets and Event IDs 18 and 41. (Attached screenshot) Adding a positive offset of 2 to the curve optimizer didn’t help much, though it reduced crashes somewhat. Just before my vacation, I upgraded to a 1000W EVGA PSU, a 360mm Corsair AIO, and a new 5000T case. After finishing the rebuild, all cables were properly seated and I added an extra 4 PIN CPU cable with this PSU for more power. I undervolted by a factor of 10 yesterday just to test the situation, but crashes continued. I reverted the undervolt to a positive 3 in the curve optimizer. Despite all this investment, I’m still facing hard power crashes with the same Event IDs. I’m unsure what to do next. Any advice would be greatly appreciated—I’d rather not lose my computer again but am open to suggestions.

R
Rakedge
Member
227
05-24-2020, 01:07 AM
#2
Disable global state management as well.
R
Rakedge
05-24-2020, 01:07 AM #2

Disable global state management as well.

C
CPaul
Junior Member
14
05-24-2020, 06:02 AM
#3
Check the BIOS settings or use Ryzen Master to locate the information.
C
CPaul
05-24-2020, 06:02 AM #3

Check the BIOS settings or use Ryzen Master to locate the information.

A
awesomness44
Junior Member
8
05-24-2020, 07:11 AM
#4
BIOS
A
awesomness44
05-24-2020, 07:11 AM #4

BIOS

K
Kuji
Member
133
05-24-2020, 07:20 AM
#5
Recorded in low light, my 5900X sometimes crashed randomly when the screen was blank. It took a while to determine the issue was a DRAM problem—turns out the RAM model wasn’t listed in the QVL for my board. Since it’s only been a few days since installation, it’s still early to say it’s fixed. I added RAM that matches the QVL and has the same timing as the old setup, and it hasn’t caused blank screens anymore. It even runs faster now. First thing to check is your RAM SKU against the QVL for Vermeer processors. Also worth noting is a trend of people reporting crashes with Corsair RAM paired with Ryzens—could be a specific kit or model, or maybe the QVL list affected it. Updated August 22, 2022 by An0maly_76 Added more details
K
Kuji
05-24-2020, 07:20 AM #5

Recorded in low light, my 5900X sometimes crashed randomly when the screen was blank. It took a while to determine the issue was a DRAM problem—turns out the RAM model wasn’t listed in the QVL for my board. Since it’s only been a few days since installation, it’s still early to say it’s fixed. I added RAM that matches the QVL and has the same timing as the old setup, and it hasn’t caused blank screens anymore. It even runs faster now. First thing to check is your RAM SKU against the QVL for Vermeer processors. Also worth noting is a trend of people reporting crashes with Corsair RAM paired with Ryzens—could be a specific kit or model, or maybe the QVL list affected it. Updated August 22, 2022 by An0maly_76 Added more details