cancel
Showing results for 
Search instead for 
Did you mean: 

Drivers & Software

sTi
Adept II

PC occasionally freezes during Windows startup

My self-built PC occasionally freezes during windows startup, around 5-10% of the time. 

The freeze always happens around the same time, shortly before the windows desktop should appear. The dots under the user name stop spinning, the computer freezes completely and I have to restart manually. Sometimes after the next boot the AMD graphics driver is deactivated and reverted back to the Microsoft basic display driver. I then have to manually re-activate the  "AMD Radeon graphics" device in the device manager, which suggests to me that the freeze may be related to the graphics driver. Usually the freeze does not leaves a trace in the event log, but very occasionally the freeze may generate a blue screen like this: 

634515a4-d296-4b78-a4d7-2560da3f74db.jpg

 

 

 

==================================================
Dump File         : 110921-5359-01.dmp
Crash Time        : 09.11.2021 12:13:57
Bug Check String  : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code    : 0x100000ea
Parameter 1       : ffffa10d`e264c080
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : amdkmdag.sys
Caused By Address : amdkmdag.sys+1ae5ab
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+3f72a0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\110921-5359-01.dmp
Processors Count  : 16
Major Version     : 15
Minor Version     : 19041
Dump File Size    : 1.877.340
Dump File Time    : 09.11.2021 12:16:21
==================================================

 

 

 

The freeze only happens during startup, once the Windows desktop appears the system is stable (tested with Prime95, Furmark, Memtest...)  

Configuration:  

  • AMD Ryzen 5700G 
  • Asus B550-F Gaming Wifi, latest BIOS 2423 
  • 32GB RAM Crucial DDR4-3200 
  • Seasonic Prime Fanless 500W 
  • Windows 10 Home, Version 21H2, latest updates installed
  • Windows fast boot deactivated 
  • Latest AMD chipset drivers 

DXDiag: https://pastebin.com/Y6R5pmk7  

 

I have tried the following so far: 

Hardware measures

Swapping everything that could cause a hardware-related crash: 

  • CPU: with another 5700G 
  • RAM: With a different 2x16GB kit from a different manufacturer  
  • Mainboard: With another Asus B550-F Gaming Wifi 
  • PSU: With another Seasonic Prime Fanless 500W 
  • SSD: With an SSD from a different manufacturer + reinstall Windows

 

Nothing made a difference. So now I am pretty confident that the issue is not caused by faulty hardware. 

 

Software measures

  • Reinstalling Windows (several times...)
  • Disabling all autostart programs 
  • Disabling all non-Windows services during startup 
  • Reinstalling latest WHQL AMD drivers from AMD website (after removing previous driver with AMD cleanup utility)  (did so several times...)

 

Again, nothing made a difference. Currently I am using the latest driver that I installed manually via Windows update after a clean Windows install, but the issue remains the same. 

I am out of ideas what else to troubleshoot, nothing seems to make a difference. The evidence so far suggests that the freezes are most likely caused by the graphics driver, but what can I do besides doing a clean reinstall of different driver versions (including the one provided by Microsoft Windows update), none of which solved the issue?

30 Replies
amdman
Challenger

Seems to point to AMD drivers or the 5700G conflicting with Citrix, I noticed you have 'Card name: Citrix Indirect Display Adapter'. This could be part of the problem. Others have mentioned that Citrix can sometimes cause problems. Look further into it by searching on this board. Remove it temporarily if you can to see if that fixes it.

Also does it do it with fast start enabled? Turning fast start off does solve some problems, but usually you should be able to just leave it on if the system is fairly new hardware. I hope you get it fixed.

Thank you for your reply. Fast startup is already disabled. Unfortunately I need Citrix for work, so I need to have it installed in some form. Actually I previously suspected that it might be the source of the freezes but a search for issues like this did not turn up anything. For some people it might lead to problems like lower frame rates in games (like in a thread on this board) but I have never found another report about it freezing computers. For troubleshooting purposes I already disabled the autostart entry, and a look at running processes and services confirms that nothing related to Citrix is running after startup. What I could do is disabling the Citrix indirect display adapter in the device manager and just activate it when I actually need it, or wouldn't this make any difference during Windows startup`?

