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
given that you've tried two operating systems, we can rule out existing cache, I don't see any troublesome dll injections in your stack, so we can rule out that too.
windows was probably up to date in at least one of those installations, your driver is good.
disable dlc for SF6 (world tour, specifically, as it's large and has many shaders)
ensure you have ample free space on your C drive for shader caching (at least 50gb).
if it works, and you want to play world tour, re-enable it.
exception C0000005 is an invalid memory address, which is a bit tricky to troubleshoot.
the above helped people crashing during shader compilation, so there could be something not working quite right during that process, world tour seems to have quite a few graphic related problems currently.
edit: if you're overclocking significantly, try turning it down a little, it could also be hardware failures in ram or gpu, or something wrong with one of your run time environments (unlikely given your circumstances), or an issue with SF6 itself.
I appreciate the insight and effort! So thank you.
So I do not play world tour and actually have never had it installed so I can probably rule that out. I only play ranked matches from fighting grounds main menu (or training mode) and sometimes in battle hub. But the crashes have happened in both situatuations.
As far as overclocking the only overclocking present is enabling the XMP profile for my ram to run at its native frequency. I could try disabling the xmp profile and play for an hour and report but. But it's worth noting that I played so much of the demo (probably around 80 hours) and the entirety of the open beta and never had any of these issues. And on top of that, I never had this fatal d3d error until like 4 days after the game had launched but played it very frequently up until that point.
I should note that if it takes a while for these crashes to happen, it's very likely just a memory leak, I get those after a few hours, usually prefaced by some minor graphical artifacts which (usually) gives me time to finish whatever match I'm in and restart the game.
an issue that wasn't present for me in the demo either, and not something us players can address ourselves.
given the differences in our systems I'm afraid I can't help much more than that since I won't be able to reproduce your crash if it's something else.
best of luck friend!
I appreicate it! Someone told me for them disabling XMP worked so I'll give it a shot. At this point I got nothing to lose anyways so might as well try. But yeah it does suck how long it takes for the crash to happen. We'll see. Thanks again!
I have legit tried everything(TdrDelay, Nvidia Debug mode, sfc scan, verify game files, ran stress test, Memtest to eliminate hardware problems, disable XMP/lower timings, etc)
All the usual suggestions. No other game nor stress test(3dMark, Uniengine, OCCT crashes my display driver. Ruling out any hardware problems. Lowering some graphical settings delays this from happening but it still happens every now and then.
Specifically error Fatal D3D Error (25) which crashes the display driver. If you go to event viewer you will see "The description for Event ID 0 from source nvlddmkm cannot be found" for Nvidia GPUs. As far as I know there is no concrete fix for this. Also you can have an 8 hour session and nothing happens then next time it crashes within 30 mins lol. Just seems very random or like some type of leak with VRAM/GPU which would make sense why lowering graphical settings gives you more time.
I have a 1080TI 11GB
Have you found a fix other than lowering graphical settings?
EDIT: also turned off steam overlay
If anyone can give me a fix or some insight I'd be eternally grateful!
Upgrading my GPU from a 10 series (GTX 1080) to an RTX 3070 fixed the problem. I haven't had crashes since I made this post (around the time I upgraded).
But I also did a full reinstall of windows as well as going from win 10 to windows 11. and in that time also getting a new boot drive instead of my old SSD. I do believe it was a hardware problem. If your game is still crashing with an RTX card, try installing the game on a separate drive if you can? Other than that, this issue I felt was unsolvable cause I had tried everything.