Gpu Driver Or Hardware Issue?

[Enthyos]

Hello folks,

 

Hopefully I am in the right section as this issue appeared after my GPU upgrade from a RTX 2080Ti to RTX 3090.

I am encountering an issue with one my most played games (World of Tanks), the client is crashing into a black screen at random times (sound and other programs still run in the background - can use TeamSpeak for example).

This issue only happens in World of Tanks and is reproductible while in battle, does not happen while in idle or just browsing around in the garage interface. No other game I have tried so far gave me any crash - DX11 or 12.

*Did notice a weird thing that went away after the last driver update (v.461.09), the in-game gamma settings were greyed out - so I thought I’d mention this anyways.

I am at a loss here as I have run out of ideas and I can’t seem to figure out if this is an issue with hardware or is it somehow tied to the way the game works.

The crashes began mid-November and since then I have contacted the player and technical support teams @Wargaming – the company behind World of Tanks creating multiple tickets that lead nowhere so far.

My rig config – pc part picker link here.

Age of the computer (hardware) ranging from new – GPU to 1 and a half years old for most of the system hardware.

OS wise the system was installed around 08/19.

 

Here is a list of things I tried after reading around on the internet on various forums and asking all my tech-savvy friends for help:

§  Updated/Rolled back the GPU drivers using DDU in Safe mode – Not connected to the internet / Windows Drivers Updates off > tried the versions (Studio and Game Ready): 442.74*did not recognize my GPU as expected* - 456.38 - 457.30 - 460.97 (beta) and the latest drivers as well - now running Game Ready 461.09.

§  Made sure my temps are low and there is no overheating - at an ambient temp of roughly 23-4 C degrees - I get to a maximum 71C on GPU and 68/70 CPU side during stress test or even lower temps when just under intense gaming (CoD – Cold War / Metro Exodus for example) - and high 50 C CPU / low 60C on the GPU.

§  Cleaned the registry using CCleaner.

§  Modified the page file system to a higher value and reverted to windows default (32 GB of physical RAM memory should be more than enough- but hey I gave it a shot anyway)

§  Updated the latest chipset drivers from AMD site.

§  Updated the GPU firmware and latest Aorus software.

§  Updated to the latest BIOS (now running F31j)

§  Disabled the XMP Profile in BIOS / and using all stock settings in BIOS.

§  Updated to the latest Creative Sound Blaster sound card drivers

§  Used the windows default recommended sound settings (suggested by the Wargaming Support team)

§  Rebooted my router & network devices for a few minutes (suggested by the Wargaming Support team)

§  In Nvidia Control Panel set the game to use Maximum Performance mode as some user recommended in a similar issue with Apex Legends.

§  Disabled G-Sync + gave it a go with V Sync on and off (Using a G-Sync monitor @ 1440p 165hz)

§  Downclocked my GPU using the Aorus tool to the reference RTX 3090 specs.

§  Enabled and tested Low Latency mode

§  Updated to the latest chipset from the AMD site.

§  Tried running the game with no Antialiasing / Off in NVCP as well.

§  Launched the game in Windowed - Windowed borderless - Fullscreen

§  Lowered the resolution from 1440p to 1080p and 720p

§  Tried to run the game with the lowest graphical settings in all the above resolutions

§  Since the game client has the option – tried both x32/x64 clients

§  Tried Compatibility mode Windows 7 & 8

§  Launched the game in safe mode

§  Used both HD and SD client (lower end machines version)

§  Ran the game integrity check (suggested by the Wargaming Support team)

§  Added the game as a firewall exception (suggested by the Wargaming Support team)

§  Removed the Appdata WoT folder that contains all the game settings (suggested by the Wargaming Support team)

§  Reinstalled the game multiple times

§  Made sure the DirectX Suite is up to date

§  Uninstalled Easy Tune Engine Service/ Team Viewer (as suggested by the Wargaming Support team)

§  Disabled & Uninstalled iCue / Aorus Software / RGB Fusion 2 (suggested by the Wargaming Support team)

§  Clean booted - Windows Default Only

§  Deleted the cache Nvidia Shader Cache

§  Disabled onboard sound in Device Manager

§  Used a TDR Manipulator  and disabled / reenabled it.

§  Updated my Windows 10 to the latest build 20H2

§  Rather recently replaced my PSU unit (end of 2019)

