WS2019 regular bsod

[andruhasms]

hi. we receive a bsod on our windows server 2019 server every day

 

[Maxstar]

FYI: See the following thread in the Windows Update section for the SysnativeFileCollectionApp.zip file.

A

Post in thread 'WS2019 DISM Error "The specified file cannot be found."'

Nov 18, 2024

Hi, Done

• andruhasms

 

[andruhasms]

dump and SysnativeFileCollectionApp logs are attached. Please help me solve the problem

 

[ET_Explorer]

Your SysnativeFileCollection is all in Russian, can't read it.

 

[ubuysa]

The one dump shows that the BSOD happened during a graphics operation, we see the Windows DirectX drivers being called repeatedly. You're using the Intel iGPU and the driver for that is a tad old, dating from November 2021...

0: kd> lmDvmigdkmdn64
Browse full module list
start             end                 module name
fffff800`995a0000 fffff800`9b378000   igdkmdn64   (deferred)             
    Image path: \SystemRoot\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_38c9bcde75985bb6\igdkmdn64.sys
    Image name: igdkmdn64.sys
    Browse all global symbols  functions  data  Symbol Reload
    Timestamp:        Mon Nov 15 21:52:08 2021 (6192BA68)
    CheckSum:         01DDB2BC
    ImageSize:        01DD8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

The website for your motherboard has a much more recent version of the Intel graphics driver dated October 16th 2024, I suggest in the first instance that you install that driver.

For the future, please change your system language to English before running the Sysnative data collection app.

 

[andruhasms]

the video driver has been updated When installing the English language, it gives the error "language settings". Error code 0x80240022

 

[ubuysa]

I've no idea what that error is saying. Do you have the English language pack installed?

Now you have updated the graphics driver let's see how things go. If you do get more BSODs run the data collector app again and upload the new output. If you are unable to change the system language to English before running the data collector app then that will very seriously compromise our ability to help you, because we won't be able to read many of the logs.

 

[Maxstar]

This error 0x80240022 has to due with the Windows Update issues and corruptions in the COMPONENTS hive. That is also the reason why the english language package cannot be installed.

 

[andruhasms]

This error 0x80240022 has to due with the Windows Update issues and corruptions in the COMPONENTS hive. That is also the reason why the english language package cannot be installed.

Hi, Any ideas how to fix it? or is there no chance without collecting a log in English?

 

[Maxstar]

Please let us know if you are still experiencing BSODs. If so download the LanguagePack ISO for Server 2019 using the link below.

https://software-download.microsoft...4.rs5_release_SERVERLANGPACKDVD_OEM_MULTI.iso

Extract the English Language Pack and try to install it manually using LPKsetup.exe.
- Open the start menu and type LPKsetup.exe and press enter.
- Then click on "Install display languages"
- Browse to the English Language Pack, click next and accept the terms, then the install will begin.

 

[andruhasms]

Hi, the problem of blue screens has not been solved. The English package is not installed. Just writes are not installed!

 

[ubuysa]

TBH BlueScreenView is about as much use for analyzing dumps as a chocolate teapot.

I also wonder whether your inability to install the English language pack and the 0x80240022 error analyzed above by @Maxstar is just another symptom? I'm starting to question the integrity of your entire Windows system. If we could read the logs we might have more clues.

It's probably worth testing your RAM (that's always worth doing when you have unexplained BSODs)....

1. Download Memtest86 (free)[/*]
2. , use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.[/*]
3. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.[/*]
4. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.[/*]

I would also check your system drive, either with chkdsk /f /x (or chkdsk /r /x if an HDD) - you'll have to reboot afterwards - or with the diagnostic tool/dashboard/Control Panel for your specific SSD drive.