Windows 10: New RAM causing IRQL_not_less_or_equal BSOD - caused by Direct X?

I installed some new RAM 16GB 2x8, 3200 MHz onto my motherboard. It didn't seem to work with my existing RAM 8GB, 3200 MHZ as the 16GB was marked as 'hardware reserved' and unusuable if you have a solution to this, please say, but this isn't the focus of my question.


Everything has been fine, except when in a very specific situation - when playing the game Victoria II, it crashes after a few button clicks. The BSOD error was 'IRQL_not_less_or_equal'.


Looking in the error logs, I thought that around the time of the crash there was some odd activity around the programme VMWare, so I removed it. This seemed to fix the issue for several days, strangely enough.


However now it has started again. The error log seemed to point to Direct X being an issue. I have the dump here:


080520-181468-01.dmp 05/08/2020 16:20:12 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000020 00000000`00000002 00000000`00000001 fffff801`6463a69e dxgkrnl.sys dxgkrnl.sys+afe10 DirectX Graphics Kernel Microsoft® Windows® Operating System Microsoft Corporation 10.0.19041.423 WinBuild.160101.0800 x64 ntoskrnl.exe+3ddf40 C:\WINDOWS\Minidump\080520-181468-01.dmp 12 15 19041 2,514,068 05/08/2020 16:24:01


I have run memtest and it produced no issues.

My memory is compatable.


My motherboard is B450 GAMING PRO CARBON AC

:)

 

Unknown cause of BSODs IRQL_NOT_LESS_OR_EQUAL.

Hi,

I'm having serious problems with BSODs in my system. (Desktop computer, CPU= amd ryzen 1600, ram=2x8gb ddr4 @2933Mhz, mobo=GA-AB350-Gaming 3).

BSODs happen when I'm gaming (Tom clancy's rainbow six siege) and browse google chrome / firefox simultaneously on the side, I get a IRQL_NOT_LESS_OR_EQUAL error.

The BSOD dumps/logs are of little to no help to me as they always report a windows component as being the culprit. I collected 12 error logs - all are the same BSOD and cause. I even tried playing around with WhoCrashed program and WinDBG to have a
closer look at the logs but I don't really understand much in there..

If someone could have a look at the logs in the dropbox link and make some sense of them for me, that would really be appreciated.

Dropbox - Link not found

I ran a memtest86 overnight and got a good 10 passes with 0 errors, so RAM seems to be fine.

A format and a fresh reinstall of windows didn't help.

Kind regards!

 

BSOD: IRQL_NOT_LESS_OR_EQUAL, SYSTEM_THREAD_NOT_HANDLED

Greetings,

last week i made some hardware changes to my laptop (lenovo z70-80). I installed a new ssd and upgraded my 4gb RAM to 16 gb RAM . The next day i experienced some BSOD errors (only at a cold startup, after the reboot of the system everything works just fine).
Most commonly the cause of BSOD was SYSTEM_THREAD_NOT_HANDLED and just lately the IRQL_NOT_LESS_OR_EQUAL. I post the info from the last BSOD as got from blue screen viewer :

Bug Check String;

IRQL_NOT_LESS_OR_EQUAL

Bug Check Code: 0x0000000a

Parameter1: 00000000`00060001

Parameter2: 00000000`000000ff

Parameter3: 00000000`00000000

Parameter4: fffff802`8266bf72

Caused by Driver: ntoskrnl.exe

Caused by Address: ntoskrnl.exe+16c580

File Description: NT Kernel & System

thanks in advance.

 

BSOD Hardware Caused???

they do weird things like that, which all seem like something else is failing.
One of the worst things to diagnose, they seem to only quit when they want to.

Memtest is a good next step, if you rule out RAM and Power Supply make sure you disconnect all unnecessary peripherals and try to start the system with as little hardware as possible, if it works then, you can narrow down the culprit by trial and error.

the follow was taken from some website:

It's very difficult to determine if a failure is caused by the CPU because many other components can cause the same symptom when they fail.

1. System fails to boot
2. System re-boots intermittently
3. General Protection Fault
4. Illegal Operation
5. Stop Error, or BSoD (Blue Screen OfDeath)

Actually, CPUs rarely fail, and about the only way to determine if the CPU is causing the failure is to swap it out with a known working CPU of the same type and speed. Since this is difficult, the best bet is to first rule out every other possibility.

Before suspecting the CPU, rule out all the possibilities listed below.

1. The Operating System
2. A peripheral port device
3. A bad memory module
4. The hard disk drive
5. The power supply
6. The motherboard

If you have ruled out out all the other possibilities, investigate the items listed below.

1. Overheating
2. A short circuit
3. ESD