- Jan 8, 2022
- 5
- 0
- 10
I recently did a clean install of Windows 11 on my laptop, and hoped that it might resolve some of my previous issues. However, I still get blue screens when playing games. I suspect it is a RAM issue, however I don't want to pay for new RAM and repair without making sure. Minidump file is as follows:
Really hope someone can decipher anything important in the dumb file, I know I cant
Thanks in advance
Loading Dump File [C:\Windows\Minidump\010822-12390-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 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff800`26800000 PsLoadedModuleList = 0xfffff800`27429750
Debug session time: Sat Jan 8 17:21:40.937 2022 (UTC - 5:00)
System Uptime: 0 days 15:16:40.591
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
..........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`26c159c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff800f`2eca04d0=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: 0000000000006160, memory referenced
Arg2: 0000000000000002, 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: fffff80026a14fd6, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2858
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 18609
Key : Analysis.Init.CPU.mSec
Value: 436
Key : Analysis.Init.Elapsed.mSec
Value: 34337
Key : Analysis.Memory.CommitPeak.Mb
Value: 78
Key : WER.OS.Branch
Value: co_release
Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z
Key : WER.OS.Version
Value: 10.0.22000.1
FILE_IN_CAB: 010822-12390-01.dmp
BUGCHECK_CODE: a
BUGCHECK_P1: 6160
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff80026a14fd6
READ_ADDRESS: fffff80027505450: 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
0000000000006160
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Risk of Rain 2.exe
TRAP_FRAME: ffff800f2eca0610 -- (.trap 0xffff800f2eca0610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000614f
rdx=ffffd20b73c571c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80026a14fd6 rsp=ffff800f2eca07a0 rbp=ffff800f2eca0849
r8=ffffd20b520f8c30 r9=000000000000001e r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KiAbTryIncrementIoWaiterCounts+0x6:
fffff800`26a14fd6 80791100 cmp byte ptr [rcx+11h],0 ds:00000000`00006160=??
Resetting default scope
STACK_TEXT:
ffff800f`2eca04c8 fffff800`26c285a9 : 00000000`0000000a 00000000`00006160 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff800f`2eca04d0 fffff800`26c24700 : fffff800`22f3d000 ffffd20b`52174040 00000000`ffffffff 00000000`00000105 : nt!KiBugCheckDispatch+0x69
ffff800f`2eca0610 fffff800`26a14fd6 : fffff800`27535bc0 00000000`00000001 ffffd20b`73c570c0 fffff800`22cc8180 : nt!KiPageFault+0x440
ffff800f`2eca07a0 fffff800`26b34132 : fffff800`22cc8180 00000000`ffffffff 00000000`00000000 00000000`00000000 : nt!KiAbTryIncrementIoWaiterCounts+0x6
ffff800f`2eca07d0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff800`22cc8180 ffffd20b`73c570c0 : nt!KiAbProcessContextSwitch+0x242
SYMBOL_NAME: nt!KiAbTryIncrementIoWaiterCounts+6
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22000.376
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 6
FAILURE_BUCKET_ID: AV_nt!KiAbTryIncrementIoWaiterCounts
OS_VERSION: 10.0.22000.1
BUILDLAB_STR: co_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a14e8f1a-d7bc-4995-3770-3a2d50e87f2d}
Followup: MachineOwner
---------Really hope someone can decipher anything important in the dumb file, I know I cant
Thanks in advance
Facebook
Twitter
Instagram