Question Lagging, stuttering and freezing issues on a new prebuilt PC ?

[Turbo27]

Hi, first time posting on here.
So I just recently bought myself a new prebuilt PC and am experiencing some issues with it. I've tested a few things that might be the cause but so far no luck.

A little bit of backstory:
So it all began when I was setting up my new PC downstairs (not enough room for both upstairs) so I could transfer some of my files from my old PC upstairs to the new one. The new one downstairs ran fine, saw no issues with it, but since I needed a monitor off of my old 2 monitor setup, I removed one monitor from my old PC and plugged it into the new one. I also had to use a old mouse for my old PC since I needed two of those as well. As I said, the new PC was running fine, no issues or anything, but when I went to use my old PC suddenly the mouse was very laggy, but I thought that was probably just the old mouse not having drivers installed on my old PC or something, so I ignored it.

After having transferred all the files and unplugging my old PC and setting up the new PC upstairs instead of my old one, I've started to have issues however. Now all of this doesn't happen all the time and some of it might be just me not remembering to turn off some setting or something in the NVIDIA app, but I am just unsure what I should do at this point, so I wanted to turn to people here who know more than I ever could.

First off, let me give you the specs of my new PC:

• CPU: AMD Ryzen 7 7800X3D
• RAM: Teamgroup Delta RGB 32GB DDR5 6000 CL38 (2x16GB)
• Motherboard: MSI X670E Tomahawk Wifi
• Graphics Card: GeForce RTX™ 5070 Ti 16GB
• Power Supply: MSI MAG A850GL Gold PCIE5
• OS: Windows 11 Home

Now the main issue I've experienced is that sometimes when I start my PC up from sleep my PC is pretty laggy. At first it doesn't seem like anything is wrong but for example when you try to type on Discord it like "freezes" for a bit and then instantly adds in all the text you've been writing at once, instead of normally just adding in the letters as you press them. Not to mention even when my PC is idle, opening up something simple like Firefox, freezes my mouse for like a second. This happened to me again this morning, after I woke my PC up from Sleep mode and the way I fixed it was to just put my PC back to sleep and wake it up again. This never happened with my old PC.

I've also had my games freeze a few times, then my screens just go black and my PC fans speed up and nothing works until I restart my PC again. Not fully sure if that's the game causing it or not since it only ever happened when playing the same game, but it was caused by me opening up the steam overlay with Shift+Tab. It didn't instantly do it either, I could use the overlay fine and go in and out of the game multiple times before it did that.

I had this issue a few times before and I ended up asking an AI (I know) for pointers what could be the issue. I was told that it could be a driver or a power issue, mainly. So I ended up installing Snappy Driver Installer Origin, installed all the drivers needed and waited to see if the issue would persist. It did. So I ended up asking more about the power issue I could be facing. I was told that my new PC parts were basically "too high tech" and more sensitive that they needed more stable power - compared to my old PC - so I ended up getting a socket tester just to see if there's an issue with my power or wiring, but all the wiring seems to be good and the power seems to be more or less stable. Can't really do much about that unless I invest in an UPS and I'd rather not if I can avoid it.

If there's anything else I can provide, even my old PC specs for whatever reason, I'll do my best.

Edit: I had provided the wrong specs, I updated them.

 

[Lutfij]

Welcome to the forums, newcomer!

IMHO, if you're away from the system, best just shut it down so you're not incurring vampiric power draw. With the advent of SSD's, it actually doesn't take as long as it did a decade or so ago to power up a system from a cold boot.

So I ended up installing Snappy Driver Installer Origin, installed all the drivers needed and waited to see if the issue would persist.
Never use third party apps to tell you if your platform is pending a driver/BIOS/system update. There are instances where they've caused a platform to end up bricked as it thought a BIOS update was pending/necessary. Unbeknownst to the user, who went forward and ruined their system.

You mentioned moving your games from another PC, can you state how you did so? Where did you source the installer for the games? Did you migrate your older drives to the new PC?

What BIOS version are you on for your motherboard?

 

[Turbo27]

Welcome to the forums, newcomer!

IMHO, if you're away from the system, best just shut it down so you're not incurring vampiric power draw. With the advent of SSD's, it actually doesn't take as long as it did a decade or so ago to power up a system from a cold boot.

