I've also secured all the plugs and connectors.ģ. It's as clean as a small old case can get, and the fans are all dust/dirt free. I have spent over 30-45 minutes today opening my case, totally dusting it off using a powerful air-dryer, wiping everything up with damp soft cloth and airing it up.
2440x1440 the talos principle backgrounds full#
GPU: 62~ C degrees full load (30-42 idle)įollowing the FAQ suggestions, and past experience: I am checking with monitor programs and all my main hardware components are running very low, cool temps: I've never experienced this issue with any other game. I deeply appreciate the help, but this just doesn't add up, in my opinion, and here's why:ġ. There's a whole section in the FAQ about it. This is usually caused by underpowering, overheating, bad connectors, or some other hardware problem.
2440x1440 the talos principle backgrounds driver#
This means that the GPU has locked up and afterwards the driver cannot recover it. My GPU is GTX 670, and my screen is an old 1920 x 1200 DELL 24". I can try to roll back into an older driver ,but I am not sure which one and whether it's worth the effort. I am running the latest Nvidia Driver, installed cleanly using DDU software. Today I had the issue happening 3 times in a 15 minutes. Last night I played over 2-3 hours straight on Full Screen with zero issues. It seems the frozen display issue is not related to Windowed Mode afterall. Thing is, this sometimes happens after 50minutes of gameplay, sometimes after a few minutes. Less than a minute from starting the game - Screen frozen, after about 10 seconds, the audio and game keeps running in the backgroud (I can pause, jump, walk - etc) - but the display is frozen. UPDATE: Issue just happened to me in Borderless Mode! Which is different from fullscreen which goes directly to the hardware to take over the entire monitor. It is essentially the same thing - it still runs in a window, just one that covers the entire screen. Yes, you can try borderless, it is likely that it will work just as stable as windowed. It could even be that in full-screen it can reach higher framerate than in windowed, so it perhaps triggers some problem like overheating or undervoltage. The actual cause is either a driver bug, or some subtle hardware error. (Sorry if this is a strange explanation, but I'm trying to keep it simple.) In windowed mode, the screen presentation is left to the windows compositor, so it can usually be more stable in some problematic corner cases. When running in full-screen mode, the driver does more things "hard core" and is more likely to lock up. Ursprünglich geschrieben von AlenL:Well, it is hard to say why, but it from your OP it seemed as if it could be a driver problem.
0 kommentar(er)
