Question VIDEO_DXGKRNL_FATAL_ERROR Blue screen while playing games

[Ox1ee]

Hello, so I have this problems like a year now. When I was playing games like forza horizon 4, cs go, R6,etc my game crashed and my laptop did not detect my NVIDIA driver and I have to restart my laptop, so when I restart my laptop it got blue screen and it says VIDEO_DXGKRNL_FATAL_ERROR. I have tried many solutions from youtube like uninstalling graphic card with DDU an install the new one, updating windows, memory test, sfc /scannow and it does not work.

This is the detailed problem i got from windows reliability

Source
Windows

Summary
Hardware error

Date
‎22/‎02/‎2022 00:12

Status
Not reported

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffffd78ad87c0010
Parameter 2: fffff80586b8cd60
Parameter 3: 0
Parameter 4: 0
OS version: 10_0_22000
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.22000.2.0.0.768.101
Locale ID: 14345




Description
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000113 (0x0000000000000019, 0x0000000000000002, 0x00000000000010de, 0x0000000000001f11). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: b4621485-71d7-41e8-adc4-4c820b58d1a9.




Source
Windows

Summary
Shut down unexpectedly

Date
‎22/‎02/‎2022 00:14

Status
Not reported

Problem signature
Problem Event Name: BlueScreen
Code: 113
Parameter 1: 19
Parameter 2: 2
Parameter 3: 10de
Parameter 4: 1f11
OS version: 10_0_22000
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.22000.2.0.0.768.101
Locale ID: 14345


And this is link for my mini dump
https://drive.google.com/drive/folders/1_2XMKRRCvMehwsf7-tPNWIkE2JAa0xMO?usp=sharing



Please help me

 

[Colif]

Tried running DDU and getting the Display drivers from the laptop website, they likely older Nvidia drivers but if they have problems too, we have to look at GPU as cause.

Does laptop have win 11 drivers? this doesn't matter so much if it has win 10 drivers as they mostly work. have you tried updating it?
Did you have these problems on win 10?

 

[Ox1ee]

Tried running DDU and getting the Display drivers from the laptop website, they likely older Nvidia drivers but if they have problems too, we have to look at GPU as cause.

Does laptop have win 11 drivers? this doesn't matter so much if it has win 10 drivers as they mostly work. have you tried updating it?
Did you have these problems on win 10?

I already install the newest driver and it still causing blue screen and now I'm using 472.12 NVIDIA driver and still have that blue screen. Yes I have these problem when using windows 10

 

[Colif]

Does the laptop site link to newest? I suggested it as if the drivers that are for the laptop don't work, it might not be a software problem.

You might need to get laptop repaired.

Did you clean install win 11?

 

[Ox1ee]

Does the laptop site link to newest? I suggested it as if the drivers that are for the laptop don't work, it might not be a software problem.

You might need to get laptop repaired.

Did you clean install win 11?

I think the link give me the newest graphic driver. I already repaired my laptop and they said my motherboard is broken so they replaced it. Yeah I think I did clean install windows 11

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/txj1zek4/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: Dump File Results

File information:	022222-17187-01.dmp (Feb 21 2022 - 12:29:04)
Bugcheck:	VIDEO_DXGKRNL_FATAL_ERROR (113)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	0 Day(s), 0 Hour(s), 04 Min(s), and 36 Sec(s)

File information:	022222-17031-01.dmp (Feb 21 2022 - 12:24:03)
Bugcheck:	VIDEO_DXGKRNL_FATAL_ERROR (113)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	0 Day(s), 0 Hour(s), 10 Min(s), and 08 Sec(s)

File information:	022222-16078-01.dmp (Feb 21 2022 - 15:06:57)
Bugcheck:	VIDEO_DXGKRNL_FATAL_ERROR (113)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	0 Day(s), 1 Hour(s), 04 Min(s), and 04 Sec(s)

File information:	022222-15812-01.dmp (Feb 21 2022 - 12:13:32)
Bugcheck:	VIDEO_DXGKRNL_FATAL_ERROR (113)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	0 Day(s), 0 Hour(s), 20 Min(s), and 22 Sec(s)

File information:	022122-18484-01.dmp (Feb 21 2022 - 11:52:47)
Bugcheck:	VIDEO_DXGKRNL_FATAL_ERROR (113)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	0 Day(s), 0 Hour(s), 57 Min(s), and 11 Sec(s)

Motherboard: MS-16P7
Possible Motherboard page: https://us.msi.com/support/download/
The horrible layout of the MSI page prevents me from checking if there is a BIOS update for you or not. If there is one, wait for additional information before deciding to update or not.

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

 

[johnbl]

the directx graphics was surprised to find your graphics card was removed while the system was running and called a bugcheck.
but the stack was corrupted. I will look to see if I can tell what corrupted the stack.
kernel memory dump would help for that.

system running at a strange speed:
~MHz = REG_DWORD 2208

I would be looking at:
\SystemRoot\System32\drivers\RivetNetworks\Killer\KfeCo10X64.sys Tue Nov 20 08:27:17 2018

