I'm getting a BSOD (DRIVER_IRQL_NOT_LESS_OR_EQUAL) when I play COD Warzone. I usually get one BSOD per hour.
What I tried:
Driver verifier: BSOD on startup => "logi audio surround.sys" There seems to be a problem with this driver.
But I don't know if the ingame crashes are related to this issue.
With Driver verifier enabled, I couldnt get passed the booting phase, so I didn't have the chance to run the game to try get a BSOD.
PC Boots normally again with driver verifier turned off.
Below I posted 2 dumps: One of the game crash, one of the Logitech BSOD on startup with Driver Verifier enabled.
I also uploaded the mini dumps here.
Normal dump when game crashes
Loading Dump File 051020-16562-01.dmp
Mini Kernel Dump File: Only registers and stack trace are available
Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff801
Debug session time: Sun May 10 22:06:36.185 2020 (UTC + 2:00)
System Uptime: 0 days 8:46:21.516
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801
2: kd> !analyze -v
***
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: fffff80187bd179e, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff80187bd179e, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 1
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-LJGAJ30
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 3
Key : Analysis.Memory.CommitPeak.Mb
Value: 72
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: d1
BUGCHECK_P1: fffff80187bd179e
BUGCHECK_P2: 2
BUGCHECK_P3: 8
BUGCHECK_P4: fffff80187bd179e
READ_ADDRESS: fffff80107f7b3b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80107e323c8: Unable to get Flags value from nt!KdVersionBlock
fffff80107e323c8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
fffff80187bd179e
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Battle.net.exe
TRAP_FRAME: fffffa0188d5f1d0 -- (.trap 0xfffffa0188d5f1d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000cb9000 rbx=0000000000000000 rcx=00000000c0000100
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80187bd179e rsp=fffffa0188d5f360 rbp=000024efb59bbfff
r8=00000000000000d0 r9=0000000000000000 r10=fffff80928f815a0
r11=ffffc609849b4080 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
fffff801
STACK_TEXT:
fffffa01
fffffa01
fffffa01
fffffa01
SYMBOL_NAME: nt!KiPageFault+469
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.815
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 469
FAILURE_BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {73cd60cc-83fa-6b76-df08-1961c31d7403}
Followup: MachineOwner
---------
Dump of BSOD on startup with Driver Verifier enabled
Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804
Debug session time: Wed May 13 13:19:20.736 2020 (UTC + 2:00)
System Uptime: 0 days 0:00:11.416
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804
10: kd> !analyze -v
***
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
Arg2: fffff802e9786473, The address in the driver's code where the error was detected.
Arg3: 0000000000000000, Pool Type.
Arg4: 00000000324c5044, Pool Tag (if provided).
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 1
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-LJGAJ30
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 1
Key : Analysis.Memory.CommitPeak.Mb
Value: 69
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: c4
BUGCHECK_P1: 2000
BUGCHECK_P2: fffff802e9786473
BUGCHECK_P3: 0
BUGCHECK_P4: 324c5044
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffe981
ffffe981
ffffe981
ffffe981
ffffe981
ffffe981
SYMBOL_NAME: logi_audio_surround+6473
MODULE_NAME: logi_audio_surround
IMAGE_NAME: logi_audio_surround.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 6473
FAILURE_BUCKET_ID: 0xc4_2000_logi_audio_surround!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {11e623ce-dfdf-0535-997f-db5cda3a3590}
Followup: MachineOwner
---------
What I tried:
Driver verifier: BSOD on startup => "logi audio surround.sys" There seems to be a problem with this driver.
But I don't know if the ingame crashes are related to this issue.
With Driver verifier enabled, I couldnt get passed the booting phase, so I didn't have the chance to run the game to try get a BSOD.
PC Boots normally again with driver verifier turned off.
Below I posted 2 dumps: One of the game crash, one of the Logitech BSOD on startup with Driver Verifier enabled.
I also uploaded the mini dumps here.
Normal dump when game crashes
Loading Dump File 051020-16562-01.dmp
Mini Kernel Dump File: Only registers and stack trace are available
Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff801
07a08000 PsLoadedModuleList = 0xfffff801
07e50150Debug session time: Sun May 10 22:06:36.185 2020 (UTC + 2:00)
System Uptime: 0 days 8:46:21.516
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801
07bca390 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffa01
88d5f090=000000000000000a2: kd> !analyze -v
***
- *
- 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: fffff80187bd179e, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff80187bd179e, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 1
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-LJGAJ30
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 3
Key : Analysis.Memory.CommitPeak.Mb
Value: 72
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: d1
BUGCHECK_P1: fffff80187bd179e
BUGCHECK_P2: 2
BUGCHECK_P3: 8
BUGCHECK_P4: fffff80187bd179e
READ_ADDRESS: fffff80107f7b3b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80107e323c8: Unable to get Flags value from nt!KdVersionBlock
fffff80107e323c8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
fffff80187bd179e
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Battle.net.exe
TRAP_FRAME: fffffa0188d5f1d0 -- (.trap 0xfffffa0188d5f1d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000cb9000 rbx=0000000000000000 rcx=00000000c0000100
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80187bd179e rsp=fffffa0188d5f360 rbp=000024efb59bbfff
r8=00000000000000d0 r9=0000000000000000 r10=fffff80928f815a0
r11=ffffc609849b4080 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
fffff801
87bd179e ?? ???
Resetting default scope
FAILED_INSTRUCTION_ADDRESS:
+0
fffff801
87bd179e ?? ???STACK_TEXT:
fffffa01
88d5f088 fffff801
07bdc1e9 : 000000000000000a fffff801
87bd179e 0000000000000002 00000000
00000008 : nt!KeBugCheckExfffffa01
88d5f090 fffff801
07bd8529 : ffff910197d84180 fffff801
084c237b 0000000000000000 00000000
0000076a : nt!KiBugCheckDispatch+0x69fffffa01
88d5f1d0 fffff801
87bd179e : fffff80105ea1180 00000000
00000000 fffff80107f99400 fffff801
07bd1116 : nt!KiPageFault+0x469fffffa01
88d5f360 fffff801
05ea1180 : 0000000000000000 fffff801
07f99400 fffff80107bd1116 00000000
00000010 : 0xfffff80187bd179e
fffffa01
88d5f368 0000000000000000 : fffff801
07f99400 fffff80107bd1116 00000000
00000010 0000000000040200 : 0xfffff801
05ea1180SYMBOL_NAME: nt!KiPageFault+469
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.815
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 469
FAILURE_BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {73cd60cc-83fa-6b76-df08-1961c31d7403}
Followup: MachineOwner
---------
Dump of BSOD on startup with Driver Verifier enabled
Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804
5d6b8000 PsLoadedModuleList = 0xfffff804
5db00150Debug session time: Wed May 13 13:19:20.736 2020 (UTC + 2:00)
System Uptime: 0 days 0:00:11.416
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804
5d87a390 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe981
4393f420=00000000000000c410: kd> !analyze -v
***
- *
- Bugcheck Analysis *
- *
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
Arg2: fffff802e9786473, The address in the driver's code where the error was detected.
Arg3: 0000000000000000, Pool Type.
Arg4: 00000000324c5044, Pool Tag (if provided).
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 1
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-LJGAJ30
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 1
Key : Analysis.Memory.CommitPeak.Mb
Value: 69
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: c4
BUGCHECK_P1: 2000
BUGCHECK_P2: fffff802e9786473
BUGCHECK_P3: 0
BUGCHECK_P4: 324c5044
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffe981
4393f418 fffff804
5e0286e3 : 00000000000000c4 00000000
00002000 fffff802e9786473 00000000
00000000 : nt!KeBugCheckExffffe981
4393f420 fffff804
5d9e1c9b : fffff8045dae5878 00000000
00002000 fffff802e9786473 00000000
00000000 : nt!VerifierBugCheckIfAppropriate+0xdfffffe981
4393f460 fffff804
5e01fb98 : 00000000324c5044 fffff804
5dae5878 fffff802e9786473 00000000
00000000 : nt!VfReportIssueWithOptions+0x103ffffe981
4393f4b0 fffff804
5e03863a : 0000000000000000 00000000
00000001 0000000000000018 ffffe981
4393f550 : nt!VfCheckPoolType+0x90ffffe981
4393f4f0 fffff802
e9786473 : 0000000000000000 00000000
00000005 0000000000000000 fffff802
e97863f0 : nt!VerifierExInitializeNPagedLookasideList+0x5affffe981
4393f570 00000000
00000000 : 0000000000000005 00000000
00000000 fffff802e97863f0 00000000
00000018 : logi_audio_surround+0x6473SYMBOL_NAME: logi_audio_surround+6473
MODULE_NAME: logi_audio_surround
IMAGE_NAME: logi_audio_surround.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 6473
FAILURE_BUCKET_ID: 0xc4_2000_logi_audio_surround!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {11e623ce-dfdf-0535-997f-db5cda3a3590}
Followup: MachineOwner
---------
Last edited: