Repeated reboot in Windows 10 (Event ID 41)

[Comp_expert_wannabe]

Hi everyone,

I hope I chose the right forum to post this thread at.
I bought myself a new computer a few weeks ago (full list of components is detailed below) and installed (a legal version of) Windows 10 Education (20H2) on it.
The problem is that my computer consistently performs a reboot, without properly shutting down first.
After the reboot, a critical error (event ID 41) appears in Windows event viewer (see below), without any event before the critical one that may suggest what is the source of the error.

I originally thought that the reboot always happen during high loads on the GPU, and ran a few benchmarks (Furmark GPU tests, Cinebench CPU test, OCCT test and also used Windows memory memory diagnostic without finding any errors), during which the computer didn't reboot (the PSU parameters, such as voltage look good, without major fluctuations). In any case, the reboot also happened today while I worked on the web browser (without running anything demanding on the GPU or CPU).
As for windows - the sleep or shutdown options in the power menu are all disabled.


EDIT :
I am not sure if this has anything to do with the original problem, but I noticed that a few seconds after the reboot, a fatal hardware error appears in the event viewer:

What might be the reason for this strange reboots?

Looking forward to any help or suggestions.

Thank you!



CPU: AMD Ryzen 5900
GPU: Gigabyte Eagle OC 3090
PSU: Corsair HX1000
MB: Asus B550 E-gaming
RAM: 4x16 GB , G.Skillz Trident Z Neo 3600CL16
NOCTUA NH-D15

ORIGINAL ERROR:
Event ID : 41
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

[DeathtoGnomes]

If you still have the logs, upload the last 25 errors before the error 41.

It appears it might be related to a potentially bad PSU. If this is still under warranty, it would be easier to take it in to where you purchased it and let them look at it.

 

[Comp_expert_wannabe]

If you still have the logs, upload the last 25 errors before the error 41.

It appears it might be related to a potentially bad PSU. If this is still under warranty, it would be easier to take it in to where you purchased it and let them look at it.

Thanks for the suggestion! If it is a PSU problem - shouldn't I see something in the voltage/power part during the OCCT test? Is there any way to check if this is indeed a PSU problem?

Here are the errors before error 41:

The details of the upper 10:
*)File System Filter 'npsvctrig' (10.0, ‎2025‎-‎01‎-‎06T04:41:12.000000000Z) has successfully loaded and registered with Filter Manager.
*) File System Filter 'atc' (10.0, ‎2020‎-‎09‎-‎15T18:00:21.000000000Z) has successfully loaded and registered with Filter Manager.
*) File System Filter 'FileCrypt' (10.0, ‎2002‎-‎03‎-‎01T13:12:42.000000000Z) has successfully loaded and registered with Filter Manager.
*) Volume C: (\Device\HarddiskVolume3) is healthy. No action is needed.
*) File System Filter 'bdprivmon' (10.0, ‎2020‎-‎01‎-‎17T10:43:47.000000000Z) has successfully loaded and registered with Filter Manager.
*) File System Filter 'gzflt' (10.0, ‎2020‎-‎09‎-‎02T10:09:29.000000000Z) has successfully loaded and registered with Filter Manager.
*) File System Filter 'Gemma' (Version 10.0, ‎2020‎-‎09‎-‎10T16:25:59.000000000Z) unloaded successfully.
*) File System Filter 'Gemma' (10.0, ‎2020‎-‎09‎-‎10T16:25:59.000000000Z) has successfully loaded and registered with Filter Manager.
*) File System Filter 'Wof' (10.0, ‎2029‎-‎03‎-‎19T10:57:47.000000000Z) has successfully loaded and registered with Filter Manager.
*) File System Filter 'FileInfo' (10.0, ‎2062‎-‎12‎-‎23T07:21:06.000000000Z) has successfully loaded and registered with Filter Manager.

 

[RaceJay]

Maybe your MoBo/CPU combo doesn't like your NVidia GPU... perhaps it wants a AMD/Radeon instead...

 

[Caring1]

Disable C states in the Bios.
C7 in particular.

 

[Comp_expert_wannabe]

Maybe your MoBo/CPU combo doesn't like your NVidia GPU... perhaps it wants a AMD/Radeon instead...

I find it hard to believe, but is there any way to check if this might be the problem?

Disable C states in the Bios.
C7 in particular.

Can you please elaborate? In particular, how can this help if this issue did not appear when I ran CPU benchmarks (arriving at 100% CPU usage for at least half an hour) ?

Thank you both!

 

[Caring1]

Can you please elaborate? In particular, how can this help if this issue did not appear when I ran CPU benchmarks (arriving at 100% CPU usage for at least half an hour) ?

C states allow your CPU to enter a low power state, which won't happen under load during benchmarks.

 

[Comp_expert_wannabe]

C states allow your CPU to enter a low power state, which won't happen under load during benchmarks.

and this low power state will lead to a sudden reboot? (without any warning, or properly shutting down first?)

 

[Deleted member 193596]

that's an issue with Zen 3.
i had this problems with my 5800X. but the latest bios fixed it for me.

forgo to mention that it only was "fixed" after having a full CMOS Reset.

 

[Calmmo]

If you're on bios 1401 try going back to a stable 1.1.1.0 release.
Agesa 1.1.8.0 is supposedly bug ridden (aka 1401). Doesn't hurt to try does it?

 

[Deleted member 193596]

If you're on bios 1401 try going back to a stable 1.1.1.0 release.
Agesa 1.1.8.0 is supposedly bug ridden. Doesn't hurt to try does it?

weird.. for me 1.1.8.0 is the ONLY stable bios of all available version, patches and other stuff.

 

[Caring1]

and this low power state will lead to a sudden reboot? (without any warning, or properly shutting down first?)

If your system is unstable, ram timings etc.

 

[StefanM]

To which softwares do the listed kernel drivers belong?
'bdprivmon' = Bit Defender - i remember to have read somewhere that users had trouble with 3rd party antivirus in recent Windows versions

EDIT:
Try a clean boot (not to be confused with safe boot) to rule out 3rd party software

https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows

 

[DeathtoGnomes]

All these suggestions are fine, but if its still under warranty, take it in and save yourself the headache.

You really should not enter the BIOS if you dont know what you are doing and it could void further warranty if you mess something up.

 

[RJARRRPCGP]

That error indicates a faulty CPU or a motherboard problem. Please clear the CMOS then reconfigure the date, time and the boot order.

 

[Comp_expert_wannabe]

Thank you everyone for many helpful suggestions! I will contact my warranty provider and see what he thinks is the best way to approach this.

 

[jaggerwild]

Take it back its brand new, or is it?