bluescreen IRQL_NOT_LESS_OR_EQUAL

[Tw1N]

Hello guys,

first of all, sorry if my english isn't the best.
And this is also my first forum post every, so I am sorry if I did something wrong

I have a problem with my PC.
Everytime when I am starting my PC I get a blue screens after ~2 minutes.

Sometimes I don't get an error code but most likely the bluescreen says "IRQL_NOT_LESS_OR_EQUAL".
I have no clue what is causing this problem and no clue how to figure it out exactly since I am not really good with such things.

If possible explaining things in a easy way would be appreciated.

Please help me, would be really appreciated.


 

042821-7453-01.dmp

[Noah0302]

I always get that bluescreen when OCing.

 

Is your system overclocked?

[Radium_Angel]

OK, give me a moment to look over the crash file.

More crash files would be helpful, allow me to pinpoint what is happening.

As @Noah0302 said, are you running XMP or OverClocking anything? If so, turn that off.

Test your RAM with MemTest86 as well.

[Radium_Angel]

Ok, I'm going to post the important parts form the crash file, then my thoughts on what may have happened below that

___

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000000000c8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8023a66585c, address which referenced memory

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  x2.exe
___

 

Ok, the X2.exe file crashed, but that doesn't mean the program is bad, only that it tried to do something invalid. Again, I'd suspect RAM first, so test that. If you have any more crash dumps, please upload them here, it will help establish a pattern.

 

May also want to ensure your BIOS and drivers are up to date.

[Tw1N]

@Radium_Angel
The uploaded .dmp was the lastest but overall there are round about 5 of them.

I never used a kernal debugger, do I have to download it or do it with cmd?

And we tested the RAM with memtest64:
The programm was running for ~5 minutes and nothing happened. (We made a check on "Stop on error")
Do I have to test with Memtest86?

About the X2.exe:
It's a game we are all playing and this never happened before nor to anybody of my mates.

I also updated all drivers if I am not mistaken.
Tried to find some old drivers with a programm to update them manually, I prob. missed some.
Do you have some recommendations to check on updateable driver?

@Noah0302
The PC is not overclocked or anything.

[-rascal-]

10 minutes ago, Tw1N said:

@Radium_Angel
The uploaded .dmp was the lastest but overall there are round about 5 of them.

I never used a kernal debugger, do I have to download it or do it with cmd?

And we tested the RAM with memtest64:
The programm was running for ~5 minutes and nothing happened. (We made a check on "Stop on error")
Do I have to test with Memtest86?

About the X2.exe:
It's a game we are all playing and this never happened before nor to anybody of my mates.

I also updated all drivers if I am not mistaken.
Tried to find some old drivers with a programm to update them manually, I prob. missed some.
Do you have some recommendations to check on updateable driver?

@Noah0302
The PC is not overclocked or anything.

 

MemTest64 takes a long time to run, especially if you are doing multiple extensive passes.

Depending on the amount of RAM you have installed, and the density of the sticks, it could take HOURS, not minutes....

5 minutes of MemTest64 it way too short.

[Tw1N]

Just now, -rascal- said:

 

MemTest64 takes a long time to run, especially if you are doing multiple extensive passes.

Depending on the amount of RAM you have installed, and the density of the sticks, it could take HOURS, not minutes....

5 minutes of MemTest64 it way too short.

Oh, okay. 
Thanks for the information.

So I will use Memtest86 then!

[Radium_Angel]

38 minutes ago, Tw1N said:

there are round about 5 of them

Please upload all of them, it will help establish a pattern.

You do not need to do anything, I will handle the rest

 

39 minutes ago, Tw1N said:

Do you have some recommendations to check on updateable driver?

Just the website of your motherboard maker, they will have all the drivers you need

[Tw1N]

@Radium_Angel
Sorry for replying that late.

Here are the other .dmp.
Since I have to go now I will do the MemTest86 in the evening and tell you the result.

But I received a new bluescreen which is NOT shown in bluescreenview and had the error: Apc index mismatch 
 

042721-6890-01.dmp 042021-6375-01.dmp 042021-6125-01.dmp

[Radium_Angel]

Ok, give me a few to look them over.

[Radium_Angel]

OK, first dump:

__

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffad0437b08cb0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800a5261783, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MsMpEng.exe

SYMBOL_NAME:  dump_wmimmc+1783

MODULE_NAME: dump_wmimmc

IMAGE_NAME:  dump_wmimmc.sys
FAILURE_BUCKET_ID:  AV_R_INVALID_dump_wmimmc!unknown_function

___

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffff9a0c61aca080, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

PROCESS_NAME:  services.exe

CRITICAL_PROCESS:  services.exe

ERROR_CODE: (NTSTATUS) 0x6915e080 - <Unable to get error code text>
___

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000001799c0fb880, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8055c665656, address which referenced memory

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  nvcontainer.exe
___

 

None of your crash dumps are repeating, which says to me, bad RAM.

 

