FSlogix BSOD frxdrvvt.sys on Windows Server 2022

Bart Vaneygen 110 Reputation points
2023-05-03T08:40:51.2+00:00

Hi,

Anyone else seen this yet?

  • Windows Server 2022 standard install.
  • Microsoft FSLogix 2210 hotfix 1 (2.9.8440.42104)
  • User profile disk

When I search for e.g. *.PDF in "C:\Users\username" (Within an FSlogix mounted profile) all is well and I get my results.

When I search for e.g. *.PDF in "\\127.0.0.1\C$\Users\username" (Within an FSlogix mounted profile) the system freezes and bluescreens. This happened first when I searched the user profile of a remote system. Browsing the user profile doesn't cause a bluescreen, but a search does.

BSOD info:

KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffffc0000005 fffff8064df67ab2 0000000000000000 0000000000000048 frxdrvvt.sys frxdrvvt.sys+7ab2

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,574 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.
474 questions
0 comments No comments
{count} votes

8 answers

Sort by: Most helpful
  1. Limitless Technology 44,096 Reputation points
    2023-05-04T16:02:53.05+00:00

    Hello there,

    Have you tried the given troubleshooting steps in the following link https://learn.microsoft.com/en-us/fslogix/troubleshooting-old-temp-local-profiles

    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>.

    If corruption is detected, I 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

    Hope this resolves your Query !!

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


  2. Limitless Technology 44,096 Reputation points
    2023-05-04T16:07:21.5066667+00:00

    Hello there,

    Have you tried the given troubleshooting steps in the following link https://learn.microsoft.com/en-us/fslogix/troubleshooting-old-temp-local-profiles

    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>.

    If corruption is detected, I 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

    Hope this resolves your Query !!

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

    0 comments No comments

  3. Bart Vaneygen 110 Reputation points
    2023-05-26T11:23:34.8633333+00:00

    Hi,

    Nobody seems to experience the same issue, however I have created a ticket with Microsoft and they just confimed they were able to recreate the issue with ease.

    So I'm happily awaiting a root cause analysis and hopefully a fix :).

    0 comments No comments

  4. K1ngb0rA 0 Reputation points
    2023-06-21T07:25:50.02+00:00

    Hello,

    we are facing a similar issue, but in our case the terminalserver get a BSOD when we copy files/folders to a users profile under "C:\Users\username".
    we are also getting the BSOD when searching locally in "C:\Users\username"
    nothing happens when we copy the files/folders from another client to "\<terminalserver>\C$\Users\username"

    a fix would be highly appreciated!

    0 comments No comments

  5. Bart Vaneygen 10 Reputation points
    2023-06-21T12:22:51.61+00:00

    Hi,

    Microsoft tested my scenario and were able to recreate the BSOD. They have it fixed now and it should be in the preview version of FSlogix. I haven't been able to get it though. I filled in everything to be allowed in the preview program, but that was 2 weeks ago already ... .