- Jul 15, 2017
- 9
- 0
- 18,510
Hi everyone,
Recently my PC just froze while playing FIFA. Screen turned black and after a minute or two it restarted on its own. When it did, it gave me the USB over current status detected error and after a while it stopped doing that but whenever I start it up it, it freezes at the welcome screen and gives me the Watchdog violation BSOD. I tried restoring and then I tried a fresh windows installation, but nothing worked.
AMD 7900X
Asus x670e proart
Rtx 4090
64GB DDR5 corsair
1200W corsair
2 x 1TB Crucial T500
2TB Crucial T500
Right now, I can use the PC as long as my monitor is connected to the motherboard instead of the GPU. I extracted the dump files and this is the latest I got:
************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds************* Waiting for Debugger Extensions Gallery to Initialize **************>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 42Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\abdel\OneDrive\Desktop\011225-12296-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 26100 MP (24 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSEdition build lab: 26100.1.amd64fre.ge_release.240331-1435Kernel base = 0xfffff800`a1200000 PsLoadedModuleList = 0xfffff800`a20f4730Debug session time: Sun Jan 12 16:09:06.509 2025 (UTC + 1:00)System Uptime: 0 days 0:02:27.359Loading Kernel Symbols............................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list............For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff800`a16b8680 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9400`8dbc1ce0=00000000000001332: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION (133)The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVELor 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: fffff800a21c33a0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeoutArg4: 0000000000000000Debugging 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: 1156 Key : Analysis.Elapsed.mSec Value: 9613 Key : Analysis.IO.Other.Mb Value: 4 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 27 Key : Analysis.Init.CPU.mSec Value: 328 Key : Analysis.Init.Elapsed.mSec Value: 35994 Key : Analysis.Memory.CommitPeak.Mb Value: 94 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.LegacyAPI Value: 0x133 Key : Bugcheck.Code.TargetModel Value: 0x133 Key : Failure.Bucket Value: 0x133_ISR_nvlddmkm!unknown_function Key : Failure.Hash Value: {f97493a5-ea2b-23ca-a808-8602773c2a86} Key : Hypervisor.Enlightenments.ValueHex Value: 7497cf94 Key : Hypervisor.Flags.AnyHypervisorPresent Value: 1 Key : Hypervisor.Flags.ApicEnlightened Value: 1 Key : Hypervisor.Flags.ApicVirtualizationAvailable Value: 0 Key : Hypervisor.Flags.AsyncMemoryHint Value: 0 Key : Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key : Hypervisor.Flags.CpuManager Value: 1 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 0 Key : Hypervisor.Flags.DynamicCpuDisabled Value: 1 Key : Hypervisor.Flags.Epf Value: 0 Key : Hypervisor.Flags.ExtendedProcessorMasks Value: 1 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: 1 Key : Hypervisor.Flags.Phase0InitDone Value: 1 Key : Hypervisor.Flags.PowerSchedulerQos Value: 0 Key : Hypervisor.Flags.RootScheduler Value: 0 Key : Hypervisor.Flags.SynicAvailable Value: 1 Key : Hypervisor.Flags.UseQpcBias Value: 0 Key : Hypervisor.Flags.Value Value: 38408431 Key : Hypervisor.Flags.ValueHex Value: 24a10ef Key : Hypervisor.Flags.VpAssistPage Value: 1 Key : Hypervisor.Flags.VsmAvailable Value: 1 Key : Hypervisor.RootFlags.AccessStats Value: 1 Key : Hypervisor.RootFlags.CrashdumpEnlightened Value: 1 Key : Hypervisor.RootFlags.CreateVirtualProcessor Value: 1 Key : Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key : Hypervisor.RootFlags.HostTimelineSync Value: 1 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key : Hypervisor.RootFlags.IsHyperV Value: 1 Key : Hypervisor.RootFlags.LivedumpEnlightened Value: 1 Key : Hypervisor.RootFlags.MapDeviceInterrupt Value: 1 Key : Hypervisor.RootFlags.MceEnlightened Value: 1 Key : Hypervisor.RootFlags.Nested Value: 0 Key : Hypervisor.RootFlags.StartLogicalProcessor Value: 1 Key : Hypervisor.RootFlags.Value Value: 1015 Key : Hypervisor.RootFlags.ValueHex Value: 3f7 Key : Stack.Pointer Value: ISR Key : WER.OS.Branch Value: ge_release Key : WER.OS.Version Value: 10.0.26100.1BUGCHECK_CODE: 133BUGCHECK_P1: 1BUGCHECK_P2: 1e00BUGCHECK_P3: fffff800a21c33a0BUGCHECK_P4: 0FILE_IN_CAB: 011225-12296-01.dmpTAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202bFAULTING_THREAD: ffffb886f5611280DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDEDTRAP_FRAME: ffffa689e6e6e6a0 -- (.trap 0xffffa689e6e6e6a0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000002000 rbx=0000000000000000 rcx=00000000002e0404rdx=0000000000b81010 rsi=0000000000000000 rdi=0000000000000000rip=fffff80076aba8b4 rsp=ffffa689e6e6e830 rbp=ffffb8870a81fca8 r8=ffffa689e6e6e878 r9=0000000000b81010 r10=0000fffff800769fr11=ffff83fa24400000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl nz ac pe ncnvlddmkm+0xca8b4:fffff800`76aba8b4 488b5c2430 mov rbx,qword ptr [rsp+30h] ss:0018:ffffa689`e6e6e860=ffffb8870a81f000Resetting default scopeBLACKBOXBSD: 1 (!blackboxbsd)BLACKBOXNTFS: 1 (!blackboxntfs)BLACKBOXPNP: 1 (!blackboxpnp)BLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemSTACK_TEXT: ffff9400`8dbc1cd8 fffff800`a15b87a9 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`a21c33a0 : nt!KeBugCheckExffff9400`8dbc1ce0 fffff800`a1469f41 : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`000024d6 : nt!KeAccumulateTicks+0x589ffff9400`8dbc1d50 fffff800`a1409dfb : 00000000`57d54ef1 00000000`00000000 00000000`00000002 ffffb886`f55c8fc0 : nt!KiUpdateRunTime+0xc9ffff9400`8dbc1dd0 fffff800`a140b4ad : ffffb886`f55c8fc0 00000000`00000000 ffffb886`f55c9070 fffff800`a218dc10 : nt!KeClockInterruptNotify+0x96bffff9400`8dbc1f50 fffff800`a1875cde : 00000000`00b81002 ffffb886`f55c8fc0 ffffa689`e6e6e6a0 00000000`57d85ccc : nt!KiCallInterruptServiceRoutine+0x2edffff9400`8dbc1fb0 fffff800`a18764ec : 00000000`00000000 fffff800`76ad0059 1819fa61`37a54960 00000002`00000002 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4effffa689`e6e6e6a0 fffff800`76aba8b4 : ffffb887`00000000 00000000`00000000 00000000`00b81010 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3cffffa689`e6e6e830 ffffb887`00000000 : 00000000`00000000 00000000`00b81010 00000000`00000000 00000000`00b81010 : nvlddmkm+0xca8b4ffffa689`e6e6e838 00000000`00000000 : 00000000`00b81010 00000000`00000000 00000000`00b81010 fffff800`76aeaaa9 : 0xffffb887`00000000SYMBOL_NAME: nvlddmkm+ca8b4MODULE_NAME: nvlddmkmIMAGE_NAME: nvlddmkm.sysSTACK_COMMAND: .process /r /p 0xfffff800a21cdf80; .thread 0xffffb886f5611280 ; kbBUCKET_ID_FUNC_OFFSET: ca8b4FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_functionOS_VERSION: 10.0.26100.1BUILDLAB_STR: ge_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}Followup: MachineOwner---------
I tried everything I found online regarding how to fix nvlddmkm.sys issues but nothing worked. What I noticed though is that I get the BSOD when I plug my monitor to the GPU but when it's plugged to the motherboard, the PC runs "fine" but the graphics are really bad. Does that mean my GPU is dead or is there a fix for this?
Thank you.
Recently my PC just froze while playing FIFA. Screen turned black and after a minute or two it restarted on its own. When it did, it gave me the USB over current status detected error and after a while it stopped doing that but whenever I start it up it, it freezes at the welcome screen and gives me the Watchdog violation BSOD. I tried restoring and then I tried a fresh windows installation, but nothing worked.
AMD 7900X
Asus x670e proart
Rtx 4090
64GB DDR5 corsair
1200W corsair
2 x 1TB Crucial T500
2TB Crucial T500
Right now, I can use the PC as long as my monitor is connected to the motherboard instead of the GPU. I extracted the dump files and this is the latest I got:
************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds************* Waiting for Debugger Extensions Gallery to Initialize **************>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 42Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\abdel\OneDrive\Desktop\011225-12296-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 26100 MP (24 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSEdition build lab: 26100.1.amd64fre.ge_release.240331-1435Kernel base = 0xfffff800`a1200000 PsLoadedModuleList = 0xfffff800`a20f4730Debug session time: Sun Jan 12 16:09:06.509 2025 (UTC + 1:00)System Uptime: 0 days 0:02:27.359Loading Kernel Symbols............................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list............For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff800`a16b8680 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9400`8dbc1ce0=00000000000001332: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION (133)The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVELor 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: fffff800a21c33a0, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeoutArg4: 0000000000000000Debugging 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: 1156 Key : Analysis.Elapsed.mSec Value: 9613 Key : Analysis.IO.Other.Mb Value: 4 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 27 Key : Analysis.Init.CPU.mSec Value: 328 Key : Analysis.Init.Elapsed.mSec Value: 35994 Key : Analysis.Memory.CommitPeak.Mb Value: 94 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.LegacyAPI Value: 0x133 Key : Bugcheck.Code.TargetModel Value: 0x133 Key : Failure.Bucket Value: 0x133_ISR_nvlddmkm!unknown_function Key : Failure.Hash Value: {f97493a5-ea2b-23ca-a808-8602773c2a86} Key : Hypervisor.Enlightenments.ValueHex Value: 7497cf94 Key : Hypervisor.Flags.AnyHypervisorPresent Value: 1 Key : Hypervisor.Flags.ApicEnlightened Value: 1 Key : Hypervisor.Flags.ApicVirtualizationAvailable Value: 0 Key : Hypervisor.Flags.AsyncMemoryHint Value: 0 Key : Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key : Hypervisor.Flags.CpuManager Value: 1 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 0 Key : Hypervisor.Flags.DynamicCpuDisabled Value: 1 Key : Hypervisor.Flags.Epf Value: 0 Key : Hypervisor.Flags.ExtendedProcessorMasks Value: 1 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: 1 Key : Hypervisor.Flags.Phase0InitDone Value: 1 Key : Hypervisor.Flags.PowerSchedulerQos Value: 0 Key : Hypervisor.Flags.RootScheduler Value: 0 Key : Hypervisor.Flags.SynicAvailable Value: 1 Key : Hypervisor.Flags.UseQpcBias Value: 0 Key : Hypervisor.Flags.Value Value: 38408431 Key : Hypervisor.Flags.ValueHex Value: 24a10ef Key : Hypervisor.Flags.VpAssistPage Value: 1 Key : Hypervisor.Flags.VsmAvailable Value: 1 Key : Hypervisor.RootFlags.AccessStats Value: 1 Key : Hypervisor.RootFlags.CrashdumpEnlightened Value: 1 Key : Hypervisor.RootFlags.CreateVirtualProcessor Value: 1 Key : Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key : Hypervisor.RootFlags.HostTimelineSync Value: 1 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key : Hypervisor.RootFlags.IsHyperV Value: 1 Key : Hypervisor.RootFlags.LivedumpEnlightened Value: 1 Key : Hypervisor.RootFlags.MapDeviceInterrupt Value: 1 Key : Hypervisor.RootFlags.MceEnlightened Value: 1 Key : Hypervisor.RootFlags.Nested Value: 0 Key : Hypervisor.RootFlags.StartLogicalProcessor Value: 1 Key : Hypervisor.RootFlags.Value Value: 1015 Key : Hypervisor.RootFlags.ValueHex Value: 3f7 Key : Stack.Pointer Value: ISR Key : WER.OS.Branch Value: ge_release Key : WER.OS.Version Value: 10.0.26100.1BUGCHECK_CODE: 133BUGCHECK_P1: 1BUGCHECK_P2: 1e00BUGCHECK_P3: fffff800a21c33a0BUGCHECK_P4: 0FILE_IN_CAB: 011225-12296-01.dmpTAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202bFAULTING_THREAD: ffffb886f5611280DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDEDTRAP_FRAME: ffffa689e6e6e6a0 -- (.trap 0xffffa689e6e6e6a0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000002000 rbx=0000000000000000 rcx=00000000002e0404rdx=0000000000b81010 rsi=0000000000000000 rdi=0000000000000000rip=fffff80076aba8b4 rsp=ffffa689e6e6e830 rbp=ffffb8870a81fca8 r8=ffffa689e6e6e878 r9=0000000000b81010 r10=0000fffff800769fr11=ffff83fa24400000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl nz ac pe ncnvlddmkm+0xca8b4:fffff800`76aba8b4 488b5c2430 mov rbx,qword ptr [rsp+30h] ss:0018:ffffa689`e6e6e860=ffffb8870a81f000Resetting default scopeBLACKBOXBSD: 1 (!blackboxbsd)BLACKBOXNTFS: 1 (!blackboxntfs)BLACKBOXPNP: 1 (!blackboxpnp)BLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemSTACK_TEXT: ffff9400`8dbc1cd8 fffff800`a15b87a9 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`a21c33a0 : nt!KeBugCheckExffff9400`8dbc1ce0 fffff800`a1469f41 : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`000024d6 : nt!KeAccumulateTicks+0x589ffff9400`8dbc1d50 fffff800`a1409dfb : 00000000`57d54ef1 00000000`00000000 00000000`00000002 ffffb886`f55c8fc0 : nt!KiUpdateRunTime+0xc9ffff9400`8dbc1dd0 fffff800`a140b4ad : ffffb886`f55c8fc0 00000000`00000000 ffffb886`f55c9070 fffff800`a218dc10 : nt!KeClockInterruptNotify+0x96bffff9400`8dbc1f50 fffff800`a1875cde : 00000000`00b81002 ffffb886`f55c8fc0 ffffa689`e6e6e6a0 00000000`57d85ccc : nt!KiCallInterruptServiceRoutine+0x2edffff9400`8dbc1fb0 fffff800`a18764ec : 00000000`00000000 fffff800`76ad0059 1819fa61`37a54960 00000002`00000002 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4effffa689`e6e6e6a0 fffff800`76aba8b4 : ffffb887`00000000 00000000`00000000 00000000`00b81010 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3cffffa689`e6e6e830 ffffb887`00000000 : 00000000`00000000 00000000`00b81010 00000000`00000000 00000000`00b81010 : nvlddmkm+0xca8b4ffffa689`e6e6e838 00000000`00000000 : 00000000`00b81010 00000000`00000000 00000000`00b81010 fffff800`76aeaaa9 : 0xffffb887`00000000SYMBOL_NAME: nvlddmkm+ca8b4MODULE_NAME: nvlddmkmIMAGE_NAME: nvlddmkm.sysSTACK_COMMAND: .process /r /p 0xfffff800a21cdf80; .thread 0xffffb886f5611280 ; kbBUCKET_ID_FUNC_OFFSET: ca8b4FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_functionOS_VERSION: 10.0.26100.1BUILDLAB_STR: ge_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}Followup: MachineOwner---------
I tried everything I found online regarding how to fix nvlddmkm.sys issues but nothing worked. What I noticed though is that I get the BSOD when I plug my monitor to the GPU but when it's plugged to the motherboard, the PC runs "fine" but the graphics are really bad. Does that mean my GPU is dead or is there a fix for this?
Thank you.
Facebook
Twitter
Instagram