IRQL_NOT_LESS_OR_EQUAL

Try forcing Windows to show failed drivers and produce minidump files, enable Driver Verifier for this;

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

Let the BSOD happen 3 times and then see if the files were created.

Before running Driver Verifier, create a new system restore point.

If you have problems starting Windows after enabling Driver Verifier, follow these steps:

Start your PC, as soon as Windows tries to load (spinning dots appear), press and hold the power button for 5 to 10 seconds to perform a forced shutdown

Do this two or three times.

Windows will boot into the Recovery Environment.

Go to Troubleshoot > Advanced Option > Startup Settings and click Restart.

When restarting, press 4 to enter safe mode.

Open command prompt as administrator, run these two commands and restart your PC.

verifier /reset

verifier /bootmode resetonbootfail

I have no more files left.

The file also does not indicate any specific cause.

If you have more minidump files, please send them all.

Thanks for the reply. Yes, but it's not IRQL_NOT_LESS_OR_EQUAL. It's KMODE_EXCEPTION_NOT_HANDLED

https://1drv.ms/u/c/d8ef1f488ecf9975/Ea4YEZtStiZOk8likwHn2eMBtDuo34cjYiSybPYGxb0LKw?e=nhcPmc

Hello my name is Jonathan, I'm here to help you with this problem.

The minidump file do not indicate any driver or hardware causes, only memory corruption.

Do you have more minidump files ?