"Turning fast start off does solve some problems, but usually you should be able to just leave it ON if the system is fairly new hardware"

Leave fast start up ON as a test. If that doesn't fix it, try what you were mentioning with disabling Citrix. Hopefully you will be able to find a solution, anything that is a little different can lead to finding the root cause.

0 Likes

Thank you. The freeze also happened before I disabled fast boot, so it does not seem to make a difference.

The jury is still out on whether disabling the Citrix adapter makes a difference. Is there anything else I can check to find the cause?

0 Likes

If it still happens after disabling Citrix, the next step would be to document all the settings for Citrix and uninstall it. Is it easy to configure again for your work? If so, try that. If for some reason you can't do that, other things to try are, did it begin doing this after a driver update? Uninstall the drivers, use AMD Cleanup Utility or DDU in safe mode and install some older AMD drivers. You already reinstalled Windows so it seems that should not be the problem. If you uninstall Citrix and you still see the problem it could be the hardware, maybe a bug in the 5700G, contact the manufacturer and AMD, but you already replaced a bunch of stuff. Maybe a bug in all 5700G? It's a difficult one!

The PC froze again yesterday even with Citrix disabled...

As I have ruled out actual hardware defects by swapping practically everything (see 1st post) and as it has happened with multiple Windows installs and AMD drivers there are now only 2 things left I can think of as likely causes:

  1. AMD graphics driver issues with the Ryzen 5000 series APUs
  2. Asus Bios issues with the Ryzen 5000 series APUs

What would be the best means of getting in touch with either AMD or Asus to work with them on solving this issue?

 

0 Likes

See if by following Citrix Troubleshooting procedures might fix your problem: https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/director/troubleshoot-deployments/user-is...

Screenshot 2022-01-06 123016.png

@amdman  is correct the Citrix has caused many problems with other drivers.

If possible try booting into a Clean Windows environment. This basically running Safe Mode on a regular Windows desktop with all 3rd party startups disabled. If Windows boots up fine then start enabling 3rd party startups to see which one is causing Windows to freeze during loading of Windows OS: How to perform a clean boot in Windows 

EDIT: Have you tried to use Asus own AMD VGA Driver and install the latest Asus AMD CHIPSET Driver package?

You can open a AMD Support ticket from here: https://www.amd.com/en/support/contact-email-form as for Asus Support I suggest you use the Chat feature which is fastest under Asus Warranty: https://rog.asus.com/us/motherboards/rog-strix/rog-strix-b550-f-gaming-wi-fi-model/helpdesk_warranty

Screenshot 2022-01-06 123016.png

You will need your Asus Motherboard S/N to start the Chat session.

Thank you for your reply. I already tried the "clean boot" strategy and the freezes also occurred with all autostart and services disabled.

As for the drivers: I tried

  1. The Asus way: All drivers installed directly from Asus
  2. The AMD way: Latest graphics & chipset drivers directly from AMD, nothing from Asus
  3. The Microsoft way: Graphics driver installed from Windows update.

All three strategies showed the same occasional freezes during Windows startup.

 

0 Likes

Edit this reply after re-reading your original post.

So you have used a different SSD, Motherboard, RAM and installed Windows from scratch with the same results.

When you install Windows again did the issue appear again before you started installing any 3rd party programs?

If the issue didn't occur after installing a fresh Windows than try installing all your 3rd party programs except Citrix and see if the problems occurs. That would definitely remove Citrix as the culprit causing your hangup when Windows loads.

You can also enable Windows Verifier to see which driver exactly is causing your startup issue. You can google Windows Verifier to see how to use that helpful Windows  Troubleshooting feature.

I would open a AMD Support - Warranty ticket and see if your CPU might be defective even though personally I don't believe your symptoms are from a defective processor from here unless it is related to the Integrated Graphics: https://www.amd.com/en/support/contact-email-form