§  Ran a 3D Mark benchmark (Firestrike Demo) while logging with Hwinfo64 * Sensors Only – Log here (3D Mark Results + Hwinfo64 Log) (advised by the user Greybear on Nvidia Forums)

After the latest tests (here) advised by the user Greybear  in my post  on the Nvidia Forums the readings in the log file he points out there is an anomaly, you can see it in the Images in the 12v LOW column "" 0 "" .

Open the Google Drive Link above access the .csv file and scroll across to column LV - MD - see all the 0 entries.... notice that the 12 readings appear in the wrong column on some of the 0 reading in the LV column.

He recommended that I set the RAIL performance to SINGLE RAIL on my PSU.

 

My knowledge on PSU’s is quite limited - Any thoughts on that?

 

*I will redo the benchmarks and log the info as soon as I get home from work. *

After digging for any leads in my crash logs, I found the following information into the game’s crash log and Windows Event logger:

 

Python Log here World of Tanks client:

INFO: [Info] FATAL ERROR: RenderSystemDeviceAccess::genericInterfaceCallFailureHandler - device in unsupported state: The device has been removed.”

 

This seems to be synchronized time stamp wise - with the report from the Windows Event logger that points to the nvlddmkm file stopping to work:

 

" Event id - 1062600691 in Source "nvlddmkm" cannot be found. The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them. The following information is part of the event: \Device\Video3 Graphics Exception on (GPC6, PPC 0)"

I have tried capturing a screenshot right after the black screen crash to see if it pops any information but the screenshots are black.

 

I am aware that this is a long post, but I am still having hope that there is a way to find a fix for this.

Thank you very much for your time and patience.

Any help is highly appreciated.

Edited January 11, 2021 by Enthyos

[Ixion]

Looks like a pretty comprehensive list of things you've tried.

 

The one step which may be missing is a completely clean from scratch driver install (although you mention using Safe mode so may have already done this). Use DDU https://www.techspot.com/drivers/driver/file/information/17830/ to completely remove any old drivers then install 461.09 with default settings.

[Enthyos]

  On 11/01/2021 at 12:03, Ixion said:

Looks like a pretty comprehensive list of things you've tried.

 

The one step which may be missing is a completely clean from scratch driver install (although you mention using Safe mode so may have already done this). Use DDU https://www.techspot.com/drivers/driver/file/information/17830/ to completely remove any old drivers then install 461.09 with default settings.

Expand  

Hello @Ixion, thank you for your reply, i did use DDU to reinstall my drivers.

Unfortunetly that does not seem to help with my issue.

 

[jnelsoninjax]

Honestly I might say that it is the game itself, since you said you have not had any issues with other games. Is the game up to date?

[farmeunit]

I have issues with Rainbow Six from time to time, and it's always seems to coincide with an update for the game.

 

There was an older driver that's been the most reliable.  I see you tried, that, though.  Have you contacted their support and sent them logs?

[Enthyos]

  On 11/01/2021 at 15:26, jnelsoninjax said:

Honestly I might say that it is the game itself, since you said you have not had any issues with other games. Is the game up to date?

Expand  

Yes, and the support team concluded that it's my system that needs to be checked...

  On 11/01/2021 at 15:39, farmeunit said:

I have issues with Rainbow Six from time to time, and it's always seems to coincide with an update for the game.

 

There was an older driver that's been the most reliable.  I see you tried, that, though.  Have you contacted their support and sent them logs?

Expand  

Yes been doing that back and forth ever since it first happened. Had no issues with my 2080Ti before.

 

[+Biscuits Brown MVC]

If the game is that important to you, I'd get a spare SSD, take all the drives out of my computer. Reinstall windows on the spare SSD then install WoT. Nothing else.  If that works, well you know the issue isn't hardware related. If it still fails, you only have a few options and I'd start with putting the 2080Ti back in and test.  If that works either your 3090 is bad or the PSU is sufficient (or just crappy) for that 3090. Your parkpicker link isn't there so we cant see your system. 

[Enthyos]

  On 11/01/2021 at 16:13, Biscuits Brown said:

If the game is that important to you, I'd get a spare SSD, take all the drives out of my computer. Reinstall windows on the spare SSD then install WoT. Nothing else.  If that works, well you know the issue isn't hardware related. If it still fails, you only have a few options and I'd start with putting the 2080Ti back in and test.  If that works either your 3090 is bad or the PSU is sufficient (or just crappy) for that 3090. Your parkpicker link isn't there so we cant see your system. 