[Tw1N]

But I already had a dead PC once and it just came back 1 month ago.
How is this a thing?

[Tw1N]

@Radium_Angel
So we did the MemTest86 and nothing is wrong with my RAM at least.

I am now trying to check my BIOS and Mainboard if they are up to date.

(Sorry for not responding for a long time)

 

[Radium_Angel]

29 minutes ago, Tw1N said:

@Radium_Angel
So we did the MemTest86 and nothing is wrong with my RAM at least.

I am now trying to check my BIOS and Mainboard if they are up to date.

(Sorry for not responding for a long time)

 

All good, MemTest said everything is okay? That's...puzzling.

How are your temps of the CPU and GPU?

[Tw1N]

CPU: min. 47; max. 76; avr. 59
GPU: No information at the moment

[Tw1N]

I have 2 new more .dmp files in case they help you seeing a pattern in there @Radium_Angel

One of the bluescreens said "system service exception" and the other was another IRQL.

Greetings 
Tw1N

 

051021-6593-01.dmp 050821-6343-01.dmp

[Radium_Angel]

Ok, give me a bit to look over them.

[Radium_Angel]

As usual, some relevant info and thoughts below

___

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffaa0000000009, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8027ac6f9a3, address which referenced memory

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  x2.exe
___

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: 0000000000000007, Address of the instruction which caused the bugcheck
Arg3: ffff80030134ea60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  csrss.exe
___

 

The game X2.exe crashed again, but the csrss.exe is more troubling, It kind of points to (BUT NOT ALWAYS!) bad video card, or corrupted video card driver.

I assume you've tried sfc /scannow from a command prompt?

 

Also, if it's enabled in BIOS (IIRC that's where it is) turn off Fast Boot, that can impact things as well.

[Beerzerker]

IRQL_NOT_LESS_OR_EQUAL errors are normally due to RAM instability, usually bumping the RAM voltage up takes care of it..... Mind you I said usually, not always.

 

If you have your RAM clocked up too high, wrong settings and so on, you can get the same error. 

To fix:
Make sure your RAM is at stock settings and speeds, also be sure RAM voltage is correct, either at stock or even a tad over their stock voltage  - Won't hurt a thing to set it manually to do that.

Do all that and test.

It's also possible to have a stick going bad, causing this error to appear.
You can check that with a run of Prime 95 or other RAM testing bench/util.

[Tw1N]

On 5/13/2021 at 5:38 AM, Beerzerker said:

IRQL_NOT_LESS_OR_EQUAL errors are normally due to RAM instability, usually bumping the RAM voltage up takes care of it..... Mind you I said usually, not always.

 

If you have your RAM clocked up too high, wrong settings and so on, you can get the same error. 

To fix:
Make sure your RAM is at stock settings and speeds, also be sure RAM voltage is correct, either at stock or even a tad over their stock voltage  - Won't hurt a thing to set it manually to do that.

Do all that and test.

It's also possible to have a stick going bad, causing this error to appear.
You can check that with a run of Prime 95 or other RAM testing bench/util.

About the the PC:

It came back from the Company, it's prebuild from a german Website.

We had to send the PC to them once since the PC was not able to find a Source and iirc they replaced the RAM.

So I am really confused why this happens. 

The PC was bought in September and the problems happened ~1-2 Month after buying and using.

 

The RAM and everything is NOT clocked or anything.

[Tw1N]

On 5/13/2021 at 4:35 AM, Radium_Angel said:

As usual, some relevant info and thoughts below

___

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffaa0000000009, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8027ac6f9a3, address which referenced memory

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  x2.exe
___

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: 0000000000000007, Address of the instruction which caused the bugcheck
Arg3: ffff80030134ea60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  csrss.exe
___

 

The game X2.exe crashed again, but the csrss.exe is more troubling, It kind of points to (BUT NOT ALWAYS!) bad video card, or corrupted video card driver.

I assume you've tried sfc /scannow from a command prompt?

 

Also, if it's enabled in BIOS (IIRC that's where it is) turn off Fast Boot, that can impact things as well.

We just recently Updated the driver of her GPU.

 

Yes, we tried the scannow and nothing Was wrong there 

 

I just disabled the "Fast boot" in the BIOS.

[Radium_Angel]

7 minutes ago, Tw1N said:

We just recently Updated the driver of her GPU.

 

Yes, we tried the scannow and nothing Was wrong there 

 

I just disabled the "Fast boot" in the BIOS.

Ok, let us know if anything improves or not.

[Tw1N]

On 5/14/2021 at 8:12 PM, Radium_Angel said:

Ok, let us know if anything improves or not.

I think I got it.
And I feel really sorry for your time.

It was the driver of my BIOS probably.
I updated the driver yesterday and today there was no Bluescreen.
I will keep looking if I get some in the next days but it seems like this was the problem.

I am sorry.

[Radium_Angel]

No worries, glad it's fixed