Mainboard: MSI x570 Unify
Mainboard-BIOS: 7C35vA82 (Beta version)
CPU: Ryzen 5900x
RAM: Crucial Ballistix BL2K32G36C16U4B 3600 MHz, 64GB (32GB x2)
Drive: M.2 Samsung 970 Evo+ 1TB SSD
Graphics: SAPPHIRE Nitro+ Radeon RX 5700 XT
PSU: be quiet straight power 11 750w Platinum
OS: Win 10 Pro (64bit) - all updates installed
Chipset driver: 18.104.22.1689 (released 2020-11-09)
I first assembled the PC with a Ryzen 3800x a week ago because it was unclear if and when I would get the Ryzen 5900x I ordered. Worked with the included AMD Prism Wrath CPU cooler for one week without any problems.
- Today I installed a Ryzen 5900x and a Scythe Fuma 2 CPU cooler.
- After 20 min the first crash/restart with the following entries in the Event Viewer: WHEA-Logger ID 18 and critical error Kernel-Power ID 41.
- Happens irregularly again and again, sometimes after minutes, sometimes longer: Windows freezes for a few seconds and then the PC reboots. Doesn't matter if load or not.
- CPU temperature between 30 and 40 °C
- Updated to BIOS and chipset driver mentioned above: Problem still exists
- XMP Profile disabled (RAM on 2600 MHz): problem still exists
- CMOS Reset: Problem still exists
Either there is a compatibility problem of something with the CPU, or the CPU is defective?
What to do? Really frustrating.
Solved! Go to Solution.
Im having a similar issue, x570 aorus and 5600x. Have same errors on windows.
Disable CBP and PBO and run it at default settings (3.7 ghz and xmp on). That works for me.
I got a new angle on this. So deactivating PBO and CBS definetely works, PC was running stable for a week now. But you'll loose performance.
So I wrote to the MSI support and the AMD support.
MSI suggested to try increasing the DRAM Voltage by 0.05 V, which I did. System seems to be stable, no crashes so far - neither in idle or while gaming.
Same problem for me i make a thrads about it
On a lot of motherboards you can Disable Global C-States AND ALSO Set Idle Current to Typical, not energy savings mode.
I set this things and for the moment the system is stable. I will give you guys an update if anything goes wrong.
Thx @rumple !
"Do you have any records in this folder?
I see only empty WHEA folder inside
Every time you check a WHEA, validate that there is no information or even a folder within this path.
friend i'm brazilian and i had the same problem ryzen 3600x rx5600xt evo just disable amd relive that will return to normal or try an older drive
MSI x570 gaming pro carbon wifi, Ryzen 5900x, XMP/CPB/PBO enabled - finally solved the issue by adding +0.05V vcore offset, as it mentioned on MSI forum here https://forum-en.msi.com/index.php?threads/msi-x570-b550-beta-bios-update-bug-status.348919/#post-20...
System now stable, no WHEA bsod anymore. Took me 3 weeks to test different solutions and bios, I'm using ComboAM4PIV2 22.214.171.124 now.
It is known that you can fix this with a positive offset (ideally do it in the curve on the specific core that's affected is better). The thing is that well.. You shouldn't have to be running at higher voltages than normal for it to work at stock settings.
Glad it solved your problem.
Same problem here with an Ryzen 5800x , Asus ROG Strix X470 f-gaming, 32 go DDR4 @3600 mhz.
Having the same exact issues with my 5900x
I got a prebuilt from CyberpowerPC. Booted up Warzone. Hard reboot after about 15 seconds being in the menu.
Immediately thought I had bad RAM or a bad PSU. Updated every possible driver, reinstalled windows, everything listed on this forum. I did have some luck boosting my VRAM Voltage to 1.4 (was at 1.35) and can now play Warzone for an hour or so before getting another hard reset. Also happens to me in other applications. I've found I can often trigger it by loading up chrome in the background and listening to spotify, assuming this is all CPU related.
any word from amd about this?
Seriously, why is disabling CBP considered a valid solution? Disabling CBP shouldn't be a "solution". This will seriously hinder your performance. I honestly can't believe you guys are OK doing that and calling it a day.
In my case, I can almost consistently reproduce this WHEA Logger Error 18 if I run Cinebench (or other CPU heavy tasks). Crashes haven't happened while gaming or idle yet. The time it takes for the crash to occur varies from 2 to 15 minutes but they happen!
My specs are:
Ryzen 9 5900x
X570 Aorus Elite WIFI (BIOS F33a AGESA v126.96.36.199)
EVGA RTX 3080 FTW3 Ultra
G.Skill Trident Z Neo 2x16 3600mhz CL18 RAM
I wish I knew what caused this. It's very frustrating.
"Seriously, why is disabling CBP considered a valid solution? Disabling CBP shouldn't be a "solution". This will seriously hinder your performance. I honestly can't believe you guys are OK doing that and calling it a day."
That is not a solution for sure. There is only one reasonable solution here - RMA.
Les voy contar mi experiencia cuando compre mi PC:
Procesador: Ryzen 5 3600X
Placa: Asus Tuf Gaming B550m-Plus
RAM: Corsair Veng 16 GB a 3200Mhz
Grafica: Gigabyte Nvidia GT 730 DDR5 2GB (es una tarjeta modesta)
Pantalla: LG 19" HD (es modesta) cuando tenia los problemas, ahora tengo una LG 25LGUM58 WFHD
Tenia los siguientes problemas:
1.- Whea-Logger 19: Al parecer "parecian problemas del procesador"
Despues de leer muchos foros por casi un mes y probando de todo(los ya mencionados aqui), no dejaba de mostrarse en el registro de eventos.
Lo que me funciono al final:
Restaurar todo a fabrica en la BIOS (obviamente configurando lo necesario para el BOOT y virtualizacion, dejando el overclock automatico[IA Tweaker]).
- Primero instale una Beta la BIOS Agesa, o actualizar al ultimo BIOS de su placa
- Segundo: Fuí a: Panel de control>Hardware y sonido>Opciones de Energia>Elegir la accion de los botones de inicio/apagado
Desactivar: Activar inicio rapido (si ya lo tienen desactivado, volver a desactivarlo, es decir activarlo y luego volver a desactivarlo luego reiniciar el equipo).
Haciendo estos pasos desaparecio mi problema.
2.- Apagado aleatorio y otros de la pantalla: Mi tarjeta grafica es muy sencilla asi que era inaceptable esos parpadeos, congelamientos, etc.
Como ven la mia es Nvidia, pero la configuracion que tengo es la siguiente:
-Controlar la configuracion 3D->Configuracion global:
GPU de renderizado de OpenGL: Geforce GT730
Modo de control de energia: Preferir rendimiento maximo
Sincronizacion Vertical: Desactivado
Adicionalmente tienen que arreglar el TrDelay en windows (linux creo que tambien lo tiene)
Esta solucion para la tarjeta grafica NVIDIA aplica tambien para las ultimas tarjetas de video
Ahora, con las tarjetas AMD, debe haber una configuracion similar y eso deberia solucionar el problema.
Something worth trying is to enable PBO but set the limits to the defaults for a 105W TDP Processor. (PPT=142W, TDC=95A, and EDC = 140A). Test the system and see if you have any errors.
If you do not, slowly raise PPT, TDC and EDC until the errors return. You can turn on PBO and set those limits to auto and look in Ryzen Master. The levels set in there will be the absolute limits for your motherboard. Take note of those, as those area the limits you won't want to exceed. Those levels are usually something ridiculous and it seems that by just blanket turning on PBO, the system is actually exposing a weak link somewhere.
You can just turn PBO off, but it is possible you can squeeze out a little bit of extra performance without crashing the system.
For some background, I have a Ryzen 9 5950X on an ASUS Crosshair VII X470 motherboard with an EKWB custom loop. I have four single rank DDR4 DIMMs (8 GB each) at 3600 MHz, matched 1:1 with Infinity fabric at 1.35V.
My system was stable with simply turning on PBO, but would crash immediately when running OCCT small data set, extreme, with constant load.
Eventually I settled on the approach above, and ended up with (PPT = 215W, TDC = 140A and EDC =160A) I stop at these settings as it was where my CPU hit around 70C under load and the voltage on a all core load was at 1.3V. Anything higher and those voltages and temps just got higher for minimal performance gains. Cinebench R23 scored just over 29500 in multicore and 1659 in single core.
Are the errors you are all hitting from overclocking only? I was trying to get a 5950x but had read some stability concerns and wondered if it would be a headache. I have no plans to overclock but really would like to avoid issues. I was going to go with an Asus board and if I don't got this route it was going to be the 11900x but based on the early signs there I know 5950x or 5900x is the better performing option.
Don't know if this will help but I've found that the newer AGESA releases 1.2.0.x seem to be problematic.
ASUS ROG Strix X570-F Gaming
32 GB TeamGroup DDR-3600 (2 x 16GB) with 16-16-16-38-55 timings (dual-rank DIMMs)
2 TB Sabrent Rocket nVME
Palit Gamerock Premium GTX 1080
Windows 10 (21H1 release)
EVGA 850w 80-plus Gold PSU
I recently had BIOS 3602 installed with AGESA 188.8.131.52 and found I was getting WHEA BSODs when gaming - usually between 20-90 minutes. The error code was along the lines of:
Processor APIC ID: 14 - Bus/Interconnect Error
With an earlier BIOS (3405) with AGESA 184.108.40.206, the WHEA error was similar but the description was "Cache Hierarchy" error.
I have since downgraded back to BIOS 3001 with AGESA 220.127.116.11 - so far no more WHEA errors or BSODs when gaming.
Interestingly, the CPU-Z benchmark score is also higher with AGESA 18.104.22.168 than the newer versions (around 2-3%)
It is frustrating as my last two builds were with a Ryzen 2700x and a 3900x, which had no issues. Before that I ran Intel (i7-4790k), again without these sorts of issues.
MSI dont have a bios with AGES 22.214.171.124, from 126.96.36.199 jump to 188.8.131.52 or 184.108.40.206 or 220.127.116.11 (beta)
In this momento i have PBO advanced only with curve +5, is a little more stable without games, today one crash meanwhile watch a movie.
X570 chipset have a lot of issue with 5000x cpu series, but B550 is a lot more stable chipset
adding my self to the list;
Same crashes with 5600x latest bios did not fix.
Just tried the latest beta (3603) for my board (AGESA 18.104.22.168 Patch A) but this time, I've not enabled DOCP - I've just left things to automatic but manually set the RAM speed (3,600), IF speed (1,800), and timings manually (16-16-16-38-55). When I used 4 x 8 GB DIMMs, setting DOCP would fail but moving to 2 x 16 GB DIMMs, DOCP seemed to work but started getting WHEA errors.
Played around 1.5 hours of AC Valhalla with no WHEA error although I got a blank screen after a loading transition but I think this is just likely a bug in the game and I was able to kill the process and continue.
I've also tried OCCT and Prime95, using CPU Affinity to cycle through the cores without any error. Will monitor over the next couple of days/weeks and update if anything else happens.
Is the WHEA error after KERNEL-Power error? 10 to 20s after?
If you "Disable" DRAM Power Options under AiTweaker>DRAM Timing Control>Power Down Enable
Also located in Advance>AMD OC'ing>AMD OC'ing>DDR & Infinity Fabric Frequency/Timings>DDR Frequency & Timings>DFRAM Controller Configuration>DRAM Power Options: "Disable"
Have you set the DRAM voltage to 1.35? Higher for B-die (Samsung Single Channel). I have 64GB of Corsair RGB running at 1.45 @ 1800/3600, they are CL18/3600MHz, no timing adjustments.
I still think this is a power detection issue from 10+ years ago buried in the AmeriTrend Bios base. These new processors will pull over their 105W TDP & 95A TDC base without hesitation due to water cooling. Its a server processor on a PC platform, made affordable for multi-tasking & gaming thanks to ASUS & others. When they quick boost vs. long boost the transient voltages & current draw erratic. Logging shows .1ms spikes.
Then you can look and research all the issues with AMD chipsets, Microsoft Windows, WHEA & KERNAL Errors going back 10+ years. Issues with WHEA are predominant in Laptops with high-end processors
I am running the new ASUS Beta Bios as well. Same KERNAL-Power Critical Errors every 12 hours or so. My PC is on 18-20 hours a day. However, I am still running an aggressive PBO 2 Curve with 125MHz. So, hopefully my latest curve adjustments will rectify that or I will turn the PBO2 down. I have gone to a EVGA G3 1000W 80+ Gold PSU. I will end up trying a 1200+ Watt Platinum or Titanium next. My new Red Devil RX 6900 XT has 3 power plugs...
Can you able to stabilize your mainboard finally?
"These new processors will pull over their 105W TDP & 95A TDC base without hesitation due to water cooling."
They will not, unless you turn on "Precision Boost Overdrive", with that on, your PPT, TDC and EDC will be set at motherboard limits and not the package limits of 142W, 95A and 140A. The motherboard limits are usually something ridiculous that a CPU will never be able to hit regardless of cooling. It is best to turn on PBO, and manually set the PPT/TDC/EDC limits to the stock limits. This should mirror stock settings. You can then slowly raise those limits until you hit the temp/voltage you are comfortable with or you start to see errors. Once that is done, you can play around with curve optimizer and the clock speed limits to get some additional performance.
On my 5950X I got to PPT 215W, TDC 140A, and EDC 160A. At those settings I am TDC bound on an all core load. TDC 100%, PPT 94%. My voltage on all core is right around 1.3V and temps are right at 70C on an EKWB custom loop. Going any higher just raises the voltage and temps with little performance gain. I have a +100 MHz to clock speed and also played with the curve optimizer a bit after the fact.
My DRAM is 4 single rank DIMMS (32 GB total) at 1.35V. Set at 3600 MHz (CL14) and IF at 1800MHz. Timings are custom, I did not use the DOCP profile.
No errors or crashes with those settings. I can pass OCCT large data set, extreme, variable without error as well as the small data set, extreme, continuous.
["These new processors will pull over their 105W TDP & 95A TDC base without hesitation due to water cooling."
"They will not, unless you turn on "Precision Boost Overdrive", with that on, your PPT, TDC and EDC will be set at motherboard limits and not the package limits of 142W, 95A and 140A. The motherboard limits are usually something ridiculous that a CPU will never be able to hit regardless of cooling. It is best to turn on PBO, and manually set the PPT/TDC/EDC limits to the stock limits. This should mirror stock settings. You can then slowly raise those limits until you hit the temp/voltage you are comfortable with or you start to see errors. Once that is done, you can play around with curve optimizer and the clock speed limits to get some additional performance."]
Excuse me? In context to the messages (replies) with that individual, that statement does not remove the fact of how many times I have mentioned PBO2 and my Boost Curve.
I did not use the words "stock BIOS settings" or "out of the box settings", therefore I never insinuated what you are claiming I did. Why would I mention water cooling...obviously not in an OEM scenario.
I do understand that you specifically were using precision boost overdrive, I merely sought to clarify the statement you made.
"These new processors will pull over their 105W TDP & 95A TDC base without hesitation due to water cooling."
" therefore I never insinuated what you are claiming I did."
Just based on the simply meaning of words, let's break that down.
The statement implies that all Ryzen 5000 processors (These processors) will pull over their designated TDP as long as water cooling is applied (due to water cooling), which is categorically false. So no, you didn't insinuate it, you flat out said it.
No Ryzen processor will boost past stock settings, water or not without PBO enabled. Furthermore, the statement also implies that Ryzen will not boost past stock operation if water cooling is not applied. Again, that is false. They will in fact pull over the TDP with air cooling as well as long as PBO is turned on, as most higher end air coolers will keep a chip cool past 142W PPT.
So as a general statement "These new processors will pull over their 105W TDP & 95A TDC base without hesitation with precision boost overdrive and adequate cooling" would be better.
Since you were actually referring to your own situation in particular, I would have gone with
"My new processor will pull over it's 105W TDP & 95A TDC base without hesitation due to water cooling."
That makes it very clear that you are referring to your situation and not making a generalized statement about all Ryzen processors.
Back to the matter at hand. Just turning on Precision Boost Overdrive by itself and not manually setting the PPT/TDC/EDC could be what is causing the instability. And it may be worthwhile to slowly raise those, as I did, until the stability issues reappear.
Back to the point I am trying to bring to the surface that no one seems to be discussing:
In MY Opinion & from Research I have gathered the following to be true -
1.) WHEA ID 18 is secondary to the KERNEL-Power ID 41 (63)
2.) KERNEL-Power error comes 10-20 seconds before the WHEA; a longtime issue not specific to AMD and 5000 Series; but for some reason Windows/BIOS/MoBo's are extremely sensitive to the issue as if the PC was a laptop on battery trying to do too much & cannot draw the power it needs to stay alive.
3.) I have received KERNEL-power errors that do not always log a matching WHEA; over last 30 days ratio is 70%
4.) Issues with this go back to the beginning days of the BIOS PCI/Bus circa 2006 - as found from 10+ year old Microsoft forum discussions. (see my other posts for links)
5.) The issue has plagued the AMD & Windows OS for 10 plus years - same Microsoft forum discussions, which have interesting details around 2011 regarding old Java scripts from early years (see my other posts for links)
5.) Power saving "features" in Windows seem to be a culprit but are not the final solution is the AMD chip is highly active
6.) Multi-core (IMO - 8 & over, per reading forums) are the most susceptible, 5800X, 5900X, 5950X, even though I could re-create the same errors on a different ASUS board & my 3900X
7.) On top of #6, the latest Ryzen 5000 series are triggering this scenario once Tweaking happens; from the use of my 3900X to my current 5900X
8.) Running the 5900X closer to 5.1MHz on my ASUS B550-E seems to be my cut off, not because of thermals or power consumption, but the quick milli-second boosts to that speed and over when at idle, even though it would run for several hours at a time, with PBO2 Boost spikes to 5150MHz on my preferred cores. Could this be VRMs, I don't thing so, 14+2 power stages have been solid
9.) Setting custom voltages and testing custom PBO2 Boost Curves will yield the best results in ASUS BIOS
10.) Quality power supply, name brand 80+ Gold and Up, depending on MoBo/Ryzen 5000 series CPU Boost Goals (Everyday vs. Tweaker)/GPU power requirements; I am using an EVGA G3 1000W to achieve my current goals; Once I turn up the 6900 XT I think I will be short or less stable at full-tilt (My Red Devil RX 6900 XT has pulled into the 400 Watt Range (Wattman+MPT) with it's 3 power plugs, PCI=75W, Plugs x3=450W, Total Hardware=525W, Manufacturer states 480W draw capable (hopefully coming with Core voltage increase) and a 900W PSU preferred! Last AMD Driver update let some guys go over 2700MHz stable on 6800/6900XTs); No power left over for Boost spikes, then errors will come for sure.
11.) Temperature - Room Ambient Temp/MoBo Temps/CPU Tdie Temp/GPU Hot Spot Temp all must stay way below their thermal limits for performance; a lot of the errors I read and then read their temps, well that'll do it...
While I can sense everyone's frustration, I think this specific scenario is not what it appears regarding WHEA errors. IMO from testing the combinations of hardware & settings, it is related to CPU Clocks in relation to Single or Dual Channel RAM &/or Processors plus Boost Setting (be it auto settings when on (AMD Issue or activates an issue described above) or custom settings being out of the capabilities of the board/CPU/WinOS combination.) The MoBo manufactuers have given us all the tools we need to show the capabilities of these impressive processors but the other side of that coin is we can quickly create a scenario of Red Team Sucks. When in fact, it is because of the scenario you have created in your system.
Again, my opinion, my experience, I hope it helps you to create tests & log your data to come up with what works best, and ultimately find your ryZEN, in your AMD system.
can you put your bios parameters? i have a MSI mobo with 5900X.
can you put your bios parameters? i have a MSI mobo with 5900X.
I have and X470 ASUS Crosshair VII with the latest UEFI update and an Ryzen 9 5950X. Cooling is an EKWB custom loop with a monoblock (cools CPU as well as VRM components).
DRAM is 4 single rank DIMMs at 1.35V, 3600MHz and CL14. I can post full manual timing here if needed, but I do not use the DOCP profile.
All other settings at at default except...
CSM is disabled.
Precision boost overdrive is enabled in "AMD Overclocking" However, PPT/TDC/EDC are set manually with 215W/140A/160A. Scalar is 1X and the auto overclocking is set to +100.
Those power settings were determined based on my cooling solution (EKWB custom loop). I recommend starting with PO on, but setting PPT/TDC/EDC to 142W/95A/140A. Those are the stock settings and should behave identical to having PBO disabled. If the system is 100% stable with those settings, you can then slowly raise them until your errors return, the system becomes unstable, you hit the temperature you want, or your all core boost starts to climb over 1.3V.
For me, I stopped at the settings listed above because going further saw pretty dramatic increases in temperature with minor performance gains. The all core boost voltage also started to creep over 1.3V as well, which you certainly don't want for silicon longevity.
These settings are 100% stable for me. No random restarts, and I can pass OCCT large and small data sets without issue.
I was having WHEA 18 crashes almost everyday, but one day I was searching for possible solutions and in a HWinfo forum someone discovered the issue to be caused by the AMD RX 6000 series GPU paired with a Ryzen 3000 and 5000 Series as both use the same IO die, this was not a hardware problem but a software problem related with the sleep state of the GPU. There are beta versions of HWinfo that are supposed to fix the problem and the same applies for AIDA64, there is no info on AIDA64 forums like there was for HWinfo but since they share very similar code, I tested the latest Beta version of AIDA64 Extreme and no more WHEA crashes, I haven't had a crash in a little more than 2 weeks, before updating to beta, I had crashes almost everyday.
My BIOS settings: ALL default except for D.O.C.P. 3600MHz, CPU multiplier - 40x and core voltage at 1v, this is mainly to keep power consumption and temperatures down, while still having more than enough power for gaming and other tasks.
Edit: I should have said that my solution might not fix the crashing for everyone, it's just a common issue with people using monitoring software with latest AMD GPUs and CPUs, and forgot to mention I'm in AGESA 22.214.171.124 on an ASUS ROG STRIX X570-E GAMING, Ryzen 9 5900X and RX 6900XT.
with hwinfo? how setting? portable or installed?
Yes HWinfo and AIDA64 and both installed and portable as files are the same. If you want to test just disable all GPU related sensors or update to the latest beta. For me AIDA64 was causing crashes with the latest stable, but with latest beta crashes are completely gone for more than 2 weeks.
Just an update on this. So far, beta BIOS 3603 with AGESA 126.96.36.199 Patch A is proving stable. Not had any more WHEA/BSODs during normal use (work and gaming).
I have left DOCP off with the timings/speed/voltage manually configured as stated in my previous message. I have disabled the "DRAM Power Down" option as was suggested as well but left everything else on automatic.
Also quickly dabbled with PBO by enabling it and stress-testing proved stable as well with quite a significant uplift in CB23 scores but have decided to leave it off for now until any remaining bugs with BIOS/AGESA are ironed out in the coming weeks/months.
Just also remembered that prior to upgrading to 2 x 16 GB sticks of RAM, I used to run 4 x 8 GB sticks (similar speed but looser timings) that when switching DOCP on it led to failure to boot until I removed 2 sticks whereas manually configurating the speed/timings/voltage (with all 4 sticks) was fine.
I can confirmed that, my system with 5900x with PBO disabled randomly restarts the system. No error page, i immedeatly found by self on bios bootup sequence.
My system is:
32x2 Spectrix d50 3200mhz ram
Asrock b550m steel legend
gtx 1070 zotac
latest windows (tried re-intstall)
I can provide any additional information yet this is so random that i can not reproduce the problem easily
Is there any valid solution to this yet?
well i got my RMA in, 4th week 2021 cpu. I no longer have WHEA errors but my computer still re-starts once a night about 3ish AM while idle due to a bug check error. I'm going to try re-installing windows and see if it helps. I have never had these issues with an intel processor ever
Do you have a KERNEL-Power Error Event ID 41 (63) before a WHEA Error Event ID 18?
If so research that error and the things to turn off in Windows.
AS a matter of record are you on the latest version of Windows? 20H2 build 19042.870?
Received my RMA this morning. Took 12 days to ship from Canada to US using Canada Post, They examined and approved the CPU 3 hours after receiving it, shipped one back to me that same day and it took 4 days to ship to me.
New CPU was 2104, and so far has been working perfect. Shoved it in first thing this morning, reset bios to defaults except DOCP enabled (CPU I RMA'd needed PBO & CPB turned off to not WHEA) and now it's been 9 hours so far of fortnite running, 3 video streams going, and me doing my day job all day without a single WHEA... will continue letting it go but so far so good! The previous CPU would WHEA usually within 20 minutes of fortnite running.
**bleep**. I’m having the same issues! Rma’ed my 5950x due to whea errors, now getting BSODs due to bug check with the replacement CPU. Multiple reinstallations of win 10. Did not help. Come on AmD!