cancel
Showing results for 
Search instead for 
Did you mean: 

Processors

CrispyCrunch
Adept II

Re: Ryzen 5900x: System constantly crashing/restarting WHEA-Logger ID 18 and critical error Kernel-P

Jump to solution

@nsargentum wrote:

I'm having the exact same issue on a 5600x with a msi tomahawk b550. I have a x570 gigabyte aorus master and a r9 3900x I was thinking of swapping this CPU with that and testing there.

OK; Get ready for this, Here's everything I've done so far to eliminate variables:

  1. Swapped the system drive (nvme) and reinstalled windows from scratch
  2. Unplugged all other drives
  3. Swapped GPUs
  4. Swapped PSU
  5. Swapped memory from 3200Mhz Gskill TridentZ CL16 to 2667Mhz CL16 Corsair Vengeance
  6. Swapped the Msi Tomahawk B550 with another MSI tomahawk B550 to verify it wasn't the board.

Ensured I'm on the latest bios for the MOBO and the previous 1 which was also post Ryzen 5000 release.

 
7C91vA51(Beta version)
Release Date
2020-11-16
 
Description
- Support AMD SAM(SMART ACCESS MEMORY) function
 
AND
7C91vA4
Release Date
2020-11-04
 
 
Description
- Updated AMD AGESA ComboAm4v2PI 1.1.0.0 Patch C
 
I have literally done everything you can do aside from swapping the CPU and turning off PBO or any other bios settings. So if anyone is wondering if this exact error and restarting behavior is a single component in the system, in my case, it's not. It's the CPU or the microcode that hasn't been updated yet. Now.... I've seen forums where people with 3000 series CPUs were getting the same thing. I'm at the point of buying a 5950x *(when it's available) to replace my 3900x, buy it's super annoying that I may have to RMA my CPU for my main gaming rig the 5600x when there is almost no stock and I got lucky enough to buy a CPU with the supply being so low.

For reference, these are the CPUs I've owned, none of which have had this issue:
fx 6300
fx 8150
r5 1600
r7 1700x
r7 1800x
r7 2700
ThreadRipper 2950x
r5 3600x
r9 3900x
4500U
 
 
Obviously, being a computer engineer and a HUGE AMD fan, this behavior is concerning to me. Especially when I'm patiently waiting for the 5950x and a 6900xt.
 
I'll put the tridentz back in and try disabling CPB And PBO

Try upping the DRAM voltage by 0.05 V. That's what the MSI support told me and so far it's been working without crashes. PBO and CPB are in default settings.
(I'm the OP of this thread)

0 Likes
CrispyCrunch
Adept II

Re: Ryzen 5900x: System constantly crashing/restarting WHEA-Logger ID 18 and critical error Kernel-P

Jump to solution

@mackbolan777 wrote:

If it's still working, can you mark it as a "solution". Not for me to get "points" but so others will find it easily in the "knowledgebase". A lot with AsRock boards are having this issue. Thanks.


Well, the original post was about trouble with a MSI board. So I don't think it makes a lot of sense to mark a solution for AsRock mainboards?

0 Likes
cashby
Adept II

Re: Ryzen 5900x: System constantly crashing/restarting WHEA-Logger ID 18 and critical error Kernel-P

Jump to solution

Oh man. So I got the error again. Had been playing and was going well stopped playing. Was surfing net for a bit then decided to log in to Disney plus and watch Mando. Whole system **bleep** down after the recap. When I went back in same errors were reported. She's and crits... So annoyed. I'm at a loss. 

0 Likes
cashby
Adept II

Re: Ryzen 5900x: System constantly crashing/restarting WHEA-Logger ID 18 and critical error Kernel-P

Jump to solution

Upping the dram voltage by .05. have you got xmp enabled? You have auto turned off and manually set everyone but added an extra .05 for voltage? 


@CrispyCrunch wrote:

@nsargentum wrote:

I'm having the exact same issue on a 5600x with a msi tomahawk b550. I have a x570 gigabyte aorus master and a r9 3900x I was thinking of swapping this CPU with that and testing there.

OK; Get ready for this, Here's everything I've done so far to eliminate variables:

  1. Swapped the system drive (nvme) and reinstalled windows from scratch
  2. Unplugged all other drives
  3. Swapped GPUs
  4. Swapped PSU
  5. Swapped memory from 3200Mhz Gskill TridentZ CL16 to 2667Mhz CL16 Corsair Vengeance
  6. Swapped the Msi Tomahawk B550 with another MSI tomahawk B550 to verify it wasn't the board.

Ensured I'm on the latest bios for the MOBO and the previous 1 which was also post Ryzen 5000 release.

 
7C91vA51(Beta version)
Release Date
2020-11-16
 
Description
- Support AMD SAM(SMART ACCESS MEMORY) function
 
AND
7C91vA4
Release Date
2020-11-04
 
 
Description
- Updated AMD AGESA ComboAm4v2PI 1.1.0.0 Patch C
 
I have literally done everything you can do aside from swapping the CPU and turning off PBO or any other bios settings. So if anyone is wondering if this exact error and restarting behavior is a single component in the system, in my case, it's not. It's the CPU or the microcode that hasn't been updated yet. Now.... I've seen forums where people with 3000 series CPUs were getting the same thing. I'm at the point of buying a 5950x *(when it's available) to replace my 3900x, buy it's super annoying that I may have to RMA my CPU for my main gaming rig the 5600x when there is almost no stock and I got lucky enough to buy a CPU with the supply being so low.

