Windows 10 IRQL_NOT_LESS_OR_EQUAL BSOD

  • Thread starter Thread starter TimDoldersum
  • Start date Start date
T

TimDoldersum

Guest
Hallo,


Sinds een paar weken krijg ik steeds last van een terugkomende BSOD, namelijk IRQL_NOT_LESS_OR_EQUAL.


Ik heb een poosje het internet afgezocht en daardoor een paar dingetjes uitgeprobeerd, bijvoorbeeld een schone installatie van Windows 10 en gecheckt of al mijn drivers up-to-date waren.


Hiernaast heb ik ook nog een paar keer Windbg geprobeerd. Alleen hier werd ik zelf niet veel wijzer van en ik hoop jullie wel :)


Dit gaf de bugcheck aan:


[COLOR=rgba(30, 30, 30, 1)]Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\040921-10078-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 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`16600000 PsLoadedModuleList = 0xfffff807`1722a490
Debug session time: Fri Apr 9 18:55:08.591 2021 (UTC + 2:00)
System Uptime: 0 days 0:06:12.238
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run [/COLOR][COLOR=rgba(0, 0, 255, 1)]!analyze -v
[/COLOR][COLOR=rgba(30, 30, 30, 1)]nt!KeBugCheckEx:
fffff807`169f5db0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9280`ebc76160=000000000000000a
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: 0000000000000004, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff8071684a4c0, address which referenced memory

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3780

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 29623

Key : Analysis.Init.CPU.mSec
Value: 421

Key : Analysis.Init.Elapsed.mSec
Value: 12678

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: a

BUGCHECK_P1: 4

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8071684a4c0

WRITE_ADDRESS: fffff807172fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000000004

BLACKBOXBSD: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxbsd[/COLOR][COLOR=rgba(30, 30, 30, 1)])


BLACKBOXNTFS: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxntfs[/COLOR][COLOR=rgba(30, 30, 30, 1)])


BLACKBOXPNP: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxpnp[/COLOR][COLOR=rgba(30, 30, 30, 1)])


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffff9280ebc762a0 -- [/COLOR][COLOR=rgba(0, 0, 255, 1)](.trap 0xffff9280ebc762a0)
[/COLOR][COLOR=rgba(30, 30, 30, 1)]NOTE: The trap frame does not contain all registers.
[/COLOR][COLOR=rgba(0, 0, 255, 1)]Some register values may be zeroed or incorrect.
[/COLOR][COLOR=rgba(30, 30, 30, 1)]rax=ffffe603508e1180 rbx=0000000000000000 rcx=ffffe60353e72580
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8071684a4c0 rsp=ffff9280ebc76430 rbp=ffffba8b00000000
r8=ffffe603531ab3f0 r9=ffffe603508e1180 r10=7ffffffffffffffc
r11=ffff9280ebc76528 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KeSetEvent+0x290:
fffff807`1684a4c0 836b0401 sub dword ptr [rbx+4],1 ds:00000000`00000004=????????
Resetting default scope

STACK_TEXT:
ffff9280`ebc76158 fffff807`16a07d69 : 00000000`0000000a 00000000`00000004 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffff9280`ebc76160 fffff807`16a04069 : 00000000`00000000 00000000`00000240 ffff9280`ebc76790 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff9280`ebc762a0 fffff807`1684a4c0 : 00000000`00000000 ffffba8b`00000000 ffffe603`55099ae0 ffffd081`26f2c180 : nt!KiPageFault+0x469
ffff9280`ebc76430 fffff807`16c67924 : ffffe603`53e72580 00000000`00000000 ffffba8b`4ef226e0 ffffe603`531ab3f0 : nt!KeSetEvent+0x290
ffff9280`ebc764c0 fffff807`16c681c1 : ffffba8b`52b754a0 00000000`00000018 ffff9280`00000001 00000000`00000000 : nt!ExpWnfNotifyNameSubscribers+0x124
ffff9280`ebc76530 fffff807`16c67ede : 00000000`00000000 ffffe603`4f005000 00000000`00000000 ffffe603`402a6040 : nt!ExpNtUpdateWnfStateData+0x2d5
ffff9280`ebc76650 fffff807`16a077b8 : 00000000`00000000 ffffba8b`4fc136b8 00000000`00000000 00000000`00000000 : nt!NtUpdateWnfStateData+0x2e
ffff9280`ebc766a0 fffff807`169f9c10 : fffff807`18540ddd 00000000`00000002 00000000`00000002 ffffe603`4cbeb3c0 : nt!KiSystemServiceCopyEnd+0x28
ffff9280`ebc768a8 fffff807`18540ddd : 00000000`00000002 00000000`00000002 ffffe603`4cbeb3c0 00000000`00000000 : nt!KiServiceLinkage
ffff9280`ebc768b0 fffff807`18540c18 : 00000000`00000001 ffffffff`800061e0 00000000`35a4e900 00000000`ddde7546 : dxgmms2!VidMmInterface+0x214fd
ffff9280`ebc76940 fffff807`1856c043 : ffffe603`4f00ec60 ffffe603`4f005000 ffff9280`ebc76b00 ffffe603`4f00ec70 : dxgmms2!VidMmInterface+0x21338
ffff9280`ebc76a00 fffff807`18576759 : ffffba8b`430dd370 ffffe603`4cbeb200 00000000`00000000 00000000`051cb000 : dxgmms2!VidMmInterface+0x4c763
ffff9280`ebc76be0 fffff807`16917e85 : ffffe603`4cbeb280 fffff807`18576750 ffffba8b`430dd370 000f8067`b4bbbdff : dxgmms2!VidMmInterface+0x56e79
ffff9280`ebc76c10 fffff807`169fd408 : ffffd081`26f2c180 ffffe603`4cbeb280 fffff807`16917e30 00300030`0030002d : nt!PspSystemThreadStartup+0x55
ffff9280`ebc76c60 00000000`00000000 : ffff9280`ebc77000 ffff9280`ebc71000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VidMmInterface+214fd

MODULE_NAME: [/COLOR][COLOR=rgba(0, 0, 255, 1)]dxgmms2

[/COLOR][COLOR=rgba(30, 30, 30, 1)]IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.906

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 214fd

FAILURE_BUCKET_ID: AV_dxgmms2!VidMmInterface

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ef68a26f-67dc-d331-cae4-ef7e4fd01531}

Followup: MachineOwner
---------[/COLOR]

Continue reading...
 
Back
Top