Blackscreen Crash, NO BSOD, VIDEO_TDR_FAILURE (116)

Hi HardResetting, I am Rob, an Independent Advisor not affiliated with Microsoft and a 15 time and dual award Microsoft MVP specializing in Windows troubleshooting and Bluescreen analysis. Please remember as independents we are not responsible for the development of Windows or the computer hardware and drivers. If you will work with me I will be here to help until the issue is resolved.

The BugCheck 116 is indeed a BSOD though since you also lost the video you only saw a black screen.

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys <-- this is the Nvidia video driver.

So you either have a problem with the video driver or the video card is the issue or other hardware, such as memory, is causing the issue.

Check with Nvidia Support, their online docs, drives, diagnostics, and ask in their forums about any known issues. If there are no newer drivers you may need to revert back to an older stable driver per their instructions. Use the DDU method to remove and then install the video drivers.

-------

Display Driver Uninstaller - Free
https://www.guru3d.com/files-details/display-dr...

Nvidia - Drivers - Use OPTION 1 to manually enter your driver info to get the most current drivers.
http://www.nvidia.com/Download/index.aspx?lang=...

Nvidia Support - check with Support as it could be a known issue
http://www.nvidia.com/page/support.html

Nvidia Forums - also check for forums as it could be a known issue and/or others likely to have it
http://forums.nvidia.com/

=======

If the above does not resolve the issue then you definitely need to contact the system builder and/or the motherboard and other major device makers' supports for diagnostics help and possible RMAs'.

Since the computer is new and still under warranty please contact System Maker's Support and the seller. As OEM they are responsible for the proper operation of both the hardware and Windows. So regardless of the cause, it is theirs to resolve. And the unit is under full warranty and may be in need of repairs or replacement. Added that even if you are able to resolve the issue you would want it fully documented just in case there are related problems down the road. Remember the more you do the more they will say it is something you have done.

Please do the above as I have seen many others, as well as myself, make that mistake only to end up with a useless brick when the problems worsened further down the road.

==================

If you really want to try to troubleshoot this further without the system/device makers' supports then here are the methods. Keep in mind that even a simple analysis did indicate the video driver or the video device/card as the most likely culprits.

This utility makes it easy to see which major device driver versions are loaded :

Run DriverView - set VIEW to Hide Microsoft drivers - update those without Dump in their names (and update BIOS and chipset drivers).

DriverView - Free - utility displays the list of all device drivers currently loaded on your system. For each driver in the list, additional useful information is displayed: load address of the driver, description, version, product name, company that created the driver, and more.
http://www.nirsoft.net/utils/driverview.html

