Windows Server 2022 BSOD Stop Code 0x24

Brett Parker 15 Reputation points
2023-01-25T15:45:27.4266667+00:00

Over the course of the past 2 months, we have suffered multiple (22) blue screen of death events on our remote environment. The blue screen has been isolated to one virtual machine and has thrown the same stop code (0x24) with the same arguments (Arg1: 00000241001616c5 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: 0000000000000000). We have tried everything we have thought to resolve the issue. I will go into depth on this below.

Our Environment:

We have Windows 2022 Virtual Machines hosted from a Hyper-V server. On the Hyper-V Host, we have FSlogix profiles which are mapped via group policy/registry to mount on the Virtual Machines. We are running FSlogix on version  2.9.8171.14983. We recently downgraded from FSlogix version 2.9.8228.50276 to have the version line up with our other 7 RDS environments that have not had any issues. FSlogix is configured using best practice deployment (reference: https://ramprasadtech.com/wp-content/uploads/2020/09/FSLogix-Group-Policy-Settings-Profile-Conatiner-Best-Practices-v1.0-17Sep20.pdf)

Asset information:

Asset type: Windows

OS: Windows Server 2022 Datacenter (64 bit)

Build: 10.0.20348S.1249

Version: 21H2

What we have tried:

  1. We spun up a brand new virtual machine and migrated users over to the new machine. Despite doing this, the error stayed the same - BSOD with Stop Code 0x24
  2. We ran a DISM and SFC /scannow during off hours to check our disk to ensure there was no corruption
  3. We checked all drivers on the machine
  4. Downgraded our version of FSlogix to have the version line up with all other RDS environments
  5. Recreated all FSlogix profile containers for users that access the Server

We have a collection of dump logs that show the same data (12, but I am unsure how to share them here.). Below is a screenshot of the most recent dmp logs from BlueScreenView.

User's image

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,119 questions
FSLogix
FSLogix
A set of solutions that enhance, enable, and simplify non-persistent Windows computing environments and may also be used to create more portable computing sessions when using physical devices.
463 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Limitless Technology 43,931 Reputation points
    2023-01-26T16:57:44.1033333+00:00

    Hello there,

    An NTFS file system blue screen error may also occur if the system disk has errors or bad sectors.

    I would recommend that you run a full fledged chkdsk /r on the disk in case corruption is found.

    We can find corruption by running chkdsk <drive_letter> or check id the dirty bit is set using the command fsutil dirty query <drive_letter>.

    In case corruption is detected, I would recommend running a chkdsk /r. Why i would recommend this is simple, if chkdsk finds some files in lost clusters, it would attempt to recover them and would put them in a folder titled found.xxx where xxx=001,002 etc.

    The below thread discusses the same issue and you can try out some troubleshooting steps from this and see if that helps you to sort the Issue.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/bae06c14-ed8f-4e0e-897d-e936f720aae8/does-chkdsk-r-for-vhds-make-sense?forum=winserverhyperv

    https://social.technet.microsoft.com/Forums/en-US/2ca1dff1-5612-4571-9736-d62a80e86f8e/hyperv-backup-defrag-checkdisk?forum=winserverhyperv

    Hope this resolves your Query !!

    --If the reply is helpful, please Upvote and Accept it as an answer–

    1 person found this answer helpful.