Question My PC gets BSODs daily while gaming and I can't track down the cause ?

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
Sort by date Sort by votes
Please place new dumps into a new folder and provide a link each time. Or link directly to a new .ZIP file. Thanks.

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/t6fd43Lq/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.

File information:021022-5500-01.dmp (Feb 10 2022 - 16:08:07)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for Netwtw10.sys
Probably caused by:memory_corruption (Process running at time of crash: System)
Uptime:0 Day(s), 14 Hour(s), 25 Min(s), and 43 Sec(s)

Crashing driver:
Jan 03 2022Netwtw10.sysIntel Wi-Fi driver

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Upvote 0 Downvote
Colif said:
sorry. I shouldn't rush you, its your problem. take your time if you have other things you have to do. I should be around somewhere.
Click to expand...
Hey no worries man. I mean, you’re helping me fix this for free. Most people charge for this kind of stuff. I reinstalled the drivers again so hopefully that’ll fix it. I played for a couple hours last night and I didn’t have any crashes so that’s a good sign at least.
 
Upvote 0 Downvote
HolyDiver836 said:
ntkrnlmp.exe.
Click to expand...
Part of windows kernel.
Long time ago I tried to work out what it meant. NT Kernel Multiprocessor. And given its mentioned on this page, I think that is right. LInk just makes me wonder if I ever seen a UP driver before. Uniprocessor Driver... but anyway, just learning as I go :)
@gardenman suggested it was Multiprocessor years ago.

Its what crashed, it likely shows in the process field. But its the victim, very rarely do I find a BSOD where the process is the cause. Its often just a clue.
This isn't a clue really, lets see what dumps show us.
 
Upvote 0 Downvote
I ran the dump file through the debugger and got the following information: https://jsfiddle.net/5wrond2s/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.

File information:021322-5406-01.dmp (Feb 14 2022 - 01:46:57)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Probably caused by:memory_corruption (Process running at time of crash: GTA5.exe)
Uptime:1 Day(s), 2 Hour(s), 45 Min(s), and 03 Sec(s)

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

Edit: Results for dump file below: https://jsfiddle.net/c9agvspy/show
 
Last edited:
Upvote 0 Downvote
Satan-IR said:
Can you remember if you made any changes just before the BSODs started happening?

Changes such as installing any new game/software/hardware, especially one that would come with drivers or would require changes/updates to the existing drivers?
Click to expand...
I can't think of anything. When it first happened I was playing a game I had installed for months already. It first happened in December and the last time I got a new game before then was during the black friday sale. I don't think there was any new software or anything.
 
Upvote 0 Downvote
HolyDiver836 said:
Just got another BSOD while browsing the internet trying to find out how to test my drives. Here is the link to the dump: https://1drv.ms/u/s!AmAuDhC0ZlvkgQfegHDjJg4kY7js?e=fFbm3l
It will be Dump File 5
Click to expand...
I looked at the memory dump but for this error you need to change the memory dump type to kernel memory dump rather than minidump. the kernel dump includes the required data.
when the problem happens again, then provide the memory.dmp file as it will have the correct saved data.
from the memory dump provided all I can see is the problem is caused by
!kdexts.thread ffffd28958415040
but can not get the name of the thread owner.
------------
also go into bios and turn off any special network functions if you have them.
special network filtering or anything that is to give you special game functions.
you might also go into windows control panel device management find the network card, select the properties, find the power management and tell windows not to allow it to be turned off to save power.

--------
you might be able to set your windows system into high performance mode and prevent this bug from getting triggered. (just fyi )
-----
one of the dumps showed a unknown function.
this generally means a service called a function in a driver and it was not there. this would mean that the service version does not match the driver version. most likely the intel network driver and what ever service called into the driver. ( can not read the name in a minidump, only a kernel dump)
 
Last edited:
Upvote 0 Downvote
johnbl said:
I looked at the memory dump but for this error you need to change the memory dump type to kernel memory dump rather than minidump. the kernel dump includes the required data.
when the problem happens again, then provide the memory.dmp file as it will have the correct saved data.
from the memory dump provided all I can see is the problem is caused by
!kdexts.thread ffffd28958415040
but can not get the name of the thread owner.
------------
also go into bios and turn off any special network functions if you have them.
special network filtering or anything that is to give you special game functions.
you might also go into windows control panel device management find the network card, select the properties, find the power management and tell windows not to allow it to be turned off to save power.

--------
you might be able to set your windows system into high performance mode and prevent this bug from getting triggered. (just fyi )
-----
one of the dumps showed a unknown function.
this generally means a service called a function in a driver and it was not there. this would mean that the service version does not match the driver version. most likely the intel network driver and what ever service called into the driver. ( can not read the name in a minidump, only a kernel dump)
Click to expand...
My system is already in high performance mode. I switched to kernel dumps and my pc crashed a couple minutes ago, but I can't find the dump file. In event viewer it says "dump file generation successful" but I can't find it anywhere.
 
Upvote 0 Downvote
Mini dumps are usually saved to: c:\Windows\Minidump\filename.dmp

Kernel dumps are usually saved to c:\Windows\memory.dmp
And it's a larger file, usually 1 GB to 4GB.

But it's possible it wasn't created for some reason or another. Sometimes just crashing again will create it.
 
Upvote 0 Downvote
Ye
gardenman said:
Mini dumps are usually saved to: c:\Windows\Minidump\filename.dmp

Kernel dumps are usually saved to c:\Windows\memory.dmp
And it's a larger file, usually 1 GB to 4GB.