For Drivers check System Maker as fallbacks and Device Maker's which are the most current. Right Click the Start Button - Device Manager - Display Adapter - write down the make and complete model of your video adapter - double click - Driver's tab - write down the version info. Now click Update Driver (this may not do anything as MS is far behind certifying drivers) - then Right Click - Uninstall - REBOOT this will refresh the driver stack.

Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse, and Keyboard if 3rd party with their own software and drivers and any other major device drivers you have.

Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and then Device Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their latest versions. (Look for BIOS, Chipset, and software updates at System Maker's site while there.)

Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN -
REBOOT after each installation.

Always check in Device Manager - Drivers tab to be sure the version you are installing actually shows up. This is because some drivers roll back before the latest is installed (sound drivers particularly do this) so install a driver - reboot - check to be sure it is installed and repeat as needed.

Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check manually by model.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht...

====================================================

Memory tests do not catch all errors such as mismatched memory (possible even for sticks that appear to be identical) and when faster memory is placed in the system behind slower memory. So it is best to also swap sticks in and out to check for those even if all memory tests fail to show a problem.

To test RAM check here - let it run 4+ hours or so - overnight is best. <-- best method
www.memtest.org

MemTestX86 - Test RAM With
http://www.tenforums.com/tutorials/14201-memtes...

================================================

After doing ALL the updates you can, and if the issue continues, then run Driver Verifier.

Driver Verifier can help find some BSOD issues :

Driver Verifier-- tracking down a misbehaving driver.
https://answers.microsoft.com/en-us/windows/for...

Driver Verifier - Enable and Disable in Windows 10
https://www.tenforums.com/tutorials/5470-enable...

Using Driver Verifier to identify issues with Windows drivers for advanced users
http://support.microsoft.com/kb/244617

How To Troubleshoot Driver Problems in Windows Vista or 7. (8/8.1 and 10
are essentially the same).
http://www.winvistaclub.com/t79.html

Using Driver Verifier

https://msdn.microsoft.com/en-us/library/window...

WINKEY + X - RUN - type in -> verifier /reset hit enter to disable

If Driver Verifier creates a minidump upload it and post the link here so we can analyze it.

======

Please note that consumer-level troubleshooting software rarely specifies a particular piece of hardware so a lot of close observation is required.

PassMark Burnin Test - Free Trial - note the trial version will only run for 15 minutes and it really needs to be used for many hours. So if you use this you will need to faithfully and quickly restart it every 15 minutes.

PassMark - BurninTest - Free Trial
https://www.passmark.com/products/burnintest/

Running OCCT for Home Use (Free) and the Stress Tests may help indicate a cause.

OCCT - Free for Home use
https://www.ocbase.com/

Running Stress Tests might help indicate a cause - use ALL of these.

PC Stress Test free software for Windows 10
https://www.thewindowsclub.com/pc-stress-test-f...

Here to help,

Rob

------
Standard Disclaimer: Those may be non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

Please let us know the results and if you need further assistance. Feedback definitely helps us help all.

have you found a solution to this problem? I have crashes with the nearly identical minidump. For me, I'm experiencing crashes everytime I run 3dmark for a few minutes, or run any more intensive games.

Hey there!

I haven't posted anything yet as there are no results so far.

The seller had me first test the machine for possible RAM-Errors. I was supposed to do so by using only one stick at a time.

Windows couldn't detect a faulty stick with either of them plugged in. As I couldn't replicate the crashes (for me they happen infrequently) I told them about my new findings.

Previously I didn't let the crashes finish and just restarted the pc as I thought that a BlackScreen means complete failure and no dump would be created.

The one I posted here was after I pulled one stick of RAM out and tried to use the system for a week.

After sending them the new dump they told me that they believe it could be the GPU that is faulty.

So now I'm waiting for a replacement part which I will swap out with the old one to send it back to them.

We will see if I'll be able to run the PC for a month or so without crashes.

Until then I cannot contribute anything more to the question - sorry.

Yours

HardResetting

First of all: Thank you for your help!

I thought of replying after I recieve my new GPU to tell if it was at fault or my problem persists.

As you pointed out I shall use my warranty instead of going through the trouble myself.

I'll get back to you as soon as I have anything new!

Until then: Thank you and have a nice one!

Yours

HardResetting

Good move, they will now be responsible for fixing the computer throughout the process. Plus you will have some history and protection in case similar issues happen again down the road.

Please let me know if you have any further questions. If you have a moment, it would be greatly appreciated if you would rate my assistance in handling your ticket and have a great day!

Here to help,

Rob (in my other persona)

"Cos here there's lots of room for doing

The things you've always been denied

So look and gather all you want to

There's no one here to stop you trying"

- The Moody Blues

Hey again,

funnily enough, I still have not received my new GPU. Turns out they don't have it in stock, so I'm stuck waiting.

In the meantime, I did not experience ANY crashes except today when playing VR again (Note that I played VR for prolonged times without anything happening except today).

And it did produce a new dmp.. If it helps solve the problem in any way - here it is :)

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
	DISPATCH_LEVEL or above. The offending component can usually be
	identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff805426fa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2702

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 33457

    Key  : Analysis.Init.CPU.mSec
    Value: 265

    Key  : Analysis.Init.Elapsed.mSec
    Value: 11701

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 73

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff805426fa320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff80547276a10 -- (.trap 0xfffff80547276a10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80555ec979c rbx=0000000000000000 rcx=ffff8b0fab07cb10
rdx=ffff8b0fabb31000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80541dffdd7 rsp=fffff80547276ba8 rbp=fffff80547276cb0
 r8=0000000000000000  r9=0000000000000000 r10=0000fffff80555ec
r11=ffff8bfb1c000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!guard_dispatch_icall+0x67:
fffff805`41dffdd7 7505            jne     nt!guard_dispatch_icall+0x6e (fffff805`41dffdde) [br=1]
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  vrmonitor.exe

