Jump to content

Hey guys, I've been having a problem with my PC since this morning.

My PC was working perfectly fine 3-4 days ago, but today when I turned it on, I started getting continuous blue screens after 2-3 minutes with the following stop codes:

  • IRQL_NOT_LESS_OR_EQUAL
  • Memory management
  • Page fault in non-paged area
  • ntoskrnl.exe

I have already run MEMTEST86+ on each of my RAM sticks separately, and no errors were found.
I ran chkdsk /f /r, and no errors were found.
I ran sfc /scannow, and no errors were found.

I tried booting the PC with only one RAM stick, but the blue screen still appeared (I tested both sticks separately).

I reset Windows, but the issue remains the same.

I also did a CLEAR CMOS, but it didn't change anything.

Is my last option to try two different RAM sticks?

For reference, my RAM sticks are: Corsair Vengeance DDR5 64GB (2 x 32GB) 5600 MHz CL40.

 

Thanks for your help!

Link to comment
https://linustechtips.com/topic/1601444-blue-screens-new-computer/
Share on other sites

Link to post
Share on other sites

These are error messages commonly caused by bad memory.

If the RAM sticks are good, it may be the fault of the motherboard or the CPU (where the memory controller is). 

If the RAM sticks are testing ok, I'd check if the CPU is correctly seated and no bent/damaged/missing pins.

And full specs would be appreciated.

Link to post
Share on other sites

Hello, 

 

Thanks everyone for your answers !

 

Here is my full PC specs :

  •  Samsung SSD 990 EVO Plus M.2 PCIe NVMe 2 To
  • Corsair Vengeance DDR5 64 Go (2 x 32 Go) 5600 MHz CL40 - Noir
  • MSI Z790 GAMING PLUS WIFI
  • be quiet! Pure Loop 2 FX 360 mm
  • Intel Core i7-14700KF (3.4 GHz / 5.6 GHz)
  • Radeon RX 7900 XTX
  • MSI MPG A1000G PCIE5 1000W 

 

To answer your questions

I do no have reseated my CPU

It is not a clean install of windows, maybe I should install it on the NVME now ?

I had done a BIOS update but I’ve made a CLEAR CMOS because of the blue screens

Drivers have all been updated to their newest…

 

Thanks for your answers ! 

Link to post
Share on other sites

If that could be helpful here is the dump file of the most recent BSOD.

 

 

*******************************************************************************
*                                                                             *
*                        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: ffff898153eeed28, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000048, 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: fffff805e1489d64, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 875

    Key  : Analysis.Elapsed.mSec
    Value: 2127

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Bugcheck.Code.TargetModel
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_nt!KiSystemCall64

    Key  : Failure.Hash
    Value: {c29d4b06-1535-2efb-adfa-98e2fa018dd2}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 34a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  a

BUGCHECK_P1: ffff898153eeed28

BUGCHECK_P2: ff

BUGCHECK_P3: 48

BUGCHECK_P4: fffff805e1489d64

FILE_IN_CAB:  022125-8968-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffe50afc625080

READ_ADDRESS: fffff805e1dc34b0: 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
 ffff898153eeed28 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  msedgewebview2

