A recently installed PC experiences NVIDIA driver problems on Windows 11.
A recently installed PC experiences NVIDIA driver problems on Windows 11.
PC Specs:
cpu -
Intel Core i9-13900K - Core i9 13th Gen Raptor Lake 24-Core
gpu - RTX 4080 (old one was RTX 2080 ti)
motherboard -
ASRock Z790M-ITX WIFI Intel LGA1700 (14th,13th,12th Gen) Mini-ITX Mainboard
psu -
Cooler Master V750 SFX Gold White Edition Full Modular, 750W
ram -
Team Elite Plus 32GB (2 x 16GB) DDR5 5200 (PC5 41600) Desktop Memory Model TPSD532G5200HC42DC01
internal ssd -
MSI SPATIUM M390 M.2 2280 1TB PCIe Gen3 x4, NVMe 1.4 3D NAND Internal Solid State Drive (SSD)
cpu cooler -
DeepCool LT520 Premium Liquid CPU Cooler, 240mm, High-Performance FK120 FDB Fans
Note:
My GPU does use a riser cable to connect to the motherboard.
Question:
I am having WEIRD issues with my PC. Recently I have been having issues installing drivers for my 2080 ti. The nvidia installer always would fail to install and sometimes it would work sometimes not. I then was trying to work in after effects and I was getting weird crashes that occured out of nowhere just randomly. Some games would crash randomly, really only "the finals". After that I started to get crashes in blender and I tried to look at the crash file and it was relating to "EXCEPTION_ACCESS_VIOLATION" some of them were relating to things like "nvgpucomp64.dll". So i decided to completely reinstall windows 11. I did that and the problems persisted. At that point I tried to do all the other trouble shooting things like Memtest, sfc/scannow, DDU and reinstall fresh drivers, CHKDSK, things like that. All came back with no problems, sfc/scan now had some corrupted files but fixed and said all was good. The issue still persisted. So I did another clean install of windows 11 and things got crazy. My system got in a restart cycle that was taking me to the blue screen "why did my pc restart?" screen. I belive the code displayed on screen was "0xc00021a" So at some point i thought okay my GPU must be dying or something... so I got a new gpu a RTX 4080. Installed that and things seemed to be working windows booted up and installed the automatic driver for the gpu "528.24" and it worked. Then i open up my blender project and it imediatly gave me the same "EXCEPTION_ACCESS_VIOLATION" crash. After that I said okay let me update my driver maybe that will help. Nope the driver failed to install the first time and then I belive it installed the second attempt but windows was so glitchy... like glitches in the video, stutters, all sorts of issues. So i restarted the pc and was getting a "video scheduler internal error" based on analyzing the dmp file. The only way I am able to use this graphics card was when I went into safe mode and used DDU to wipe the drivers completely, then restart and let windows intstall it old driver "528.24". But i continue to get crashes in blender that point to "EXCEPTION_ACCESS_VIOLATION". So I am just at a loss here. Could it be windows? Could it be my RAM? Could it be my motherboard? Any ideas? If there is anything I can provide that will help someone please let me know! I really need this to be fixed.
The crashes/bsod from my most recent driver install issue have this in the dmp file:
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: ffffae8bd01aa860
Arg4: ffffb00977791780
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 640
Key : Analysis.Elapsed.mSec
Value: 2403
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: 125
Key : Analysis.Init.Elapsed.mSec
Value: 7313
Key : Analysis.Memory.CommitPeak.Mb
Value: 105
Key : Bugcheck.Code.LegacyAPI
Value: 0x119
Key : Dump.Attributes.AsUlong
Value: 1808
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: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
Key : Failure.Hash
Value: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
Key : Hypervisor.Enlightenments.ValueHex
Value: 1417df84
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
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: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1
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: 21631230
Key : Hypervisor.Flags.ValueHex
Value: 14a10fe
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
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffffae8bd01aa860
BUGCHECK_P4: ffffb00977791780
FILE_IN_CAB: 011224-17734-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffae8b`d01aa6f8 fffff801`55f25685 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffae8b`d01aa860 : nt!KeBugCheckEx
ffffae8b`d01aa700 fffff801`6abf53ba : 00000000`00000000 ffffb009`6fdfe400 ffffb009`6fdfe408 ffffb009`6fdfe410 : watchdog!WdLogSingleEntry5+0x3b45
ffffae8b`d01aa7b0 fffff801`6ac79caa : ffffb009`00000000 ffffb009`77791700 ffffb009`776d2000 ffffb009`77791780 : dxgmms2!VidSchiSendToExecutionQueue+0x1bf4a
ffffae8b`d01aa980 fffff801`6acd56ec : ffffb009`77791780 ffffae8b`d01aaa39 ffffb009`776d2000 fffff801`6abd7bbc : dxgmms2!VidSchiSendToExecutionQueueWithWait+0x5a
ffffae8b`d01aa9b0 fffff801`6acacbb8 : fffff801`73a70000 ffffb009`776a0010 ffffb009`7ab60010 ffffb009`77795820 : dxgmms2!VidSchiSubmitPagingCommand+0x358
ffffae8b`d01aaaa0 fffff801`6ac86bba : 00000000`00000000 fffff801`6ac86af0 ffffb009`776d2000 00000000`00050246 : dxgmms2!VidSchiRun_PriorityTable+0x25fa8
ffffae8b`d01aaaf0 fffff801`4ff07167 : ffffb009`7775a480 fffff801`00000001 ffffb009`776d2000 006fe47f`b19bbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffae8b`d01aab30 fffff801`5001bb94 : ffffc500`9fea2180 ffffb009`7775a480 fffff801`4ff07110 00000000`00000000 : nt!PspSystemThreadStartup+0x57
ffffae8b`d01aab80 00000000`00000000 : ffffae8b`d01ab000 ffffae8b`d01a4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+1bf4a
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.22621.1258
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1bf4a
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
———————————————————-
Update 01:
I tried out new RAM, issues still persist.
I chose to reinstall Windows 11 entirely. You need to rebuild the bootable USB installer to avoid a faulty setup, then set up the OS in offline mode. After installation, manually add drivers for every device using an elevated command—right-click the installer and select Run as Administrator, then connect to the internet so the system updates automatically. Make sure to verify all connections from your power supply to your devices.
Each time I set up Windows, it came as a bootable USB. It felt like I was starting from scratch with a fresh installation. When I install Windows, it’s in offline mode because the WiFi isn’t active until I manually install the “Intel Wireless Lan driver ver:22.150.0.3_G” from the Asrock motherboard site under the support section. I need to do some manual steps when Windows 11 prompts for network setup during installation. Using the terminal, typing “oobe\bypassnro” restarts the setup and lets me skip the network configuration. I haven’t tried installing drivers with elevated privileges yet. Will I have to give that a try? Should I download all the necessary drivers from the Asrock website and install them before Windows 11 updates automatically? Could that really prevent the strange artifacts and stuttering I experience when updating graphics drivers?
The issue turned out to be my riser cable only supported PCIe 3.0 while the motherboard was attempting to use PCIe 4.0. I adjusted the BIOS settings to switch to PCIe 3.0 instead of auto, and after that change everything worked properly! Wow, what a frustrating situation! I tried two different motherboards, two power supplies, and even rebuilt the whole system just to identify the problem. Please don’t be me—I spent a lot of money trying to solve this. If you encounter similar issues, just visit a store for help.