Ongoing BSOD in custom build, irql_not_less_or_equal

awarthestel · 29 Feb 2020

I have the occasional irql bsod that happens every few computer sessions, sometimes weeks apart. This time it was irql_not_less_or_equal , atikmdag.sys. Any help would be greatly appreciated!

Windows version 1909 (18363.657)

zbook · 29 Feb 2020

Hi awarthestel,

Welcome to the BSOD forum.

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) Uninstall everything AMD using Display driver uninstaller and install new drivers from the AMD website.

15) 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.2 (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

https://support.amd.com/en-us/downlo...indows+10+-+64

Code:

atikmdag.sys Fri Jan 17 12:09:46 2020 (5E22148A)

awarthestel · 02 Mar 2020

Microsoft Windows [Version 10.0.18363.657]
(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.1

Image Version: 10.0.18363.657

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

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

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

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

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

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

975659841 KB total disk space.
437487220 KB in 471865 files.
262924 KB in 72044 indexes.
0 KB in bad sectors.
984169 KB in use by the system.
65536 KB occupied by the log file.
536925528 KB available on disk.

4096 bytes in each allocation unit.
243914960 total allocation units on disk.
134231382 allocation units available on disk.

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

C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\MINAS-ITHIL\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\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 - - -

I removed and reinstalled the graphics drivers. It ran smoothly for about a day or two and just bsod tonight. This time irql_not_less_or_equal on fwpkdnt.sys. The bsod got hung up for a while and it didn't post a new .dmp file.

zbook · 02 Mar 2020

For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

awarthestel · 03 Mar 2020

Here you go--

Dropbox - pc troubleshoot - Simplify your life

zbook · 03 Mar 2020

1) Turn off Windows updates of non-Microsoft drivers:

Enable or Disable Driver Updates in Windows Update in Windows 10

2) Uninstall AMD GPU drivers using DDU

3) Find an earlier version (do not reinstall 26.20.15015.1007)

4) If there are recurrent BSOD despite multiple driver versions then the hardware needs to be tested

5) See if you can find a friend, neighbor, relative, or local computer store to swap the GPU card.
The swap can be AMD or Nvidia.

6) Perform two tests:
a) Test a new card in the problematic computer
b) Test the card from the problematic computer in another computer

Code:

Name	AMD Radeon RX 5700 XT
PNP Device ID	PCI\VEN_1002&DEV_731F&SUBSYS_38101462&REV_C1\6&139E6340&0&00000008
Adapter Type	AMD Radeon Graphics Processor (0x731F), Advanced Micro Devices, Inc. compatible
Adapter Description	AMD Radeon RX 5700 XT
Adapter RAM	(1,048,576) bytes
Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\u0351300.inf_amd64_6d6cbd77ac26f221\B351053\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0351300.inf_amd64_6d6cbd77ac26f221\B351053\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0351300.inf_amd64_6d6cbd77ac26f221\B351053\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0351300.inf_amd64_6d6cbd77ac26f221\B351053\amdxc64.dll
Driver Version	26.20.15015.1007
INF File	oem21.inf (ati2mtag_Navi10 section)
Color Planes	Not Available
Color Table Entries	4294967296
Resolution	1920 x 1080 x 60 hertz
Bits/Pixel	32
Memory Address	0xE0000000-0xF01FFFFF
Memory Address	0xF0000000-0xF01FFFFF
I/O Port	0x0000E000-0x0000EFFF
Memory Address	0xF7B00000-0xF7BFFFFF
IRQ Channel	IRQ 4294967291
I/O Port	0x000003B0-0x000003BB
I/O Port	0x000003C0-0x000003DF
Memory Address	0xA0000-0xBFFFF
Driver	C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\U0351300.INF_AMD64_6D6CBD77AC26F221\B351053\ATIKMPAG.SYS (26.20.15015.1007, 577.80 KB (591,672 bytes), 1/27/2020 4:44 PM)

Code:

atikmdag.sys Fri Jan 17 12:09:46 2020 (5E22148A)

awarthestel · 04 Mar 2020

Thanks again, I uninstalled and rolled back to 26.20.11000.13586. I'll swap the gpu with the other one in our house and let you know what I find.

- - - Updated - - -

I swapped out my gpu for another last night and just BSOD again, this time kernel_security_check failure. I've uploaded the log file, but again windows did not write a new memory.dmp and the log pulled in the old one from February 29.

zbook · 04 Mar 2020

Windows driver verifier is a tool that stresses drivers.
Misbehaving drivers may be able to be debugged from dump files.

Read these links: (learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode)

Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Make a new restore point:

Create System Restore Point in Windows 10

Start the tool with the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 displayed in the Microsoft link.

There can be performance problems and slow boot while using the tool.
If necessary the customized settings can be modified.

Plan to run the tool for 48 hours and for an additional 36 hours after the last BSOD.

For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive