Windows Server 2019 BSOD CRITICAL_SERVICE_FAILED Bug Check: 0x0000005A

Zach 1 Reputation point
2022-05-09T17:08:51.557+00:00

I have a brand new Dell R340 server that I have installed Windows Server 2019 on.
This server will be for all of our CAD documents and revision control. I am using SolidWorks PDM 2022 SP2, no other software gets installed on this server other than whats needed for SolidWorks PDM to function. EDIT: I install SQL Server Management Studio 18.11.1 as well, this is needed for the backup process

I install and configure Windows Server 2019(bare metal), then I install SolidWorks PDM and get it fully configured with its included SQL Express 19 installation and then lastly I configure the backups of the SolidWorks PDM/SQL components using some batch scripts and the Task Scheduler. (following this tutorial

https://www.goengineer.com/blog/solidworks-pdm-guide-to-pdm-standard-backups I have tried both Option 1 and Option 2 when it comes to Backup Method 3)

But without fail the server will BSOD on me with stop error code CRITICAL_SERVICE_FAILED 0x0000005A.

I have attempted every repair of the installation that I can find online(sfc, dism, bcdedit, bootrec etc) and none of them work to fix and boot the Server 2019 install.

I think this issue may be related to the Task Scheduler but I am not sure. The reason I think this is because on multiple occasions right before a BSOD happens, I will try to open the Task Scheduler and error will pop up that says "An administer has blocked you from running this app. For more information contact the administer."
200308-image.png
This happens while I am logged in as the administer and sometimes it will happen right after I had just closed the Task Scheduler, realized I forgot something and I will try to open it again to the error I just mentioned. But when this error comes up, the very next time I restart this server it will BSOD. If I don't restart it right then, then it will still eventually BSOD on its own within the following 24hours.
This has happened 5+ times exactly like this.

I have contacted Dell and their support has said that it must be a software or driver conflict because they have run multiple hardware diagnostics and everything passes. I have also contacted SolidWorks and they have no records of other people experiencing this error with SolidWorks PDM 2022 SP2 and Windows Server 2019.

Also, for the record I initially used SolidWorks PDM 2019 SP5 which uses SQL Express 14 and encountered the same issue, so I switched to 2022 because 2019-2021 all use SQL Express 14 but 2022 uses SQL Express 19.

I was able to pull a MEMORY.DMP file from one of the crashes but I don't really know what I am looking at.
From the dump file:
CRITICAL_SERVICE_FAILED (5a)
Arguments:
Arg1: 0000000000000001
Arg2: ffff81881b36ea10
Arg3: ffffc800f9990bc0
Arg4: ffffffffc0000428

I also saw this in the tool BlueScreenView:
200406-image.png

I am open to any sort of debugging just let me know what to do.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,588 questions
0 comments No comments
{count} votes

10 answers

Sort by: Most helpful
  1. Docs 15,491 Reputation points
    2022-05-09T22:23:05.503+00:00

    Please run the DM log log collector and post a share link into this thread using one drive, drop box, or google drive.

    If the server can run the V2 log collector it will collect more useful log files.

    https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

    https://www.elevenforum.com/t/bsod-posting-instructions.103/

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post there is /\ with a number: click = a helpful post
    .
    .
    .
    .
    .

    0 comments No comments

  2. Zach 1 Reputation point
    2022-05-10T12:52:19.91+00:00

    I tried to run V2 but can't get past this error.
    I found that in Powershell(x86) I could run "Import-Module Defender" and then run "Get-MpPreference" and I'd get a response
    201123-image.png
    but when I ran the "log-collector" shortcut or even just try to run "main.ps1" I get these errors.

    Any suggestions?

    201152-image.png
    200662-image.png

    The DM Log Collector was able to run though and that zip is here: https://1drv.ms/u/s!ArdnGrTN3rCtaVmaaFUL3pF8u2o

    Also: I intend this be a BareMetal install when its stable but since I'm still debugging this, I've recently switched to using Hyper-V installations as its quicker to recover from, and lets me test multiple configurations at once.

    0 comments No comments

  3. Zach 1 Reputation point
    2022-05-10T16:39:47.693+00:00

    In an effort to narrow down what could be the cause of this I decided to make another Hyper-V virtual machine with Windows Server 2019 and all I did was install the OS and all of the updates through Windows Update(no SQL or SolidWorks PDM). Then I set up the same Task Scheduler script I have been using this entire time.
    200677-image.png
    Its simple a batch script that deletes the contents of a network drive folder and then calls robocopy to copy a folder to that same location on a network drive. (On this Virtual Machine Test it's set to an arbitrary folder I created with some empty text files in it, as SolidWorks PDM isn't installed so the normal folder I'd backup doesn't exist.)
    200702-image.png

    This ran fine and I rebooted it 5 times while making sure to run the Task Scheduler event once between each reboot.

    Then I connected it to a Test Domain(default setup, not being used for anything other than this test) I had created on another Hyper-V VM.
    Then I was going to reboot it 5 more times while still making sure to run the task scheduler event once between each reboot but on the 3rd reboot I got this
    200670-image.png
    It fails to do its automatic repair and just bootloops but if I disable driver signature enforcement then I can get it to boot. This time I was able to successfully run the V2 Log Collector. The zip is here: https://1drv.ms/u/s!ArdnGrTN3rCta--Nui8wXrdkMAI?e=Rbqpcd

    0 comments No comments

  4. Docs 15,491 Reputation points
    2022-05-10T21:45:55.357+00:00

    Nice work getting V2 to run.
    The exception code was: c0000428 Windows cannot verify the digital signature or this file.

    The DM log collector: did not collect any dump files, the logs did not display any unexpected shutdowns or restarts
    The V2 log collector: collected 3 dump files, all were 21A

    This may have been a one time event.

    Troubleshooting could resume if there were a new crash.

    Non-Windows drivers can be stress tested.

    If you can arrange server downtime consider using Windows Driver Verifier (WDV).

    https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html
    https://www.tenforums.com/tutorials/4571-create-system-restore-point-windows-10-a.html

    If there is no immediate BSOD then open administrative command prompt and type or copy and paste:

    verifier /querysettings

    Post a share link into this thread

    For any BSOD post a log collector share link.

    If there are no performance problems the customized tests will be modified to stress test drivers.

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post there is /\ with a number: click = a helpful post
    .
    .
    .
    .
    .


  5. Zach 1 Reputation point
    2022-05-11T15:57:36.417+00:00

    This server isn't live because it's brand new and currently isn't stable enough to push into production, so currently there is plenty of down-time to debug.

    I recreated the same installation as before and I enabled WDV following the tutorial @Docs linked. The only issue is that when WDV is enabled, the BSoD that follows the next restart is seemingly frozen on the BSoD(normally it finishes saying it can't repair it and then it loads into the Windows Recovery Environment):
    I read that WDV can make things run much slower, currently its been on the 100% BSOD screen for 20mins, I'll leave it for a while longer to see if it eventually changes.
    201102-image.png

    0 comments No comments