Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
Then any further Windows Updates afterwards after the reboot & updating process is all done.
DDU wipe the Drivers & GFE in Safe Mode.
Reboot normally when cleaning done.
Download and install latest for AMD Ryzen Chipset Driver and NVIDIA GPU DCH Drivers from their official websites. Do not install GFE.
When you swap CPUs, reset the BIOS fully and then boot back into BIOS and make your needed changes; such as changes to RAM with regards to XMP/EXPO.
If still have GPU related problems, change these in NVIDIA Control Panel >
> Power Management = Prefer Max Performance
> Shader Cache = Unlimited
Since you are wanting to do Benchmarks, ensure VSync & GSync is all disabled.
Re-enable later or set on a game by game basis. GSync however is something you must set Globally though; either on or off.
On pretty much every build ever since Win10 came out (and it has not changed) I also use TDR Manipulator and raise all of the TDR timeouts because Win10/11 has those set too low by default.
http://www.cpuid.com/softwares/cpu-z.html
cpuz -> validate button -> submit button
it will open a browser, copy the url (address) and paste it here
make sure ram is set to the xmp profile
Sometimes, the issue isn't with a specific part but a combination of them. You have a different motherboard, RAM configuration, and PSU from the other PC it was tested to work in. Start there. The vast drive setup difference might also be a variable.
And if you swap PSUs to test, do not swap the PSU itself without also swapping the cables. Yes, that matters. People have fried parts doing that.
If you're feeling adventurous, you can underclock (not undervolt) the GPU and/or VRAM in increments of 50 MHz or so and see if stability is ever gained. You know the graphics card works in another system though, so it's up to you if you want to spend time on that side of things, or if you want to invest troubleshooting efforts into the other variables in your system.
Per the bold part...
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x133-dpc-watchdog-violation
...As is common, many things that people think are "driver issues" might indeed be common occurrences, but not necessarily issues with the drivers themselves. Hardware faults or other stability issues cascade into a certain driver or software process failing a lot.
Look in these directories...
Windows/LiveKernelReports/WHEA
Windows/LiveKernelReports/WATCHDOG
And look for the presence of dump files that correspond to the time of these issues. WinDbg can be used to open and analyze them.
While I would agree that the issue sounds like it lies with the graphics card somehow (hardware or software) given the symptoms of it, plus the fact it showed up when the graphics card was changed, this is complicated by the fact that it was tested in a second system it seems to work fine there, and it fails with multiple driver versions on the first system. Therefore, this suggests the card itself may be fine and the drivers may also be fine, so it's worth also looking at other variables in the first system.
Besides, you didn't read very well, did you?
I get missing stuff here and there, but... it was mentioned not once, but twice. You're also talking about what to do when swapping CPUs in your first reply and no CPU was ever swapped? Those were different PCs it was tested in.
It's like some of you just skim and don't even read, and then you're so fast to repeat the "just DDU it" or "just reinstall Windows" lines out the gate that you don't even see when it was already attempted...
First off use Group Policy Edit and disable Windows ability to update your drivers, otherwise that might lead to problems during testing while the PC is connected online.
And I wouldn't use the latest NVIDIA Driver unless you have RTX 40 series. Try 555.99 or older.
And again WinOS is plagued by that low TDR timeout issue, lower those values.
Not to mention the evidence that suggest many suffer from performance issues whenever using 23H2 at all. So I would highly suggest Win10 22H2 or go get Win11 24H2
Disable Fast Startup + Hibernation as well.
Just run the benchmark with the GPU set to "Debug" mode within the NVIDIA CP Help menu and check if the benchmark crashes while using the standard model clocks.