TRAP_FRAME:  ffff840fabf5f9f0 -- (.trap 0xffff840fabf5f9f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000006 rbx=0000000000000000 rcx=00007ffbc9e9f724
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff805e1489d64 rsp=ffff840fabf5fb88 rbp=0000000000000070
 r8=0000000000000000  r9=00003ee4022b7340 r10=0000000000000d94
r11=0000000000000246 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!KiSystemCall64+0x24:
fffff805`e1489d64 65488b0c25289d0000 mov   rcx,qword ptr gs:[9D28h] gs:00000000`00009d28=????????????????
Resetting default scope

STACK_TEXT:  
ffff840f`abf5f8a8 fffff805`e148abe9     : 00000000`0000000a ffff8981`53eeed28 00000000`000000ff 00000000`00000048 : nt!KeBugCheckEx
ffff840f`abf5f8b0 fffff805`e1485ea8     : 00000000`00000000 00000074`cd9feb40 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff840f`abf5f9f0 fffff805`e1489d64     : 00007ffb`c9e9f724 00000000`00000033 00000000`00000246 00000074`cd9ff598 : nt!KiPageFault+0x468
ffff840f`abf5fb88 00007ffb`c9e9f724     : 00000000`00000033 00000000`00000246 00000074`cd9ff598 00000000`0000002b : nt!KiSystemCall64+0x24
ffff840f`abf5fb90 00000000`00000033     : 00000000`00000246 00000074`cd9ff598 00000000`0000002b ffff840f`abf60000 : 0x00007ffb`c9e9f724
ffff840f`abf5fb98 00000000`00000246     : 00000074`cd9ff598 00000000`0000002b ffff840f`abf60000 ffff840f`abf59000 : 0x33
ffff840f`abf5fba0 00000074`cd9ff598     : 00000000`0000002b ffff840f`abf60000 ffff840f`abf59000 00000000`00000000 : 0x246
ffff840f`abf5fba8 00000000`0000002b     : ffff840f`abf60000 ffff840f`abf59000 00000000`00000000 00000000`00000000 : 0x00000074`cd9ff598
ffff840f`abf5fbb0 ffff840f`abf60000     : ffff840f`abf59000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2b
ffff840f`abf5fbb8 ffff840f`abf59000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff840f`abf60000
ffff840f`abf5fbc0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff840f`abf59000


SYMBOL_NAME:  nt!KiSystemCall64+24

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.2314

STACK_COMMAND:  .process /r /p 0xffffe50afc3d1080; .thread 0xffffe50afc625080 ; kb

BUCKET_ID_FUNC_OFFSET:  24

FAILURE_BUCKET_ID:  AV_nt!KiSystemCall64

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c29d4b06-1535-2efb-adfa-98e2fa018dd2}

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

Link to post
Share on other sites

11 minutes ago, Thiibault said:

If that could be helpful here is the dump file of the most recent BSOD.

 

 

*******************************************************************************
*                                                                             *
*                        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: ffff898153eeed28, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000048, 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: fffff805e1489d64, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 875

    Key  : Analysis.Elapsed.mSec
    Value: 2127

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Bugcheck.Code.TargetModel
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_nt!KiSystemCall64

    Key  : Failure.Hash
    Value: {c29d4b06-1535-2efb-adfa-98e2fa018dd2}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 34a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  a

BUGCHECK_P1: ffff898153eeed28

BUGCHECK_P2: ff

BUGCHECK_P3: 48

BUGCHECK_P4: fffff805e1489d64

FILE_IN_CAB:  022125-8968-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffe50afc625080

READ_ADDRESS: fffff805e1dc34b0: 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
 ffff898153eeed28 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  msedgewebview2