Does Device Manager show any errors when you open it?

How about Windows Event Viewer under Errors?

Anything that can lead you to find out what hardware or software is causing the issue?

 

0 Likes

Thanks, I will re-check if Citrix is an issue and also try the Verifier. Although by now I am pretty confident that the driver causing this is the AMD display driver as after some freezes the iGPU reverts back to the Microsoft basic display driver after re-starting. The problem is that I have tried all sensible versions of the ´graphics driver by now and they all show the same problem.

As I already swapped the CPU I can rule out a defect there.

The Device manager looks fine. Unfortunately the freezes never leave a trace in the event log. 

I will also contact AMD and Asus and see if they can help.

 

What I am trying to find out is if the AMD driver is in conflict with another program or driver.

Since you physically used different hardware with the same results seems to indicate a driver conflict. Since you mentioned you have used several AMD Driver versions with the same results. This indicates it isn't a AMD Driver issue per se but rather either a conflict with another driver or program or your APU processor might be defective.

You don't have a GPU Card installed do you? Not sure if you mentioned it or not in your previous replies.

Windows Verifier is good for finding troublesome drivers. But you need to know how to use it correctly to be useful.

Does DXDIAG.exe saved file show anything under the last category -Diagnostic- in the saved DXDIAG file?

By the way this isn't a Server type environment is it?

Because if it is maybe by posting at AMD Forum's Server GURUS (https://community.amd.com/t5/server-gurus/ct-p/amd-server-gurus) you might get better answers.

 

Thank you for your help. Here is a copy of the diagnostics section:

Spoiler

---------------
Diagnostics
---------------

Windows Error Reporting:
+++ WER0 +++:
Fehlerbucket 1290034324207024344, Typ 5
Ereignisname: RADAR_PRE_LEAK_64
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: 7zG.exe
P2: 21.6.0.0
P3: 10.0.19044.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Angefügte Dateien:
\\?\C:\Users\stefa\AppData\Local\Temp\RDR14E.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER15E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER16F.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER17D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER19D.tmp.txt

Diese Dateien befinden sich möglicherweise hier:


Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 2b4e7348-9193-40a6-b62c-e28a64c9f251
Berichtstatus: 268435456
Bucket mit Hash: 307db721f6b197b471e71f620a6bb8d8
CAB-Datei-Guid: 0
+++ WER1 +++:
Fehlerbucket 1463731736759330275, Typ 5
Ereignisname: RADAR_PRE_LEAK_64
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: rawtherapee.exe
P2: 0.0.0.0
P3: 10.0.19044.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Angefügte Dateien:
\\?\C:\Users\stefa\AppData\Local\Temp\RDR7848.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7859.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7869.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7877.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7897.tmp.txt

Diese Dateien befinden sich möglicherweise hier:


Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: eb9b465a-7bbc-4bfa-900f-641288e1efe7
Berichtstatus: 268435456
Bucket mit Hash: d690bc04dd5aa05ea4503842680165e3
CAB-Datei-Guid: 0
+++ WER2 +++:
Fehlerbucket 1999206449981989218, Typ 5
Ereignisname: BEX
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: phonostar.exe
P2: 4.1.5.0
P3: 61b1e7df
P4: StackHash_2beb
P5: 0.0.0.0
P6: 00000000
P7: PCH_E0_FROM_ntdll+0x00072F8C
P8: c0000005
P9: 00000008
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE427.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE580.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE591.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE58F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE5AF.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_phonostar.exe_47ac4a9afeeee34da4335a586336c074eefae8_4c536058_e5aa905f-2f5b-4578-b71d-3ce915e984e2

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: e7130d90-a345-4f26-bba7-e180f1909c81
Berichtstatus: 268435456
Bucket mit Hash: 7e6e8ad18d78b5afbbbe9bac8bd8a162
CAB-Datei-Guid: 0
+++ WER3 +++:
Fehlerbucket , Typ 0
Ereignisname: LiveKernelEvent
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: 193
P2: 801
P3: ffffffffc0000001
P4: 0
P5: 0
P6: 10_0_19044
P7: 0_0
P8: 768_1
P9:
P10:

