Solved BSOD UNEXPECTED_KERNEL_MODE_TRAP

Gianmarco · Aug 17, 2023

x BlueRobot said:
Thanks, it looks like everything ran successfully, let's just double check that the Microsoft Gaming Services app has been removed though, using the following Powershell command:

Code:

Get-AppxPackage -AllUsers *GamingServices*

You will need to run it from an administrative (elevated) Powershell window. Please post the output in your next post.

Seems to be stopped, maybe?

zbook said:
Please continue / complete WDV testing as per post #48.

Restarting pc with all the cutomized test and let's see what happen.

x BlueRobot · Aug 17, 2023

Gianmarco said:
Seems to be stopped, maybe?

Yeah it should be completely removed, hopefully it will now mean that gameflt.sys isn't installed again.

Gianmarco · Aug 18, 2023

zbook said:
Please continue / complete WDV testing as per post #48.

Near the end of the 24hours testing, arrived a BSOD. Here the link to log: BSOD-(2023-08-18_10-21-44).zip
The WDV is still running after reboot

zbook · Aug 18, 2023

The WDV run was without [ ] 0x00000004 Randomized low resources simulation.

How come it was not included?

If there were major performance problems including very slow boot please restart WDV
using only [ ] 0x00000004 Randomized low resources simulation

If there were no performance problems then restart WDV using all customized tests including [ ] 0x00000004 Randomized low resources simulation

The goal is to see whether WDV causes a driver to crash.

Run the tool continuously for 24 hours.

The findings so far are typical of malfunctioning or incompatible hardware.

Memtest86 only tests for malfunctioning RAM.

It was not designed to test for incompatible RAM.

The installed RAM were seen on a QVL for a CPU not present in this computer.

If you saw these together on the QVL please post images or share links into this thread:

RAM: CMW32GX4M2D3600C18
CPU: Ryzen 7 3800XT

If you're not able to find these hardware together on the QVL then swap test RAM on the QVL.

At the same time open a support ticket with ASUS and ask them about the use of these CPU and RAM on the same computer.

Gianmarco · Aug 18, 2023

zbook said:
The WDV run was without [ ] 0x00000004 Randomized low resources simulation.

How come it was not included?

If there were major performance problems including very slow boot please restart WDV
using only [ ] 0x00000004 Randomized low resources simulation

If there were no performance problems then restart WDV using all customized tests including [ ] 0x00000004 Randomized low resources simulation

The goal is to see whether WDV causes a driver to crash.

Run the tool continuously for 24 hours.

The findings so far are typical of malfunctioning or incompatible hardware.

Memtest86 only tests for malfunctioning RAM.

It was not designed to test for incompatible RAM.

The installed RAM were seen on a QVL for a CPU not present in this computer.

If you saw these together on the QVL please post images or share links into this thread:

RAM: CMW32GX4M2D3600C18
CPU: Ryzen 7 3800XT

If you're not able to find these hardware together on the QVL then swap test RAM on the QVL.

At the same time open a support ticket with ASUS and ask them about the use of these CPU and RAM on the same computer.

The missing test is my fault.
Cpu and ram are compatible as you can see from the image attached, I used the corsair builder here to check MB, CPU, RAM and GPU (case is just a missclick): Custom PC Builder | PC Build Guide | CORSAIR

zbook · Aug 18, 2023

If there were no significant performance problems then run WDV with all customized tests for 48 hrs.

a) Test all non-Microsoft drivers
b) Test no Microsoft drivers

Post a querysettings or V2 as needed.

x BlueRobot · Aug 18, 2023

It looks like another Stop 0x7F, I would suggest that you remove any ASUS motherboard software, particularly anything which uses AsIO*.sys which used to cause several problems on Windows 7 machines. I'm not sure what it is like now but I feel it is a worthwhile troubleshooting step.

I would use the ASUS Armoury Crate removal tool which is available here: [ASUS Armoury Crate] Armoury Crate FAQ | Official Support | ASUS Global

We can then check what is left over afterwards and then remove them manually if needs be.

zbook · Aug 19, 2023

When available post a querysettings share link into the newest post.

After competing WDV testing make free backup images using third party software and save the images to another disk drive or the cloud.

(Acronis, Aoemi, EaseUS, Macrium, Paragon, etc.)

