S
stefanolongari
Hi all,
I have seen multiple replies on similar topics but couldn't find a solution that fixed it for me.
Specifically, that error happens always and only if I turn on an old version of WoW and I change the settings to fullscreen. If I do so, in a time between 1 to 20 seconds i get the BSOD. On newer games the issue doesn't persist.
I already re-installed the graphic drivers.
My setup is:
MSI b450 gaming plus max
Ryzen 5 3600
Radeon 5700
gskill Ripjaws 2x8gb
If someone could help me out pinpointing the problem I'd be extremely grateful.
Here's the latest BSOD minidump:
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Stefano\Downloads\091620-7546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff807`58600000 PsLoadedModuleList = 0xfffff807`58a460f0
Debug session time: Wed Sep 16 02:53:29.898 2020 (UTC + 2:00)
System Uptime: 0 days 0:01:20.568
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`587c2990 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff807`5d7f7620=000000000000000a
0: 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: 0000000000000020, 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: fffff807586506ea, address which referenced memory
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5749
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1OENUJK
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 67560
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: a
BUGCHECK_P1: 20
BUGCHECK_P2: 2
BUGCHECK_P3: 1
BUGCHECK_P4: fffff807586506ea
WRITE_ADDRESS: fffff80758b713b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80758a283b8: Unable to get Flags value from nt!KdVersionBlock
fffff80758a283b8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000020
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: fffff8075d7f7760 -- (.trap 0xfffff8075d7f7760)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000513662ad98 rbx=0000000000000000 rcx=ffffc5013ef46000
rdx=0000005100000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff807586506ea rsp=fffff8075d7f78f0 rbp=fffff8075d7f79f0
r8=0000000000000000 r9=0000000000000000 r10=ffffc5014a685f88
r11=fffff8075d7f7b10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KiExecuteAllDpcs+0x2ea:
fffff807`586506ea 49894720 mov qword ptr [r15+20h],rax ds:00000000`00000020=????????????????
Resetting default scope
STACK_TEXT:
fffff807`5d7f7618 fffff807`587d4829 : 00000000`0000000a 00000000`00000020 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff807`5d7f7620 fffff807`587d0b69 : 00000000`00000000 00000000`00000002 ffffc501`490c6000 fffff807`6e8d9597 : nt!KiBugCheckDispatch+0x69
fffff807`5d7f7760 fffff807`586506ea : fffff807`55656f80 ffffc501`400da000 fffff807`5d7f78a8 00000000`00000002 : nt!KiPageFault+0x469
fffff807`5d7f78f0 fffff807`5864fd5f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x2ea
fffff807`5d7f7a30 fffff807`587c64be : 00000000`00000000 fffff807`55654180 fffff807`58b8f400 ffffc501`51bf5080 : nt!KiRetireDpcList+0x1ef
fffff807`5d7f7c60 00000000`00000000 : fffff807`5d7f8000 fffff807`5d7f2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7e
SYMBOL_NAME: nt!KiExecuteAllDpcs+2ea
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.1082
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 2ea
FAILURE_BUCKET_ID: AV_nt!KiExecuteAllDpcs
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {b88a28a0-fcde-99e9-6174-619833d00ab9}
Followup: MachineOwner
---------
Continue reading...
I have seen multiple replies on similar topics but couldn't find a solution that fixed it for me.
Specifically, that error happens always and only if I turn on an old version of WoW and I change the settings to fullscreen. If I do so, in a time between 1 to 20 seconds i get the BSOD. On newer games the issue doesn't persist.
I already re-installed the graphic drivers.
My setup is:
MSI b450 gaming plus max
Ryzen 5 3600
Radeon 5700
gskill Ripjaws 2x8gb
If someone could help me out pinpointing the problem I'd be extremely grateful.
Here's the latest BSOD minidump:
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Stefano\Downloads\091620-7546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff807`58600000 PsLoadedModuleList = 0xfffff807`58a460f0
Debug session time: Wed Sep 16 02:53:29.898 2020 (UTC + 2:00)
System Uptime: 0 days 0:01:20.568
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`587c2990 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff807`5d7f7620=000000000000000a
0: 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: 0000000000000020, 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: fffff807586506ea, address which referenced memory
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5749
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1OENUJK
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 67560
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: a
BUGCHECK_P1: 20
BUGCHECK_P2: 2
BUGCHECK_P3: 1
BUGCHECK_P4: fffff807586506ea
WRITE_ADDRESS: fffff80758b713b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80758a283b8: Unable to get Flags value from nt!KdVersionBlock
fffff80758a283b8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000020
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: fffff8075d7f7760 -- (.trap 0xfffff8075d7f7760)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000513662ad98 rbx=0000000000000000 rcx=ffffc5013ef46000
rdx=0000005100000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff807586506ea rsp=fffff8075d7f78f0 rbp=fffff8075d7f79f0
r8=0000000000000000 r9=0000000000000000 r10=ffffc5014a685f88
r11=fffff8075d7f7b10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KiExecuteAllDpcs+0x2ea:
fffff807`586506ea 49894720 mov qword ptr [r15+20h],rax ds:00000000`00000020=????????????????
Resetting default scope
STACK_TEXT:
fffff807`5d7f7618 fffff807`587d4829 : 00000000`0000000a 00000000`00000020 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff807`5d7f7620 fffff807`587d0b69 : 00000000`00000000 00000000`00000002 ffffc501`490c6000 fffff807`6e8d9597 : nt!KiBugCheckDispatch+0x69
fffff807`5d7f7760 fffff807`586506ea : fffff807`55656f80 ffffc501`400da000 fffff807`5d7f78a8 00000000`00000002 : nt!KiPageFault+0x469
fffff807`5d7f78f0 fffff807`5864fd5f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x2ea
fffff807`5d7f7a30 fffff807`587c64be : 00000000`00000000 fffff807`55654180 fffff807`58b8f400 ffffc501`51bf5080 : nt!KiRetireDpcList+0x1ef
fffff807`5d7f7c60 00000000`00000000 : fffff807`5d7f8000 fffff807`5d7f2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7e
SYMBOL_NAME: nt!KiExecuteAllDpcs+2ea
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.1082
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 2ea
FAILURE_BUCKET_ID: AV_nt!KiExecuteAllDpcs
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {b88a28a0-fcde-99e9-6174-619833d00ab9}
Followup: MachineOwner
---------
Continue reading...