Crash BOD

Question

Getting the following in event viewer system area:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x00000000aade90fd, 0x0000000000000002, 0x0000000000000000, 0xfffff8076d85a679). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: cd15979a-e459-4fa7-b9b4-46e70de9c665.

and

The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931

PC info

Device name

Processor AMD Ryzen 7 3700X 8-Core Processor 3.60 GHz

Installed RAM 32.0 GB

Device ID A08E61A2-1FB5-44BC-81CD-CE07DBA495EA

Product ID 00325-96584-77673-AAOEM

System type 64-bit operating system, x64-based processor

Pen and touch Pen support

and

Edition Windows 11 Home

Version 23H2

Installed on ‎6/‎4/‎2024

OS build 22631.4037

Experience Windows Feature Experience Pack 1000.22700.1027.0

<PII Removed>

Answer 1

Thank you for that information.

To try to force Windows 11 show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

Before you run Driver Verifier, please create a new System Restore Point

https://answers.microsoft.com/en-us/windows/for...

---

Note, if you have any difficulty getting into Windows with Driver Verifier enabled:

Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

Do this twice

On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

Go to Troubleshoot - Advanced Option - Startup Settings and click Restart

Upon restart, press 4 to enter Safe Mode

Open Command Prompt as Administrator and run these two commands, then restart your PC.

verifier /reset

verifier /bootmode resetonbootfail

Answer 2

ongoing. I upgraded to Win11 a couple of months ago and it started around then.

Answer 3

That minidump file just indicate RAM corruption as the cause of that crash.

Did your PC only crash once, or if this is an on-going problem, do you have any more minidump files available that you can upload for analysis?

Answer 4

Here is the minidmp.

090124-15875-01.dmp

Answer 5

Hi, I am Dave, I will help you with this.

Your link was removed to protect your privacy, a large Memory.dmp file can contain personal data.

Please check if there are any minidump files in C:\Windows\Minidump and if there are any minidump files, please upload them for analysis.