Gianmarco · Aug 19, 2023

zbook said:
If there were no significant performance problems then run WDV with all customized tests for 48 hrs.

a) Test all non-Microsoft drivers
b) Test no Microsoft drivers

Post a querysettings or V2 as needed.

Some slow response by the keyboard and some little lag on some games, but lowering resolution settings could be helpful. Now the WDV restarted, here the attach image of the querysettings.

x BlueRobot said:
It looks like another Stop 0x7F, I would suggest that you remove any ASUS motherboard software, particularly anything which uses AsIO*.sys which used to cause several problems on Windows 7 machines. I'm not sure what it is like now but I feel it is a worthwhile troubleshooting step.

I would use the ASUS Armoury Crate removal tool which is available here: [ASUS Armoury Crate] Armoury Crate FAQ | Official Support | ASUS Global

We can then check what is left over afterwards and then remove them manually if needs be.

Removed, I tought it could be usefull for update driver or check mb or cpu status but seems it generated only problems. Thinking about Armoury Crate, it was really slow to open up and it was affected by often crashes. How can I check if there is something else to remove? Thank you very much.

zbook said:
When available post a querysettings share link into the newest post.

After competing WDV testing make free backup images using third party software and save the images to another disk drive or the cloud.

(Acronis, Aoemi, EaseUS, Macrium, Paragon, etc.)

Yes that's a thing I've to do after we find the solution. Ah before the WDV start I updated BIOS to the last version.
While I was writing this post a BSOD occured here the log: BSOD-(2023-08-19_14-16-20).zip

Gianmarco · Aug 19, 2023

Another BSOD : BSOD-(2023-08-19_14-27-42).zip

zbook · Aug 19, 2023

Nice.

Both BSODs were bugcheck 50 and both were caused by misbehaving AMD GPU drivers.

amdkmdag.sys

Turn off WDV.

Uninstall the AMD GPU drivers using Display Driver Uninstaller (DDU).

Reinstall using the AMD website.

Display Driver Uninstaller: How to use

How to Use Display Driver Uninstaller to Uninstall any Installed Display Driver

www.sevenforums.com

How to use Display Driver Uninstaller (DDU) Guide / Tutorial

Display Driver Uninstaller (DDU) Tutorial/Guide By - /u/GhostMotley This tutorial was written for version V17.0.8.2, future versions may differ slightly. Please feel free to contact me via PM on Reddit if you think I should update the guide. DISCLAIMER: I take no responsibility for any damages...

www.wagnardsoft.com

Display Driver Uninstaller (DDU) download latest version 18.0.9.1

Official Display Driver Uninstaller (DDU) download website. DDU is a driver removal utility that can help you completely uninstall AMD/NVIDIA/INTEL graphics card drivers and packages from your system, trying to remove all leftovers (including registry keys, folders and files, driver store).

www.wagnardsoft.com

https://www.amd.com/en/support

After the new GPU installation run Furmark for 30 minutes.

FurMark - GPU Stress Test

Stress test your GPU for stability issues with FurMark

www.tenforums.com

Make note of the warnings to abort testing.

Record the continuous test duration and maximum temperature.

Post images or share links into this thread using one drive, drop box, or google drive.

Code:

Name    AMD Radeon RX 6900 XT
PNP Device ID    PCI\VEN_1002&DEV_73BF&SUBSYS_0E3A1002&REV_C0\6&8B06BD&0&00000019
Adapter Type    AMD Radeon Graphics Processor (0x73BF), Advanced Micro Devices, Inc. compatible
Adapter Description    AMD Radeon RX 6900 XT
Adapter RAM    (1,048,576) bytes
Installed Drivers    C:\Windows\System32\DriverStore\FileRepository\u0394441.inf_amd64_57e767cb37419fb0\B394106\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\u0394441.inf_amd64_57e767cb37419fb0\B394106\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\u0394441.inf_amd64_57e767cb37419fb0\B394106\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\u0394441.inf_amd64_57e767cb37419fb0\B394106\amdxc64.dll
Driver Version    31.0.21023.2010
INF File    oem8.inf (ati2mtag_Navi21 section)
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\U0394441.INF_AMD64_57E767CB37419FB0\B394106\AMDKMDAG.SYS (31.0.21023.2010, 95.12 MB (99,737,448 bytes), 8/2/2023 8:57 PM)

