Share via

Computer Keeps Crashing - Graphics Drivers?

Anonymous
2024-10-27T12:12:39+00:00

Hi,

So I keep having repeated crashes on my PC, I have tried updating Windows, updating the BIOS, Nvida drivers, rolling back to older versions, removing and reinstalling drivers using DUU, updating motherboard drivers and a number of other things, including opening up my pc and cleaning it out - but I still keep getting the following crashes:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000116 (0xffffcf812171d010, 0xfffff804441d0a40, 0xffffffffc000009a, 0x0000000000000004). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 90509124-cb97-4b5c-ac89-9bdbbb904bf8.

Anyone able to offer some insight into what might cause this, or what I can do. I have searched online and tried doing the recommended things, but nothing seems to work.

Dump file says the following:

VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: ffffcf812171d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff804441d0a40, The pointer into responsible device driver module (e.g. owner tag). Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvmdi.inf_amd64_8de72197f4c7fa03\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Check Image - Checksum mismatch - Dump: 0x48878f, File: 0x4947be - C:\ProgramData\Dbg\sym\dxgkrnl.sys\5525936F486000\dxgkrnl.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 1578

Key  : Analysis.Elapsed.mSec
Value: 2508

Key  : Analysis.IO.Other.Mb
Value: 0

Key  : Analysis.IO.Read.Mb
Value: 1

Key  : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key  : Analysis.Version.DbgEng
Value: 10.0.27725.1000

Key  : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key  : Analysis.Version.Ext
Value: 1.2408.27.1

Key  : Bugcheck.Code.KiBugCheckData
Value: 0x116

Key  : Bugcheck.Code.LegacyAPI
Value: 0x116

Key  : Bugcheck.Code.TargetModel
Value: 0x116

Key  : Dump.Attributes.AsUlong
Value: 1000

Key  : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key  : Dump.Attributes.ErrorCode
Value: 0

Key  : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key  : Dump.Attributes.ProgressPercentage
Value: 100

Key  : Failure.Bucket
Value: 0x116\_IMAGE\_nvlddmkm.sys

Key  : Failure.Hash
Value: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Key  : Hypervisor.Enlightenments.Value
Value: 0

Key  : Hypervisor.Enlightenments.ValueHex
Value: 0

Key  : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key  : Hypervisor.Flags.ApicEnlightened
Value: 0

Key  : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key  : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key  : Hypervisor.Flags.CpuManager
Value: 0

Key  : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key  : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key  : Hypervisor.Flags.Epf
Value: 0

Key  : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key  : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key  : Hypervisor.Flags.MaxBankNumber
Value: 0

Key  : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key  : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key  : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key  : Hypervisor.Flags.Phase0InitDone
Value: 0

Key  : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key  : Hypervisor.Flags.RootScheduler
Value: 0

Key  : Hypervisor.Flags.SynicAvailable
Value: 0

Key  : Hypervisor.Flags.UseQpcBias
Value: 0

Key  : Hypervisor.Flags.Value
Value: 16908288

Key  : Hypervisor.Flags.ValueHex
Value: 1020000

Key  : Hypervisor.Flags.VpAssistPage
Value: 0

Key  : Hypervisor.Flags.VsmAvailable
Value: 0

Key  : Hypervisor.RootFlags.AccessStats
Value: 0

Key  : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key  : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key  : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key  : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key  : Hypervisor.RootFlags.IsHyperV
Value: 0

Key  : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key  : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key  : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key  : Hypervisor.RootFlags.Nested
Value: 0

Key  : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key  : Hypervisor.RootFlags.Value
Value: 0

Key  : Hypervisor.RootFlags.ValueHex
Value: 0

Key  : SecureKernel.HalpHvciEnabled
Value: 0

Key  : WER.OS.Branch
Value: ni\_release

Key  : WER.OS.Version
Value: 10.0.22621.1

BUGCHECK_CODE: 116

BUGCHECK_P1: ffffcf812171d010

BUGCHECK_P2: fffff804441d0a40

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FILE_IN_CAB: MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1000

FAULTING_THREAD: ffffcf8107ae6040

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffcf812171d010 Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffbc015deac868 fffff8042e5cb00e : 0000000000000116 ffffcf812171d010 fffff804441d0a40 ffffffffc000009a : nt!KeBugCheckEx ffffbc015deac870 fffff8042e57ce32 : fffff804441d0a40 ffffcf811202c820 0000000000000080 ffffcf811202c8e0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe ffffbc015deac8b0 fffff8042e5753a9 : ffffcf811ace3000 ffffcf8107ae6040 ffffcf811ace3b50 ffffcf811ace3b50 : dxgkrnl!ADAPTER_RENDER::Reset+0x12a ffffbc015deac8e0 fffff8042e5ca765 : 0000000000000100 ffffcf8107ae6040 0000000000000000 ffffcf812475e1b0 : dxgkrnl!DXGADAPTER::Reset+0x60d ffffbc015deac990 fffff8042e5ca8c2 : 0000000000000000 ffffcf811f63df90 0000000000000000 fffff8042014aac0 : dxgkrnl!TdrResetFromTimeout+0x15 ffffbc015deac9c0 fffff8041f6b7bf5 : ffffcf8107ae6040 ffffcf8104ec3a20 ffffbc0100000000 ffffffff00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x22 ffffbc015deaca00 fffff8041f74d487 : ffffcf8107ae6040 000000000000006c ffffcf8107ae6040 fffff8041f6b7aa0 : nt!ExpWorkerThread+0x155 ffffbc015deacbf0 fffff8041f819f64 : ffffa9019052a180 ffffcf8107ae6040 fffff8041f74d430 0000000000000000 : nt!PspSystemThreadStartup+0x57 ffffbc015deacc40 0000000000000000 : ffffbc015dead000 ffffbc015dea7000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: nvlddmkm+1700a40

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xffffcf8104efd040; .thread 0xffffcf8107ae6040 ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Followup: MachineOwner

Windows for home | Windows 11 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

7 answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. DaveM121 891.1K Reputation points Independent Advisor
    2024-10-27T13:11:20+00:00

    All your minidump files do indicate it is only the Nvidia drivers causing your system to crash, there is no other contributing factor listed.

    You indicate you have used DDU to remove the drivers and then tied installing other versions of the drivers, if you cannot find a version of that driver that stabilises your system, it may be best to have your graphics tested at a PC Repair Shop.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-10-27T13:03:11+00:00

    Was this answer helpful?

    0 comments No comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  5. DaveM121 891.1K Reputation points Independent Advisor
    2024-10-27T12:45:36+00:00

    Hi, I am Dave, I will help you with this.

    That does indicate it is the Nvidia drivers that is causing your system to crash, there are many reported problems with Nvidia drivers for quite a while now.

    Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.

    Open Windows File Explorer.

    Navigate to C:\Windows\Minidump

    Copy any minidump files onto your Desktop, then zip those up.

    Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

    Then post the link here to the zip file, so we can take a look for you.

    Was this answer helpful?

    0 comments No comments