Occasional stuttering and system crashes on Windows 11 with Nvidia RTX4060 Ti
Occasional stuttering and system crashes on Windows 11 with Nvidia RTX4060 Ti
Hello everyone, I’m facing a recurring problem that happens roughly halfway through each boot. Around half of the time, my system freezes and runs extremely slowly. It feels like it’s stuck, with videos stuttering and sound issues. Sometimes it even crashes completely with a BSOD displaying “VIDEO_SCHEDULER_iNTERNAL_ERROR (0x119)”. This affects all components—even basic tasks like opening Notepad become problematic.
This issue started after upgrading to Windows 11 version 23H2, paired with an AMD RTX 4060 Ti graphics card. I bought the GPU specifically for HDR support and also got a 16GB RAM module for CUDA work.
I’ve tried several NVIDIA drivers from older to the latest versions, but nothing works smoothly. After installing Windows 11, I disabled FTPM (it seemed to cause stuttering on my system). I also adjusted HDR settings, turned off monitors, and checked refresh rates—still no improvement. Sometimes lowering the refresh rate helps, but not consistently.
During sleep resumes, the stuttering can disappear temporarily, though it often returns afterward. About 20% of those resumes cause a hidden BSOD followed by a reboot. If the system starts fine, I can play games and use my desktop without trouble for hours. But once it crashes, it’s a total mess.
There’s another odd detail: when stuttering happens, the GPU temperature reading in Task Manager disappears. It could mean the GPU isn’t being accessed properly or the driver didn’t load correctly. It might just be a coincidence.
System specs: AMD Ryzen 3800X, not overclocked, 3.9GHz base, 64GB DDR4 (not DDR3), 2400MHz RAM, Gigabyte B450M DS3H motherboard with RTX4060 Ti 16GB (N406TWF2OC-16GD). No overclocking. Two 4K monitors connected, using a dummy plug for HDR via Sunshine/Moonlight (tried both on and off). I have a Samsung EVO 980 2TB M.2 SSD and a 650W G2 EVGA PSU. Voltage checks during instability showed no issues.
I recorded the problem here: https://imgur.com/a/uuR8IAP
Thanks for your help!
Could you explain why this is a problem? Looking into this now. SSD is 2 months old, but will see if I can get a firmware update. BIOS is probably 'stock'.
They referred to the "DDR3 2400" specification. The AM4 socket supports DDR4, so those 2400 MHz modules were compatible...
Absolutely, that's a solid update. DDR4 is definitely the way to go now, especially since DDR3 is becoming less common in modern PCs. I'll keep an eye on the BIOS changes and let you know if anything shifts. If you don't hear back soon, it might be worth double-checking the system.
Connect to the discussion board via smartphone, tablet, smart television, and more.
I'm a chicken. If I've got no other choice I'll update the BIOS but there's nothing in the changelogs that suggests this will improve the issue and far too many stories of BIOS updates on Gigabyte motherboards bricking the system. I have no other usable spare motherboards for this CPU and this board doesn't have dual BIOS so I'd be desoldering the SPI chip myself and reflashing manually it if it went bad, no good as I need it running tomorrow for work. Just a quick Google shows things like Q-Flash might randomly freeze with some USB drives... "@"BIOS is a steaming pile of garbage, etc. etc... (I just tried to use it and it crashed 3-4 times. Without even getting to the 'flash BIOS' part. Nope! Nope!) Is there anything else to try? I trust Samsung's firmware updater more so than Gigabyte's, so I'll try to run that, though I'm not convinced an SSD issue could explain the graphics corruption I see. (I'll try to grab a screenshot when that next occurs, assuming the framebuffer actually contains that and it isn't somewhere else. If not, phone 'screenshot'.) I'm running the F50 BIOS, which is the stock one. This doesn't include any AMD fTPM fixes if those are relevant but I think they won't be as the fTPM is currently disabled. W11 doesn't seem to have noticed yet, though.
I managed to update the BIOS to F64 and resolved the problem. I had a spare motherboard ready just in case it got damaged, though it didn’t brick it—though the first reboot was a bit unsettling. It’s confusing why they don’t offer a bootloader or recovery option, but I suppose there are good reasons behind it.