Code:

amdwddmg    amdwddmg    c:\windows\system32\driverstore\filerepository\u0394441.inf_amd64_57e767cb37419fb0\b394106\amdkmdag.sys

x BlueRobot · Aug 20, 2023

I wouldn't necessarily update those GPU drivers immediately since in another thread, @zbook enabled all of the Driver Verifier options and then the user immediately had a random Stop 0x7E bugcheck. These ceased once Driver Verifier was completely disabled.

Here is the thread for reference: BSOD when watching YouTube

zbook said:
Both BSODs were bugcheck 50 and both were caused by misbehaving AMD GPU drivers.

Yes, probably because you enabled "Low Resources Simulation" which can lead to random unpredictable crashes.

Gianmarco said:
How can I check if there is something else to remove? Thank you very much.

I checked under Services, the two drivers are still there so let's disable them for now using the following from command prompt:

Code:

sc config asusgio2 start= disabled
sc config asusgio3 start= disabled

You will need to reboot the system for the changes to take effect. Afterwards, open command prompt again and then check that the services have been disabled by running:

Code:

sc qc asusgio2
sc query asusgio2
sc qc asusgio3
sc query asusgio3

You may want to create a restore point before disabling the services just as a precaution. You shouldn't have any issues though.

Gianmarco · Aug 20, 2023

This morning I did everything, seems there was also an update to the AMD Software that previously didn't show up (don't know why, it said to me that everything was updated).
Anyway I run the Furmark for 30 mins and here a onedrive folder with images and the log of the test: FurMark test

Gianmarco · Aug 20, 2023

x BlueRobot said:
I wouldn't necessarily update those GPU drivers immediately since in another thread, @zbook enabled all of the Driver Verifier options and then the user immediately had a random Stop 0x7E bugcheck. These ceased once Driver Verifier was completely disabled.

Here is the thread for reference: BSOD when watching YouTube

Yes, probably because you enabled "Low Resources Simulation" which can lead to random unpredictable crashes.

I checked under Services, the two drivers are still there so let's disable them for now using the following from command prompt:

Code:

sc config asusgio2 start= disabled sc config asusgio3 start= disabled

You will need to reboot the system for the changes to take effect. Afterwards, open command prompt again and then check that the services have been disabled by running:

Code:

sc qc asusgio2 sc query asusgio2 sc qc asusgio3 sc query asusgio3

You may want to create a restore point before disabling the services just as a precaution. You shouldn't have any issues though.

Just did it and seems everything is ok here some attachements for the cmd prompt

zbook · Aug 20, 2023

Nice progress with the AMD GPU driver updates and testing.

Please make free backup images as per post #68.

x BlueRobot · Aug 20, 2023

Gianmarco said:
Just did it and seems everything is ok here some attachements for the cmd prompt

Looks good to me too, I would use the system as normally would and then upload any dump files if it crashes again.

Gianmarco · Aug 26, 2023

After some days there is still no BSOD. Seems that everything is ok, now it's time to do the backup image like you told me.
Thank you both Blue Robot and zbook for the help and the hints. And for the patience. I know it's not an easy task to solve this strange problems.

zbook · Aug 26, 2023

Please post a new V2 share link into the newest post.

Gianmarco · Aug 26, 2023

zbook said:
Please post a new V2 share link into the newest post.

Here the link to the log: J (2023-08-26_15-03-16).zip

zbook · Aug 26, 2023

The logs were unremarkable.

The last BSOD and unexpected shutdown and restart were on 08/21/2023.

Looks good.

Solved BSOD UNEXPECTED_KERNEL_MODE_TRAP

Active member

Attachments

My Computer

Account Closed

My Computer

Active member

My Computer

Well-known member

My Computer

Active member

Attachments

My Computer

Well-known member

My Computer

Account Closed

My Computer

Well-known member

My Computer

Active member

Attachments

My Computer

Active member

My Computer

Well-known member

My Computer

Account Closed

My Computer

Active member

My Computer

Active member

Attachments

My Computer

Well-known member

My Computer

Account Closed

My Computer

Active member

My Computer

Well-known member

My Computer

Active member

My Computer

Well-known member

My Computer

Similar threads