[SOLVED] BSOD ntoskrnl.exe with new build (IRQL_NOT_LESS_OR_EQUAL)

[az0t]

Hi
I'm here because I need your help, I can't figure out my IRQL_NOT_LESS_OR_EQUAL BSOD problem... I can't figure out if its the CPU, GPU, Drivers, .... I just don't know..

I run into BSODs with my new build. Before I post the logg I might have some information which can help:

My Build
-ryzen 3700x
-MSI x570 gaming pro carbon wifi
-Corsair Vengeance Pro, 3200, DIMM 288
-Gigabyte RX 5700 XT gaming OC

Additonal things:
-BIOS is updated to latest Version, BSOD occurs on latest and second latest version
-AMD chipset is installed
-MSI Overclock is not enabled
-XMP profile (3200) is activated, BUT no BSOD with memtest86 (see below)
-several hours of gaming (also with 3200)= no BSOD
-BSOD occured at least twice while browsing (firefox), but on the other hand also long time browsing and no bsod...

What I have done
-memtest86 for 5 hours (4passes) no errors.
-reinstall AMD drivers (19.9.1) with amd-clean up
-sfc scannow
-3dmark stresstest and benchmarks, no problems...


I hope you can help me

Here are my loggs:
WhoCrashedOutput: https://pastebin.com/5TRdqTjj
Latest Minidump: https://drive.google.com/open?id=1ZCSA_fEqsIlnnjK3zXcfR4xh0q5Yj9Oa

Thanks and cheers!

 

[PC Tailor]

I have run the dump file and you can see the full report here: https://pste.eu/p/RTca.html

Summary of findings:

BugCheck A
Probably caused by : dxgmms2.sys ( dxgmms2!VidMmiAllocateMdl+24 )

Bugcheck Description:
IRQL_NOT_LESS_OR_EQUAL
"This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at an invalid address while at a raised interrupt request level (IRQL).
This is typically either a bad pointer or a pageability problem.

P1 is the address that could not be referenced."

About your bugcheck:
"Bug check 0xA is usually caused by kernel mode device drivers using improper addresses. This is either a bad memory pointer or a pageability problem with the device driver code. Examine the third party drivers .

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time window as the blue screen."

Some things to consider:
I would highly advise you to view the full report above, as this will contain much more detail as to the bugcheck and modules running at the time.

• Your dump file blames DX kernel, which are MS graphics - which often means your GPU drivers can be to blame.
• There has been some instability with latest ATI drivers I believe, so we may need to revert back to previous drivers.
• I would also remove/disable MSI Afterburner as this can cause various BSOD (especially GPU ones).

There are other modules we can look at, but I would focus on above first before we move on, then see how it goes

 

[az0t]

I have run the dump file and you can see the full report here: https://pste.eu/p/RTca.html

Summary of findings:


Some things to consider:
I would highly advise you to view the full report above, as this will contain much more detail as to the bugcheck and modules running at the time.

• Your dump file blames DX kernel, which are MS graphics - which often means your GPU drivers can be to blame.
• There has been some instability with latest ATI drivers I believe, so we may need to revert back to previous drivers.
• I would also remove/disable MSI Afterburner as this can cause various BSOD (especially GPU ones).

There are other modules we can look at, but I would focus on above first before we move on, then see how it goes

Hello!

Thanks for the analysis. So, based on your information:

• I downloaded DDU and did another deinstallation of the drivers
• and installed the latest 19.9.2 GPU driver. (no revert back).
• I don't own MSI Afterburner. Before you answered I had Gigabyte Aorus Software installed (but not running), so I deinstalled this software to make sure.

So I try to browse and use my computer today and the next few days, I will check back in how it goes!

Thanks and cheers!