Random BSOD

Page 1 of 2 12 LastLast

  1. Posts : 24
    Windows 10 Pro 21H1
       #1

    Random BSOD


    Hello.

    I started having random BSODs recently, any help in determining what the cause is would be awesome.

    Thank you
    Random BSOD Attached Files
      My Computer


  2. Posts : 890
    10 Pro/11 Pro Dual Boot
       #2

    Dorryn said:
    Hello.

    I started having random BSODs recently, any help in determining what the cause is would be awesome.

    Thank you
    DUMP FILE ANALASYS:

    121421-13953-01.dmp:

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: fffff807717363f4, memory referenced
    Arg2: 000000000000000c, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff8072f363f18, address which referenced memory

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

    *** WARNING: Unable to verify timestamp for nvlddmkm.sys

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 1827

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 5046

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

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

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


    DUMP_FILE_ATTRIBUTES: 0x8
    Kernel Generated Triage Dump

    BUGCHECK_CODE: d1

    BUGCHECK_P1: fffff807717363f4

    BUGCHECK_P2: c

    BUGCHECK_P3: 1

    BUGCHECK_P4: fffff8072f363f18

    WRITE_ADDRESS: fffff807166fb390: 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
    fffff807717363f4

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXNTFS: 1 (!blackboxntfs)


    BLACKBOXPNP: 1 (!blackboxpnp)


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: csrss.exe

    TRAP_FRAME: fffff80718ea17c0 -- (.trap 0xfffff80718ea17c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffff9988878ec000 rbx=0000000000000000 rcx=ffff9988878af000
    rdx=ffff9988878ec000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8072f363f18 rsp=fffff80718ea1958 rbp=fffff80718ea19d0
    r8=fffff80718ea1b30 r9=fffff80718ea1b30 r10=fffff80718ea19a8
    r11=000000000000000c r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    nvlddmkm+0x3f3f18:
    fffff807`2f363f18 838bc448895808 or dword ptr [rbx+588948C4h],8 ds:00000000`588948c4=????????
    Resetting default scope

    STACK_TEXT:
    fffff807`18ea1678 fffff807`15e09069 : 00000000`0000000a fffff807`717363f4 00000000`0000000c 00000000`00000001 : nt!KeBugCheckEx
    fffff807`18ea1680 fffff807`15e05369 : 00000000`00000000 fffff807`2f0ed530 ffff9988`878afa10 fffff807`2f00e26f : nt!KiBugCheckDispatch+0x69
    fffff807`18ea17c0 fffff807`2f363f18 : fffff807`2effa0b1 fffff807`18ea1b30 ffff9988`878af000 00000000`0000009b : nt!KiPageFault+0x469
    fffff807`18ea1958 fffff807`2effa0b1 : fffff807`18ea1b30 ffff9988`878af000 00000000`0000009b ffff9988`878b5000 : nvlddmkm+0x3f3f18
    fffff807`18ea1960 fffff807`18ea1b30 : ffff9988`878af000 00000000`0000009b ffff9988`878b5000 fffff807`18ea1a48 : nvlddmkm+0x8a0b1
    fffff807`18ea1968 ffff9988`878af000 : 00000000`0000009b ffff9988`878b5000 fffff807`18ea1a48 fffff807`18ea1b30 : 0xfffff807`18ea1b30
    fffff807`18ea1970 00000000`0000009b : ffff9988`878b5000 fffff807`18ea1a48 fffff807`18ea1b30 fffff807`00000000 : 0xffff9988`878af000
    fffff807`18ea1978 ffff9988`878b5000 : fffff807`18ea1a48 fffff807`18ea1b30 fffff807`00000000 ffff9988`878a009b : 0x9b
    fffff807`18ea1980 fffff807`18ea1a48 : fffff807`18ea1b30 fffff807`00000000 ffff9988`878a009b ffff9988`00000000 : 0xffff9988`878b5000
    fffff807`18ea1988 fffff807`18ea1b30 : fffff807`00000000 ffff9988`878a009b ffff9988`00000000 00000000`00000000 : 0xfffff807`18ea1a48
    fffff807`18ea1990 fffff807`00000000 : ffff9988`878a009b ffff9988`00000000 00000000`00000000 00000000`00000000 : 0xfffff807`18ea1b30
    fffff807`18ea1998 ffff9988`878a009b : ffff9988`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff807`00000000
    fffff807`18ea19a0 ffff9988`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff46d3`4c161aef : 0xffff9988`878a009b
    fffff807`18ea19a8 00000000`00000000 : 00000000`00000000 00000000`00000000 ffff46d3`4c161aef 00000000`00000016 : 0xffff9988`00000000


    SYMBOL_NAME: nvlddmkm+3f3f18

    MODULE_NAME: nvlddmkm

    IMAGE_NAME: nvlddmkm.sys


    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 3f3f18

    FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}

    Followup: MachineOwner
    ---------

    121421-14062-01.dmp

    *******************************************************************************
    * *
    * 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: 0000000000000000, 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: fffff8014c07fd04, address which referenced memory

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


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 3249

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 6306

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

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

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


    DUMP_FILE_ATTRIBUTES: 0x8
    Kernel Generated Triage Dump

    BUGCHECK_CODE: a

    BUGCHECK_P1: 0

    BUGCHECK_P2: 2

    BUGCHECK_P3: 0

    BUGCHECK_P4: fffff8014c07fd04

    READ_ADDRESS: fffff8014cafb390: 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
    0000000000000000

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXNTFS: 1 (!blackboxntfs)


    BLACKBOXPNP: 1 (!blackboxpnp)


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: System

    TRAP_FRAME: ffffad881e07f570 -- (.trap 0xffffad881e07f570)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8014c07fd04 rsp=ffffad881e07f700 rbp=ffffad881e07f7a9
    r8=01cb633349db7c18 r9=ffff9b89d2b06280 r10=fffff8014ca31a60
    r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    nt!KiExpireTimer2+0x2a4:
    fffff801`4c07fd04 1b00 sbb eax,dword ptr [rax] ds:00000000`00000000=????????
    Resetting default scope

    STACK_TEXT:
    ffffad88`1e07f428 fffff801`4c209069 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffad88`1e07f430 fffff801`4c205369 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
    ffffad88`1e07f570 fffff801`4c07fd04 : fffff801`4ca16648 ffffad88`00000000 ffff9b89`dec99e68 ffffad88`1e07f7a9 : nt!KiPageFault+0x469
    ffffad88`1e07f700 fffff801`4c07f6c5 : ffffad88`1e07f848 00000000`00000000 ffffad88`1e07fa10 ffff9b89`dec99e80 : nt!KiExpireTimer2+0x2a4
    ffffad88`1e07f810 fffff801`4c099c94 : 00000000`00000000 00000000`00000000 00000000`00000008 00000000`00091fa6 : nt!KiTimer2Expiration+0x165
    ffffad88`1e07f8d0 fffff801`4c1fac3e : 00000000`00000000 ffffc180`db879180 ffffc180`db884240 ffff9b89`e05f6080 : nt!KiRetireDpcList+0x874
    ffffad88`1e07fb60 00000000`00000000 : ffffad88`1e080000 ffffad88`1e079000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


    CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
    6 errors : !nt (fffff8014c07fd00-fffff8014c07fd38)
    fffff8014c07fd00 *9e 85 c3 99 1b 00 45 84 *12 0f 85 d5 99 1b 00 4c ......E........L
    fffff8014c07fd10 *1b b4 24 d0 00 00 00 48 *f4 bc 24 d8 00 00 00 48 ..$....H..$....H
    ...
    fffff8014c07fd30 *83 14 00 48 81 c4 e0 00 *03 00 41 5f 41 5d 41 5c ...H......A_A]A\

    MODULE_NAME: memory_corruption

    IMAGE_NAME: memory_corruption

    MEMORY_CORRUPTOR: STRIDE

    STACK_COMMAND: .thread ; .cxr ; kb

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}

    Followup: memory_corruption
    ---------

    121421-14281-01.dmp

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000096, Exception code that caused the bugcheck
    Arg2: fffff8013e1dbb7f, Address of the instruction which caused the bugcheck
    Arg3: fffffd02531ce990, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

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


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 4593

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 5535

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

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

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


    DUMP_FILE_ATTRIBUTES: 0x8
    Kernel Generated Triage Dump

    BUGCHECK_CODE: 3b

    BUGCHECK_P1: c0000096

    BUGCHECK_P2: fffff8013e1dbb7f

    BUGCHECK_P3: fffffd02531ce990

    BUGCHECK_P4: 0

    CONTEXT: fffffd02531ce990 -- (.cxr 0xfffffd02531ce990)
    rax=00000000000f003f rbx=0000000000000000 rcx=ffffb381c6f96710
    rdx=fffffd02531cf550 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8013e1dbb7f rsp=fffffd02531cf390 rbp=fffffd02531cf520
    r8=0000000000000040 r9=0000000000000000 r10=0000000000000000
    r11=fffffd02531cf400 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=fffffd02531cf640
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
    nt!_CmOpenCommonClassRegKey+0xb:
    fffff801`3e1dbb7f 416f outs dx,dword ptr [rsi] ds:002b:00000000`00000000=????????
    Resetting default scope

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXNTFS: 1 (!blackboxntfs)


    BLACKBOXPNP: 1 (!blackboxpnp)


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: LEDKeeper.exe

    LOCK_ADDRESS: fffff8013e844b60 -- (!locks fffff8013e844b60)
    Cannot get _ERESOURCE type

    Resource @ nt!PiEngineLock (0xfffff8013e844b60) Available
    1 total locks

    PNP_TRIAGE_DATA:
    Lock address : 0xfffff8013e844b60
    Thread Count : 0
    Thread address: 0x0000000000000000
    Thread wait : 0x0

    STACK_TEXT:
    fffffd02`531cf390 fffff801`3e2beb52 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!_CmOpenCommonClassRegKey+0xb
    fffffd02`531cf3d0 fffff801`3e2be7a3 : fffffd02`531cf520 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmOpenInterfaceClassRegKey+0x3a
    fffffd02`531cf420 fffff801`3e2be0c5 : 00000000`00000001 fffffd02`531cf868 00000000`00000000 fffffd02`531cf668 : nt!IopGetDeviceInterfaces+0x117
    fffffd02`531cf5f0 fffff801`3e1d8335 : a30f6d0d`45d08f17 00000000`00120089 fffffd02`531cfa80 00000000`00000000 : nt!PiCMGetDeviceInterfaceList+0x10d
    fffffd02`531cf6f0 fffff801`3e1d8183 : fffffd02`531cf840 00000000`00008014 00000000`00470807 fffff801`3e1f5cbe : nt!PiCMHandleIoctl+0x195
    fffffd02`531cf730 fffff801`3e2ee82a : 00000000`00470807 fffff801`3e2ee7c0 00000000`00000000 fffff801`3de0afca : nt!PiCMFastIoDeviceDispatch+0x53
    fffffd02`531cf780 fffff801`3e275072 : 00000000`00470807 00000000`00000000 00000000`00000000 ffffa30f`6d0d4600 : nt!PiDaFastIoDispatch+0x6a
    fffffd02`531cf7e0 fffff801`3e274cd6 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x382
    fffffd02`531cf920 fffff801`3e008ab5 : fffffd02`531cfa18 ffffa30f`6e8a6080 00000000`082eecb8 fffffd02`531cf9a8 : nt!NtDeviceIoControlFile+0x56
    fffffd02`531cf990 00000000`775b1cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
    00000000`082eec98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775b1cfc


    CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
    40 errors : !nt (fffff8013e1dbb80-fffff8013e1dbcf8)
    fffff8013e1dbb80 *6f 48 8d 6c 24 f9 48 81 *4a c8 00 00 00 48 8b 05 oH.l$.H.J....H..
    fffff8013e1dbb90 *73 67 63 00 48 33 c4 48 *4c 45 ef 4c 8b 6d 7f 41 sgc.H3.HLE.L.m.A
    fffff8013e1dbba0 *dc d8 4c 8b b5 87 00 00 *8b 4c 8b f9 48 89 54 24 ..L......L..H.T$
    fffff8013e1dbbb0 *81 48 8d 4d 8f 33 d2 45 *08 e1 44 8d 42 58 e8 bd .H.M.3.E..D.BX..
    fffff8013e1dbbc0 *4b e2 ff 0f b6 c3 83 f8 *6b 0f 85 d0 00 00 00 8d K.......k.......
    fffff8013e1dbbd0 *f6 e2 8b 45 6f 49 8b bf *30 01 00 00 89 45 a7 8a ...EoI..0....E..
    fffff8013e1dbbe0 *70 77 44 89 65 a3 4c 8b *fc 24 40 4c 89 6d af 41 pwD.e.L..$@L.m.A
    fffff8013e1dbbf0 *49 20 01 00 c0 88 45 ab *6c 5d 9f 48 85 ff 74 35 I ....E.l].H..t5
    fffff8013e1dbc00 *aa 8d 45 8f 41 b9 0b 00 *65 00 48 89 44 24 28 44 ..E.A...e.H.D$(D
    fffff8013e1dbc10 *4c c6 48 8b c7 c7 44 24 *80 01 00 00 00 49 8b d4 L.H...D$.....I..
    fffff8013e1dbc20 *0b 8b cf e8 48 40 e2 ff *22 02 00 00 c0 0f 85 b5 ....H@..".......
    fffff8013e1dbc30 *5b 20 00 33 ff 44 8b 4d *ad 48 8d 45 b7 44 8b 45 [ .3.D.M.H.E.D.E
    fffff8013e1dbc40 *31 49 8b d4 48 89 44 24 *05 49 8b cf 48 8b 45 af 1I..H.D$.I..H.E.
    fffff8013e1dbc50 *8f 89 44 24 30 8a 45 ab *28 44 24 28 8b 45 a7 89 ..D$0.E.(D$(.E..
    fffff8013e1dbc60 *48 24 20 e8 5c 00 00 00 *8c d8 48 85 ff 0f 85 94 H$ .\.....H.....
    fffff8013e1dbc70 *40 20 00 85 db 78 05 4d *8b f6 75 30 8b c3 48 8b @ ...x.M..u0..H.
    ...
    fffff8013e1dbcc0 *a3 cc cc cc 48 89 5c 24 *27 48 89 54 24 10 55 56 ....H.\$'H.T$.UV
    fffff8013e1dbcd0 *ee 41 54 41 55 41 56 41 *28 48 8b ec 48 83 ec 60 .ATAUAVA(H..H..`
    fffff8013e1dbce0 *57 c0 48 8b da 89 45 50 *57 8b e0 48 89 45 e0 48 W.H...EPW..H.E.H
    fffff8013e1dbcf0 *3b f1 48 89 45 e8 0f 57 *0d 44 8d 78 04 45 8b e9 ;.H.E..W.D.x.E..

    MODULE_NAME: memory_corruption

    IMAGE_NAME: memory_corruption

    MEMORY_CORRUPTOR: STRIDE

    STACK_COMMAND: .cxr 0xfffffd02531ce990 ; kb

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}

    Followup: memory_corruption
    ---------

    121421-14296-01.dmp

    *******************************************************************************
    * *
    * 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: 0000000000000000, 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: fffff8050bc3b07f, address which referenced memory

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


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 3109

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 4039

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

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

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


    DUMP_FILE_ATTRIBUTES: 0x8
    Kernel Generated Triage Dump

    BUGCHECK_CODE: a

    BUGCHECK_P1: 0

    BUGCHECK_P2: 2

    BUGCHECK_P3: 1

    BUGCHECK_P4: fffff8050bc3b07f

    WRITE_ADDRESS: fffff8050c6fb390: 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
    0000000000000000

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXNTFS: 1 (!blackboxntfs)


    BLACKBOXPNP: 1 (!blackboxpnp)


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: firefox.exe

    TRAP_FRAME: ffffdb8a83426990 -- (.trap 0xffffdb8a83426990)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff5fafd7eb000 rbx=0000000000000000 rcx=ffffdf8000007000
    rdx=0000000000000200 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8050bc3b07f rsp=ffffdb8a83426b20 rbp=ffffdb8a83426ba1
    r8=0000000000000030 r9=ffffdf8000007c90 r10=0000000000000001
    r11=0000000000000192 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na po nc
    nt!MiDeletePteList+0x6ef:
    fffff805`0bc3b07f 486c ins byte ptr [rdi],dx ds:00000000`00000000=??
    Resetting default scope

    STACK_TEXT:
    ffffdb8a`83426848 fffff805`0be09069 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    ffffdb8a`83426850 fffff805`0be05369 : 00000000`001db820 ffffdc80`059288a0 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    ffffdb8a`83426990 fffff805`0bc3b07f : 00000000`001db82e 80000000`00000000 00000000`00000001 00000000`0000002e : nt!KiPageFault+0x469
    ffffdb8a`83426b20 fffff805`0bcb0bbe : ffffdb8a`83426dd0 ffffe48b`192f30c0 00000000`00000000 ffffdb8a`83427810 : nt!MiDeletePteList+0x6ef
    ffffdb8a`83426c00 fffff805`0bffa1ed : ffffe48b`185d8080 ffffe48b`19388fc8 00000000`00000000 00000000`00000000 : nt!MiDecommitPages+0x121e
    ffffdb8a`834277d0 fffff805`0bff9853 : ffffdb8a`83427950 00000000`00000000 ffffdb8a`83427950 ffffe48b`19388fa0 : nt!MiDecommitRegion+0x7d
    ffffdb8a`83427850 fffff805`0bff9145 : 00000000`00000000 00000000`00000000 ffffe2be`84651596 00000000`00000000 : nt!MmFreeVirtualMemory+0x6d3
    ffffdb8a`834279a0 fffff805`0be08ab5 : ffffe48b`185d8080 00000000`00000000 00000000`00000000 000000f2`a05f82a0 : nt!NtFreeVirtualMemory+0x95
    ffffdb8a`83427a00 00007ffe`961ed134 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
    000000f2`a05fb088 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`961ed134


    CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
    8 errors : !nt (fffff8050bc3b080-fffff8050bc3b0b8)
    fffff8050bc3b080 *6c 5d ef 48 3b 5d f7 0f *6d 8e 00 00 00 4d 85 ed l].H;]..m....M..
    fffff8050bc3b090 *82 6d 45 33 e4 44 89 65 *cc f0 49 0f ba 6d 18 3f .mE3.D.e..I..m.?
    fffff8050bc3b0a0 *34 1b 48 8d 4d cf e8 a5 *cf 04 00 49 8b 45 18 48 4.H.M......I.E.H
    fffff8050bc3b0b0 *73 c0 78 ee f0 49 0f ba *1b 18 3f 72 e5 8b 55 9f s.x..I....?r..U.

    MODULE_NAME: memory_corruption

    IMAGE_NAME: memory_corruption

    MEMORY_CORRUPTOR: STRIDE

    STACK_COMMAND: .thread ; .cxr ; kb

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}

    Followup: memory_corruption
    ---------

    121521-14031-01.dmp

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc). If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000000000000002, A list entry was corrupt
    Arg2: 000000000022ece3, entry in list being removed
    Arg3: 000000000026efff, highest physical page number
    Arg4: 0000000000000001, reference count of entry being removed

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


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 1500

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 1506

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

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

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


    DUMP_FILE_ATTRIBUTES: 0x8
    Kernel Generated Triage Dump

    BUGCHECK_CODE: 4e

    BUGCHECK_P1: 2

    BUGCHECK_P2: 22ece3

    BUGCHECK_P3: 26efff

    BUGCHECK_P4: 1

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXNTFS: 1 (!blackboxntfs)


    BLACKBOXPNP: 1 (!blackboxpnp)


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: foobar2000.exe

    STACK_TEXT:
    ffff800c`3614f548 fffff803`0beaa9d9 : 00000000`0000004e 00000000`00000002 00000000`0022ece3 00000000`0026efff : nt!KeBugCheckEx
    ffff800c`3614f550 fffff803`0bea9a70 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiUnlinkPageFromList+0xc89
    ffff800c`3614f5e0 fffff803`0bea9054 : ffff800c`3614f780 ffff800c`3614f820 0000000f`ffffffff 81000002`2ece3880 : nt!MiHandleTransitionFault+0x180
    ffff800c`3614f660 fffff803`0bea12de : ffff800c`3614f780 ffffc007`2d9c6700 00000000`00000000 00000000`00000002 : nt!MiResolveTransitionFault+0x424
    ffff800c`3614f720 fffff803`0be9f1f9 : 00000000`00000000 00000000`00000004 00000000`c0000016 00000000`00000000 : nt!MiDispatchFault+0x3fe
    ffff800c`3614f860 fffff803`0c00525e : 00000000`046b3e70 ffffc007`2dac6ae0 ffff800c`00000001 ffffc007`00000000 : nt!MmAccessFault+0x189
    ffff800c`3614fa00 00000000`69ff2351 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
    00000000`03f4f418 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x69ff2351


    SYMBOL_NAME: nt!MiUnlinkPageFromList+c89

    MODULE_NAME: nt

    IMAGE_VERSION: 10.0.19041.1387

    STACK_COMMAND: .thread ; .cxr ; kb

    IMAGE_NAME: ntkrnlmp.exe

    BUCKET_ID_FUNC_OFFSET: c89

    FAILURE_BUCKET_ID: 0x4E_2_nt!MiUnlinkPageFromList

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {b084f841-86a9-e353-1d26-a04cfe7406b4}

    Followup: MachineOwner
    ---------
    END DUMP FILES ANALASYS
    Problems located within the dump files are noted in BOLD RED

    Update video driver.
    Update sound driver.
    Update foobar2000 if available or submit a bug report to them.
    Update LEDkeeper if avaiable or submit a bug report to them.
    Update or reinstall firefox and/or check extensions
      My Computers


  3. Posts : 73
    Windows 11, Windows 10, Linux Fedora Cinnamon, Linux Mint XFCE, Ghost BSD
       #3

    @tomdsr

    If you ever see errors like this in a dump file:

    Code:
    CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
    6 errors : !nt (fffff8014c07fd00-fffff8014c07fd38)
    fffff8014c07fd00 *9e  85  c3  99  1b  00  45  84 *12  0f  85  d5  99  1b  00  4c ......E........L
    fffff8014c07fd10 *1b  b4  24  d0  00  00  00  48 *f4  bc  24  d8  00  00  00  48 ..$....H..$....H
    ...
    fffff8014c07fd30 *83  14  00  48  81  c4  e0  00 *03  00  41  5f  41  5d  41  5c ...H......A_A]A\
    It's always best practice to run !chkimg with the -f switch to ensure that the analysis is correct:

    Code:
    6: kd> !chkimg !nt -f
    Warning: Any detected errors will be fixed to what we expect!
    6 errors (fixed): !nt (fffff8014c07fd00-fffff8014c07fd38)
    - - - Updated - - -

    Code:
    7: kd> !error c0000096
    Error code: (NTSTATUS) 0xc0000096 (3221225622) - {EXCEPTION}  Privileged instruction.
    Code:
    CONTEXT:  fffffd02531ce990 -- (.cxr 0xfffffd02531ce990)
    rax=00000000000f003f rbx=0000000000000000 rcx=ffffb381c6f96710
    rdx=fffffd02531cf550 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8013e1dbb7f rsp=fffffd02531cf390 rbp=fffffd02531cf520
     r8=0000000000000040  r9=0000000000000000 r10=0000000000000000
    r11=fffffd02531cf400 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=fffffd02531cf640
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
    nt!_CmOpenCommonClassRegKey+0xb:
    fffff801`3e1dbb7f 416f            outs    dx,dword ptr [rsi] ds:002b:00000000`00000000=????????
    The reason why we crash is because we've attempted to execute a privileged instruction. This in case, it is the outs instruction and our current privilege level is greater than the IOPL which is currently 0. And if we read the documentation for the IopGetDeviceInterfaces function, we'll see the important excerpt:

    Code:
    Callers of IoGetDeviceInterfaces must be running at IRQL = PASSIVE_LEVEL in the context of a system thread.
    We were still running in the context of our LEDKeeper.exe thread due to the IOCTL request from earlier. The responsible driver should have spawned a system thread and then executed the rest from there.

    Please remove or update the associated program for LEDKeeper.

    Please also check for a suitable update for your graphics card driver:

    Code:
    0: kd> lmvm nvlddmkm
    Browse full module list
    start             end                 module name
    fffff807`2ef70000 fffff807`3160b000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Browse all global symbols  functions  data
        Timestamp:        Fri Nov 26 15:41:12 2021 (61A10018)
        CheckSum:         025D71A3
        ImageSize:        0269B000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
        Information from resource tables:
    I suspect that there may be possible hardware issues, however, let's focus on the immediate problems at hand first.
      My Computer


  4. Posts : 24
    Windows 10 Pro 21H1
    Thread Starter
       #4

    Thank you for the quick response.

    So I uninstalled the program associated with LEDKeeper.exe (MSI Mystic Lights). It never made problems before so it would be weird that it's the culprit.

    As for the graphic driver, that one's tricky. The thing is, when the BSODs first started I was already running on the latest driver (497.09), so my first though was that maybe it was responsible since I had done the update not that long ago. I went back to the one I'd been using for a long time and never gave me trouble, 456.71 (using DDU in safe mode the whole shebang), the BSODs didn't stop.

    I also tested my RAM last night with memtest86, did 8 passes and not a single error.

    I'll let you know if any more BSOD occur.
      My Computer


  5. Posts : 73
    Windows 11, Windows 10, Linux Fedora Cinnamon, Linux Mint XFCE, Ghost BSD
       #5

    Okay thank you, please keep us informed.
      My Computer


  6. Posts : 890
    10 Pro/11 Pro Dual Boot
       #6

    Win10Warlord said:
    @tomdsr

    If you ever see errors like this in a dump file:

    Code:
    CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
    6 errors : !nt (fffff8014c07fd00-fffff8014c07fd38)
    fffff8014c07fd00 *9e  85  c3  99  1b  00  45  84 *12  0f  85  d5  99  1b  00  4c ......E........L
    fffff8014c07fd10 *1b  b4  24  d0  00  00  00  48 *f4  bc  24  d8  00  00  00  48 ..$....H..$....H
    ...
    fffff8014c07fd30 *83  14  00  48  81  c4  e0  00 *03  00  41  5f  41  5d  41  5c ...H......A_A]A\
    It's always best practice to run !chkimg with the -f switch to ensure that the analysis is correct:

    Code:
    6: kd> !chkimg !nt -f
    Warning: Any detected errors will be fixed to what we expect!
    6 errors (fixed): !nt (fffff8014c07fd00-fffff8014c07fd38)
    Was way overtired. Still working 12+ hour days and chemo bleh
      My Computers


  7. Posts : 24
    Windows 10 Pro 21H1
    Thread Starter
       #7

    Well, for a while I actually thought my problem was solved, but no. Just another BSOD while updating a game. Logs attached.

    - - - Updated - - -

    I had five BSODs last night. I should point out that I wasn't actively running the computer as I was asleep. The first time, only firefox was running and playing a videos. The other four times, nothing except background apps.
    Random BSOD Attached Files
      My Computer


  8. Posts : 73
    Windows 11, Windows 10, Linux Fedora Cinnamon, Linux Mint XFCE, Ghost BSD
       #8

    Please enable Driver Verifier using the following instructions - Using Driver Verifier – Windows Vista and Beyond | Machines Can Think
      My Computer


  9. Posts : 24
    Windows 10 Pro 21H1
    Thread Starter
       #9

    Win10Warlord said:
    Please enable Driver Verifier using the following instructions - Using Driver Verifier – Windows Vista and Beyond | Machines Can Think
    Okay, it's done. Do I just wait for the next BSOD now? Is it going to create a report of some kind?
      My Computer


  10. Posts : 73
    Windows 11, Windows 10, Linux Fedora Cinnamon, Linux Mint XFCE, Ghost BSD
       #10

    Just wait for the system to crash again, if it does, then please disable Driver Verifier and then upload the dump file(s).
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:10.
Find Us




Windows 10 Forums