[SOLVED] ntoskrnl.exe BOSD

[jetpackmaniac]

I have been getting two different blue screen errors, the first one is Video_TDR_Failure(116), and happens whenever I anything graphics intensive with my graphics card installed. It also appears to be related to DirectX, because whenever I do something that uses OpenGL, like rendering a scene in blender, it doesn't blue screen. When I downloaded BlueScreenView, it highlighted three files, amdkmdag.sys, dxgkrnl.sys, and ntoskrnl.exe. However, if I take the card out and just use my CPUs integrated graphics, things seem to work fine, until just recently. I have been using integrated graphics as a temporary work around while I try to figure out why my graphics card refuses to work, and I have got another blue screen, PFN_LIST-CORRUPT. I have gotten this error three times so far, and according to BlueScreenView, ntoskrnl.exe is at fault again, and on one of them, it also highlights dxgmms2.sys. I have ran Memtest86, and after a 4 pass test it found no errors. Also when I first got the Video_TDR_Failure error, I thought it was the graphics card, and went though the RMA process with XFX, (yes, I've been at this issue for a while) and a new card didn't change much. At this point I'm a little lost about what to do next, any advice on where to look next would be greatly appreciated, thanks!

Specs:
CPU: intel core i5 9600k
Motherboard: ASUS prime Z390-P
Ram: 16GB DDR4 2400MHz
GPU: AMD RX 570
BIOS version:2606

 

[Colif]

I saw

Video_TDR_Failure(116),

and guessed you had an AMD GPU before I looked at bottom

amdkmdag.sys, dxgkrnl.sys, and ntoskrnl.exe.

normal suspects in a GPU driver related crash, DirectX, GPU drivers and the windows kernel.
NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause. If it was the problem windows wouldn't be able to work. At all.

and a new card didn't change much

Was the old card also an AMD card? does this mean you still getting TDR errors?


What PSU do you have?



Can you go to c windows/minidump

copy the minidump files to documents

upload the copies from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

 

[jetpackmaniac]

Was the old card also an AMD card? does this mean you still getting TDR errors?

Yes, I sent the card into XFX and they were unable to recreate my issues, but they sent back an identical replacement anyway. When I got the new card, it seemed to work fine for a bit, but it started cashing a day or so after I got it. And yes it was the same TDR failure.
Also my PSU is a EVGA 600 BR.

Here are the minidumps.
https://drive.google.com/drive/folders/15qVdQNf2AzG8NDY4U__pAcdOAvflCWGR?usp=sharing

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/gbay1f2t/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

Spoiler

File information:	103020-6968-01.dmp (Oct 30 2020 - 14:21:58)
Bugcheck:	PFN_LIST_CORRUPT (4E)
Driver warnings:	*** WARNING: Unable to verify timestamp for voxaldriverx64.sys
Probably caused by:	memory_corruption (Process: audiodg.exe)
Uptime:	0 Day(s), 5 Hour(s), 56 Min(s), and 32 Sec(s)

File information:	103020-5765-01.dmp (Oct 30 2020 - 19:11:41)
Bugcheck:	PFN_LIST_CORRUPT (4E)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 4 Hour(s), 49 Min(s), and 23 Sec(s)

File information:	102120-12093-01.dmp (Oct 21 2020 - 22:10:54)
Bugcheck:	PFN_LIST_CORRUPT (4E)
Probably caused by:	memory_corruption (Process: System)
Uptime:	11 Day(s), 2 Hour(s), 25 Min(s), and 39 Sec(s)

File information:	101020-6765-01.dmp (Oct 10 2020 - 13:36:46)
Bugcheck:	VIDEO_TDR_ERROR (116)
Driver warnings:	*** WARNING: Unable to verify timestamp for amdkmdag.sys
Probably caused by:	memory_corruption (Process: System)
Uptime:	1 Day(s), 2 Hour(s), 13 Min(s), and 12 Sec(s)

File information:	100920-7203-01.dmp (Oct 9 2020 - 11:23:12)
Bugcheck:	VIDEO_TDR_ERROR (116)
Driver warnings:	*** WARNING: Unable to verify timestamp for amdkmdag.sys
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 1 Hour(s), 14 Min(s), and 43 Sec(s)

Possible Motherboard page: https://www.asus.com/us/Motherboards/PRIME-Z390-P/
There are BIOS updates available for your system. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

crash 1 caused by

Nov 14 2019

voxaldriverx64.sys

Voxal Voice Changer driver (NCH Software)

i don't know if there is a newer version.
crash 2 & 3 looks a lot like crash 1. So could be same cause.
bottom 2 caused by AMD display drivers

which oem makes the GPU? Do they maybe have drivers for it on their site?
another choice is run DDU and then run Windows update after the restart and let windows find older AMD drivers to use - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

 

[jetpackmaniac]

Sorry for the late response.

Possible Motherboard page

Yes that is the correct motherboard.

which oem makes the GPU? Do they maybe have drivers for it on their site?

The card is built by XFX, and they just link to the AMD website for drivers.

another choice is run DDU and then run Windows update after the restart and let windows find older AMD drivers to use

Would it be a good idea to make sure I'm running the latest bios version before reinstalling drivers?

 

[Colif]

So randomly there is no support page showing here which makes it difficult to update the bios - https://www.asus.com/au/Motherboards/PRIME-Z390-P/

I am sure it will reappear... you can update them over web in the bios tool but I would have liked to see if it might help as updating bios isn't something I suggest doing on a whim.

Guess only other choice with GPU drivers then is windows update since AMD don't have older drivers on there normally.

 

[jetpackmaniac]

I built this computer back in January, and I was having some problems with phantom key presses. One of the things I tried was a bios update. Turned out it was just a grounding issue, but that is when I updated to bios version 2606. Before that my GPU worked fine as I recall, I didn't do much before I updated the bios, but I do remember playing Kerbal Space Program at least once on high graphics settings and it worked great. Now if I do anything in KSP it crashes, even on lower settings. I am going to just try running the DDU and reinstalling drivers first, because flashing the bios terrifies me. But I recently remembered that the GPU seemed to work fine before updating to 2606 and thought I would mention it here.
Also while talking with AMD tech support, they did give me an old version of their drivers to try, but it didn't work.

 

[Colif]

I can see bios page now, and you are 2 versions behind current. Last 2 bios updates were to Improve system stability so they could help in your case.

I guess you know how but page 2-1 here shows you - https://dlcdnets.asus.com/pub/ASUS/mb/LGA1151/PRIME_Z390-P/E15011_PRIME_Z390-P_UM_v3_web.pdf

 

[jetpackmaniac]

Yesterday I ran the DDU that was linked for both Intel and AMD drivers and reinstalled the latest version of drivers for my GPU. That seems to have worked, I played KSP for a while yesterday and was getting 144 fps at medium high settings with no issues. If it was to start crashing again I could update the bios, but I think its fixed. Thing is, AMD tech support had me do basically the same thing with their own DDU they sent me, and it didn't work. I guess the different DDU is what made the difference?
Thanks so much for the help, I really appreciate it!