Expand  

Hello Biscuits Brown,

Appreciate the support here, i have not thought about doing that, pretty neat ideea.

I will give it a  try and come back with some feedback after the install is done.

Unfortunetly i do not have the 2080ti anymore, but i guess i could try and find someone willing to help me out for further testing near me.

Pc build here. - Was i wrong to go for the Corsair RM1000x psu ?

Much appreciated.

 

In the meantime do you guys have by chance any troubleshooting experience when it comes to  the nvlddmkm.sys error?

 

[+Biscuits Brown MVC]

Since it's only one game causing the issue and the issue is related to the video card driver really points to something the game is doing that is conflicting with your setup. I'm still thinking the fresh install will help isolate this. I'd even go so far as to install windows and NOT install any NVidia drivers. Just let windows install what it wants then install WoT and give it a play. Unless you received a bad PSU, the Corsair should be MORE than sufficient. 

[goretsky Supervisor]

Hello,

 

The PSU should be adequate.  From looking at this photo of it:

the power supply has connectors for three 8-pin PCIe cables.

 

From reading this description of the video card:  https://www.gigabyte.com/us/Graphics-Card/GV-N3090AORUS-X-24GD/sp#sp the video card has connectors for three 8-ping PCIe cables.

 

Have you verified that each of the three separate connectors on the video card has its own cable going to it from the power supply, without any splitters or double-headed cables being used?

 

Regards,

 

Aryeh Goretsky

 

[Enthyos]

  On 12/01/2021 at 13:13, goretsky said:

Hello,

 

The PSU should be adequate.  From looking at this photo of it:

the power supply has connectors for three 8-pin PCIe cables.

 

From reading this description of the video card:  https://www.gigabyte.com/us/Graphics-Card/GV-N3090AORUS-X-24GD/sp#sp the video card has connectors for three 8-ping PCIe cables.

 

Have you verified that each of the three separate connectors on the video card has its own cable going to it from the power supply, without any splitters or double-headed cables being used?

 

Regards,

 

Aryeh Goretsky

 

Expand  

Thank you for your reply Mr.Goretsky

I was aware of this potential issue as i have some experience with building PC's and the limitations of a  8-pin cable, so i went for 3 separate 8-pin PCIe cables.

This weekend i will try and see if  the solution proposed by  Biscuits Brown helps in any way and proceed to a clean install. 

The more i read on the internet the more i fear that i might be one of those plagued by the "black screen with sound + 100% fan  speed RTX series" club.

What bugs me is that so far i do not experience crashing in anything else.

[goretsky Supervisor]

Hello,

My next suggestion would be to check with Gigabyte.  Perhaps there is a known issue specific to the video card with another component in the computer that they are aware of, or you received one from a batch with some faulty component known to be mixed in.

 

Regards,

 

Aryeh Goretsky

 

[Enthyos]

I am currently waiting an answer from Gigabyte, i have watched posts over the internet there does not seem to be any sort of trend going on.

Will post back any official comments on the issue.

Thanks again Aryeh Goretsky.

[Enthyos]

I know it has been a long time since my last post, unfortunately the issue is not fixed and the Gigabyte Support team redirected me to my local vendor whom offered me a refund but not a replacement due to the low stocks so I'd be at a loss given the price hike.

 

Meanwhile after following the recommendations of a fellow user JoeRambo @ Anandtech Forums to use Riva Tunner Statistics Server and even more testing over the past 3 months with the Aorus Engine I did end up having a stable GPU while playing World of Tanks.

While using RTSS I only ended up having partial success, I kept trying to find a solution and ran different clocks and configurations with the Aorus Engine.

Stable settings I am currently using with an alternate profile in Aorus Engine – GPU Clock 1625 / Memory Clock 19502 / Fan Speed Auto / Power Target 100 @ a Target temp of 83 degrees Celsius.

The issue occurred only once since then while playing League of Legends but didn’t reproduce since and i was using this custom World of Tanks profile not the standard Aorus Extreme OC – (GPU Boost 1860Mhz / Memory Clock 19500).

No other games or workload like rendering crashed my GPU, so I decided to keep the card a while more, at least until the availability issues are resolved.

Hopefully this workaround will help somebody else out there.