Instalar o Steam
Iniciar sessão
|
Idioma
简体中文 (Chinês Simplificado)
繁體中文 (Chinês Tradicional)
日本語 (Japonês)
한국어 (Coreano)
ไทย (Tailandês)
Български (Búlgaro)
Čeština (Checo)
Dansk (Dinamarquês)
Deutsch (Alemão)
English (Inglês)
Español-España (Espanhol de Espanha)
Español-Latinoamérica (Espanhol da América Latina)
Ελληνικά (Grego)
Français (Francês)
Italiano (Italiano)
Bahasa Indonesia (Indonésio)
Magyar (Húngaro)
Nederlands (Holandês)
Norsk (Norueguês)
Polski (Polaco)
Português (Brasil)
Română (Romeno)
Русский (Russo)
Suomi (Finlandês)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Relatar problema de tradução
mine is 990pro samsung, and the 2nd is WD black
The M.2 had only one firmware update since I bought it in 2021 so that was at initialization and I also saw an interesting difference running the WD Black in "Game Mode" as opposed to not using the mode.
thx for the new knowledge
I am happy about the progress.
The game sees that Windows unloaded the driver from the application, or it would be better to say that the application was restricted from accessing the graphics interface .
Reasons:
1. Another application took EXCLUSIVE control of the GPU -- this can happen with overlays or older software. It can happen with recording software as well. When overlays or recording software use hardware acceleration they are essentially calling for exclusive use of the GPU if its GPU-based recording. In modern Windows 11, this is not supposed to happen but can still happen if you use older recording software or ones written by developers not following the standard. That includes game devs...
Keep in mind that the average PC has Xbox game bar running (overlay 1), Steam overlay (overlay 2), then their GPU driver overlay (Overlay 3), etc. This actually lowers performance and causes instability.
2. The system unloaded the driver because the application referenced "bad memory." 99.9% of the time a bad RAM overclock. The framebuffer appears to be corrupted or inaccessible.
3. GPU driver reported that it failed to find data (in VRAM) too many times -- linked to bad GPU overclock, including factory ones, or the VRAM really is bad.
^ Most of the time it will be those 3 issues that cause a driver to unload like that. Game Engines are supposed to stop when those issues happen because to them it looks like the hardware might get damaged.
The entire purpose of a operating system is to stop you, the user, from damaging hardware. If you do in fact have a bad OC, it's simply working as intended.
You should always run memory test after changing RAM configuraton. If you see any error in memtest you should change memory configurarion and run again.
Any error in memtest means random crashes in OS.
If it's only one game, it could be the developer at fault. However, if only you have the issue and no one else, then it's likely linked back to something specific about your PC.
If your screen flashes all the time, sometimes mysterious lag moving the mouse, etc. when not gaming or programs crash, then the OC is bad.
You will know the symptoms of a bad OC because the PC will not perform properly elsewhere.
But the easiest way to test is always to simply remove the OC and test. The reason why it is easy is because you can just save the OC profile in BIOS or on disk and swap it back after testing.
You should also write it down just in case something weird happens like the PC won't boot without the OC (I'm not kidding this happens sometimes, though it is a rare issue and usually a sign of a different issue like a configuration one or MB failure/bad BIOS release).
It certainly saves more time than running memtest or compute applications for hours. And the worst part about that is that there could still be an issue with the OC and those applications don't expose it.
Sometimes it really will be only one application that helps you find out the OC is bad, before others down the line do as well. That's because software developers do different practices and methods, and some methods can resist the problems OC issues cause better than others.
it mostly will crash while iam browsing while gaming
for RAM yes i kinda OC it but it's just normal routine like forced DRAM using 1.35volt,so i can get 3200 i did not use DOCP, or should i use DOCP? hell i even created a post for my problem but because the problem was only for that specific game, i blame the game and jus uninstall it lol , and i tried just using 2666mhz stock speed, yet again still crash
for Motherboard, it's a brand new,and max BIOS, and even with, 5minute i playing the game it will crash again so i believe it might be OC problem
for GPU i bring it to the asus they check no problem at all, there is no way they are lying right
still learning how to CPU OC, so i can deselect all those auto OC/ PBO stuff
But, it’s also a good sign it might need more volts to stop the crashes at the higher clock. But, search a safe volt to go up to. I had to do that to a Nv card, it eventually died though. You might be alright though or just prolonging the death either way. Unless maybe a BIOS update addresses it.