Nvlddmkm \Device\Video3 Error occurred on GPUID: 900

Yes, I'm aware that using Debug sets it to reference specifications.

Forwarding users to either disable GPU Scheduling or enable Debug mode are both better than telling users to use overclock software to manually undervolt their GPU. Most who frequent this page are looking for simple answers, not someone to tell them to use a different app that can have adverse effects if misunderstood.

Regardless, this doesn't change the issue at hand, they are band-aid fixes. The issue is occurring only in specific titles. Stress tests have ignored the problem. If this was a voltage issue, the stress testing would behave identically. There are other posts on this topic but results are on both sides of the fence.

My suggestions to try, to readers:

• If you're on a Laptop, ensure your device is plugged into the wall. Try not using a Surge Protector / extension cable.
• Disable GPU Scheduling within Windows or use Debug Mode in NVCP to force the GPU's Reference Specifications.
• XMP Profile for RAM being enabled can cause the issue, try disabling it in your BIOs.
• If the above has no result, try swapping the RAM / take one out / try new sticks. MemTest may be unreliable.
• As a last resort, pick up a sufficient PSU for your system, maybe a step or two over what you'd think.

When testing RAM and a PSU, keep in mind you can return these to the store if these do not resolve the problem.

To the glorious people on here coming up with the nonsense turning on "debug mode" inside Nvidia control panel """solves"" the issue btw here is WHY:

https://www.nvidia.com/en-us/geforce/forums/geforce-graphics-cards/5/314151/debug-mode/

"DEBUG lowers the factory OC to REFERENCE levels and this also lowers the draw on the PSU. DEBUG tells you something is unstable." Which is the same as lowering the power profile.

HUH. Weird. Hmmmm. How strange.

Same as turning off hardware accelerated GPU scheduling, which lowers the chance it happens under unstable power conditions, because it is a more hardware level access where critical timings are relevant. Tiny little lag in timings because of non stable voltages will cause the issue to happen more frequently. In the end, your PC is unstable because of voltage drops, either main board, GPU, or PSU issue.

Sounds good. I'll do the opposite on my end if it comes to it.

As added to my original post, disabling hardware accelerated GPU scheduling appears to have resolved our issue already. If the crashes occur again, I will try this solution as an alternative.

Moderator note.

mkxy your willingness to help other users in the Microsoft community is much appreciated, however please keep it friendly.

From the Microsoft Community Code of Conduct
Please do:

• Be polite and respectful in your posts, and in your replies to other people.
• Keep it clean. No profanity, obscenity, insulting or bigoted comments please. No name-calling.

Acerbic comments and name calling may result in your profile being suspended or removed.