So I ended up installing Snappy Driver Installer Origin, installed all the drivers needed and waited to see if the issue would persist.
Never use third party apps to tell you if your platform is pending a driver/BIOS/system update. There are instances where they've caused a platform to end up bricked as it thought a BIOS update was pending/necessary. Unbeknownst to the user, who went forward and ruined their system.

You mentioned moving your games from another PC, can you state how you did so? Where did you source the installer for the games? Did you migrate your older drives to the new PC?

What BIOS version are you on for your motherboard?

Thanks for the quick reply!

I understand the point that third-party driver installers could be problematic, but I'm not sure how I would go about finding all the drivers that could be out of date let alone installing them without the help of these programs. I was also more so talking about drivers like motherboard drivers etc, I don't think I saw a BIOS driver there. For my GPU I use the NVIDIA app.
Not sure if it's safer to install non-BIOS drivers from a third party software or not, just thought I'd clarify it a bit. I will take care to install BIOS drivers and updates manually, that's for sure.

As for moving games and files, I just used an USB stick to copy stuff over from Steam folders and such, I was more looking to preserve save data and not the installed games themselves. I reinstalled the games later.

Msinfo32.exe tells me that my BIOS version/date is "American Megatrends International, LLC. 1.H0, 14/03/2025", so probably outdated judging by the date.

 

[MJS WARLORD]

Was the new pc working ok before you started transferring items to it
IMHO I think reason why you are having problems is because of how you transferred steam ( or any ) games to your new pc. You should never put games or other programs on a usb to transfer them to another pc and the reason i say this is because you will only have got folders and game data , their will be some items in the registry of your old pc that have not been put onto your new pc.

Try this ..... find a game on your old pc that you dont want to use then go into the registry and delete anything that you can find related to that game. Now go back and try and run the game ... i bet it wont work.

Before i get a new pc i go through all my games folders and make copies of the saves , you will even find some in your documents folders...... re-install your games and after the first save has been made replace it with your back up saves ...... better still ... if you had cloud saves enabled your steam client wont even know its on a new pc so you will be able to carry on where you left off on your old pc.

 

[Turbo27]

Was the new pc working ok before you started transferring items to it
IMHO I think reason why you are having problems is because of how you transferred steam ( or any ) games to your new pc. You should never put games or other programs on a usb to transfer them to another pc and the reason i say this is because you will only have got folders and game data , their will be some items in the registry of your old pc that have not been put onto your new pc.

Try this ..... find a game on your old pc that you dont want to use then go into the registry and delete anything that you can find related to that game. Now go back and try and run the game ... i bet it wont work.

Before i get a new pc i go through all my games folders and make copies of the saves , you will even find some in your documents folders...... re-install your games and after the first save has been made replace it with your back up saves ...... better still ... if you had cloud saves enabled your steam client wont even know its on a new pc so you will be able to carry on where you left off on your old pc.

The new PC was working fine before I started transferring items to it, yes, but the issues I have aren't constant. I sometimes have these issues and sometimes don't. These issues could've been there but I might have just gotten lucky since it was the first boot right after I set up windows. The mouse is also not laggy for me every time I boot up my PC or bring it out of sleep, it's random.

I'm not a 100% on this, but I doubt me copying my steamapps folder from one PC to another would cause my mouse to freeze and my screens to go black. I must also preface that the game that I had the issue with (screens going black and PC becoming unresponsive) was a new game I had bought after I already had issues with my mouse lagging. Before I started transferring my saves from one PC to another, I fully uninstalled all of my steam games, so I didn't end up moving any files that weren't my saves. I do understand the point about the registry and stuff, but from what I found online, I don't think I would need to change my registry on a new PC just to use some of my game saves properly.

 

[MJS WARLORD]

The new PC was working fine before I started transferring items to it, yes, but the issues I have aren't constant. I sometimes have these issues and sometimes don't. These issues could've been there but I might have just gotten lucky since it was the first boot right after I set up windows. The mouse is also not laggy for me every time I boot up my PC or bring it out of sleep, it's random.

