Bsod - thread_stuck_in_device_driver

PiCASSiMO · 08 Apr 2020

It's been a while since I've posted to the forums, where fortunately I haven't had issues with my old build.

Unfortunately, on this Ryzen 5 build (Windows 10, Version 1909, OS Build 18363.752), we've been getting a lot of Windows 10 freezing, along with too many too count BSOD with the THREAD_STUCK_IN_DEVICE_DRIVER message.

Below are both the system info and V2 dump:

Ryzen5BSOD-SystemInfo.zip
RYZEN5-(2020-04-08_19-22-00).zip

BSOD - Google Drive

Many thanks in advance.

Macboatmaster · 08 Apr 2020

1. I see many indications of problems quite part from the BSOD dump which I have NOT let looked at.

2. As the OS on this computer was installed on
InstallDate : 05/27/2019 8:45:50 PM

Why please it is installed in legacy mode. There are a number of reasons why UEFI is the better choice not least of which is Secure boot, enables the ELAM - Early launch Anti Malware which is not available in the legacy - traditional BIOS

3. Is this Windows 10, the same Windows 10 as is in use on the Gigabyte System.

4. Are you turning off by registry key or by some others means the Software Protection Service please.

zbook · 08 Apr 2020

Hi PiCASSiMO,

Welcome to the Ten Forums BSOD forum.

For all steps / tests please post images into the thread:
Take Screenshot in Windows 10

How to Upload and Post Screenshots and Files at Ten Forums

Please perform the following steps:

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

13) Make sure that there is no over clocking while troubleshooting

14) Create a brand new restore point.
Create System Restore Point in Windows 10

15) Sometimes there are problems in the bios that produce BSOD

16) To ensure that there are no improper bios settings please reset the bios

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computer’s CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow
3 Easy Ways to Clear CMOS (Reset BIOS)
How to Clear CMOS (AKA Reset BIOS Settings)

16) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10

17) Uninstall everything AMD using Display driver uninstaller and install new drivers from the AMD website.

18) On the AMD web site be sure the "clean install" box is checked and only install the graphics driver.

Official Display Driver Uninstaller DDU Download

Display Driver Uninstaller Download version 18.0.2.3 (or newer version if available)

Display Driver Uninstaller: How to use - Windows 7 Help Forums

http://support.amd.com/en-us

https://www.amd.com/en/support/kb/faq/rs-install

Code:

Name	AMD Radeon(TM) RX Vega 11 Graphics
PNP Device ID	PCI\VEN_1002&DEV_15D8&SUBSYS_15D81002&REV_C8\4&28056CF2&0&0041
Adapter Type	AMD Radeon Graphics Processor (0x15D8), Advanced Micro Devices, Inc. compatible
Adapter Description	AMD Radeon(TM) RX Vega 11 Graphics
Adapter RAM	(2,147,483,648) bytes
Installed Drivers	C:\Windows\System32\DriverStore\FileRepository\u0353575.inf_amd64_8e19095ae833d985\B353558\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\u0353575.inf_amd64_8e19095ae833d985\B353558\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\u0353575.inf_amd64_8e19095ae833d985\B353558\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\u0353575.inf_amd64_8e19095ae833d985\B353558\amdxc64.dll
Driver Version	26.20.15029.20013
INF File	oem28.inf (ati2mtag_PicassoAM4 section)
Color Planes	Not Available
Color Table Entries	4294967296
Resolution	2560 x 1080 x 60 hertz
Bits/Pixel	32
Memory Address	0xE0000000-0xEFFFFFFF
Memory Address	0xF0000000-0xF01FFFFF
I/O Port	0x0000F000-0x0000F0FF
Memory Address	0xFCB00000-0xFCB7FFFF
IRQ Channel	IRQ 4294967262
IRQ Channel	IRQ 4294967261
IRQ Channel	IRQ 4294967260
I/O Port	0x000003B0-0x000003BB
I/O Port	0x000003C0-0x000003DF
Memory Address	0xA0000-0xBFFFF
Driver	C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\U0353575.INF_AMD64_8E19095AE833D985\B353558\ATIKMPAG.SYS (26.20.15029.20013, 578.22 KB (592,096 bytes), 04/06/2020 10:56 AM)

Code:

atikmdag.sys Fri Feb 28 17:32:59 2020 (5E59A32B)

Code:

atikmpag.sys Fri Feb 28 17:11:58 2020 (5E599E3E)

Macboatmaster · 09 Apr 2020

PiCASSiMO
I will leave you with my colleague
I have always been of the opinion that in issues of analysing and attempting to solve BSOD problems, it is far better from all aspects to work with just one person, until they solve your problem, or reach the end of attempts to do so.

That is only my opinion and whilst "I am the new boy on the block" here on this site, I do have some experience, as you can see from my visitor message.

I am NOT an expert by any means, but as I said I really believe it is far easier for you to be following and responding to just one persons recommendations.

I wish you good luck with it, the only point I would make is, as mentioned on my first reply, it appears to me that your system is installed in legacy BIOS, rather than UEFI

I do not know if that is part of the problem, or indeed the main cause of the problem

https://www.amd.com/en/support/kb/faq/cpu-uefi-mode

For users running the AMD Ryzen™ Processor with Radeon™ Vega Graphics, AMD strongly recommends that your motherboard firmware (“UEFI”) be configured full UEFI Mode to ensure optimal performance, compatibility, and stability with the Windows® 10 operating system