But it's possible it wasn't created for some reason or another. Sometimes just crashing again will create it.
Click to expand...
Yeah it looks like maybe it wasn’t created. I’ll have to wait until it happens again.
 
Upvote 0 Downvote
HolyDiver836 said:
Had another crash tonight. Here is the link to the kernel dump: https://1drv.ms/u/s!AmAuDhC0ZlvkgRPffGGDmI9r6vYu
Click to expand...
for this you would look in the windows event viewer system log to see if it names the drivers that spent too long to process. The bugcheck indicated it was not one driver bug the overall effect of many drivers took too long and violated the rules.

I would guess it is the lenovo power management tools add too much overhead to the intel thermal management drivers and cause the violation.

I would remove the extra lenovo software utilities and see if your problem goes away.
you have utilities like these running:
Lenovo.Modern.ImController.PluginHost.Device.exe
LenovoVantage-(VantageCoreAddin).exe
it is not clear what these will actually do.

if you can, you might uninstall some lenovo utilities and only keep the minimum required subset for power management. (keep and update the intel drivers)

have your system stay in high performance mode until you resolve this problem. It could help since the system would not have the delay of waiting to wake up devices.
(problems like devices on usb ports going to sleep, then the usb port going to sleep adds wake up delays for devices)
-------------
other info:
Processor Version Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz
Processor Voltage 88h - 0.8V
External Clock 100MHz
Max Speed 4300MHz
Current Speed 2871MHz

2871MHz is a strange underclock speed
-----------
cpu released Q2'20
--------
Vendor LENOVO
BIOS Version O4NKT19A
BIOS Starting Address Segment f000
BIOS Release Date 12/16/2020
---------
one of the internal logs indicated that the mouse driver was in a unknown state. you might pull the mouse and try a different one.

---------
be sure to go to the motherboard vendors website and update the items in
Motherboard Devices (core chipset, onboard video, PCIe switches)
try the intel firmware update tool if you have not used it.
these don't show the dates so I am not sure if they are updated.
you could also use the intel update tool
i think it is here :Intel® Driver & Support Assistant

looks like the firmware was updated in 20 May 2021
looks like your intel files are old from
esif_lf.sys Tue Nov 5 18:36:39 2019

apply any intel firmware update then update the intel files. it could fix your problems so the drivers match your cpu release date
 
Last edited:
Upvote 0 Downvote
ok, i just found a new debugger command
!dpcwatchdog fffff8000ad05330

this seems to show that dxgkrnl on processor 0 is eating up the bulk of the watchdog timer.
this would hint that the graphics driver might be the cause of the problem.
(it could also be normal while running a game. just not sure)
 
Upvote 0 Downvote
johnbl said:
ok, i just found a new debugger command
!dpcwatchdog fffff8000ad05330

this seems to show that dxgkrnl on processor 0 is eating up the bulk of the watchdog timer.
this would hint that the graphics driver might be the cause of the problem.
(it could also be normal while running a game. just not sure)
Click to expand...
I'll try uninstalling those lenovo programs. I have uninstalled and reinstalled the graphics driver a million times so I doubt that's the culprit.
 
Upvote 0 Downvote
Also, this appears in event viewer almost every time it crashes: The driver \Driver\WudfRd failed to load for the device ROOT\SYSTEM\0001.
I'm not sure what this means or if it even helps.
 
Upvote 0 Downvote
HolyDiver836 said:
Here's the link to dump files from tonight's crash: https://1drv.ms/u/s!AmAuDhC0ZlvkgRPffGGDmI9r6vYu?e=4pUVMe
I hate that this is a daily thing
Click to expand...
HolyDiver836 said:
Here's the link to dump files from tonight's crash: https://1drv.ms/u/s!AmAuDhC0ZlvkgRPffGGDmI9r6vYu?e=4pUVMe
I hate that this is a daily thing
Click to expand...
looks like 6 different CPUs had directx calls. that they were waiting on.

here are some suspects:
EoCApp.exe (looks like some game app)
msedgewebview2.exe (you might disable widgets and see if it fixes the problem)
-----------
this was the info on
Device instance path ROOT\SYSTEM\0001
(not sure what it is for)
11: kd> !wdfldr iMDriver.dll
PEB is paged out (Peb.Ldr = 0000002b`d0f13018). Type ".hh dbgerr001" for details

Version v2.15
Service \Registry\Machine\Software\Microsoft\Windows NT\CurrentVersion\WUDF\Services\iMDriver

!wdflogdump iMDriver.dll
---------------------------------------------------------------
UMDF Device Instances using iMDriver.dll
---------------------------------------------------------------
Process DevStack DeviceId
0xffffe588b86ac080 23ade4103b0 \Device\00000011 !wdfdriverinfo
-----------
debugger indicates
*** 158814 kernel stack PTE allocations have failed **
*** 1 kernel stack growth attempts have failed **

your game was using a lot of memory and was trying to free some at the time of the crash. directx might just have run out of resources and was had various cpus waiting for some directx object to be release by the game. (guessing)
 
Last edited:
Upvote 0 Downvote
HolyDiver836 said:
Here's the link to dump files from tonight's crash: https://1drv.ms/u/s!AmAuDhC0ZlvkgRPffGGDmI9r6vYu?e=4

you have something running called:
_iu14D2N.tmp
this is suspect it is not a normal .exe file

also something called:
LSBSetup (1).tmp
again not a normal .exe file to run from.



looks like you have two copies of something called
GTA5.exe running but they are too small to be the game. you should try to find out what they are.
Click to expand...
 
Last edited:
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom