New computer getting crashes/restarts

Question

New computer getting crashes/restarts

Jokur 0

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 44

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


Loading Dump File [C:\Windows\Minidump\061425-9046-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 26100 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff806`e8a00000 PsLoadedModuleList = 0xfffff806`e98f4aa0
Debug session time: Sat Jun 14 08:59:13.711 2025 (UTC + 2:00)
System Uptime: 0 days 12:25:27.561
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................
Loading User Symbols

Loading unloaded module list
.................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`e8f00a70 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffc400`3f1b6d10=000000000000000a
11: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................
Loading User Symbols

Loading unloaded module list
.................................
*******************************************************************************
*                                                                             *
*                        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: ffffde8f57f32180, 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: fffff806e8d3ce52, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 781

    Key  : Analysis.Elapsed.mSec
    Value: 779

    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: 13601

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Bugcheck.Code.TargetModel
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    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!MiRestoreTransitionPte

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff806e8d3ce52

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0x33ce52

    Key  : Failure.Hash
    Value: {37d4886d-fd49-86e8-3405-f2978c32f33e}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    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: 38408431

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x24a10ef

    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: 0x3f7


BUGCHECK_CODE:  a

BUGCHECK_P1: ffffde8f57f32180

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff806e8d3ce52

FILE_IN_CAB:  061425-9046-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffda8f5d2b3040

READ_ADDRESS: fffff806e99c44c0: 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
 ffffde8f57f32180 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffc400`3f1b6d08 fffff806`e90b85e9     : 00000000`0000000a ffffde8f`57f32180 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffc400`3f1b6d10 fffff806`e90b38a8     : ffffda8f`24597e40 fffff806`e8ce75d1 ffffa380`07688100 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffc400`3f1b6e50 fffff806`e8d3ce52     : ffffa380`07688108 ffffc400`3f1b7059 ffffa380`0fc68110 ffffa380`07688110 : nt!KiPageFault+0x468
ffffc400`3f1b6fe0 fffff806`e8d3c7fb     : de8f57f3`218004c0 ffffc400`00000000 de8f57f3`218004c0 fffff806`e9838800 : nt!MiRestoreTransitionPte+0x31a
ffffc400`3f1b70c0 fffff806`e8c0d32c     : fffff806`e9839678 00000000`00000000 fffff806`00000000 ffffa680`00000001 : nt!MiUnlinkStandbyPage+0x5cb
ffffc400`3f1b71b0 fffff806`e8d27aab     : 00000000`005422b0 00000000`00000000 fffff806`e983ca10 fffff806`00000001 : nt!MiRemoveLowestPriorityStandbyPage+0x25c
ffffc400`3f1b72e0 fffff806`e8e69a06     : 00000000`000001e4 fffff806`00000000 ffffda8f`2458f700 00000000`00000202 : nt!MiPruneStandbyPages+0x18f
ffffc400`3f1b7360 fffff806`e8d6124c     : ffffda8f`5d2b3040 ffffc400`3f1b7490 ffffda8f`24702ae0 00000000`00000000 : nt!MiRebalanceZeroFreeLists+0xb6
ffffc400`3f1b7390 fffff806`e8ea361a     : ffffda8f`5d2b3040 ffffda8f`5d2b3040 fffff806`e8d60c60 ffffda8f`24702ae0 : nt!ExpWorkerThread+0x5ec
ffffc400`3f1b7570 fffff806`e90a5764     : ffff8300`ee66b180 ffffda8f`5d2b3040 fffff806`e8ea35c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
ffffc400`3f1b75c0 00000000`00000000     : ffffc400`3f1b8000 ffffc400`3f1b1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!MiRestoreTransitionPte+31a

MODULE_NAME: nt

IMAGE_VERSION:  10.0.26100.4343

STACK_COMMAND: .process /r /p 0xffffda8f24590040; .thread 0xffffda8f5d2b3040 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  31a

FAILURE_BUCKET_ID:  AV_nt!MiRestoreTransitionPte

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {37d4886d-fd49-86e8-3405-f2978c32f33e}

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

Can anyone point me in the right direction?

Bheemani Anji Babu 430 Reputation points Microsoft External Staff Moderator

2025-06-15T06:17:48.08+00:00

Hi Jokur

To help further diagnose this issue, could you please clarify the following details:

Is this system a physical machine or a virtual machine (VM)? and which windows version and build number is installed? You can check this by running winver. Have you made any recent hardware changes like new RAM, SSD, etc.? Are there any third-party drivers or software such as antivirus, virtualization tools recently installed?

These details will help narrow down the possible root causes of the crashes.

-Thank you.
Jokur 0 Reputation points

2025-06-15T22:38:04.9633333+00:00

it is a physical machine, newly built and freshly installed.

Version 24H2 (OS-Version 26100.4351)

Your answer

Bheemani Anji Babu 430 Reputation points Microsoft External Staff Moderator

2025-06-15T06:17:48.08+00:00

Hi Jokur

To help further diagnose this issue, could you please clarify the following details:

Is this system a physical machine or a virtual machine (VM)? and which windows version and build number is installed? You can check this by running winver. Have you made any recent hardware changes like new RAM, SSD, etc.? Are there any third-party drivers or software such as antivirus, virtualization tools recently installed?

These details will help narrow down the possible root causes of the crashes.

-Thank you.
Jokur 0 Reputation points

2025-06-15T22:38:04.9633333+00:00

it is a physical machine, newly built and freshly installed.

Version 24H2 (OS-Version 26100.4351)

Share via

New computer getting crashes/restarts

Your answer