UPDATE- Have to Disable Hyper-V to stop Event 137 Kernel Power Errors when exit sleep

I have no problem putting my PC to sleep nor do I have a problem waking it up. But every time I wake it, I get the following error in event viewer: Event 137 The system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S4). This can result in reduced resume performance. I do not get any errors from a cold boot. I have the latest bios.

I don't know how long these errors have been happening as they went further back than the event log showed.

I can disable Hyper-V in bios and the event stops yet the details of this show nothing relating to hyper-v. The only reason I tried it is I ran across an obscure article where it was suggested.

Fast startup is not even an enabled feature, nor is hibernate.

The strange thing is Powercfg -a shows that sleep state S4 is not available. Only S3 is available, so I can’t understand why I continue to get S4 related events. The only thing that stands out to me is in bios, deep sleep is enabled in s4 and s5, yet the OS does not have s4 enabled.

Here is a link to my onedrive folder of screenshots and bios photos taken with my phone. I tried to zip them and post them here, but it kept saying the file is too large. I cropped them as much as I could. These bios options are what came on the PC from Dell. Y'all tell me what I'm missing here.
screenshots1

UPDATE 1/12/22 The workaround of disabling Hyper-V is no longer working and I am back to where I started. Event Viewer is flooded with these errors again. I have searched for some way to force this machine to use the S3 sleep state to no avail. Last night I performed a repair install which changed nothing. Despite S4 and hibernate not being available as an option, the system is still trying to use it.
Update 1/31/22 A bios update was released 1/28/22. It solved my problem.

I have the same issue. It seemed to be related to the "wake with no video" problem I was having a few months ago and more recently BSoD's but not all of the time. Sometimes it wakes fine with the error logged and I don't notice any performance hit at all. I have 456 of them total in my EV log and only 12 of them followed by error 63 unclean shutdown. I too have no S4 or hibernation in powercfg, and I am on a completely different rig. We share almost specs, so I wonder if we both have memory in common? I run W10e64 and see it's not a very common error from my research.

@Post You did not fill in complete system specs in your profile so I cannot compare. My Dell has had multiple bios updates since I got it. I am now on version 1.10.2 Hibernate now works, though I do not use it. I strictly use S3 sleep and as stated no longer get the event 137 errors. When I was getting those errors, I was totally unaware I was getting them as operation of the computer itself was not affected. I would not have known there was an issue at all had I not looked at event viewer.
I hope you do not have the same motherboard as me (0J37VM A01) You can see by running Cpuz. If you do, my latest round of battles with Dell has uncovered a troubling thing that I will share with you in a private message.

We share almost NO specs - a correction here because there's a weird time limit to making edits?
@ glasskutter I filled in specs after the posting to avoid that time limit - they're showing up now.
Guess I should look at what Dell did in that new BIOS for a clue to help on an Asus Prime board. Thanks