Angefügte Dateien:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211224-1539.dmp
\\?\C:\Windows\TEMP\WER-95796-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DB6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DC7.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DC6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DD7.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_193_4c6b3c6c89168961fe1c755672a717ef132480ff_00000000_cab_efea7460-80b8-4d88-8be4-27dc2927c6da

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: efea7460-80b8-4d88-8be4-27dc2927c6da
Berichtstatus: 2049
Bucket mit Hash:
CAB-Datei-Guid: 0
+++ WER4 +++:
Fehlerbucket , Typ 0
Ereignisname: LiveKernelEvent
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: 193
P2: 801
P3: ffffffffc0000001
P4: 0
P5: 0
P6: 10_0_19044
P7: 0_0
P8: 768_1
P9:
P10:

Angefügte Dateien:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20211224-1539.dmp
\\?\C:\Windows\TEMP\WER-95796-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DB6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DC7.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DC6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DD7.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_193_4c6b3c6c89168961fe1c755672a717ef132480ff_00000000_efea7460-80b8-4d88-8be4-27dc2927c6da

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: efea7460-80b8-4d88-8be4-27dc2927c6da
Berichtstatus: 4
Bucket mit Hash:
CAB-Datei-Guid: 0
+++ WER5 +++:
Fehlerbucket , Typ 0
Ereignisname: AppHangTransient
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: FreeCommander.exe
P2: 2022.0.0.860
P3: 61bcc31d
P4: unknown
P5: unknown
P6: unknown
P7: unknown
P8:
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3565.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3576.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3577.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3597.tmp.txt

Diese Dateien befinden sich möglicherweise hier:


Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 7d20cb34-bc28-489e-a5e4-7c261b39a3d7
Berichtstatus: 2049
Bucket mit Hash:
CAB-Datei-Guid: 0
+++ WER6 +++:
Fehlerbucket 1881821357096669146, Typ 5
Ereignisname: AppHangB1
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: FreeCommander.exe
P2: 2022.0.0.860
P3: 61bcc31d
P4: f649
P5: 134217728
P6:
P7:
P8:
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAF.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBC0.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBCE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBDF.tmp.txt
\\?\C:\Users\stefa\AppData\Local\Temp\WER5B82.tmp.appcompat.txt

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_FreeCommander.ex_2b338a47cc4d3585de42a65e63ebe7a6794a20_9cb492f3_40c4f9ef-9fb0-44f1-8d43-19b7bb7b7753

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: f7f98d3e-7bb6-4d9b-8a80-d0b0628e9451
Berichtstatus: 268435456
Bucket mit Hash: 0d07ce3a64d4ecb87a1d928dd07d8fda
CAB-Datei-Guid: 0
+++ WER7 +++:
Fehlerbucket 2098073175763247046, Typ 5
Ereignisname: RADAR_PRE_LEAK_64
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: mpc-hc64.exe
P2: 1.9.17.0
P3: 10.0.19044.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Angefügte Dateien:
\\?\C:\Users\stefa\AppData\Local\Temp\RDRC5FC.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC60D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC61D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC62B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC64B.tmp.txt

