Windows 10: DRIVER_IRQL_NOT_LESS_OR_EQUAL d1

Microsoft R Windows Debugger Version 10.0.25200.1003 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\ThsnGre\Desktop\101722-12234-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 8 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS Personal

:)

 

driver_irql_not_less_or_equal (d1) (nvlddmkm.sys)


Hi


When I play demanding games I can get a bsod, the latest game being Rise of the Tomb Raider. This is the first game that bsods within 10 minutes no matter what. And so far this is what I can read out of the .dmp files : "driver_irql_not_less_or_equal (d1)" - (nvlddmkm.sys).

What happens is: without warning or fps drop the screen goes black (disconnects). Then the sound goes on for a bit, before it's cut goes into a loop. Then the PC restarts, or I have to push the restart button.
I have used the Display Driver Uninstaller 15.7.4.0 and reinstalled the Nvidia driver. Daemon tools have also been removed. Have stopped the Nvidia streamer service through msconfig too, just to see if it helped. No luck with any of the "fixes". I have run Furmark test without any issues, and a "sfc/ scannow". I've been monitoring the CPU and GPU temp before the crash, but no spikes in temperature.
*Side note - If I run Intel extreme tuning utility CPU stress test, the CPU reach almost 100 C in about 3 min. But that's under 100% load. But I guess that's unrelated, since the CPU don't get that load or temp during games. Still a indicator that something is wrong. And the Intel Diagnostic tool tells me there is something wrong with CPU Freq (Module - CPUFreq.exe did not create a results file.) , and it does not pass the stress test there as well. But I can't find anything about that in the .dmp file.


I'm not experienced enough to understand the rest. But so far by comparing similar problems others have had, I understand that Rise of the Tomb Raider are sending an invalid call/path to the Nvidia driver and makes it crash. correct me if i'm wrong.

Any tips on what to do?

---

ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+4d5acf )

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000004e7d75, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff800133d5acf, address which referenced memory

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL

A. Analysis Results

1. File Name: 120618-39843-01.dmp

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

IMAGE_NAME: tcpip.sys

*** ERROR: Module load completed but symbols could not be loaded for rtwlane.sys

2. File Name: 120618-42093-01.dmp

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

IMAGE_NAME: tcpip.sys

*** ERROR: Module load completed but symbols could not be loaded for rtwlane.sys

3. File Name: 120618-40718-01.dmp

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

IMAGE_NAME: tcpip.sys

*** ERROR: Module load completed but symbols could not be loaded for rtwlane.sys

B. Third Party Drivers

1. rtwlane.sys - Realtek Wireless Driver

Driver Date - 23-Jul-2018

C. Recommendations

1. Create a system restore point so that if something wrong happens you can revert.

Type restore point in Cortana Search > Create a Restore point > Check whether against your drive, Protection is ON or not. If not ON, click Configure button below to Make it ON > Now press Create to create a restore point

2. Realtek Wireless Driver - Go to computer manufacturer's website and see if any driver is released after 23-Jul-18.

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

*
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffd000262a8000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8009498885a, address which referenced memory

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for igdkmd64.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 1

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on GOC-ITDT001

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 3

Key : Analysis.Memory.CommitPeak.Mb
Value: 96

Key : Analysis.System
Value: CreateObject

BUGCHECK_CODE: d1

BUGCHECK_P1: ffffd000262a8000

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8009498885a

READ_ADDRESS: fffff801c024e500: Unable to get MiVisibleState
fffff801c0193e80: Unable to get Flags value from nt!KdVersionBlock
ffffd000262a8000

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffffd001bfad2c00 -- (.trap 0xffffd001bfad2c00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000fff rbx=0000000000000000 rcx=0000000000000fff
rdx=ffffc00171ecb541 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8009498885a rsp=ffffd001bfad2d90 rbp=ffffd001bfad2ed0
r8=ffffd001bfad2cd8 r9=0000000000000002 r10=000000001a8f2000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
igdkmd64+0xc885a:
fffff800`9498885a 8b0407 mov eax,dword ptr [rdi+rax] ds:00000000`00000fff=????????
Resetting default scope

STACK_TEXT:
ffffd001`bfad2ab8 fffff801`bffe15a9 : 00000000`0000000a ffffd000`262a8000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd001`bfad2ac0 fffff801`bffdfdc8 : fffff800`00000000 fffff800`00000001 ffffd001`bfad2cd0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd001`bfad2c00 fffff800`9498885a : ffffe001`1db3a000 00000000`1a8f2ffb ffffd001`bfad2e98 ffffe001`1a29e7d8 : nt!KiPageFault+0x248
ffffd001`bfad2d90 ffffe001`1db3a000 : 00000000`1a8f2ffb ffffd001`bfad2e98 ffffe001`1a29e7d8 00000000`00000000 : igdkmd64+0xc885a
ffffd001`bfad2d98 00000000`1a8f2ffb : ffffd001`bfad2e98 ffffe001`1a29e7d8 00000000`00000000 00000001`00000000 : 0xffffe001`1db3a000
ffffd001`bfad2da0 ffffd001`bfad2e98 : ffffe001`1a29e7d8 00000000`00000000 00000001`00000000 ffffd001`00000fff : 0x1a8f2ffb
ffffd001`bfad2da8 ffffe001`1a29e7d8 : 00000000`00000000 00000001`00000000 ffffd001`00000fff 00000001`00000fff : 0xffffd001`bfad2e98
ffffd001`bfad2db0 00000000`00000000 : 00000001`00000000 ffffd001`00000fff 00000001`00000fff 00000000`00000001 : 0xffffe001`1a29e7d8

SYMBOL_NAME: igdkmd64+c885a

MODULE_NAME: igdkmd64

IMAGE_NAME: igdkmd64.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: c885a

FAILURE_BUCKET_ID: AV_igdkmd64!unknown_function

OS_VERSION: 10.0.10240.16384

BUILDLAB_STR: th1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ae6ed5da-86a4-a1ba-84df-0618cafaf7fa}

Followup: MachineOwner
---------

3: kd> .trap 0xffffd001bfad2c00
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000fff rbx=0000000000000000 rcx=0000000000000fff
rdx=ffffc00171ecb541 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8009498885a rsp=ffffd001bfad2d90 rbp=ffffd001bfad2ed0
r8=ffffd001bfad2cd8 r9=0000000000000002 r10=000000001a8f2000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
igdkmd64+0xc885a:
fffff800`9498885a 8b0407 mov eax,dword ptr [rdi+rax] ds:00000000`00000fff=????????