Jump to content

Forums Announcement

Read-Only Mode for Announcements & Changelogs

Dear Survivors, we'd like to inform you that this forum will transition to read-only mode. From now on, it will serve exclusively as a platform for official announcements and changelogs.

For all community discussions, debates, and engagement, we encourage you to join us on our social media platforms: Discord, Twitter/X, Facebook.

Thank you for being a valued part of our community. We look forward to connecting with you on our other channels!

Stay safe out there,
Your DayZ Team

fisH2o

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

1 Neutral

About fisH2o

  • Rank
    On the Coast
  1. fisH2o

    Crash to destkop, game minimizes

    UPDATE: Got to a point where it looked and acted like it was going to crash, froze for a few seconds and then carried on as normal. So I have not crashed as of yet after setting my geforce drivers to version 295.73.
  2. fisH2o

    Crash to destkop, game minimizes

    Played for 30 minutes without a crash after installing these drivers. May be a short term fix.....
  3. fisH2o

    Crash to destkop, game minimizes

    Having the same issue. Have a GTX 560ti. Only started happening after the last patch. When I get minimized I get a kernel error saying that the display driver has failed and restarted successfully or something along those lines. It doesn't stay up for very long. Read some stuff on the Geforce forums. Seems like it could be cause by a number of things. Overheating, insufficient PSU, bad drivers, different watts / volts, etc. Seems like its not just the graphics card but a combination of stuff that causes "TDRs". Some sorta of windows thing that was supposed to get rid of having so many Blue Screens of Death. Read about some people fixing the issue by using old Geforce drivers. Specifically 295.73. Going to try this now. I will report back. https://forums.geforce.com/default/topic/520920/display-driver-has-stopped-responding-but-has-recovered-kernel-error-/?offset=2
×