Livekernelevent 141 and VIDEO_TDR_FAILURE (116)

Anonymous
2023-12-07T21:20:04+00:00

So recently i decided to upgrade my computer with a new graphics card. These are the new specs:

Motherboard: Asus ROG Strix b550i WIFI

CPU: Ryzen 5 5600x

memory: Ballistix 2x8GB 3600 MHz

Storage: Samsung 980 1TB

PSU: NZXT C650W 80+ gold

GPU: I upgraded from a 2060 6G to a 4060ti 16G

After installing the new GPU the pc started crashing quite often (When I reinstalled the old 2060 it never crashed). It would only crash while doing small tasks such as watching a video or doing light work. It did however manage to not crash during a few hours of higher load gaming. I started looking into the reliability monitor and found all crashes were either a livekernelevent 141 or 117. Using WinDBG i accessed these minidumps:

VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: ffffcd85108be010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff800a52a6730, 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 nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 1843

Key  : Analysis.Elapsed.mSec
Value: 2440

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

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

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

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

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

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

Key  : Bugcheck.Code.LegacyAPI
Value: 0x116

Key  : Dump.Attributes.AsUlong
Value: 1008

Key  : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key  : Dump.Attributes.ErrorCode
Value: 0

Key  : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

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

Key  : Dump.Attributes.ProgressPercentage
Value: 0

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

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

BUGCHECK_CODE: 116

BUGCHECK_P1: ffffcd85108be010

BUGCHECK_P2: fffff800a52a6730

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FILE_IN_CAB: 120723-6234-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008 Kernel Generated Triage Dump

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

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffe309402fa828 fffff80090621a8e : 0000000000000116 ffffcd85108be010 fffff800a52a6730 ffffffffc000009a : nt!KeBugCheckEx ffffe309402fa830 fffff800905d18e2 : fffff800a52a6730 ffffcd850ee7f010 0000000000000080 ffffcd850ee7f0d0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe ffffe309402fa870 fffff800905c953d : ffffcd850ee7b000 ffffcd85032da100 ffffcd850ee7bb50 ffffcd850ee7bb50 : dxgkrnl!ADAPTER_RENDER::Reset+0x12a ffffe309402fa8a0 fffff800906211e5 : 0000000000000100 ffffcd85032da100 0000000000000000 ffffcd851575d630 : dxgkrnl!DXGADAPTER::Reset+0x60d ffffe309402fa950 fffff80090621342 : 0000000000000000 ffffcd850d01fbc0 0000000000000000 fffff8007f14aac0 : dxgkrnl!TdrResetFromTimeout+0x15 ffffe309402fa980 fffff8007e634f85 : ffffcd85032da100 ffffcd850329b620 ffffe30900000000 ffffcd8500000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x22 ffffe309402fa9c0 fffff8007e707287 : ffffcd85032da100 0000000000000094 ffffcd85032da100 fffff8007e634e30 : nt!ExpWorkerThread+0x155 ffffe309402fabb0 fffff8007e81b8e4 : ffff820083ce0180 ffffcd85032da100 fffff8007e707230 37008c1e0996e13b : nt!PspSystemThreadStartup+0x57 ffffe309402fac00 0000000000000000 : ffffe309402fb000 ffffe309402f4000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: nvlddmkm+10f6730

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner

I have tried multiple solutions such as underclocking the GPU, resetting and reinstalling Windows 11, reinstalling the drivers using DDU, tried multiple versions of the drivers, made sure every component and cable was seated properly and RMA'd the card and gotten a entirely new one. I am starting to run out of idea's after trying so many options. Any help would be appreciated.

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

14 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jonathan Deives 79,565 Reputation points Independent Advisor
    2023-12-07T22:46:28+00:00

    The logs indicate that the cause is still the graphics card NVIDIA.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-12-07T22:15:58+00:00

    Minidump 1:

    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. Arg2: 0000000000001e00, The watchdog period (in ticks). Arg3: fffff80622d1d340, 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 *** *** *** ************************************************************************* *** WARNING: Check Image - Checksum mismatch - Dump: 0x20397e, File: 0x203a06 - C:\ProgramData\Dbg\sym\BTHport.sys\5249EE07202000\BTHport.sys

    KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
Value: 1843

Key  : Analysis.Elapsed.mSec
Value: 1943

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

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

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

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

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

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

Key  : Bugcheck.Code.LegacyAPI
Value: 0x133

Key  : Dump.Attributes.AsUlong
Value: 1008

Key  : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key  : Dump.Attributes.ErrorCode
Value: 0

Key  : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

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

Key  : Dump.Attributes.ProgressPercentage
Value: 0

Key  : Failure.Bucket
Value: 0x133\_ISR\_nvlddmkm!unknown\_function