(remove it or update the file, known memory corruption in this version)

I would remove:
C:\Program Files (x86)\MSI\Dragon Center\winio64.sys Tue Jul 17 23:58:37 2018
(not sure what this does but it might be doing the strange 8 MHz overclock.)

I will look at the raw stack to see if I can tell what corrupted it.

 

[johnbl]

the directx graphics was surprised to find your graphics card was removed while the system was running and called a bugcheck.
but the stack was corrupted. I will look to see if I can tell what corrupted the stack.
kernel memory dump would help for that.

system running at a strange speed:
~MHz = REG_DWORD 2208

I would be looking at:
\SystemRoot\System32\drivers\RivetNetworks\Killer\KfeCo10X64.sys Tue Nov 20 08:27:17 2018

(remove it or update the file, known memory corruption in this version)

I would remove:
C:\Program Files (x86)\MSI\Dragon Center\winio64.sys Tue Jul 17 23:58:37 2018
(not sure what this does but it might be doing the strange 8 MHz overclock.)

I will look at the raw stack to see if I can tell what corrupted it.

raw stack just shows some nvidia kernel mode calls, then a call to plug and play and then calls to directx to handle the surprise removal.
with a minidump I can only see wat was going on with the cpu that called the bugcheck, you could have another CPU that was actually removing the card at the time of the bugcheck.

you can try removing the msi driver and update the second driver. Often I see corrupted stacks caused by audio sources that are not being used.

It looked like your system bugchecks very fast so you might remove the msi driver, update the other one. Then set your memory dump type to kernel and reboot. if you bugcheck you could provide the kernel memory.dmp file and we can look at what is going on with your other cpu cores.

machine info:
4: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.2, DMIVersion 0, Size=4426]
BiosMajorRelease = 1
BiosMinorRelease = 19
BiosVendor = American Megatrends Inc.
BiosVersion = E16P7IMS.113
BiosReleaseDate = 05/18/2020
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = GL63 8SE
SystemFamily = GL
SystemVersion = REV:1.0
SystemSKU = 16P7.1
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = MS-16P7
BaseBoardVersion = REV:1.0

it looks like you updated the BIOS but failed to update the motherboard drivers. Some of these drivers will be tied to the bios version and must match. go to the motherboard vendor website and do the driver updates.

I could not tell what version of nvidia graphics card you have. You should tell us. if it is old it may not support some functions that are turned on in the new drivers. Cases where the driver wants to throttle the GPU speed but does not get the expected response can cause this bugcheck.

update:
MSI GL63 - The Game Just Got Real
(also update the firmware)

generally you want to remove the utils and not install the new ones while trying to fix this problem

 

[johnbl]

also, make sure your video card if fully seated in the slot. I have seen systems that would pop out the video card when you picked them up and move them. (case just flexes enough so that some card pins do not make contact with the socket pins)

 

[Colif]

Hope the GPU in a laptop can't pop out, so to speak. I expect they part of motherboard?

Sep 20 2018	e2xw10x64.sys	Killer PCI-E Gigabit Ethernet Controller driver http://www.killernetworking.com/
Nov 20 2018	KfeCo10X64.sys	Killer Networking Suite driver

might be fun finding new killer drivers since Intel bought them in the last few years and stopped supporting older chips (not made by intel)

latest on laptop site shows 2019 - https://www.msi.com/Laptop/GL63-8SE/support#down-driver&Win10 64

can find newest chipset drivers at above link as well, that John mentioned.

 

[Ox1ee]

you can try removing the msi driver and update the second driver. Often I see corrupted stacks caused by audio sources that are not being used.

I don't understand this sentence? and how do i do that

 

[johnbl]

I don't understand this sentence? and how do i do that

update this driver:
\SystemRoot\System32\drivers\RivetNetworks\Killer\KfeCo10X64.sys Tue Nov 20 08:27:17 2018

remove this driver:
C:\Program Files (x86)\MSI\Dragon Center\winio64.sys Tue Jul 17 23:58:37 2018

unless you really need old versions

 

[Ox1ee]

It looked like your system bugchecks very fast so you might remove the msi driver, update the other one. Then set your memory dump type to kernel and reboot. if you bugcheck you could provide the kernel memory.dmp file and we can look at what is going on with your other cpu cores.

and I want to ask u how I locate kernel memory.dmp file?

 

[johnbl]

and I want to ask u how I locate kernel memory.dmp file?

you have to set the computer to generate one on the next bugcheck.
Generate a kernel or complete crash dump - Windows Client Management | Microsoft Docs
by default, they will be written to
c:\windows\memory.dmp

 

[Ox1ee]

you have to set the computer to generate one on the next bugcheck.
Generate a kernel or complete crash dump - Windows Client Management | Microsoft Docs
by default, they will be written to
c:\windows\memory.dmp

