Recommended Posts

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 by Enthyos
  • Like 1
Link to post
Share on other sites
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.

  • Like 1
Link to post
Share on other sites
Enthyos
3 hours ago, 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.

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.

 

Link to post
Share on other sites
+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?

Link to post
Share on other sites
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?

Link to post
Share on other sites
Enthyos
44 minutes ago, 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?

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

32 minutes ago, 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?

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

 

Link to post
Share on other sites
+Biscuits Brown

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. 

Link to post
Share on other sites
Enthyos
3 hours ago, 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. 

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?

 

Link to post
Share on other sites
+Biscuits Brown

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. 

Link to post
Share on other sites
goretsky

Hello,

 

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

image.png.a00246fe56e979af435f27403cfca79d.png

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

 

Link to post
Share on other sites
Enthyos
2 hours ago, goretsky said:

Hello,

 

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

image.png.a00246fe56e979af435f27403cfca79d.png

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

 

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.

Link to post
Share on other sites
goretsky

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

 

Link to post
Share on other sites
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.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By indospot
      The Framework Laptop is a modular and upgradable laptop coming this summer
      by João Carrasqueira

      Most laptops released nowadays, especially ultrabooks and lightweight form factors in general, tend to be hard to repair or upgrade for the consumer. Not only that but once you buy a laptop, it's very likely you're stuck with the ports and components you got at the start.

      A San Francisco-based startup called Framework is looking to change that with its announcement of the Framework Laptop (via The Verge). This laptop promises to be not only easily repairable and upgradable, but it's also a fairly high-end machine at that. It's also relatively lightweight, weighing 1.3kg and measuring 15.85mm in thickness.

      Out of the box, the Framework Laptop has a 13.5-inch display with 2256x1504 resolution, meaning it has the same 3:2 aspect ratio as Surface devices do. The specs also look promising with Intel's 11th-generation Core processors, along with options for up to 64GB of RAM and 4TB of NVMe storage. There's also a 55Wh battery, a 1080p 60fps webcam with physical switches, Wi-Fi 6E support, and a keyboard with 1.5mm of key travel.

      What makes it stand out, though, is its modularity. Framework designed an "Expansion Card" system, where multiple ports on the laptop can be swapped out for something else. There are four bays for these expansion cards, and users can choose to have a USB Type-C port, USB Type-A, an "ultra-fast" storage drive, HDMI, and so on. These expansions can be swapped out to suit the user's preferences.

      On top of that, most of the internals are also easily replaceable. Storage, RAM, and the Wi-Fi card are all socketed so they can be replaced, but the entire mainboard of the laptop can also be swapped out as new models come out with newer processors for increased performance. Not only that but parts that are heavily used, like the screen and keyboard, are magnetically attached and can be easily replaced by ordering new ones from Framework's website. Each component will have a QR code that lets users order new parts quickly. To cap it all off, Framework says it will provide an open ecosystem so other companies can create their own modules for the laptop and sell them through the Framework Marketplace.

      Customers will have the chance to buy the Framework Laptop as assembled by the company running Windows 10 Home or Pro, or they can order a DIY kit so they can assemble it themselves and install their operating system of choice. In both cases, the laptop will ship with a screwdriver so users can always tinker with it later.

      The goal is ultimately to extend the lifespan of consumer electronics by making it so that whole devices aren't thrown away when only a single component is no longer working well. The concept is generally very similar to the Fairphone 3+ we reviewed last year, but that was a phone, and it was a mid-range device at that, while this seems to be a product anyone might actually want to use.

      The Framework Laptop is promised for release in the summer, and those interested can sign up to learn more as soon as more information is revealed.

    • By Rich Woods
      Windows 10 is getting rid of the 3D Objects folder soon
      by Rich Woods

      One of the really big pushes around Windows 10 has been mixed reality. It started six months ahead of the release of the OS, when Microsoft announced HoloLens and a special version of Windows 10 called Windows Holographic. But that wasn't the end of the company's 3D ambitions, because a couple of years later, it actually added the Windows Mixed Reality shell into the OS.

      Prior to that, the firm introduced an array of VR headsets that would start at $299, a very low price for the time. And around the same time, Microsoft introduced Paint 3D to Windows 10, and at the time, Paint 3D was actually planned to replace Paint.

      Around this time, a folder called 3D Objects was added to the OS, because Microsoft truly believed that consumers would be interested in this stuff. And now, that folder is going away, signaling an end to the giant mixed reality push. The change showed up in yesterday's Windows 10 Insider Preview build (via Windows Latest), which was build 21322.

      Sadly, Microsoft's mixed reality plans never took off, at least from a consumer perspective. In the enterprise, customers have found some important use cases for it, as we've seen from products like HoloLens 2 and newer Windows Mixed Reality headsets that are aimed squarely at businesses. But for things like Paint 3D and using the Windows Mixed Reality shell in Windows 10, it turned out that it didn't have the future with consumers that Microsoft thought it would.

    • By indospot
      AdDuplex: Windows 10 version 20H2 hits 20%, version 2004 still the most used
      by João Carrasqueira



      As we near the end of February, AdDuplex has released its latest monthly report on the usage share of different versions of Windows 10. As always, the report is based on data collected from 5,000 Microsoft Store apps that are using the AdDuplex SDK v.2 or higher. Around 80,000 PCs were surveyed, and the data was collected throughout February 24.

      As more time passes from the release of Windows 10 version 20H2, the update is spreading to more users, and it grew by about 3.2% to reach 20% usage share. That's a nearly identical growth to what we saw last month, but it also means version 20H2 is spreading more slowly than version 1909 did a year ago. In February 2020, that update was already on 22.6% of Windows 10 devices.

      In fact, version 1909 remains ahead of version 20H2 right now, with 26.8% of Windows 10 users still running that version, though this is a significant drop from the 31.2% usage share it had last month. The most used version is still with May 2020 Update, or version 2004, which even increased its usage share from 39.8% to 41.8%.

      Older versions of Windows 10 only saw very slight changes in their usage share. The May 2019 Update (version 1903) dropped from 6.6% to 5.8%, and versions 1809 and 1803 both dropped a decimal point to 1.4% and 1.7%, respectively. Versions prior to that also dropped by 0.1% collectively, with Insiders conversely growing by 0.1% to reach 0.3%.

      Looking at the data trends from the past few years, it's evident that version 20H2 is taking slightly longer to expand its market share than past releases have, but it's not a drastic difference. It should continue to grow steadily until version 21H1 is released in the next couple of months.

    • By Rich Woods
      Microsoft releases Windows 10 build 19042.844 with tons of fixes
      by Rich Woods



      Today, Microsoft is releasing a new cumulative update for those that are on Windows 10 version 20H2 or 2004, which are currently the newest versions of the OS. This is considered to be a "C" week release (even though it's actually the D week), which means that it's optional. When you check for updates in Windows Update, you'll be given the option to take this update.

      The update that you're going to get is KB4601382, and it brings the build number to 19042.844 or 19041.844, depending on if you're on version 20H2 or 2004, respectively. You can manually download it here, and these are the highlights:

      Here's the full list of fixes:

      There's also one other fix, which is exclusive to 20H2:

      There are also two known issues to be aware of:

      Symptoms Workaround System and user certificates might be lost when updating a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices will only be impacted if they have already installed any Latest cumulative update (LCU) released September 16, 2020 or later and then proceed to update to a later version of Windows 10 from media or an installation source which does not have an LCU released October 13, 2020 or later integrated. This primarily happens when managed devices are updated using outdated bundles or media through an update management tool such as Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager. This might also happen when using outdated physical media or ISO images that do not have the latest updates integrated.

      Note Devices using Windows Update for Business or that connect directly to Windows Update are not impacted. Any device connecting to Windows Update should always receive the latest versions of the feature update, including the latest LCU, without any extra steps.

      If you have already encountered this issue on your device, you can mitigate it within the uninstall window by going back to your previous version of Windows using the instructions here. The uninstall window might be 10 or 30 days depending on the configuration of your environment and the version you’re updating to. You will then need to update to the later version of Windows 10 after the issue is resolved in your environment.

      Note Within the uninstall window, you can increase the number of days you have to go back to your previous version of Windows 10 by using the DISM command /Set-OSUninstallWindow. You must make this change before the default uninstall window has lapsed. For more information, see DISM operating system uninstall command-line options.

      We are working on a resolution and will provide updated bundles and refreshed media in the coming weeks.

      When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows the input of Furigana characters, you might not get the correct Furigana characters. You might need to enter the Furigana characters manually.

      Note The affected apps are using the ImmGetCompositionString() function.

      We are working on a resolution and will provide an update in an upcoming release.
      It's worth noting that Windows 10 version 21H1 is coming soon, and that's going to be an enablement package just like 20H2 was. That means that in a few months when 21H1 is out and version 1909 is no longer supported, all supported versions of Windows 10 will actually get the same updates.

      As mentioned earlier, this update will arrive via Windows Update. If you choose not to take it, the fixes will be bundled into next month's Patch Tuesday update.

    • By indospot
      Microsoft releases Windows 10 build 21322 with a bunch of fixes
      by João Carrasqueira



      After a couple of Friday builds in the last two weeks, Microsoft is finally back on its typical Wednesday schedule for new Windows 10 builds in the Dev channel, and today, we're getting build 21322. This build comes from an active development branch that isn't tied to a specific Windows 10 update, but this time, there are no new features.

      Just like most builds, though, there is a list of smaller improvements, fixes, and known issues, which you might want to check out before getting the update. First off, there are some changes, including a reversion of some new touch keyboard features due to some issues:

      Next up, there's a decently long list of fixes, though there are fewer items than we've seen in the last couple of builds:

      Finally, there are some known issues, and the list is still pretty extensive here:

      Microsoft has also noted that some updates have been made to the Feedback Hub so that Insiders can both upvote feedback and add similar feedback to it for all categories. This should help bring each piece of feedback more attention while also providing more details on the problem or suggestion mentioned.

      Since we had a shorter period between build releases this time around, it's not surprising to see fewer changes than usual and no new features at all. As we said at the start, this build isn't tied to a specific Windows 10 feature update, but at the earliest, the features in development now will show up in the 21H2 update, coming in the second half of the year. There's still quite a bit of time for features to be added and changes to be made.