BSOD help with analyze

Question

Hello,

Sometimes i get random BSOD, 1 - 2 times a week.
I think it is a memory problem but i am not sure.

Kind regards,
Sven

1: 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: 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: fffff805640a4154, address which referenced memory

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2921

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 7451

    Key  : Analysis.IO.Other.Mb
    Value: 3

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 7

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xa

    Key  : Bugcheck.Code.Register
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

FILE_IN_CAB:  040923-17718-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  a

BUGCHECK_P1: 0

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff805640a4154

WRITE_ADDRESS: fffff80564afb390: 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:  msedge.exe

TRAP_FRAME:  ffffaa07926eaeb0 -- (.trap 0xffffaa07926eaeb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffbebffc3de5d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff805640a4154 rsp=ffffaa07926eb040 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=ffffc3863dd56700
r11=ffffbedf6fb7dfff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiWalkPageTablesRecursively+0xad4:
fffff805`640a4154 0f0000          sldt    word ptr [rax] ds:00000000`00000000=????????
Resetting default scope

MISALIGNED_IP: 
nt!MiWalkPageTablesRecursively+ad4
fffff805`640a4154 0f0000          sldt    word ptr [rax]

STACK_TEXT:  
ffffaa07`926ead68 fffff805`6420e129     : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffaa07`926ead70 fffff805`64209ce3     : ffffbedf`6fb7d7f8 fffff805`6411d0a9 00480020`00330020 005c0074`0073006f : nt!KiBugCheckDispatch+0x69
ffffaa07`926eaeb0 fffff805`640a4154     : 00000000`00000000 ffffbebf`fc3de5d0 00000000`00000000 80000001`c2f41025 : nt!KiPageFault+0x463
ffffaa07`926eb040 fffff805`640a3f0b     : ffffbedf`00000000 ffffc386`3dd56700 00000000`00000000 ffffaa07`926eb5b0 : nt!MiWalkPageTablesRecursively+0xad4
ffffaa07`926eb0e0 fffff805`640a3f0b     : ffffbedf`00000000 ffffc386`3dd56700 00000000`00000001 ffffaa07`926eb5c0 : nt!MiWalkPageTablesRecursively+0x88b
ffffaa07`926eb180 fffff805`640a3f0b     : ffffbedf`6faff000 ffffc386`3dd56700 00000000`00000002 ffffaa07`926eb5d0 : nt!MiWalkPageTablesRecursively+0x88b
ffffaa07`926eb220 fffff805`64076b3b     : 00000000`00000000 ffffc386`3dd56700 ffffaa07`00000003 ffffaa07`926eb5e0 : nt!MiWalkPageTablesRecursively+0x88b
ffffaa07`926eb2c0 fffff805`640765d1     : ffffaa07`926eb560 00000000`00000000 00000000`00000002 00000000`00000000 : nt!MiWalkPageTables+0x36b
ffffaa07`926eb3c0 fffff805`64075cd9     : 00000000`00000000 00000000`00000000 ffff9501`95cf71c0 00000000`00000000 : nt!MiAgeWorkingSet+0x3d1
ffffaa07`926eb8d0 fffff805`640754e7     : 00000000`00000000 ffffaa07`926eba80 ffffaa07`926eba40 00000000`00000000 : nt!MiTrimOrAgeWorkingSet+0x3c9
ffffaa07`926eb9c0 fffff805`6415acb0     : fffff805`64a50cc0 ffffaa07`926eba80 00000000`0000006d ffff9501`00000200 : nt!MiProcessWorkingSets+0x227
ffffaa07`926eba60 fffff805`641b92f7     : 00000000`00000005 00000000`00000005 00000000`ffffffff fffff805`60767180 : nt!MiWorkingSetManager+0x110
ffffaa07`926ebb20 fffff805`64055485     : ffffc386`2bcc4080 00000000`00000080 fffff805`641b91a0 00000000`00000000 : nt!KeBalanceSetManager+0x157
ffffaa07`926ebc10 fffff805`64202d48     : ffff9501`83c80180 ffffc386`2bcc4080 fffff805`64055430 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffaa07`926ebc60 00000000`00000000     : ffffaa07`926ec000 ffffaa07`926e6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME:  nt!MiWalkPageTablesRecursively+ad4

IMAGE_VERSION:  10.0.19041.2728

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  GenuineIntel.sys

MODULE_NAME: GenuineIntel

FAILURE_BUCKET_ID:  IP_MISALIGNED_GenuineIntel.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e930d917-b247-3f7f-23cb-88a0c9f1b274}

Followup:     MachineOwner

Answer 1

Hi Sven,

Your minidump files just indicate memory (RAM) corruption no specific driver is listed

The best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors

Answer 2

Hello Dave,

https://1drv.ms/f/s!AokzRlZtIK7Csm90v3Hg6DpUnu-q?e=bHmqer

That is the link to the dump file, i have 2 of them, but i think its the same problem.

Kind regards,

Sven.

Answer 3

Hi Sven,

I am Dave, I will help you with this.

Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so we can take a look for you.