Instalar Steam
iniciar sesión
|
idioma
简体中文 (chino simplificado)
繁體中文 (chino tradicional)
日本語 (japonés)
한국어 (coreano)
ไทย (tailandés)
Български (búlgaro)
Čeština (checo)
Dansk (danés)
Deutsch (alemán)
English (inglés)
Español de Hispanoamérica
Ελληνικά (griego)
Français (francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (húngaro)
Nederlands (holandés)
Norsk (noruego)
Polski (polaco)
Português (Portugués de Portugal)
Português-Brasil (portugués de Brasil)
Română (rumano)
Русский (ruso)
Suomi (finés)
Svenska (sueco)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraniano)
Comunicar un error de traducción
I would like to see the RX 7700 series also have that much, and for the RX 7600 series take on 12 GB, rather than going with 8 GB. But the x60/x600 are seeming more and more like entry level stuff anymore rather than mid-range so who knows.
He knows a lot, though. Like, a lot.
He was probably partially responding to my above suggestion by adding that the IGP your CPU has should give enough performance for testing purposes.
yeah let me just get an overpriced 4090 no problem. PC gaming is a waste of time and money
yeah sure he knows alot giving people useless suggestions like going back to an outdated NVIDIA Driver (Which also didnt work btw) i can tell he has no experience in hardware and PC Building
Yeah monitored it uses about 7GB,s VRAM still crashes so obviously not VRAM related. RTX 3080 is a much stronger GPU than a 3060. Blame NVIDIA for making overpriced junk cards then im not spending another $2000 just for a graphics card wastte of money be outdated by the time they release the 5000 series. Rather buy a console and not deal with headaches
Try an older driver version. Maybe even 457.09.
> Could be an RT (DX12) issue.
For instance, the game 'Control' consistently crashes at the exact same event in the Anchor fight when using the DX12 API (RT). This behaviour has been reported several times since early 2020 and has not been adressed by the published/developer.
The issue is so convoluted, if you look it up, you'll find several, wildly different solutions being suggested, discussed and approved by the community. The common ground is; the issue occurs only under DX12/ RT.
Some of them "solved" the issue by disabling 'Fullscreen optimization', some people "solved" the issue by disabling Windows' Control Flow Guard, others by setting the CPU affinity to 4 threads and still others reported avoiding the crash by reducing their graphics settings to a minimum or even disabling the sound.
So, my question'd be, does the game crash under DX11?
> Recompile shaders for the game, i.e. delete shader cache.
I mean, from what I've gathered...
You've uninstalled and reinstalled drivers.
You've done so using DDU.
You were asked to try with different game settings. No word back from you in if you tried or if it worked.
You were asked to reseat the GPU (or possible try another one). Same as above.
Going on that, trying different driver versions is often good advice for troubleshooting. Again, you're getting upset at not liking the idea of it but nobody is saying you should have to like the idea of it. Troubleshooting is NOT fun. Been there, done that a bit recently. It's SUPER frustrating, even for those of us who get this stuff. And there are things you don't WANT to do because you go "well if it IS that, that's unacceptable anyway so i won't try". But you SHOULD try and do things that rule out factors and narrow down what the cause might be.
Otherwise we're all guessing in the dark.
Same for GeForce Experience. To test this, simply uninstall that fully from the system.
It's easily to reinstall later if ever need it again.
After doing a full wipe with DDU and installing 531.41 ~ and rebooting of course.
Download the latest hotfix 531.58 and install afterwards ~ rebooting when install completes.
Then try your games again and see if this helps.
If not sure where to get 531.58, here...
https://www.guru3d.com/news-story/download-nvidia-releases-hotfix-driver-531-58-to-fix-game-issues-on-geforce-rtx-30-series.html
That's kind of odd. It should have just tossed up a simple error, not a BSoD