Key  : Failure.Hash
Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}

    BUGCHECK_CODE: 133

    BUGCHECK_P1: 1

    BUGCHECK_P2: 1e00

    BUGCHECK_P3: fffff80622d1d340

    BUGCHECK_P4: 0

    FILE_IN_CAB: 120723-6000-01.dmp

    DUMP_FILE_ATTRIBUTES: 0x1008 Kernel Generated Triage Dump

    DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

    BLACKBOXBSD: 1 (!blackboxbsd)

    BLACKBOXNTFS: 1 (!blackboxntfs)

    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: System

    STACK_TEXT:
    fffff8061df9a9e8 fffff80622212bb9 : 0000000000000133 0000000000000001 0000000000001e00 fffff80622d1d340 : nt!KeBugCheckEx fffff8061df9a9f0 fffff80622212421 : 000001653c0873d0 000000000000652f 000000000000652e 0000000000000000 : nt!KeAccumulateTicks+0x239 fffff8061df9aa50 fffff8062220fa2f : 000000000000000c 0000000000001388 0000000000006500 0000000000003c4f : nt!KiUpdateRunTime+0xd1 fffff8061df9ac00 fffff80622210618 : 0000000000000000 ffff8c81f8799100 fffff8061d036180 0000000000000000 : nt!KiUpdateTime+0x63f fffff8061df9aea0 fffff8062220feda : fffff80622c5ffb8 ffff8c81f87991f0 ffff8c81f87991f0 0000000000000002 : nt!KeClockInterruptNotify+0x228 fffff8061df9af40 fffff80622324c4c : 00000000f17ce6e3 fffff80622d0d570 fffff80622d0d620 fffff8062241887b : nt!HalpTimerClockInterrupt+0x10a fffff8061df9af70 fffff80622418ada : fffff8061df8a9e0 fffff80622d0d570 000000000000001f 0000000000000000 : nt!KiCallInterruptServiceRoutine+0x9c fffff8061df9afb0 fffff80622419347 : 0000000000000002 ffff9c8400000000 0000000005000000 000000000000000c : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff8061df8a960 fffff8062226bc4b : 0000000000000000 fffff80622236d9b fffff8061df8ab50 0000000000000004 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff8061df8aaf0 fffff8064546b91f : fffff8061df8abe0 0000000000000010 ffffd86b3628acbe fffff80645452b2d : nt!KzLowerIrql+0x1b fffff8061df8ab20 fffff8061df8abe0 : 0000000000000010 ffffd86b3628acbe fffff80645452b2d 0000000000000000 : nvlddmkm+0xab91f fffff8061df8ab28 0000000000000010 : ffffd86b3628acbe fffff80645452b2d 0000000000000000 fffff8064546ccee : 0xfffff8061df8abe0 fffff8061df8ab30 ffffd86b3628acbe : fffff80645452b2d 0000000000000000 fffff8064546ccee 0000000000000000 : 0x10 fffff8061df8ab38 fffff80645452b2d : 0000000000000000 fffff8064546ccee 0000000000000000 0000000000000001 : 0xffffd86b3628acbe fffff8061df8ab40 0000000000000000 : fffff8064546ccee 0000000000000000 0000000000000001 fffff80600000010 : nvlddmkm+0x92b2d

    SYMBOL_NAME: nvlddmkm+ab91f

    MODULE_NAME: nvlddmkm

    IMAGE_NAME: nvlddmkm.sys

    STACK_COMMAND: .cxr; .ecxr ; kb

    BUCKET_ID_FUNC_OFFSET: ab91f

    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

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

    Followup: MachineOwner

    Minidump 2:

    VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: ffffcd85108be010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff800a52a6730, 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 nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys

    KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
Value: 1781

Key  : Analysis.Elapsed.mSec
Value: 2429

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

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

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

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

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

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

Key  : Bugcheck.Code.LegacyAPI
Value: 0x116

Key  : Dump.Attributes.AsUlong
Value: 1008

Key  : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key  : Dump.Attributes.ErrorCode
Value: 0

Key  : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

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