I'm not a 100% on this, but I doubt me copying my steamapps folder from one PC to another would cause my mouse to freeze and my screens to go black. I must also preface that the game that I had the issue with (screens going black and PC becoming unresponsive) was a new game I had bought after I already had issues with my mouse lagging. Before I started transferring my saves from one PC to another, I fully uninstalled all of my steam games, so I didn't end up moving any files that weren't my saves. I do understand the point about the registry and stuff, but from what I found online, I don't think I would need to change my registry on a new PC just to use some of my game saves properly.

your right you dont need to go into the registry on your new pc, just put saves on it.

 

[Turbo27]

your right you dont need to go into the reg on your new pc just put saves on it.

That's what I thought as well; sorry if I have come across as incoherent or not clear with what I say, English is not my first language and I appreciate the effort everyone goes through to even try and help me, even if it leads nowhere.

Edit: it also seems I provided the wrong specs in the original post, I am going to update them now.

 

[Turbo27]

Thanks for the quick reply!

I understand the point that third-party driver installers could be problematic, but I'm not sure how I would go about finding all the drivers that could be out of date let alone installing them without the help of these programs. I was also more so talking about drivers like motherboard drivers etc, I don't think I saw a BIOS driver there. For my GPU I use the NVIDIA app.
Not sure if it's safer to install non-BIOS drivers from a third party software or not, just thought I'd clarify it a bit. I will take care to install BIOS drivers and updates manually, that's for sure.

As for moving games and files, I just used an USB stick to copy stuff over from Steam folders and such, I was more looking to preserve save data and not the installed games themselves. I reinstalled the games later.

Msinfo32.exe tells me that my BIOS version/date is "American Megatrends International, LLC. 1.H0, 14/03/2025", so probably outdated judging by the date.

I have now updated my BIOS version to the latest one and currently I see no issues. It might take me a day or two to see if anything is wrong with my PC still, but if there's anything else I can try to do that could fix this issue, I would greatly appreciate the help.

 

[Turbo27]

I have put my PC to sleep (for consistency) and woken it up like I usually do every day/night to see if there's any issues. So far, none of the previous issues seemed to happen after I did the BIOS update, but today, when I started my PC up from sleep, my keyboard and mouse light up and so do the RGB in my PC, but my monitors stay black and then my PC restarts. I'm not sure what the cause for that could be, but I thought I'd mention it here.

On a side note, I've also been dealing with some green/black video artifacts and light audio crackling every now and then, checking my Latencymon it looks to be my NVIDIA driver causing it but even after doing a full clean reinstall of the drivers (thanks to Display Driver Uninstaller) it still hasn't gone fully away. I wonder if Game Ready Drivers are the issue and I should install Studio Drivers instead or am I just not doing it right? The DPC latency goes as high as 11000μs. It's not constant though and seems to just spike every now and then.

 

[Turbo27]

The mouse lag returned today after booting up my pc from sleep, then my mouse froze, one of my screens went black, then the other one a few seconds later, then everything else and then it all restarted my PC.

Event viewer shows me a few errors like:
The previous system shutdown at 8:11:17 PM on ‎6/‎7/‎2025 was unexpected.
and
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

There was also a dump file created it seems and reading it with WinDbg reveals that
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.

So it's probably my graphics drivers that is causing this.

 

[Turbo27]

I don't know why but I just can't seem to remove the issues no matter how many clean installs of graphics drivers I do, be they Game Ready or Studio drivers. Not really sure what to do.

 

[Roland Of Gilead]

After a bios update you must clear CMOS. If you don't, remnants of microcode from previous bios linger. This causes all manner of issues.

