New Laptop BSOD Thread Stuck In Device Driver

Hello. Had a BSOD on my two week old Lenovo Ideapad 5 Ryzen laptop. Seemingly a driver issue? Not sure so would appreaciate any help

Attachment 282643

See posting instructions.

Apologies.
Attachment 282675

New computers should not have BSOD.

Contact the computer manufacturer or vendor for Return Merchandise Authorization (RMA).

The computer has AMD CPU with integrated GPU.
The AMD GPU driver was misbehaving in the single BSOD.

Most BSOD are caused by misbehaving hardware and software drivers.
The next most common cause of BSOD is malfunctioning hardware.

On a desktop you can replace one component.
End users ordinarily cannot replace laptop hardware components and need servicing by the manufacturer or local computer store.

These are troubleshooting 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

Use this link as needed when posting results:
How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com

13) If you want to replace the driver:

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

b) The Lenovo web site is preferred:
laptops and netbooks :: 5 series :: ideapad 5 15are05 :: 81yq :: 81yqcto1ww :: pf297f3f - IE

c) Enter the computer's serial or product number and the operating system to view available drivers.

d) If you use 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.5 (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) Graphics
PNP Device ID	PCI\VEN_1002&DEV_1636&SUBSYS_381B17AA&REV_C1\4&20C24D55&0&0041
Adapter Type	AMD Radeon Graphics Processor (0x1636), Advanced Micro Devices, Inc. compatible
Adapter Description	AMD Radeon(TM) Graphics
Adapter RAM	(2,147,483,648) bytes
Installed Drivers	C:\Windows\System32\DriverStore\FileRepository\u0354027.inf_amd64_336bd49b79c0cb05\B354016\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\u0354027.inf_amd64_336bd49b79c0cb05\B354016\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\u0354027.inf_amd64_336bd49b79c0cb05\B354016\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\u0354027.inf_amd64_336bd49b79c0cb05\B354016\amdxc64.dll
Driver Version	27.20.1002.34
INF File	oem33.inf (ati2mtag_Renoir section)
Colour Planes	Not Available
Colour Table Entries	4294967296
Resolution	1920 x 1080 x 60 hertz
Bits/Pixel	32
Memory Address	0xD0000000-0xDFFFFFFF
Memory Address	0xE0000000-0xE01FFFFF
I/O Port	0x00001000-0x000010FF
Memory Address	0xFC400000-0xFC47FFFF
IRQ Channel	IRQ 4294967253
IRQ Channel	IRQ 4294967252
IRQ Channel	IRQ 4294967251
IRQ Channel	IRQ 4294967250
I/O Port	0x000003B0-0x000003BB
I/O Port	0x000003C0-0x000003DF
Memory Address	0xA0000-0xBFFFF
Driver	C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\U0354027.INF_AMD64_336BD49B79C0CB05\B354016\AMDKMDAG.SYS (27.20.1002.34, 67.71 MB (70,999,256 bytes), 28/04/2020 19:41)

Code:

amdkmdag.sys Wed Apr  1 18:00:02 2020 (5E851CF2)

Code:

09/06/2020 00:40	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 100000ea
P2: ffffbc8e1627c080
P3: 0
P4: 0
P5: 0
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\060920-9593-01.dmp
\\?\C:\Windows\TEMP\WER-14593-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER494D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER496D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER499B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49BC.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_100000ea_36bc95eb78b32a1c6adcde1dcb17d15224c_00000000_cab_c85ade54-e027-4321-b0af-d2e4b014bf08

Analysis symbol: 
Rechecking for solution: 0
Report Id: f16e63b9-49ef-4e0d-a657-5853cb32f611
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
09/06/2020 00:40	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 100000ea
P2: ffffbc8e1627c080
P3: 0
P4: 0
P5: 0
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\060920-9593-01.dmp
\\?\C:\Windows\TEMP\WER-14593-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER494D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER496D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER499B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49BC.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_100000ea_36bc95eb78b32a1c6adcde1dcb17d15224c_00000000_c85ade54-e027-4321-b0af-d2e4b014bf08

Analysis symbol: 
Rechecking for solution: 0
Report Id: f16e63b9-49ef-4e0d-a657-5853cb32f611
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Thanks for your response. Here's the cmd prompt results;

Microsoft Windows [Version 10.0.18363.900]
(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>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.900

Image Version: 10.0.18363.900

[==========================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.900

Image Version: 10.0.18363.900

[==========================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>
C:\Windows\system32>chkdsk/scan
The type of the file system is NTFS.

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

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

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

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

249397247 KB total disk space.
189205784 KB in 257915 files.
167412 KB in 69457 indexes.
0 KB in bad sectors.
450751 KB in use by the system.
65536 KB occupied by the log file.
59573300 KB available on disk.

4096 bytes in each allocation unit.
62349311 total allocation units on disk.
14893325 allocation units available on disk.

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

C:\Windows\system32>wmic recoveros set DebuginfoType = 7
Updating property(s) of '\\DESKTOP-MFJUBF7\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
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)
The specified entry type is invalid.
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.

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

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

C:\Windows\system32>

Will replace the graphics driver as you instructed, hopefully will do the trick

If it were not a brand new laptop you would replace the iGPU driver and monitor for additional BSOD.
If there are additional BSOD then you would test alternative drivers.
If alternative drivers produce BSOD then swap or replace the CPU/GPU (typically requires servicing at the computer manufacturer or local computer store).
If there are BSOD after replacing the CPU/GPU then replace the motherboard.

Given that this is a brand new laptop it should be without BSOD.
A RMA is recommended so that you start with a trouble-free computer.

Taggart said:

...
Seemingly a driver issue? Not sure so would appreaciate any help

I have the same issue with Windows 10 Build 2004. It doesn't matter if I use official lenovo driver or AMD stable/beta.

The problem solved when I install Build 1909.

I encountered the same problem before and there are a lot of solutions posted on Microsoft Community. But most of them are not sorted together in a single post. I tried out those methods and mysteriously my computer works well again. I'm not sure which of them fixed the issue, but I have used the following solutions:



Solution 1: Update Drivers

Sometimes, the computer users might install the incompatible hardware driver to the system, or the driver was corrupted or damaged during the installation, then we may encounter the Windows 10 thread stuck in device driver error after rebooting; hence, at the very first beginning, we should update the hardware drivers to the latest version in the Device Manager.

Step 1: Press Win + Q and type Device Manager, and open it.

Step 2: Look for the problematic device and then expand its tree.

Step 3: Right-click on the driver entry and click on Update driver.

Step 4: Repeat the steps to update other wanted drivers.

Solution 2: Update Windows

In some cases, the error could result from an operating system that has been updated for a considerable time. Therefore, you can try to update the operating system using the following steps:

Step 1: Right-click the Start Menu and select Settings.

Step 2: Navigate to Update & Security > Windows Update.

Step 3: On the right page, check out whether there is an update available. If so, download and install it.

Step 4: After the installation, restart your computer to see if the error persists.

There are other solutions that are too complicated to be posted here, if the aforementioned solutions don't work, you could check out this article:
Fix: Thread Stuck in Device Driver Error [16 Solutions] - Bitwarsoft