[SOLVED] Windows 10 BSOD irql minidumps attached

thecontact

Reputable
Nov 3, 2019
13
0
4,520
Hi all,
So I was playing Skyrim. Then I got a BSOD with irql_not_less_or_equal error. Then it happened again.
Here you can download the .dmp files. But I did the analyze think and below you can see the reports.
Do you know what caused the crashes?

Thanks.

Code:
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: 0000000000000000, memory referenced
Arg2: 00000000000000ff, 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: fffff8055a63a81a, address which referenced memory

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4686

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-V0D1APA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 8447

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  a

BUGCHECK_P1: 0

BUGCHECK_P2: ff

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8055a63a81a

READ_ADDRESS: fffff8055b0fa388: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8055b00f2a8: Unable to get Flags value from nt!KdVersionBlock
fffff8055b00f2a8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000000

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffffe38e5f84f720 -- (.trap 0xffffe38e5f84f720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=33df8a6049b00000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8055a63a81a rsp=ffffe38e5f84f8b0 rbp=ffffe38e5f84f860
r8=ffffe38e5f84fa10  r9=0000000000000000 r10=fffff8055a400000
r11=ffffe38e5f84fa10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na po nc
nt!KiExecuteAllDpcs+0x46a:
fffff805`5a63a81a 5e              pop     rsi
Resetting default scope

STACK_TEXT: 
ffffe38e`5f84f5d8 fffff805`5a7efa29     : 00000000`0000000a 00000000`00000000 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
ffffe38e`5f84f5e0 fffff805`5a7ebd29     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffe38e`5f84f720 fffff805`5a63a81a     : ffffbc80`cd24b240 00000000`00000008 ffffe38e`5f84f9d0 fffff805`5a6399a4 : nt!KiPageFault+0x469
ffffe38e`5f84f8b0 fffff805`5a6399a4     : 00000000`00000000 00000000`00000000 00000000`00000008 00000000`00000000 : nt!KiExecuteAllDpcs+0x46a
ffffe38e`5f84f8d0 fffff805`5a7e16ce     : 00000000`00000000 ffffbc80`cd240180 ffffbc80`cd24b240 ffffd10f`e1018080 : nt!KiRetireDpcList+0x1f4
ffffe38e`5f84fb60 00000000`00000000     : ffffe38e`5f850000 ffffe38e`5f849000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  nt!KiExecuteAllDpcs+46a

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.388

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  46a

FAILURE_BUCKET_ID:  AV_nt!KiExecuteAllDpcs

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b88a28a0-fcde-99e9-6174-619833d00ab9}

Followup:     MachineOwner


Code:
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: 000000000000008e, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000073, 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: fffff8026c6cc811, address which referenced memory

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4046

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-V0D1APA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 21555

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  a

BUGCHECK_P1: 8e

BUGCHECK_P2: ff

BUGCHECK_P3: 73

BUGCHECK_P4: fffff8026c6cc811

WRITE_ADDRESS: fffff8026d0fa388: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8026d00f2a8: Unable to get Flags value from nt!KdVersionBlock
fffff8026d00f2a8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
000000000000008e

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80272e6c490 -- (.trap 0xfffff80272e6c490)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000989
rdx=0000000000000004 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8026c6cc811 rsp=fffff80272e6c620 rbp=0000000000000000
r8=0000000000000000  r9=0000000003d9dad5 r10=0001d3d25117ff71
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na pe nc
nt!PpmIdleExecuteTransition+0x661:
fffff802`6c6cc811 80bb8d00000001  cmp     byte ptr [rbx+8Dh],1 ds:00000000`0000008d=??
Resetting default scope

STACK_TEXT:
fffff802`72e6c348 fffff802`6c7efa29     : 00000000`0000000a 00000000`0000008e 00000000`000000ff 00000000`00000073 : nt!KeBugCheckEx
fffff802`72e6c350 fffff802`6c7ebd29     : 00000000`00000002 0000143f`95e83ae1 0000007b`00000001 fffff802`6c72b537 : nt!KiBugCheckDispatch+0x69
fffff802`72e6c490 fffff802`6c6cc811     : 00000000`0000567c 000a7fad`0000005f 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x469
fffff802`72e6c620 fffff802`6c6cc034     : 00000000`00000000 00001f80`00000000 00000000`00000000 00000000`00000002 : nt!PpmIdleExecuteTransition+0x661
fffff802`72e6c9f0 fffff802`6c7e1684     : 00000000`00000000 fffff802`6d126600 ffff990b`1924c040 00000000`00000164 : nt!PoIdle+0x374
fffff802`72e6cb60 00000000`00000000     : fffff802`72e6d000 fffff802`72e66000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54


SYMBOL_NAME:  nt!PpmIdleExecuteTransition+661

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.388

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  661

FAILURE_BUCKET_ID:  AV_CODE_AV_nt!PpmIdleExecuteTransition

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3d77750b-80a6-c195-659c-ebcffecd3d05}

Followup:     MachineOwner
---------
 
Solution
clean install is the hammer approach, I prefer to fix things without wiping all the evidence and starting again.
Driver verifer might have helped, I have instructions for it to reduce the possible pain it can cause. Its a tool made by Microsoft that can break windows. Good job guys.

Colif

Win 11 Master
Moderator
minidump conversion - https://jsfiddle.net/1tx5bp8d/show
I can't tell what cause was directly but irq errors can often be drivers, so I look at old ones.
Do you use Intel WIFI?
there might be new drivers for it, try running the Intel software updater - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html

I would love to offer you a newer Killer ethernet driver but since Intel bought them out last year, they only support Intel products now. I was sad when I discovered that.

Probably new Realtek Audio drivers as well.
 

thecontact

Reputable
Nov 3, 2019
13
0
4,520
@Colif Just got another bsod with a different code. Minidump here. Couldn't update the driver yet. But this time error was SYSTEM_SERVICE_EXCEPTION (dxgmms2.sys). I hope it helps. Do you still think that its related to my realtek driver?
 

gardenman

Splendid
Moderator
I'm going to post this info so Colif can look at it later.

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/rnjx21mk/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:012221-5250-01.dmp (Jan 21 2021 - 18:00:34)
Bugcheck:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:memory_corruption (Process: System)
Uptime:2 Day(s), 4 Hour(s), 42 Min(s), and 18 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 11 Master
Moderator
@Colif Just got another bsod with a different code. Minidump here. Couldn't update the driver yet. But this time error was SYSTEM_SERVICE_EXCEPTION (dxgmms2.sys). I hope it helps. Do you still think that its related to my realtek driver?
No, that one looks a lot like the GPU drivers.
especially with Gardenmans conversion
below text runs in reverse, bottom was the first thing that happened
STACK_TEXT:
fffff1859d9df940 fffff8016616b6d2 : 0000000000000000 0000000000989680 ffffda0fd0d24000 ffffda0fd0d24000 : dxgmms2!VidSchiCheckNodeTimeout+0xaa
fffff1859d9df950 fffff801660fa8df : 0000000000000000 0000000000000000 0000000000989680 ffffda0fd0d24000 : dxgmms2!VidSchiCheckHwProgress+0x132
fffff1859d9df9c0 fffff80166178a55 : ffffda0fd9fc6000 ffffda0fd0d24000 ffffda0fd9fc6010 ffffda0fd466b920 : dxgmms2!VidSchiScheduleCommandToRun+0x4f
fffff1859d9dfa80 fffff80166178a0a : ffffda0fd0d24400 fffff80166178940 ffffda0fd0d24000 ffffc280e2940100 : dxgmms2!VidSchiRun_PriorityTable+0x35
fffff1859d9dfad0 fffff8014b146735 : ffffda0fd02220c0 fffff80100000001 ffffda0fd0d24000 000fa4efbd9bbfff : dxgmms2!VidSchiWorkerThread+0xca

dxgmms2.sys = DirectX
99% of the time I see DirectX crash its GPU drivers. The 1% is audio but I think this time its just a coincidence you were doing anything with the Audio.
Try running DDU and reinstall Nvidia drivers - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/
 

thecontact

Reputable
Nov 3, 2019
13
0
4,520
Reinstalling drivers didn't fix the issue. Still having BSOD's. I really appreciate your time. Thanks @Colif and @gardenman .
As I googled the BSOD's I come up with lots of threads about it but not a single solution. So I think there is no point to investigate this issue. I will try my luck with format and a clean installation. Microsoft support team recommended using driver verifier but looks like they are out of options too.
 

Colif

Win 11 Master
Moderator
clean install is the hammer approach, I prefer to fix things without wiping all the evidence and starting again.
Driver verifer might have helped, I have instructions for it to reduce the possible pain it can cause. Its a tool made by Microsoft that can break windows. Good job guys.
 
Solution

TRENDING THREADS