Instale o Steam
iniciar sessão
|
idioma
简体中文 (Chinês simplificado)
繁體中文 (Chinês tradicional)
日本語 (Japonês)
한국어 (Coreano)
ไทย (Tailandês)
Български (Búlgaro)
Čeština (Tcheco)
Dansk (Dinamarquês)
Deutsch (Alemão)
English (Inglês)
Español-España (Espanhol — Espanha)
Español-Latinoamérica (Espanhol — América Latina)
Ελληνικά (Grego)
Français (Francês)
Italiano (Italiano)
Bahasa Indonesia (Indonésio)
Magyar (Húngaro)
Nederlands (Holandês)
Norsk (Norueguês)
Polski (Polonês)
Português (Portugal)
Română (Romeno)
Русский (Russo)
Suomi (Finlandês)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Relatar um problema com a tradução
"PC" as in desktop, with a dedicated desktop card? Or laptop, using either Intel integrated chipset or Nvidia mobile chipset?
Incase of Intel integrated chipset: use the Nvidia mobile chipset.
Incase of Nvidia mobile chipset: downgrade the driver to an older version. Newer drivers have stability problems with lots of laptop hardware and this game taxes your hardware quite a bit. (Mostly due to it being very badly written from a performance and resource usage point of view.)
Do you have the Steam overlay enabled, by chance? If so; disable it and see if you still get these popup dialogs.
If you're looking for the reasoning behind trying this:
"Application has crashed" is usually a generic panic message coming from the top-level thread that started off the process and which houses the message pump that allows the window manager and other OS components to communicate with the process.
The Steam overlay works by injecting a foreign module into the process of the game via process hooking Direct3D, DirectInput and other system APIs. Other than running within the same process container, the overlay is a separate module which would have its own main thread, own message pump etc. (Side track: Infact; if not closed down properly together with the main game module, it could cause a zombie process container to stick around.)
Because these modules run essentially separated, the overlay could also crash (complete with the "Application has crashed" message) separate from the main game. But as long as long as you don't dismiss the dialog, it won't actually cause the entire process container to be torn down and thus it won't cause the game to close on you just yet.
The reason that the entire game would eventually crash anyway after too many of these "application crashes", is because the held up overlay will still use up part of the process's memory space, eating up RAM, and will keep other resources such as allocated VRAM in use as well. Odds are that since the overlay hooks into the game's renderer, eventually one of the crashes of its module would also fatally corrupt the game's memory management and cause it to come crashing down.
Disabling the steam overlay was one of the first things I did back when the first patch went online and I started getting the crashing popups. Thanks for the helpful description about the popups though, really insightful stuff.
yes them