Check your mobo manual on how to do it. Best thing is to take out the battery, short the two pins marked as CLRTC, or JBAT 1 (if it's a jumper), short for 30 seconds. Put battery back in, and boot up and test again.

 

[Turbo27]

Do I need to do anything after clearing CMOS? Never done it before so not fully sure what it changes for me. I will try it though. Thanks!

 

[Angel Fernandez]

Roland raises an issue that is not often talked about.
Left over microcode.
In my experience Asus has this issue but they don't mention it in their documentation.

 

[Misgar]

Now the main issue I've experienced is that sometimes when I start my PC up from sleep my PC is pretty laggy.

As @Lutfij says, the best way to avoid Sleep problems is to stop using Sleep and shut down your computer after use. I switch off my computers and monitors at the wall, to completely eliminate Vampire power. An ATX PSU and a monitor sitting in standby mode will consume a few Watts. With multiple systems, the drain and cost increases.

I take great pains to avoid Sleep, Hibernate and all power saving options for disk drives, USB ports, network chipsets, etc., on all my desktop PCs. Putting things to sleep and expecting everything to wake up normally is fraught with problems.
https://thegeekpage.com/windows-10-doesnt-wake-from-sleep/
https://techwiser.com/ways-to-fix-windows-11-not-waking-up-from-sleep/
https://www.thewindowsclub.com/windows-will-not-wake-up-from-sleep-mode

You may also be affected by Windows shutting down your disk drives, internal USB hubs, Ethernet, WiFi and Bluetooth chipsets, PCI Express Link State Power, etc., whilst the computer is up and running.

Some external USB devices react unexpectedly, when the associated internal USB hub is powered off during perods of inactivity, then back on again.

These are the steps I take for USB:
https://www.elevenforum.com/t/enable-or-disable-usb-selective-suspend-in-windows-11.10251/
https://www.supportyourtech.com/tec...-settings-in-windows-11-a-step-by-step-guide/

I perform similar steps for Ethernet, WiFi, Bluetooth, disk drives, PCIe bus, video cards, etc. A big complicated list. Basically, I switch off all Windows power saving features and Windows Fast Startup. Bad for the planet, bad for my wallet, good for my sanity.

The only time I use Sleep or Hibernate is on laptops, but I still disable all the other power saving features.

 

[Turbo27]

As @Lutfij says, the best way to avoid Sleep problems is to stop using Sleep and shut down your computer after use. I switch off my computers and monitors at the wall, to completely eliminate Vampire power. An ATX PSU and a monitor sitting in standby mode will consume a few Watts. With multiple systems, the drain and cost increases.

I take great pains to avoid Sleep, Hibernate and all power saving options for disk drives, USB ports, network chipsets, etc., on all my desktop PCs. Putting things to sleep and expecting everything to wake up normally is fraught with problems.
https://thegeekpage.com/windows-10-doesnt-wake-from-sleep/
https://techwiser.com/ways-to-fix-windows-11-not-waking-up-from-sleep/
https://www.thewindowsclub.com/windows-will-not-wake-up-from-sleep-mode

You may also be affected by Windows shutting down your disk drives, internal USB hubs, Ethernet, WiFi and Bluetooth chipsets, PCI Express Link State Power, etc., whilst the computer is up and running.

Some external USB devices react unexpectedly, when the associated internal USB hub is powered off during perods of inactivity, then back on again.

These are the steps I take for USB:
https://www.elevenforum.com/t/enable-or-disable-usb-selective-suspend-in-windows-11.10251/
https://www.supportyourtech.com/tec...-settings-in-windows-11-a-step-by-step-guide/

I perform similar steps for Ethernet, WiFi, Bluetooth, disk drives, PCIe bus, video cards, etc. A big complicated list. Basically, I switch off all Windows power saving features and Windows Fast Startup. Bad for the planet, bad for my wallet, good for my sanity.

The only time I use Sleep or Hibernate is on laptops, but I still disable all the other power saving features.

I understand that I shouldn't use sleep as there can be issues, but I'm personally just too used to it and since I use my PC a lot, it's just nice to start doing my stuff right where I left off.

My issues seem to stem mostly from my drivers and stuff like that, based on everything I've found out about. It's especially annoying since the last PC I had was fine going to sleep and waking up every single day. There were no real issues I ever had, except maybe it waking up from sleep on it's own every now and then which are easily fixable.

I don't want to have to stop using sleep if possible, but once I've eliminated every other variable and the sleep issues are the only things that remain I will stop using it. For now, I will intentionally continue using sleep just to test if the issues still persist or if I actually have fixed them. Thank you for the comment and the info shared, I will definitely look over everything you have said.

 

[Turbo27]

What I have now done:

Disabled USB Selective Suspend
PCIe Link State Power Management set to off already
Unchecked “Allow the computer to turn off this device…” for my USB devices
Already am on Ultimate Performance and have disabled Fast Startup
Updated BIOS
Cleared CMOS
Changed my 2nd monitor from a 60hz monitor to 144hz monitor and started using DisplayPort cables for both monitors
Clean install graphics drivers (studio drivers)

I will continue to observe how my system behaves upon resuming from sleep and if no issue persist, I will keep using it, if issues keep happening I'll probably stop using it.

There were also issues with DPC latency so I decided to switch out my old 60hz monitor to a new 144hz one to match my other monitor and use DP cables for both of them and reinstall the drivers, but it seems this issue still hasn't gone anywhere. So if anything, maybe I fixed my issues with booting up from sleep (yet to be seen).

Let me know if there's anything I've missed or what else I could try. Thanks again to everyone for the advice!

 

[Turbo27]

First time since I did all the things in the last post, today my PC restarted itself upon booting up again, not turning on my monitors due to display driver crash.
Here is what WinDb told me about the error that occurred:

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffd5872d31d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff800b48caae0, 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: 1015

Key : Analysis.Elapsed.mSec
Value: 3024

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: 250

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27871.1001

Key : Analysis.Version.Description
Value: 10.2505.01.02 amd64fre

Key : Analysis.Version.Ext
Value: 1.2505.1.2

Key : Bugcheck.Code.LegacyAPI
Value: 0x116

Key : Bugcheck.Code.TargetModel
Value: 0x116

Key : Dump.Attributes.AsUlong
Value: 0x1808

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0x0

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.Exception.IP.Address
Value: 0xfffff800b48caae0

Key : Failure.Exception.IP.Module
Value: nvlddmkm

Key : Failure.Exception.IP.Offset
Value: 0x198aae0

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

Key : Hypervisor.Enlightenments.ValueHex
Value: 0x1497cf94

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: 4853999

Key : Hypervisor.Flags.ValueHex
Value: 0x4a10ef

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: 0x3f7


BUGCHECK_CODE: 116

BUGCHECK_P1: ffffd5872d31d010

BUGCHECK_P2: fffff800b48caae0

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FILE_IN_CAB: 070125-19500-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

FAULTING_THREAD: ffffd5871b5e5040

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

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffd48f`b4e8a1e8 fffff800`9510f85e : 00000000`00000116 ffffd587`2d31d010 fffff800`b48caae0 ffffffff`c000009a : nt!KeBugCheckEx
ffffd48f`b4e8a1f0 fffff800`950c1822 : fffff800`b48caae0 ffffd587`2fe7f820 00000000`00000080 ffffd587`2fe7f8e0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffd48f`b4e8a230 fffff800`950b9d59 : ffffd587`3215e000 ffffd587`1b5e5040 ffffd587`3215eb50 ffffd587`3215eb50 : dxgkrnl!ADAPTER_RENDER::Reset+0x12a
ffffd48f`b4e8a260 fffff800`9510efb5 : 00000000`00000100 ffffd587`1b5e5040 00000000`00000000 ffffd587`4f142d40 : dxgkrnl!DXGADAPTER::Reset+0x60d
ffffd48f`b4e8a310 fffff800`9510f112 : 00000000`00000000 fffff800`4ba58310 ffffd587`1b5df000 fffff800`48d4aac0 : dxgkrnl!TdrResetFromTimeout+0x15
ffffd48f`b4e8a340 fffff800`482d8c25 : ffffd587`1b5e5040 ffffd587`19f561a0 ffffd587`00000000 ffffd587`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x22
ffffd48f`b4e8a380 fffff800`482ded97 : ffffd587`1b5e5040 00000000`000000d2 ffffd587`1b5e5040 fffff800`482d8ad0 : nt!ExpWorkerThread+0x155
ffffd48f`b4e8a570 fffff800`4841d054 : fffff800`4359b180 ffffd587`1b5e5040 fffff800`482ded40 00000000`00000000 : nt!PspSystemThreadStartup+0x57
ffffd48f`b4e8a5c0 00000000`00000000 : ffffd48f`b4e8b000 ffffd48f`b4e84000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: nvlddmkm+198aae0

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xffffd58719ffb040; .thread 0xffffd5871b5e5040 ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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


And event viewer had an error and critical event listed:

Critical: "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

Error1: "The previous system shutdown at 10:49:41 PM on ‎6/‎30/‎2025 was unexpected." (this is when I put it to sleep)
Error 2: "The description for Event ID 153 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video3
Error occurred on GPUID: 100

The message resource is present but the message was not found in the message table" (this should be after the restart)




After this happened today, it rebooted and my mouse started being "laggy" again. I knew this was an issue that happened before on boot and restart would fix it but I decided to start writing the post here after I checked the dump file. During this, my screens went black again and the PC restarted itself. So both of the issues I've been having happened today.

Here's what the WinDb said about the crash:

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffffde03d15272a0
Arg4: ffff998dc0484080

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 906

Key : Analysis.Elapsed.mSec
Value: 8487

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

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

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

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27871.1001

Key : Analysis.Version.Description
Value: 10.2505.01.02 amd64fre

Key : Analysis.Version.Ext
Value: 1.2505.1.2

Key : Bugcheck.Code.LegacyAPI
Value: 0x119

Key : Bugcheck.Code.TargetModel
Value: 0x119

Key : Dump.Attributes.AsUlong
Value: 0x808

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

Key : Failure.Hash
Value: {9a11bf9c-270e-962e-7a82-3efdab93c10e}

Key : Hypervisor.Enlightenments.ValueHex
Value: 0x1497cf94

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: 4853999

Key : Hypervisor.Flags.ValueHex
Value: 0x4a10ef

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: 0x3f7


BUGCHECK_CODE: 119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffffde03d15272a0

BUGCHECK_P4: ffff998dc0484080

FILE_IN_CAB: 070125-16937-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x808
Kernel Generated Triage Dump

FAULTING_THREAD: ffff998dc045c480

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffde03`d1527138 fffff807`7f395745 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffde03`d15272a0 : nt!KeBugCheckEx
ffffde03`d1527140 fffff807`bad6436b : 00000000`00000000 ffff998d`af5f5180 ffff998d`af5f5188 ffff998d`af5f5190 : watchdog!WdLogSingleEntry5+0x3c05
ffffde03`d15271f0 fffff807`badc762e : ffff998d`00000000 ffff998d`c0484000 ffff998d`c03ea000 ffff998d`c0484080 : dxgmms2!VidSchiSendToExecutionQueue+0x17a3b
ffffde03`d15273c0 fffff807`bae4684c : ffff998d`c0484080 ffffde03`d1527479 ffff998d`c03ea000 fffff807`bad4a660 : dxgmms2!VidSchiSendToExecutionQueueWithWait+0x5a
ffffde03`d15273f0 fffff807`bae1d790 : fffff807`7a4b0000 ffff998d`c0259770 ffff998d`cf3e5010 ffff998d`c00138e0 : dxgmms2!VidSchiSubmitPagingCommand+0x358
ffffde03`d15274e0 fffff807`badf781a : 00000000`00000000 fffff807`badf7750 ffff998d`c03ea000 ffff998d`a9255040 : dxgmms2!VidSchiRun_PriorityTable+0x25f20
ffffde03`d1527530 fffff807`2dcded97 : ffff998d`c045c480 fffff807`00000001 ffff998d`c03ea000 005fe07f`b8bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffde03`d1527570 fffff807`2de1d054 : ffff8981`ca9c0180 ffff998d`c045c480 fffff807`2dcded40 d47d97ef`a865971c : nt!PspSystemThreadStartup+0x57
ffffde03`d15275c0 00000000`00000000 : ffffde03`d1528000 ffffde03`d1521000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+17a3b

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.22621.5547

STACK_COMMAND: .process /r /p 0xffff998da91dc040; .thread 0xffff998dc045c480 ; kb

BUCKET_ID_FUNC_OFFSET: 17a3b

FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}

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


And here's the Event Viewer errors and criticals that are about this crash: (just about 5 minutes later after the restart)

Critical: "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

Error: "The previous system shutdown at 6:42:53 AM on ‎7/‎1/‎2025 was unexpected."




All this crashing seems to be due to my NVIDIA driver "nvlddmkm". I also see a lot of high DPC latency due to that same driver as mentioned before. So there's no doubt about this being the main issue currently. However, this seems to persist no matter what I do or how many times I fully clean install my NVIDIA drivers. I am at a loss for what I should do about it.

 

[Turbo27]

Seems like even NVIDIA can't fix it, they provided me with things to do but none of them worked so it probably is faulty hardware and I'd have to send it to get my GPU replaced.