Key  : Dump.Attributes.ProgressPercentage
Value: 0

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

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

    BUGCHECK_CODE: 116

    BUGCHECK_P1: ffffcd85108be010

    BUGCHECK_P2: fffff800a52a6730

    BUGCHECK_P3: ffffffffc000009a

    BUGCHECK_P4: 4

    FILE_IN_CAB: 120723-6234-01.dmp

    DUMP_FILE_ATTRIBUTES: 0x1008 Kernel Generated Triage Dump

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

    PROCESS_OBJECT: 0000000000000004

    BLACKBOXBSD: 1 (!blackboxbsd)

    BLACKBOXNTFS: 1 (!blackboxntfs)

    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: System

    STACK_TEXT:
    ffffe309402fa828 fffff80090621a8e : 0000000000000116 ffffcd85108be010 fffff800a52a6730 ffffffffc000009a : nt!KeBugCheckEx ffffe309402fa830 fffff800905d18e2 : fffff800a52a6730 ffffcd850ee7f010 0000000000000080 ffffcd850ee7f0d0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe ffffe309402fa870 fffff800905c953d : ffffcd850ee7b000 ffffcd85032da100 ffffcd850ee7bb50 ffffcd850ee7bb50 : dxgkrnl!ADAPTER_RENDER::Reset+0x12a ffffe309402fa8a0 fffff800906211e5 : 0000000000000100 ffffcd85032da100 0000000000000000 ffffcd851575d630 : dxgkrnl!DXGADAPTER::Reset+0x60d ffffe309402fa950 fffff80090621342 : 0000000000000000 ffffcd850d01fbc0 0000000000000000 fffff8007f14aac0 : dxgkrnl!TdrResetFromTimeout+0x15 ffffe309402fa980 fffff8007e634f85 : ffffcd85032da100 ffffcd850329b620 ffffe30900000000 ffffcd8500000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x22 ffffe309402fa9c0 fffff8007e707287 : ffffcd85032da100 0000000000000094 ffffcd85032da100 fffff8007e634e30 : nt!ExpWorkerThread+0x155 ffffe309402fabb0 fffff8007e81b8e4 : ffff820083ce0180 ffffcd85032da100 fffff8007e707230 37008c1e0996e13b : nt!PspSystemThreadStartup+0x57 ffffe309402fac00 0000000000000000 : ffffe309402fb000 ffffe309402f4000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34

    SYMBOL_NAME: nvlddmkm+10f6730

    MODULE_NAME: nvlddmkm

    IMAGE_NAME: nvlddmkm.sys

    STACK_COMMAND: .cxr; .ecxr ; kb

    FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

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

    Followup: MachineOwner

    Minidump 3:

    VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe782bb262010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80282fd6730, 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 nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1875

    Key  : Analysis.Elapsed.mSec
    Value: 2344

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x116

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

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

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x116_IMAGE_nvlddmkm.sys

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

BUGCHECK_CODE:  116

BUGCHECK_P1: ffffe782bb262010

BUGCHECK_P2: fffff80282fd6730

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FILE_IN_CAB:  120723-5796-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

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

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff984`31f47828 fffff802`6c1c1a8e     : 00000000`00000116 ffffe782`bb262010 fffff802`82fd6730 ffffffff`c000009a : nt!KeBugCheckEx
fffff984`31f47830 fffff802`6c1718e2     : fffff802`82fd6730 ffffe782`bd4bd010 00000000`00000080 ffffe782`bd4bd0d0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
fffff984`31f47870 fffff802`6c16953d     : ffffe782`bd4a0000 ffffe782`bf53f0c0 ffffe782`bd4a0b50 ffffe782`bd4a0b50 : dxgkrnl!ADAPTER_RENDER::Reset+0x12a
fffff984`31f478a0 fffff802`6c1c11e5     : 00000000`00000101 ffffe782`bf53f0c0 00000000`00000000 ffffe782`bdd2f080 : dxgkrnl!DXGADAPTER::Reset+0x60d
fffff984`31f47950 fffff802`6c1c1342     : 00000000`00000000 fffff802`5c237ea0 ffffe782`bb594000 fffff802`5c34aac0 : dxgkrnl!TdrResetFromTimeout+0x15
fffff984`31f47980 fffff802`5b834f85     : ffffe782`bf53f0c0 ffffe782`af937bb0 ffffe782`00000000 fffff802`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x22
fffff984`31f479c0 fffff802`5b907287     : ffffe782`bf53f0c0 00000000`000000b9 ffffe782`bf53f0c0 fffff802`5b834e30 : nt!ExpWorkerThread+0x155
fffff984`31f47bb0 fffff802`5ba1b8e4     : ffffd780`ff051180 ffffe782`bf53f0c0 fffff802`5b907230 00000000`00000000 : nt!PspSystemThreadStartup+0x57
fffff984`31f47c00 00000000`00000000     : fffff984`31f48000 fffff984`31f41000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME:  nvlddmkm+10f6730

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner

    Was this answer helpful?

    0 comments
  3. Jonathan Deives 79,565 Reputation points Independent Advisor
    2023-12-07T22:08:17+00:00

    Do you have any other minidump files that I can analyze?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-12-07T21:58:10+00:00

    Hello Jonathan,

    Thanks for the quick reply. I am currently not using RTX Voice nor NVIDIA Broadcaster. This minidump was created after I reinstalled windows, so the only apps i had installed were Brave and Discord.

    Was this answer helpful?

    0 comments
  5. Jonathan Deives 79,565 Reputation points Independent Advisor
    2023-12-07T21:51:47+00:00

    My name is Jonathan Deives. I'm an Independent Advisor and I'll be glad to help you today.

    The minidump log indicates that the cause of the BSOD is "nvlddmkm.sys" which is an NVIDIA driver.

    Are you using an app like RTX Voice or NVIDIA Broadcaster? If so, please uninstall and test to see if the problem occurs.

    Was this answer helpful?

    0 comments