Diese Dateien befinden sich möglicherweise hier:


Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: c4bf662a-3b64-4de4-ab70-0c72a9b82c1b
Berichtstatus: 268435456
Bucket mit Hash: 3482827afb2752d9bd1dda6ff224dfc6
CAB-Datei-Guid: 0
+++ WER8 +++:
Fehlerbucket 1419338929418093800, Typ 1
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: phonostar.exe
P2: 4.1.5.0
P3: 61b1e7df
P4: Qt5Widgets.dll
P5: 5.11.2.0
P6: 5b99eb14
P7: c0000005
P8: 000360bd
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FEE.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4147.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4157.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4155.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4166.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_phonostar.exe_d8cbe02b7907a135924f225377a531bc62e156_4c536058_e895f0f8-315b-4cc6-b25c-4f37305d4d21

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: b8ac2909-294d-4724-92e4-5979c219f265
Berichtstatus: 268435456
Bucket mit Hash: 7c59d2907a14af0bc3b2813c7fd944e8
CAB-Datei-Guid: 0
+++ WER9 +++:
Fehlerbucket 1713879425175554666, Typ 5
Ereignisname: WindowsWcpOtherFailure3
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: 10.0.19041.1371:1
P2: wcp\componentstore\storelayout.cpp
P3: ComponentStore::CRawStoreLayout::HydrateFileUsingForwardAndReverseDeltas
P4: 1682
P5: 800f0984
P6: 0xd994330e
P7:
P8:
P9:
P10:

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6ED0.tmp.WERInternalMetadata.xml

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_10.0.19041.1371__e5cb5417e0db8386a01ad51dc853893d7e3aff76_00000000_62d3e9b8-0549-42fa-9a8a-4d24ccb6dcca

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 62d3e9b8-0549-42fa-9a8a-4d24ccb6dcca
Berichtstatus: 268435456
Bucket mit Hash: c2ac544a497516dff7c8ec41b5708a6a
CAB-Datei-Guid: 0

I don't have a GPU installed, I just use the iGPU. This is not a server, just a normal PC.

0 Likes

Thank you for your help. I don't have a GPU, just the iGPU. It's not a server, just a regular PC.

This is a copy of the diagnostics section: 

https://pastebin.com/CebcxGxB

 

0 Likes

Thanks for the DXDIAG file.

First I noticed your Windows wcp\componentstore\storelayout.cpp is corrupted.

I would run in a elevated Command Prompt or Powershell the following commands to repair your Window Component Store:

Dism /Online /Cleanup-Image /ScanHealth


Dism / Online / Cleanup-Image / CheckHealth


Dism /Online /Cleanup-Image /RestoreHealth


Also you can run this command:


Dism.exe /online /Cleanup-Image /StartComponentCleanup

 

 

 

 

0 Likes

According to your DXDIAG these are the program that are recognizable as having issues in your PC:

1-Phonostar.exe - Does this program involve video or video driver? Found several errors concerning this program

2-mpc-hc64.exe - Which is part of the K-Lite Codec package ( I used K-Lite Codecs also)

3-FreeCommander.exe - Free Commander program. Found a couple of errors concerning this program

4-RawTherapee - Raw Image Processing program. Does this program install any drivers to your knowledge?

Note: Needed to use my Browser's Translation Extension to translate selected sentences into English.

EDIT: I needed to make a second reply because the above text as it is posted in this reply when added to my last reply gave me an error concerning "HTML Text Highlighted"

 

 

 

0 Likes

Thanks for your analysis. I ran the dism commands as you suggested, but it told me it could not find any errors.

As for the programs:

Phonostar was only for installed for a short time (after the issues started) and is already removed.

MPC-HC is standalone, I did not install any codec packs. It comes with integrated LAV-Filters.

Free Commander is just a file manager, I doubt it installs a driver.

Same for RawTherapee, I am pretty sure it does not install drivers.

Anyway, the freezes always occur at Windows startup (shortly before the desktop would appear), and none of these programs run at start-up or start a service at logon, so I am not sure if it is even possible for them to interfere at this stage?

 

0 Likes

If Windows freezes before reaching the desktop does indicate a driver or startup program issue or possible a hardware issue.

This Tech site gives several tips for Windows freezing: https://helpdeskgeek.com/help-desk/windows-10-keeps-freezing-up-9-ways-to-fix/

also this site: https://www.easeus.com/computer-instruction/fix-windows-10-freezing-randomly.html and https://www.partitionwizard.com/partitionmagic/win10-freezes-randomly.html

Image from the last link - Partition Magic:

Screenshot 2022-01-06 123016.png

All three pretty much the same troubleshooting tips. Some that you have done already.