My best wishes for success on the issue and - for you staying safe in this current crisis

PiCASSiMO · 13 Apr 2020

Macboatmaster said:

1. I see many indications of problems quite part from the BSOD dump which I have NOT let looked at.

2. As the OS on this computer was installed on
InstallDate : 05/27/2019 8:45:50 PM
Why please it is installed in legacy mode. There are a number of reasons why UEFI is the better choice not least of which is Secure boot, enables the ELAM - Early launch Anti Malware which is not available in the legacy - traditional BIOS
3. Is this Windows 10, the same Windows 10 as is in use on the Gigabyte System.
4. Are you turning off by registry key or by some others means the Software Protection Service please.

Hello Macboatmaster,

Thank you for the quick response. The Easter holiday's prevented me for responding sooner.

To answer your questions:

1. Not sure why it shows install date of 05/27/2019, as all the hardware purchased for it was back in early October 2019, (including the ASRock B450M-HDV R4.0 motherboard). My guess is that I got the Windows 10 Key outside the normal realms?
2. Legacy Mode. I'm not sure what that really is. I've simply created a new Windows 10 USB drive from MS and then installed Win10 on a new SSD drive. Is there anything I can do to change to UEFI?

3. The Windows 10 copies were procured from two different sources.

4. Software Protection Service. Again, not sure what this is.

Macboatmaster · 13 Apr 2020

My guess is that I got the Windows 10 Key outside the normal realms?
The Windows 10 copies were procured from two different sources.

and then you say

I've simply created a new Windows 10 USB drive from MS

I am not sure I follow what you mean
Perhaps it would help if you could clarify the
Windows 10 key outside the normal realms

PiCASSiMO · 13 Apr 2020

zbook said:

Hi PiCASSiMO,
Welcome to the Ten Forums BSOD forum.
For all steps / tests please post images into the thread:
Take Screenshot in Windows 10
How to Upload and Post Screenshots and Files at Ten Forums
Please perform the following steps:
1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}
12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

Microsoft Windows [Version 10.0.18363.752]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.752

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.752

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is 240GB.

Stage 1: Examining basic file system structure ...
546816 file records processed.
File verification completed.
8903 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
2756 reparse records processed.
737314 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
2756 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
95250 data files processed.
CHKDSK is verifying Usn Journal...
33648544 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

233835519 KB total disk space.
188209388 KB in 437692 files.
273208 KB in 95251 indexes.
0 KB in bad sectors.
658187 KB in use by the system.
65536 KB occupied by the log file.
44694736 KB available on disk.

4096 bytes in each allocation unit.
58458879 total allocation units on disk.
11173684 allocation units available on disk.

C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\RYZEN5\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk1\\Partition2"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\RYZEN5\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk1\\Partition2"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE

C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7

C:\Windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\Windows\system32>

- - - Updated - - -

QUOTE=Macboatmaster;1885631]and then you say
I am not sure I follow what you mean
Perhaps it would help if you could clarify the
Windows 10 key outside the normal realms[/QUOTE]

To clarify... for both of my newly build desktop systems, I've purchased two unique Windows 10 keys off eBay. Then I used Microsoft's Create Windows 10 installation media:

https://www.microsoft.com/en-us/soft...load/windows10

Before booting up each of the newly built systems with that Windows 10 USB drive, followed by entering the unique Win10 keys.

I don't remember any option for Legacy Mode or Software Protection Service during or after the initial installation. I'm not sure if in the case of this latest (Ryzen 5) build that I purchased a bad Windows 10 key?

zbook · 13 Apr 2020

First scannow:

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

Second scannow:

Code:

Windows Resource Protection did not find any integrity violations.

When available please update the progress with each step in post #3.

PiCASSiMO · 13 Apr 2020

zbook said:

13) Make sure that there is no over clocking while troubleshooting
14) Create a brand new restore point.
Create System Restore Point in Windows 10
15) Sometimes there are problems in the bios that produce BSOD
16) To ensure that there are no improper bios settings please reset the bios
16) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10
17) Uninstall everything AMD using Display driver uninstaller and install new drivers from the AMD website.
18) On the AMD web site be sure the "clean install" box is checked and only install the graphics driver.

13. I have not overclocked this AMD Ryzen 3400G CPU/APU.
14. I created a new restore point
15. Although no changes to BIOS have been made since purchase, outside of updating the firmware to Rev 3.7, I have reset the BIOS as request.
ASRock > B450M-HDV R4.0
16. Turned off Windows Fast Start-up.
17/18. Installed latest AMD drivers by including the Factory Reset, that uninstall all drivers, restarted Windows, and re-installed new drivers.

- - - Updated - - -

zbook said:

First scannow:

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

Second scannow:

Code:

Windows Resource Protection did not find any integrity violations.

When available please update the progress with each step in post #3.

I'll fulfill your request tomorrow, but scanning it again after going through all the 18 steps:

Microsoft Windows [Version 10.0.18363.752]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>

zbook · 13 Apr 2020

The earlier steps looked good.

The corruption that was found was fixed running scannow.

For the next few days use the computer as you typically do.
If there are no BSOD or unexpected shutdowns or restarts you can mark the thread solved.
For any BSOD run V2 and upload results directly into the thread.