Windows 2022 reboot

Question

Hello,

We have a server running Hyper-V with some VMs on Fail-over cluster, and it goes reboot itself. 
I provide with the minidump details, would you advise?

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

   EnableRedirectToV8JsProvider : 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.063 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 41

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

Loading Dump File [C:\Users\hk202\AppData\Local\Temp\7e43988a-b8c8-43bb-a8b9-95cd2e92861e_THVM01 - 28 Jul 2024 Reboot issue-20240801T043042Z-001.zip.61e\THVM01 - 28 Jul 2024 Reboot issue\072824-74640-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 20348 MP (80 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Edition build lab: 20348.859.amd64fre.fe_release_svc_prod2.220707-1832
Kernel base = 0xfffff803`25400000 PsLoadedModuleList = 0xfffff803`26033dc0
Debug session time: Sun Jul 28 06:51:43.133 2024 (UTC + 8:00)
System Uptime: 20 days 16:03:14.508
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000007c`d2b5e018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`2581fbf0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffcf89`88344730=0000000000000023
54: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

FAT_FILE_SYSTEM (23)
    If you see FatExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001c0345
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3140

    Key  : Analysis.Elapsed.mSec
    Value: 5137

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x23

    Key  : Bugcheck.Code.TargetModel
    Value: 0x23

    Key  : Failure.Bucket
    Value: 0x23_fastfat!FatDeleteVcb

    Key  : Failure.Hash
    Value: {ed15f743-0c55-b96c-e47e-28acdd0ea837}

    Key  : Hypervisor.Enlightenments.Value
    Value: 68411340

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 413dfcc

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

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

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 1

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 1c811fe

    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

    Key  : Memory.System.Errors.BadPageCount
    Value: 2

    Key  : WER.OS.Branch
    Value: fe_release_svc_prod2

    Key  : WER.OS.Version
    Value: 10.0.20348.859

BUGCHECK_CODE:  23

BUGCHECK_P1: 1c0345

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  072824-74640-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  vmms.exe

STACK_TEXT:  
ffffcf89`88344728 fffff803`3e18be49     : 00000000`00000023 00000000`001c0345 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffcf89`88344730 fffff803`3e14649e     : ffffde0b`c34db970 ffffde0b`c34db970 ffffde0b`c34db901 00000000`00000000 : fastfat!FatDeleteVcb+0x241
ffffcf89`88344770 fffff803`3e184310     : 00000000`c000014f ffffcf89`88344b00 ffffcf89`88344b59 ffffd60b`3e61c248 : fastfat!FatCheckForDismount+0xea
ffffcf89`883447b0 fffff803`3e183537     : 00000000`00000000 ffffde0b`bfd87020 ffffde0b`00000001 00000000`00000000 : fastfat!FatMountVolume+0xda4
ffffcf89`88344a40 fffff803`3e183482     : ffffd60b`3e61c010 ffffd60b`96c55b01 ffffd60b`96c55b01 ffffde0b`c1370601 : fastfat!FatCommonFileSystemControl+0x57
ffffcf89`88344a70 fffff803`25649205     : 00000000`00000000 ffffd60b`3e61c010 ffffd60b`3e61c001 ffffd60b`96c55b10 : fastfat!FatFsdFileSystemControl+0xb2
ffffcf89`88344ab0 fffff803`210604c4     : ffffde0c`0af2f270 ffffd60b`00000000 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55
ffffcf89`88344af0 fffff803`210589ed     : ffffd60b`45fd6d20 ffffd60b`3e61c010 ffffde0b`bd197010 ffffde0b`ccdebd50 : FLTMGR!FltpFsControlMountVolume+0x1f0
ffffcf89`88344bc0 fffff803`25649205     : ffffcf89`88344d21 ffffd60b`45fd6d20 ffffcf89`88344d21 fffff803`26051060 : FLTMGR!FltpFsControl+0x11d
ffffcf89`88344c20 fffff803`25b3ec77     : ffffcf89`88344d21 ffffde0b`bf2dd050 ffffd60b`45fd6d20 00000000`00000000 : nt!IofCallDriver+0x55
ffffcf89`88344c60 fffff803`25649145     : ffffde0b`fc1d1770 ffffde0b`fcde67a0 ffffd60b`3e6f1901 fffff803`25abbf01 : nt!IopMountVolume+0x3af
ffffcf89`88344d80 fffff803`25ab96c0     : 00000000`00000000 00000000`00000000 ffffcf89`883450a0 ffffde0b`c5f0e290 : nt!IopCheckVpbMounted+0x205
ffffcf89`88344de0 fffff803`25ab6e31     : ffffd60b`46466470 fffff803`25ab8a90 00000000`00000000 00000000`00000040 : nt!IopParseDevice+0xc30
ffffcf89`88344fa0 fffff803`25ab5801     : 00000000`00000001 ffffcf89`883451c0 00000000`00000040 ffffd60b`3e6f1980 : nt!ObpLookupObjectName+0x10f1
ffffcf89`88345130 fffff803`25ae7031     : 00000000`00000000 00000000`00000000 ffffde0b`c5f0e290 0000007c`d38fec40 : nt!ObOpenObjectByNameEx+0x1f1
ffffcf89`88345260 fffff803`25a4c659     : 0000007c`d38febe0 0000007c`00100080 0000007c`d38fec40 0000007c`d38febe8 : nt!IopCreateFile+0x7b1
ffffcf89`88345320 fffff803`25834685     : 0000007c`d38fee60 0000020f`47e31550 00000000`00000000 00000000`0000003c : nt!NtCreateFile+0x79
ffffcf89`883453b0 00007ffa`7c220c74     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000007c`d38feb58 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`7c220c74

SYMBOL_NAME:  fastfat!FatDeleteVcb+241

MODULE_NAME: fastfat

IMAGE_NAME:  fastfat.SYS

IMAGE_VERSION:  10.0.20348.2305

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  241

FAILURE_BUCKET_ID:  0x23_fastfat!FatDeleteVcb

OS_VERSION:  10.0.20348.859

BUILDLAB_STR:  fe_release_svc_prod2

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ed15f743-0c55-b96c-e47e-28acdd0ea837}

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

NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\ObjectiveC.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2402.24001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Usb4Kd.natvis'

Answer 1

Hello

Thank you for posting in Microsoft Community forum.

FAT_FILE_SYSTEM This indicates a problem in the FAT file system.

The cause may be a corrupted disk. Either corruption in the file system or bad blocks (sectors) on the disk can cause this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to the disk, causing errors.

Another possible cause is exhaustion of nonpaged pool memory. This error can stop the system if nonpaged pool memory is completely exhausted. However, during the indexing process, another kernel-mode driver that requires nonpaged pool memory can also trigger this error if the amount of available nonpaged pool memory is very low.

Here are some steps you can take to troubleshoot and resolve this issue:

Run CHKDSK: This tool checks for and repairs disk errors. Open Command Prompt as an administrator and run:

chkdsk /f /r

You’ll need to restart your computer for the scan to complete.

Update Drivers: Ensure all your drivers are up to date, especially SCSI and IDE drivers. You can do this through Device Manager.

Check for Faulty Hardware: Disconnect any new hardware to see if the error persists. If it does, test each piece of hardware individually.

Run System File Checker: This tool scans for and repairs corrupted system files. In Command Prompt, run:

sfc /scannow

Check Event Viewer: Look for error messages related to SCSI, FASTFAT, or Autochk in the Event Viewer to identify the problematic device or driver.

Bug Check 0x23 FAT_FILE_SYSTEM - Windows drivers | Microsoft Learn

Best Regards,

Wesley Li