TRAP_FRAME:  ffff840fabf5f9f0 -- (.trap 0xffff840fabf5f9f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000006 rbx=0000000000000000 rcx=00007ffbc9e9f724
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff805e1489d64 rsp=ffff840fabf5fb88 rbp=0000000000000070
 r8=0000000000000000  r9=00003ee4022b7340 r10=0000000000000d94
r11=0000000000000246 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!KiSystemCall64+0x24:
fffff805`e1489d64 65488b0c25289d0000 mov   rcx,qword ptr gs:[9D28h] gs:00000000`00009d28=????????????????
Resetting default scope

STACK_TEXT:  
ffff840f`abf5f8a8 fffff805`e148abe9     : 00000000`0000000a ffff8981`53eeed28 00000000`000000ff 00000000`00000048 : nt!KeBugCheckEx
ffff840f`abf5f8b0 fffff805`e1485ea8     : 00000000`00000000 00000074`cd9feb40 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff840f`abf5f9f0 fffff805`e1489d64     : 00007ffb`c9e9f724 00000000`00000033 00000000`00000246 00000074`cd9ff598 : nt!KiPageFault+0x468
ffff840f`abf5fb88 00007ffb`c9e9f724     : 00000000`00000033 00000000`00000246 00000074`cd9ff598 00000000`0000002b : nt!KiSystemCall64+0x24
ffff840f`abf5fb90 00000000`00000033     : 00000000`00000246 00000074`cd9ff598 00000000`0000002b ffff840f`abf60000 : 0x00007ffb`c9e9f724
ffff840f`abf5fb98 00000000`00000246     : 00000074`cd9ff598 00000000`0000002b ffff840f`abf60000 ffff840f`abf59000 : 0x33
ffff840f`abf5fba0 00000074`cd9ff598     : 00000000`0000002b ffff840f`abf60000 ffff840f`abf59000 00000000`00000000 : 0x246
ffff840f`abf5fba8 00000000`0000002b     : ffff840f`abf60000 ffff840f`abf59000 00000000`00000000 00000000`00000000 : 0x00000074`cd9ff598
ffff840f`abf5fbb0 ffff840f`abf60000     : ffff840f`abf59000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2b
ffff840f`abf5fbb8 ffff840f`abf59000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff840f`abf60000
ffff840f`abf5fbc0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff840f`abf59000


SYMBOL_NAME:  nt!KiSystemCall64+24

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.2314

STACK_COMMAND:  .process /r /p 0xffffe50afc3d1080; .thread 0xffffe50afc625080 ; kb

BUCKET_ID_FUNC_OFFSET:  24

FAILURE_BUCKET_ID:  AV_nt!KiSystemCall64

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c29d4b06-1535-2efb-adfa-98e2fa018dd2}

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

 

That shows a page fault so a memory issue. With memory issues though I prefer having all the dump files to look at because there are several different things that can cause memory errors. Just looking at one dump file can be very inaccurate. 

Link to post
Share on other sites

2 minutes ago, Bjoolz said:

That shows a page fault so a memory issue. With memory issues though I prefer having all the dump files to look at because there are several different things that can cause memory errors. Just looking at one dump file can be very inaccurate. 

Is there a way to send them all easily of do I open them one by one and copy them here ?

 

Link to post
Share on other sites

