cancel
Showing results for 
Search instead for 
Did you mean: 

z590 maximus xiii heros ,Event 17,WHEA-Logger

auriux840204
Level 7

hi I have a problem. Asus z 590 ROG maximus xIII hero. When playing the game, the image starts to freeze, so I started looking for the problem, and I found this. My bios is the latest, which I can find on the official Asus page. BIOS 1701 is my CPU i9 11900k. GPU 3090 rtx. Maybe you have an idea how to fix it. 

Screenshot 2023-03-25 113855.pngx it.

500 Views
7 REPLIES 7

Nate152
Moderator

Hello auriux840204,

In the bios, disable PCI-e Native Power Management.

This should stop the WHEA errors.

Hello, I tried but it didn't work, give me a yellow color. 🙂

 

I have not had that problem on my system.  I may be related to the Thunderbolt device.

I did find out, if I disabled the Native Power Management in the Bios, it caused my Ethernet ports to not allow a setting which would keep it from waking the system.  

My Z790 Hero is seeing thousands of those warnings.  

Maximus Z790 Hero,
Intel i9-13900k
Intel BE200

Maybe this will give you some guidance.  I am not sure exactly what is happening but it seems to be related to putting something to sleep, or waking it up.

Saltgrass_0-1679849874609.png

 

Maximus Z790 Hero,
Intel i9-13900k
Intel BE200

Do you think reinstalling windows would fix this? or not?

 

It did not help on the Z790 board and since I do not have the situation on the Z590, I can't say for sure.

If you were wondering, I got the attachment from the Device Manager by highlighting the 4C01 port and then switching to view devices by connection.   Maybe yours will show a different device.

You can disable the power setting, as suggested.  That does work and if don't run into any other problems, it may be fine.  

Maximus Z790 Hero,
Intel i9-13900k
Intel BE200

Thank you for trying to help, but I can't get anything. I tried to reinstall win, now the PC is clean, but the errors have not disappeared. I don't know when it will be fixed, if it can be fixed at all. And the diagnostics throw out these errors, is it somehow related to the recent errors.Screenshot 2023-03-28 170805.png