Ok I have done everything what you said, already update the bios and firmware, update the killer network. I also remove this "C:\Program Files (x86)\MSI\Dragon Center\winio64.sys " ( after i delete it i can't run dragon center anymore so i have to delete the app). I'm using 511.79 Nvidia driver version right now, i already tested in 3 games first is valorant the bsod didn't happened, second is forza horizon 4 it run pretty smooth and the last one is apex legends that after i played it for a couple minute it crash then bsod.

this is the kernel memory dmp file : https://drive.google.com/drive/folders/1J3ebCAhNa9szBnGmsvHWTu4sVHxtzO3l?usp=sharing

and i will tested my laptop again so if i have the bsod i'll tell you

 

[johnbl]

directx thinks your gpu was removed.
another cpu was trying to install this device but failed the install.
PCI\VEN_10DE&DEV_1ADB&SUBSYS_126A1462&REV_A1\4&10b966d6&0&0308

PCI\VEN_10DE&DEV_1ADB - TU106 USB Type-C UCSI Controller | Device Hunt
ven = 10DE = nvidia
dev = 1ADB = TU106 USB Type-C UCSI Controller

go into control panel device manager see if you can locate this and disable it and reboot. (USB Type-C Port Policy Controller )
install failed due to:
4: kd> !error 0xc0000490
Error code: (NTSTATUS) 0xc0000490 (3221226640) - There are no compatible drivers available for this device.


windows tried to install this driver from nvidia, it failed then windows plug and play called this function
nt!PnpProcessQueryRemoveAndEject and removed the device
which happened to be your graphics card. This caused the other cpu to bugcheck on the directx gpu call. (ie directx was surprised the GPU was gone)

I would also make sure I update window in the case this is a plug and play bug. you could also make sure the device is correctly being installed so plug and play does not make this call at some random time. are you connecting some device to the gpu usb Port?

 

[johnbl]

directx thinks your gpu was removed.
another cpu was trying to install this device but failed the install.
PCI\VEN_10DE&DEV_1ADB&SUBSYS_126A1462&REV_A1\4&10b966d6&0&0308

PCI\VEN_10DE&DEV_1ADB - TU106 USB Type-C UCSI Controller | Device Hunt
ven = 10DE = nvidia
dev = 1ADB = TU106 USB Type-C UCSI Controller

go into control panel device manager see if you can locate this and disable it and reboot. (USB Type-C Port Policy Controller )
install failed due to:
4: kd> !error 0xc0000490
Error code: (NTSTATUS) 0xc0000490 (3221226640) - There are no compatible drivers available for this device.


windows tried to install this driver from nvidia, it failed then windows plug and play called this function
nt!PnpProcessQueryRemoveAndEject and removed the device
which happened to be your graphics card. This caused the other cpu to bugcheck on the directx gpu call. (ie directx was surprised the GPU was gone)

I would also make sure I update window in the case this is a plug and play bug. you could also make sure the device is correctly being installed so plug and play does not make this call at some random time. are you connecting some device to the gpu usb Port?

best to get the correct driver for the missing device, but you could start a cmd.exe or powershell as an admin then run
net.exe stop "plug and play"
this will turn off plug and play until you reboot or turn it back on with
net.exe start "plug and play"

it will turn off the automatic install / remove of drivers for hardware.
(it can be useful when plug and play installs a bad driver that you have to manually remove from the driver store)

do you have a xbox360 controller attached to your usb-c port.
if so the system does not like it

also go into windows control panel, device manager, find the option to show hidden devices and remove any hidden devices attached to usb ports. remove any extra usb devices that you do not need. I would put older devices on a usb 2 port and newer devices on usb 3 port.
you had a usb hub that did not get set up correctly. you have a device waiting to signals on a hub that was powered down.
(maybe put to sleep and can not wake)
i think your nvidia USB was reset so it may have worked for a while.

 

[Ox1ee]

best to get the correct driver for the missing device, but you could start a cmd.exe or powershell as an admin then run
net.exe stop "plug and play"
this will turn off plug and play until you reboot or turn it back on with
net.exe start "plug and play"

it will turn off the automatic install / remove of drivers for hardware.
(it can be useful when plug and play installs a bad driver that you have to manually remove from the driver store)

do you have a xbox360 controller attached to your usb-c port.
if so the system does not like it

yeah i have a 360 xbox controller. so u tell me the way i got bsod is because the controller? and how do i get rid of it?

 

[johnbl]

yeah i have a 360 xbox controller. so u tell me the way i got bsod is because the controller? and how do i get rid of it?

I assume this is a wired controller, connected to a usb-c port?
disconnect the controller, start control panel, find device manager, go to the menu and find the option to show hidden devices.
find the various hidden devices and un install the drivers for each of them.

you could also use this method to remove the driver
Remove a Driver Package from the Driver Store (forsenergy.com)

I think this controller/driver just does not understand any of the new USB low power functions and caused the USB port to hang with a error. then the port gets reset but the controller and driver still was waiting for controls but not connected to anything. it just confused the usb controller.

remove the device, and the hidden drivers and maybe try a newer generation of game controller. (you might also be able to just put it on a USB 2 host. if you have one that is not being emulated by a usb 3.0 controller)
IE older generations of machines have a usb 3 chip and a USB 2.x chip
newer machines have a usb 3 chip and fake having a usb 2.x version.