DPC_STACK_BASE:  FFFFF80547276FB0

STACK_TEXT:  
fffff805`4727de18 fffff805`41e1f57e     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`426fa320 : nt!KeBugCheckEx
fffff805`4727de20 fffff805`41c16ac3     : 000002e6`e97ebb06 fffff805`3f1fc180 00000000`00000000 fffff805`3f1fc180 : nt!KeAccumulateTicks+0x20625e
fffff805`4727de80 fffff805`41c165aa     : fffff805`426f3780 fffff805`47276a90 fffff805`45bb3c00 00000000`0000a301 : nt!KeClockInterruptNotify+0x453
fffff805`4727df30 fffff805`41cde045     : fffff805`426f3780 00000000`00000000 00000000`00000000 ffff3df2`611b98b7 : nt!HalpTimerClockIpiRoutine+0x1a
fffff805`4727df60 fffff805`41df8c7a     : fffff805`47276a90 fffff805`426f3780 000002e6`e97e98eb 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff805`4727dfb0 fffff805`41df91e7     : fffff805`47276a30 00000000`00000014 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff805`47276a10 fffff805`41dffdd7     : fffff805`41c9a3ae fffff805`3f1ff240 ffff8b0f`a56d0000 fffff805`47276e80 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff805`47276ba8 fffff805`41c9a3ae     : fffff805`3f1ff240 ffff8b0f`a56d0000 fffff805`47276e80 fffff805`00000002 : nt!guard_dispatch_icall+0x67
fffff805`47276bb0 fffff805`41c99694     : fffff805`3f1fc180 00000000`00000000 00000000`00000002 00000000`00000004 : nt!KiExecuteAllDpcs+0x30e
fffff805`47276d20 fffff805`41dfe215     : 00000000`00000000 fffff805`3f1fc180 ffff9c01`04b7c8c0 ffff8b0f`afe29080 : nt!KiRetireDpcList+0x1f4
fffff805`47276fb0 fffff805`41dfe000     : fffff805`41df32c0 fffff805`41d25dfa 00000000`00000000 ffff9c01`04500180 : nt!KxRetireDpcList+0x5
ffffd789`9399f7b0 fffff805`41dfd8b5     : ffff8b0f`afe29080 fffff805`41df8d41 ffff8b0f`a52c27a0 00000000`00000000 : nt!KiDispatchInterruptContinue
ffffd789`9399f7e0 fffff805`41df8d41     : ffff8b0f`a52c27a0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterruptBypass+0x25
ffffd789`9399f7f0 fffff805`41ff621c     : fffff805`41ff5cef 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0xb1
ffffd789`9399f988 fffff805`41ff5cef     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpLookupHandleTableEntry+0x2c
ffffd789`9399f990 fffff805`41ff5bee     : ffff8b0f`afe29080 00000000`00000002 ffff8b0f`a52c27a0 00000000`7ffe0001 : nt!ObpReferenceObjectByHandleWithTag+0xef
ffffd789`9399fa20 fffff805`420daed0     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8b0f`ab92dce0 : nt!ObReferenceObjectByHandle+0x2e
ffffd789`9399fa70 fffff805`41e08bb8     : ffff8b0f`aeb2a080 00000000`00000000 0000015d`00000000 ffffd789`9399fb40 : nt!NtClearEvent+0x50
ffffd789`9399fac0 00007ffe`e6ead5e4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000026`206ffc48 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`e6ead5e4


SYMBOL_NAME:  nt!KeAccumulateTicks+20625e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.1165

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  20625e

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

Followup:     MachineOwner
---------

IMAGE_NAME:  ntkrnlmp.exe <-- is a Windows component which means 
something else drove it into Fault.

Rob

Hey there!

There you go:

Thanks for answering so quickly :)

I'm honestly quite invested in this by now. It's just that the crashes appear seemingly random and quite far apart at that..

No clear cause but there were a couple of possibilities.

1. Fully uninstall Nord VPN while troubleshooting, Use a Free VPN if you really need one.

The Best Free VPNs for 2021

Rob B. (in my other persona)

Hi!

After many back and forths with the seller of my system they said that they think my PSU is at fault (As it only provided 600W)

After replacing it with a higher wattage PSU I still have the same blackscreens.

I have updated all drivers and even cleanly installed the nvidia-drivers via DDU.

Nothing helped though and I'll paste the most recent dump file down below.

This is just for everyone that stumbles upon my post by searching for the error.

I'll probably have to send my system to the retailer so that they have a look at it themselves.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
	DISPATCH_LEVEL or above. The offending component can usually be
	identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff800776fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3061

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 41300

    Key  : Analysis.Init.CPU.mSec
    Value: 265

    Key  : Analysis.Init.Elapsed.mSec
    Value: 1759

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 73

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff800776fb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff8007c477680 -- (.trap 0xfffff8007c477680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd58786bec420
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80076c14c71 rsp=fffff8007c477810 rbp=fffff8007c477a00
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000004 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiInsertQueueDpc+0x51:
fffff800`76c14c71 4c896c2440      mov     qword ptr [rsp+40h],r13 ss:fffff800`7c477850=0000000000000002
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Prospect-Win64-Shipping.exe

DPC_STACK_BASE:  FFFFF8007C477FB0

STACK_TEXT:  
fffff800`7c47ee18 fffff800`76e1f57e     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`776fb320 : nt!KeBugCheckEx
fffff800`7c47ee20 fffff800`76c16953     : 00001773`7b08b2cd fffff800`7412b180 00000000`00000000 fffff800`7412b180 : nt!KeAccumulateTicks+0x2063ce
fffff800`7c47ee80 fffff800`76c1643a     : fffff800`776f3840 fffff800`7c477700 00000000`00000000 00000000`00000246 : nt!KeClockInterruptNotify+0x453
fffff800`7c47ef30 fffff800`76cde055     : fffff800`776f3840 00000000`00000000 00000000`00000000 ffff70bc`997f46e5 : nt!HalpTimerClockIpiRoutine+0x1a
fffff800`7c47ef60 fffff800`76df8c5a     : fffff800`7c477700 fffff800`776f3840 fffff800`7c477900 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff800`7c47efb0 fffff800`76df91c7     : fffff800`76df32a0 fffff800`76d25e1a fffff800`76df32a0 fffff800`76d25e1a : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff800`7c477680 fffff800`76c14c71     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff800`7c477810 fffff800`76c14c11     : ffffd587`86888a00 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInsertQueueDpc+0x51
fffff800`7c4778c0 fffff800`8a9d8edd     : ffffd587`86e0e000 ffffd587`873bb9a0 00000000`00000001 fffff800`76c18f7c : nt!KeInsertQueueDpc+0x11
fffff800`7c477900 ffffd587`86e0e000     : ffffd587`873bb9a0 00000000`00000001 fffff800`76c18f7c 0000073f`00000004 : nvlddmkm+0x88edd
fffff800`7c477908 ffffd587`873bb9a0     : 00000000`00000001 fffff800`76c18f7c 0000073f`00000004 fffff800`741331c8 : 0xffffd587`86e0e000
fffff800`7c477910 00000000`00000001     : fffff800`76c18f7c 0000073f`00000004 fffff800`741331c8 00002b00`00000000 : 0xffffd587`873bb9a0
fffff800`7c477918 fffff800`76c18f7c     : 0000073f`00000004 fffff800`741331c8 00002b00`00000000 fffff800`00000001 : 0x1
fffff800`7c477920 00000000`00000000     : 00000000`00000000 00000000`00000000 fffff800`8a9e80c0 fffff800`8a9e8308 : nt!PpmUpdatePerformanceFeedback+0x16c


SYMBOL_NAME:  nvlddmkm+88edd

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  88edd

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup:     MachineOwner
---------