EDIT: I believe running Windows  Verifier is your best bet to see if it is a driver causing the problem or verify it is the AMD Driver.

 

Thanks, one thing I found that I didn't try before was disabling the "PCI Express Link State Power Management" in energy options, so I will try this and tomorrow will run the driver verifier. I will report back with any findings.

0 Likes

@elstaci  Thanks again for your help. I may actually have found the culprit. After letting Windows Driver Verifier run for hours without issue I started up the Citrix Workspace App and logged into my account. Before the virtual desktop finished loading the PC crashed with this BSOD:

20220108_155858_cr.jpg

...which with the "damaged graphics" look reminded me of the one I encountered at a crash during a Windows boot some weeks earlier (see post 1). The minidump showed the following:

BSV.jpg

==================================================
Filename          : ctxusbmon.sys
Address In Stack  : ctxusbmon.sys+e000
From Address      : fffff807`93f50000
To Address        : fffff807`93f73000
Size              : 0x00023000
Time Stamp        : 0x611a964a
Time String       : 16.08.2021 17:46:02
Product Name      : Citrix XenApp & XenDesktop
File Description  : Citrix Client-side Usb Monitor Driver for Windows.
File Version      : 7.31.0.49
Company           : Citrix Systems, Inc.
Full Path         : C:\Windows\system32\drivers\ctxusbmon.sys
==================================================

==================================================
Filename          : VerifierExt.sys
Address In Stack  : VerifierExt.sys+2702b
From Address      : fffff805`359b0000
To Address        : fffff805`35a51000
Size              : 0x000a1000
Time Stamp        : 0x2a7d1250
Time String       : 03.08.1992 12:02:40
Product Name      : Betriebssystem Microsoft® Windows®
File Description  : Treiberüberprüfungserweiterung
File Version      : 10.0.19041.1415 (WinBuild.160101.0800)
Company           : Microsoft Corporation
Full Path         : C:\Windows\system32\drivers\VerifierExt.sys
==================================================

 

I repeated this 2 more times, with exactly the same BSOD result. The minidumps can be downloaded from here.

The misbehaving driver seems to be ctxusbmon.sys, a "Citrix Client-side Usb Monitor Driver for Windows". I checked the boot log and this driver is loaded during Windows boot even with Citrix Indirect Display adapter and autostart entries disabled. So for now unfortunately the only solution seems to be to completely remove the Citrix Workspace App. I will report the issue to Citrix and hope they can do something about it.

 

Good Troubleshooting!

Yes I have read that Citrix does cause issues with other drivers.

Take care and Glad you at least are in the right direction in having a stable PC  again.

Note: Actually @amdman was the one that caught on to Citrix possibly being the cause of your issue,which I missed when I first read your original post.

Glad you got it fixed, definitely a concerted effort from all to fix this, goes to show the more eyes you have on the problem, the greater chance at finding the root cause and fixing it!

Thanks again to all who helped solve the issue.

Great forum here!

Unfortunately I had to remove the "solved" status as the Bluescreens keep happening even after I removed Citrix. 

Here is an excerpt from a bluescreen view of a crash still with the AMD graphics driver from Windows Update: 

==================================================
Dump File : 011722-5312-01.dmp
Crash Time : 17.01.2022 08:58:14
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff801`3ccd2b70
Parameter 3 : ffffd781`1f35eb90
Parameter 4 : 00000000`00000000
Caused By Driver : dxgmms2.sys
Caused By Address : dxgmms2.sys+d2b70
File Description : DirectX Graphics MMS
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.19041.1466 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3f72e0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\011722-5312-01.dmp
Processors Count : 16
Major Version : 15
Minor Version : 19041
Dump File Size : 492.873
Dump File Time : 17.01.2022 08:58:54
==================================================

I then tried again with the latest version of the graphics driver from AMD directly from 7 January and also removed the old one beforehand with DDU in safe mode. But today I had another blue screen shortly after booting up. Strangely, the boot logo is displayed again in the lower half, although the Windows desktop was already running before the bluescreen:

20220131_083546.png

 

Here is an excerpt from Bluescreenview:

==================================================
Dump File : 013122-5265-01.dmp
Crash Time : 31.01.2022 08:34:50
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x000000ea
Parameter 1 : ffffc504`ae99a280
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+445ad
File Description : DirectX Graphics Kernel
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.19041.1466 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3f73b0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\013122-5265-01.dmp
Processors Count : 16
Major Version : 15
Minor Version : 19041
Dump File Size : 523.267
Dump File Time : 31.01.2022 08:36:29
==================================================