Dumpfile 1

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061941, The subtype of the BugCheck.
Arg2: ffff8080f8caafc0
Arg3: 0000000000000009
Arg4: ffffdf8168736460

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 843

    Key  : Analysis.Elapsed.mSec
    Value: 1400

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1a

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1a

    Key  : Dump.Attributes.AsUlong
    Value: 21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

    Key  : Failure.Hash
    Value: {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 34a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  1a

BUGCHECK_P1: 61941

BUGCHECK_P2: ffff8080f8caafc0

BUGCHECK_P3: 9

BUGCHECK_P4: ffffdf8168736460

FILE_IN_CAB:  021825-8718-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffe206ab6f4080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  DeltaForceClie

STACK_TEXT:  
ffffdf81`68736710 00000000`00000000     : ffff8080`f92e5180 00000000`00000001 fffff805`8ae7c073 00000000`00000047 : 0xffffe206`7873a280


MODULE_NAME: hardware

IMAGE_NAME:  hardware_ram

STACK_COMMAND:  .process /r /p 0xffffe20692776080; .thread 0xffffe206ab6f4080 ; kb

FAILURE_BUCKET_ID:  0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

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

 

Dumpfile 2

*******************************************************************************
*                                                                             *
*                        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: ffffdf80508eed28, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 00000000000000e8, 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: fffff80297e89d64, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 843

    Key  : Analysis.Elapsed.mSec
    Value: 1195

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Bugcheck.Code.TargetModel
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_nt!KiSystemCall64

    Key  : Failure.Hash
    Value: {c29d4b06-1535-2efb-adfa-98e2fa018dd2}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 34a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  a

BUGCHECK_P1: ffffdf80508eed28

BUGCHECK_P2: ff

BUGCHECK_P3: e8

BUGCHECK_P4: fffff80297e89d64

FILE_IN_CAB:  021825-9546-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff9304a5470080

READ_ADDRESS: fffff802987c34b0: 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
 ffffdf80508eed28 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  ffffde8ee08729f0 -- (.trap 0xffffde8ee08729f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000003e rbx=0000000000000000 rcx=00007ffa9311fe24
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80297e89d64 rsp=ffffde8ee0872b88 rbp=0000000000002e30
 r8=00000290a91c0440  r9=000000ac99ec9000 r10=0000000000000304
r11=0000000000000246 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!KiSystemCall64+0x24:
fffff802`97e89d64 65488b0c25289d0000 mov   rcx,qword ptr gs:[9D28h] gs:00000000`00009d28=????????????????
Resetting default scope

STACK_TEXT:  
ffffde8e`e08728a8 fffff802`97e8abe9     : 00000000`0000000a ffffdf80`508eed28 00000000`000000ff 00000000`000000e8 : nt!KeBugCheckEx
ffffde8e`e08728b0 fffff802`97e85ea8     : 00000290`aa16b030 00000000`00000000 00000000`00000000 00000290`b1a671f0 : nt!KiBugCheckDispatch+0x69
ffffde8e`e08729f0 fffff802`97e89d64     : 00007ffa`9311fe24 00000000`00000033 00000000`00000246 000000ac`9ae7f338 : nt!KiPageFault+0x468
ffffde8e`e0872b88 00007ffa`9311fe24     : 00000000`00000033 00000000`00000246 000000ac`9ae7f338 00000000`0000002b : nt!KiSystemCall64+0x24
ffffde8e`e0872b90 00000000`00000033     : 00000000`00000246 000000ac`9ae7f338 00000000`0000002b ffffde8e`e0873000 : 0x00007ffa`9311fe24
ffffde8e`e0872b98 00000000`00000246     : 000000ac`9ae7f338 00000000`0000002b ffffde8e`e0873000 ffffde8e`e086c000 : 0x33
ffffde8e`e0872ba0 000000ac`9ae7f338     : 00000000`0000002b ffffde8e`e0873000 ffffde8e`e086c000 00000000`00000000 : 0x246
ffffde8e`e0872ba8 00000000`0000002b     : ffffde8e`e0873000 ffffde8e`e086c000 00000000`00000000 00000000`00000000 : 0x000000ac`9ae7f338
ffffde8e`e0872bb0 ffffde8e`e0873000     : ffffde8e`e086c000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2b
ffffde8e`e0872bb8 ffffde8e`e086c000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffde8e`e0873000
ffffde8e`e0872bc0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffde8e`e086c000


SYMBOL_NAME:  nt!KiSystemCall64+24

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.2314

STACK_COMMAND:  .process /r /p 0xffff9304a076b080; .thread 0xffff9304a5470080 ; kb

BUCKET_ID_FUNC_OFFSET:  24

FAILURE_BUCKET_ID:  AV_nt!KiSystemCall64

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c29d4b06-1535-2efb-adfa-98e2fa018dd2}

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

Dumpfile 3

*******************************************************************************
*                                                                             *
*                        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: ffffa380986eed28, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000088, 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: fffff80497889d64, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 828

    Key  : Analysis.Elapsed.mSec
    Value: 825

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Bugcheck.Code.TargetModel
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_nt!KiSystemCall64

    Key  : Failure.Hash
    Value: {c29d4b06-1535-2efb-adfa-98e2fa018dd2}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 34a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  a

BUGCHECK_P1: ffffa380986eed28

BUGCHECK_P2: ff

BUGCHECK_P3: 88

BUGCHECK_P4: fffff80497889d64

FILE_IN_CAB:  022125-7859-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffb50d60fd3080

READ_ADDRESS: fffff804981c34b0: 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
 ffffa380986eed28 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Spotify.exe

TRAP_FRAME:  ffffb406967ef9f0 -- (.trap 0xffffb406967ef9f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000009 rbx=0000000000000000 rcx=00007ff8be4bf784
rdx=000000b6d17ff6e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80497889d64 rsp=ffffb406967efb88 rbp=0000311c000a0d70
 r8=000000b6d17ff608  r9=000000b6d17ff610 r10=00000000000003f8
r11=0000000000000246 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!KiSystemCall64+0x24:
fffff804`97889d64 65488b0c25289d0000 mov   rcx,qword ptr gs:[9D28h] gs:00000000`00009d28=????????????????
Resetting default scope

STACK_TEXT:  
ffffb406`967ef8a8 fffff804`9788abe9     : 00000000`0000000a ffffa380`986eed28 00000000`000000ff 00000000`00000088 : nt!KeBugCheckEx
ffffb406`967ef8b0 fffff804`97885ea8     : 00000000`00000000 0000311c`00141410 0000311c`0ceabd60 ffffb50d`00000000 : nt!KiBugCheckDispatch+0x69
ffffb406`967ef9f0 fffff804`97889d64     : 00007ff8`be4bf784 00000000`00000033 00000000`00000246 000000b6`d17ff5c8 : nt!KiPageFault+0x468
ffffb406`967efb88 00007ff8`be4bf784     : 00000000`00000033 00000000`00000246 000000b6`d17ff5c8 00000000`0000002b : nt!KiSystemCall64+0x24
ffffb406`967efb90 00000000`00000033     : 00000000`00000246 000000b6`d17ff5c8 00000000`0000002b ffffb406`967f0000 : 0x00007ff8`be4bf784
ffffb406`967efb98 00000000`00000246     : 000000b6`d17ff5c8 00000000`0000002b ffffb406`967f0000 ffffb406`967e9000 : 0x33
ffffb406`967efba0 000000b6`d17ff5c8     : 00000000`0000002b ffffb406`967f0000 ffffb406`967e9000 00000000`00000000 : 0x246
ffffb406`967efba8 00000000`0000002b     : ffffb406`967f0000 ffffb406`967e9000 00000000`00000000 00000000`00000000 : 0x000000b6`d17ff5c8
ffffb406`967efbb0 ffffb406`967f0000     : ffffb406`967e9000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2b
ffffb406`967efbb8 ffffb406`967e9000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffb406`967f0000
ffffb406`967efbc0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffb406`967e9000


SYMBOL_NAME:  nt!KiSystemCall64+24

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.2314

STACK_COMMAND:  .process /r /p 0xffffb50d5ea1f080; .thread 0xffffb50d60fd3080 ; kb

BUCKET_ID_FUNC_OFFSET:  24

FAILURE_BUCKET_ID:  AV_nt!KiSystemCall64

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c29d4b06-1535-2efb-adfa-98e2fa018dd2}

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

Dumpfile 4

*******************************************************************************
*                                                                             *
*                        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: ffffe58129aeed28, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000028, 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: fffff800c7289d64, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 890

    Key  : Analysis.Elapsed.mSec
    Value: 2201

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Bugcheck.Code.TargetModel
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_nt!KiSystemCall64

    Key  : Failure.Hash
    Value: {c29d4b06-1535-2efb-adfa-98e2fa018dd2}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 34a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  a

BUGCHECK_P1: ffffe58129aeed28

BUGCHECK_P2: ff

BUGCHECK_P3: 28

BUGCHECK_P4: fffff800c7289d64

FILE_IN_CAB:  022125-8781-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff960aa6580080

READ_ADDRESS: fffff800c7bc34b0: 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
 ffffe58129aeed28 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  msedge.exe

TRAP_FRAME:  ffff818c6fbef9f0 -- (.trap 0xffff818c6fbef9f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000006 rbx=0000000000000000 rcx=00007ffead0df724
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800c7289d64 rsp=ffff818c6fbefb88 rbp=0000000000000070
 r8=0000000000000000  r9=000033c400050460 r10=00000000000018fc
r11=0000000000000246 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!KiSystemCall64+0x24:
fffff800`c7289d64 65488b0c25289d0000 mov   rcx,qword ptr gs:[9D28h] gs:00000000`00009d28=????????????????
Resetting default scope

STACK_TEXT:  
ffff818c`6fbef8a8 fffff800`c728abe9     : 00000000`0000000a ffffe581`29aeed28 00000000`000000ff 00000000`00000028 : nt!KeBugCheckEx
ffff818c`6fbef8b0 fffff800`c7285ea8     : 00000000`00000000 0000007b`177fe700 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff818c`6fbef9f0 fffff800`c7289d64     : 00007ffe`ad0df724 00000000`00000033 00000000`00000246 0000007b`177ff158 : nt!KiPageFault+0x468
ffff818c`6fbefb88 00007ffe`ad0df724     : 00000000`00000033 00000000`00000246 0000007b`177ff158 00000000`0000002b : nt!KiSystemCall64+0x24
ffff818c`6fbefb90 00000000`00000033     : 00000000`00000246 0000007b`177ff158 00000000`0000002b ffff818c`6fbf0000 : 0x00007ffe`ad0df724
ffff818c`6fbefb98 00000000`00000246     : 0000007b`177ff158 00000000`0000002b ffff818c`6fbf0000 ffff818c`6fbe9000 : 0x33
ffff818c`6fbefba0 0000007b`177ff158     : 00000000`0000002b ffff818c`6fbf0000 ffff818c`6fbe9000 00000000`00000000 : 0x246
ffff818c`6fbefba8 00000000`0000002b     : ffff818c`6fbf0000 ffff818c`6fbe9000 00000000`00000000 00000000`00000000 : 0x0000007b`177ff158
ffff818c`6fbefbb0 ffff818c`6fbf0000     : ffff818c`6fbe9000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2b
ffff818c`6fbefbb8 ffff818c`6fbe9000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff818c`6fbf0000
ffff818c`6fbefbc0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff818c`6fbe9000


SYMBOL_NAME:  nt!KiSystemCall64+24

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.2314

STACK_COMMAND:  .process /r /p 0xffff960aa677f080; .thread 0xffff960aa6580080 ; kb

BUCKET_ID_FUNC_OFFSET:  24

FAILURE_BUCKET_ID:  AV_nt!KiSystemCall64

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c29d4b06-1535-2efb-adfa-98e2fa018dd2}

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

Link to post
Share on other sites

11 minutes ago, Thiibault said:

Is there a way to send them all easily of do I open them one by one and copy them here ?

 

You can just upload the dump files. Copy the Minidump folder somewhere else because Windows can get mad if you try doing stuff directly to files in C:\Windows, zip the folder and upload. 

 

This looks like RAM/memory controller. The memory controller is in the CPU. Use the PC normally with one stick at a time and see if only one of them causes crashes. Also remove any and all overclocking including XMP. It's much more often RAM than the CPU.

 

The Intel microcode issue that made CPUs fry themselves also look like memory so with 13th/14th gen CPUs it's a lot more common that it's the CPU. Did you update the BIOS as soon as you got the PC? 

Link to post
Share on other sites

1 minute ago, Thiibault said:

Thanks, hope it works 🙂 

Minidumps.zip 1.2 MB · 1 download

I edited in my analysis after looking at the copy pastes, but I see from the dump files that you don't have XMP enabled and the BIOS is up to date which were originally a possible issue. 

Link to post
Share on other sites

2 minutes ago, Bjoolz said:

I edited in my analysis after looking at the copy pastes, but I see from the dump files that you don't have XMP enabled and the BIOS is up to date which were originally a possible issue. 

I'll enable it right now and tell you if anything changes, thank you 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×