[SOLVED] Anyone able to help with a BSOD dump file (i cant understand it) ?

[PickkleNickk]

Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\112421-10953-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
Machine Name:
Kernel base = 0xfffff80627200000 PsLoadedModuleList = 0xfffff80627e2a2d0
Debug session time: Wed Nov 24 10:55:12.383 2021 (UTC + 0:00)
System Uptime: 0 days 5:27:36.010
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
..................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806275f72a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff48ffd6b5420=000000000000000a
11: 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: 0000002dc4095b56, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 000000000000007b, 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: fffff80627417d2d, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2171

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2184

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

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

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


FILE_IN_CAB: 112421-10953-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: a

BUGCHECK_P1: 2dc4095b56

BUGCHECK_P2: ff

BUGCHECK_P3: 7b

BUGCHECK_P4: fffff80627417d2d

WRITE_ADDRESS: fffff80627efb390: 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
0000002dc4095b56

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: fffff48ffd6b5560 -- (.trap 0xfffff48ffd6b5560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000009 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80627417d2d rsp=fffff48ffd6b56f0 rbp=0000000000000000
r8=0000000000000001 r9=000000000000000a r10=0000fffff8062752
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
nt!PpmIdleExecuteTransition+0xaad:
fffff80627417d2d 897e14 mov dword ptr [rsi+14h],edi ds:0000000000000014=????????
Resetting default scope

STACK_TEXT:
fffff48ffd6b5418 fffff80627609269 : 000000000000000a 0000002dc4095b56 00000000000000ff 000000000000007b : nt!KeBugCheckEx
fffff48ffd6b5420 fffff80627605569 : fffff80627562fa0 fffff80627542b8b 0000000000000002 fffff806274fe579 : nt!KiBugCheckDispatch+0x69
fffff48ffd6b5560 fffff80627417d2d : ffffc90b89402050 0000000000000000 0000002dc4095b42 0000002dc4095b42 : nt!KiPageFault+0x469
fffff48ffd6b56f0 fffff80627417104 : 0000000000000000 00001f80004e007b 0000000000000003 0000000000000002 : nt!PpmIdleExecuteTransition+0xaad
fffff48ffd6b5af0 fffff806275fadc4 : ffffffff00000000 ffff9400bae0b340 ffffc90b922e6080 0000000000000c3c : nt!PoIdle+0x374
fffff48ffd6b5c60 0000000000000000 : fffff48ffd6b6000 fffff48ffd6b0000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x54


SYMBOL_NAME: nt!PpmIdleExecuteTransition+aad

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1348

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: aad

FAILURE_BUCKET_ID: AV_CODE_AV_nt!PpmIdleExecuteTransition

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner

 

[Colif]

i remember 6 years ago thinking IRQ errors are easy... i learned.

can be a driver or ram. No drivers mentioned in dump text but that is the norm, Dumps will at least show drivers running so I can start there.

1. Open Windows File Explore
   
2. Navigate to C:\Windows\Minidump
   
3. Copy the mini-dump files out onto your Desktop
   
4. Do not use Winzip, use the built in facility in Windows
   
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
   
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
   
7. Then post a link here to the zip file, so we can take a look for you . . .
   

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it