Minidumps complete:

https://1drv.ms/u/s!AiCg1jUcK9R_zQEuhF-Jo5DoRnxH?e=Yh8lAl 

DXDiag: https://pastebin.com/EKAseVED  

Does this provide any new clues as to what might be causing this?

0 Likes

It's a tough one. I'd go through this list especially checking the Memory and Windows repair sections. It is entirely possible that you have a hardware failure or malware/virus. I hope not, I hope you can find a solution.

https://helpdeskgeek.com/windows-10/how-to-fix-the-dxgmms2-sys-bsod-error-in-windows-10/

Edit: At this point it may be a good idea to reinstall everything except certain programs like:

Phonostar was only for installed for a short time (after the issues started) and is already removed.

MPC-HC is standalone, I did not install any codec packs. It comes with integrated LAV-Filters.

Free Commander is just a file manager, I doubt it installs a driver.

Same for RawTherapee, I am pretty sure it does not install drivers.

And see if the problem doesn't occur, I have had several problems that I didn't think were software related, and when I removed the program, the problems went away. Try to isolate the problem, it's difficult especially if you use those for work. Essentially whatever is causing it does it occur with just Windows and drivers installed? If no, then install each program and run for a while to see where the problem is. A strong point of Windows is the dearth of applications, but it causes problems too, freedom comes at a cost. Good luck!

Thank you for your assessment. The hardware - OK, it may look like it. The problem is that I have already replaced practically everything relevant:

AMD Ryzen 5700G: already exchanged 1:1 for a new one

Asus B550 mainboard: already exchanged 1:1 for a new one

Seasonic power supply: already exchanged 1:1 for a new one (incl. connection cable)

Samsung SSD: exchanged for Western Digital SSD (incl. reinstallation of Windows)

Crucial RAM: Short exchange against G.Skill RAM (on the QVL list), since no improvement back to Crucial.

The only thing that is still the same as at the beginning is the RAM. I have already tested clocking it down and ran it through various memory and other stress tests (Memtest86, Testmem5, OCCT, Prime 95, Furmark) for hours without any problems. The freezes and bluescreens only ever occur when booting up shortly before the desktop appears or directly when starting the first programme, as soon as this critical phase is over everything runs perfectly stable and also passes all stress tests without any problems. I have also run the Windows Driver Verifier for hours without any further issues. I am really at a loss now. Would it be worth testing another brand of RAM maybe or is this unlikely to be a RAM defect or incompatibility?

0 Likes

Some motherboards when using two sticks of RAM it's recommended to have them in slots 2 and 4, you could try 1 and 3 just to see if it would make a difference. Some of these edge cases where it's so hard to track down what is causing it are the toughest problems you can troubleshoot. If you can try to find a cheap discrete GPU (yeah, I know one of the worst markets ever right now) and see if that might fix it. If you switch the RAM to another manufacturer and still have the problem, it appears to be the software, or even look at your wall outlet and make sure it's not got some sort of problem. Good luck!

Hello. I'm having the same problem, randomly encountering bsod. Did you solve your problem?

0 Likes
ssaradpon
Adept I

Glad you got this sorted!

knepich
Adept II

Did you solve the issue? I have the same issue with the latest amd drivers for my 7900xtx:-/

0 Likes
knepich
Adept II

Not sure if you solved this, but try disable PCIE native power management in Bios.

This will stop the powersaving mode for your gpu and make it more stable at booting