For reference, these are the CPUs I've owned, none of which have had this issue:
fx 6300
fx 8150
r5 1600
r7 1700x
r7 1800x
r7 2700
ThreadRipper 2950x
r5 3600x
r9 3900x
4500U
 
 
Obviously, being a computer engineer and a HUGE AMD fan, this behavior is concerning to me. Especially when I'm patiently waiting for the 5950x and a 6900xt.
 
I'll put the tridentz back in and try disabling CPB And PBO

Try upping the DRAM voltage by 0.05 V. That's what the MSI support told me and so far it's been working without crashes. PBO and CPB are in default settings.
(I'm the OP of this thread)


 

0 Likes
CrispyCrunch
Adept II

Re: Ryzen 5900x: System constantly crashing/restarting WHEA-Logger ID 18 and critical error Kernel-P

Jump to solution

I actually didn't activate XMP but instead choose settings from the "Memory Try it!" function or whatever it's called. But I think they're the same as what XMP sets. It's definetely at 3600 MHz.
Then upped the DRAM voltage by 0.05. Both XMP and "Memory Try it" set the voltage to 1.37 V, I increased it to 1.42 V, maybe even only 1.41 V.

Did this on Tuesday, no crashes ever since.

 

0 Likes
imraneo
Adept I

Re: Ryzen 5900x: System constantly crashing/restarting WHEA-Logger ID 18 and critical error Kernel-P

Jump to solution

I'm running 5900X on Asus Strix X570-F mobo and the only 1 thing I have to disable to get my system stable is CPB. I can leave everything else on.

I tried upping the DRAM voltage as you suggested but it does not work. In fact I get into worse issues like bootloops, etc. I'm using TridentZNeo 3600.

Looking at the activity in this thread, is AMD going to do something about this? I can't be running at 3.7Ghz Max as obviously we paid for something much more.

nsargentum
Adept II

Re: Ryzen 5900x: System constantly crashing/restarting WHEA-Logger ID 18 and critical error Kernel-P

Jump to solution

I mean, That's the real kicker. If you have to turn of CPB, then you're going to end up running at like 3.5 Ghz which is below the base of the processor. At least that's been my experience with the 5600x.

 

For the record, I swapped every component and the motherboard and still have the same issue, and even after going to a whole different motherboard.

 

The real question is, is this something a bios update will fix? IF so, I'm fine with it; if not, I'm definitely going to return and replace this CPU because I don't think EVERYONE who has a ryzen 5000 is having the same experience. There must be some percentage of CPUs that are behaving this way.

cashby
Adept II

Re: Ryzen 5900x: System constantly crashing/restarting WHEA-Logger ID 18 and critical error Kernel-P

Jump to solution

I Decided to start over again. When I first built my system I used a SSD with the OS on it from my old PC and then tried to reinstall windows to my new M.2 SSD. it encountered some issues but eventually got it to work however I was noticing it was not showing as the first boot option in bios and every time I tried to change it - was causing issues. 

So I used the X570 Taichi mobo tools to wipe and format the M.2 drive which had my current OS on it. I then did a clean install of windows 10 and it fixed the boot drive issues. Somehow my samsung evo game drive got wiped but that's another story... 

I then started installing very minimal things - started off with epic games and played fortnite as this would cause my issues. didn't have any at all. It's been 4 days and I have not encountered any issues at all. started installing more things and still going well. 

I have not touched bios - everything is left on auto. I've run PCmark, 3Dmark and stress tests. It's the best I've had this run since I built it. still on the 3.40 bios from ASRock. 

Not sure if this would help others though but at least I still have everything still enabled and getting full use of CPU. 

mackbolan777
Forerunner

Re: Ryzen 5900x: System constantly crashing/restarting WHEA-Logger ID 18 and critical error Kernel-P

Jump to solution

Because it was the Agesa version common in all these BIOS's that was the "solution". That messed up "Beta" is throughout every brand board causing problems, especially with the 3000 series.

"It worked before you broke it!"
0 Likes
mackbolan777
Forerunner

Re: Ryzen 5900x: System constantly crashing/restarting WHEA-Logger ID 18 and critical error Kernel-P

Jump to solution

For a 5000 series, 3.40 should work. On mine it causes issues possibly due to me running a 3600X. It causes random reboots, no performance gain, like advertised, instability, whatnot on my PC and others on another forum that run 30000 series CPU's. I dropped to 3.10. If you run the 5900X, then 3.40 makes sense, the 3.42 has the "C" patch and is "Beta", that more than likely would mess things up. It's all in that "Agesa" package version, not the entire BIOS, but you can't leave out part of the update, lol. Igor's Lab is a great place to find out what works or workarounds for BIOS issues. The site's in Russian but the guy knows his stuff. He's got translated video's on YouTube as well. But you can ask him any question, if it hasn't been asked and he responds with a solid explanation. He explains why the Agesa version 1.0.8.0 is a defect and a Beta, not just "it's a bad version", a whole paragraph on it.

Trying to reinstall Windows off any SSD/HDD by like "reset this PC", or whatever will cause issues, even with the same chipset. The UUID will mess things up and I'm surprised it worked at all. Back in a day, you could take Windows 7 off say a "Gigabyte 990FX" board and "transplant the drive to an MSI with a 990FX chipset and it would work. Windows 10 binds itself to the board's MAC address/UUID, so really tough to "fool" it into thinking it's installed on the same machine. Like X570 to X570, even the same make board would fail. 

Glad you got it working good.

"It worked before you broke it!"
0 Likes