Jump to content

Beard

Support Team
  • Posts

    4624
  • Joined

Posts posted by Beard

  1. Yes, it seems to point to nvoglv being the cause of the crash, which is the Nvidia OpenGL driver. I can only recommend reinstalling your drivers fully to see if that helps fix the issue, you can see about similar problems in the links below with other OpenGL apps;

    https://forums.developer.nvidia.com/t/bug-random-nvoglv64-dll-crash-after-driver-update/185612
    https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Faulting-module-nvoglv64-dll-when-launching-AutoCAD.html

  2. The logs seem to point to it being a graphics driver issue, but just to confirm that, can you check the Windows Reliability monitor for any ProjectZomboid application crashes there? If you do find any, can you share a screenshot of the Technical Details section so we can check the errors that show up there?

    https://www.computerworld.com/article/3575353/troubleshooting-windows-10-with-reliability-monitor.html

    https://www.dell.com/support/kbdoc/sk-sk/000178177/how-to-use-windows-reliability-monitor-to-identify-software-issues

  3. The game itself cannot cause system crashes, since a system crash is always either hardware related or a problem with the Windows. You should see a blue screen with information about the crash when it happens.

    Can you check the Windows Reliability monitor for any ProjectZomboid application or any hardware crashes there? If you do find any, can you share a screenshot of the Technical Details section so we can check the errors that show up there?


    https://www.computerworld.com/article/3575353/troubleshooting-windows-10-with-reliability-monitor.html

    https://www.dell.com/support/kbdoc/sk-sk/000178177/how-to-use-windows-reliability-monitor-to-identify-software-issues

  4. Your PC does not fulfill the minimum requirements for the game as written on the Steam page.
    I can only recommend switching to the older "Legacy" game versions by going to your Steam Library > Right click Project Zomboid > Properties > Betas > Select the Legacy 40 or older versions.

  5. The issue seems to be caused by the mods you have enabled, but they do not show sufficient logs to point to the specific mods.

    Are you able to create a new settings configuration with the same mods and start the server there? If not, I can only recommend removing the other mods to see which one causes the issue.

  6. Mac computers with the latest M1-M3 chips are not supported as written on the Steam page, issues will be expected on them, such as various resolution problems.
    However, you could try fixing them by either setting the game to Windowed or Borderless modes.

    Additionally, you may need to go to your Mac Display settings and make sure the Display Scaling is disabled there, since that can cause the issues with scaling the game.

  7. Could you try sharing the game logs again in that case? Just to confirm that the drivers have been updated successfully.

    Additionally, can you check the Windows Reliability monitor for any ProjectZomboid application crashes there? If you do find any, can you share a screenshot of the Technical Details section so we can check the errors that show up there?

    https://www.computerworld.com/article/3575353/troubleshooting-windows-10-with-reliability-monitor.html

    https://www.dell.com/support/kbdoc/sk-sk/000178177/how-to-use-windows-reliability-monitor-to-identify-software-issues

  8. There is a problem with your game install, as if there were files there that should not be there, such as an opengl file, which should not be in the game folder.
    I would either recommend removing thsoe files if you put them there, or if you did not, do a full game reinstall
    First, uninstall the game, then go to "Steam\steamapps\common\ProjectZomboid" and make sure there are no leftover files or folders there.
    Then just install the game again and see if that helps.

  9. 9 hours ago, uliii said:

    I tried disconecting the Joystick from the computer, i opened the game and it worked. but when i clicked to start it crashed.

    That is progress, can you in that case share the console.txt file found in the C:\Users\YourUserName\Zomboid folder? Or you can screenshot the alternate launch window again, the window should stay open even if the game crashes and show the error messages at the end.

    Additionally, new err_pid files might be created after this crash when you click to start, which would be different from the ones you already shared, since the issue is different now. Therefore, can you share these new files as well?

  10. Try going to the C:\Users\YourUserName\Zomboid folder and edit the options.ini file with a text editor.

    In that file, edit the fullscreen=true line to fullscreen=false

    Then try launching the game again.

    This is to test if the issue happens in Windowed mode as well.

  11. This makes the problem more clear, it seems to be a permission issue on your PC preventing the game to write in the User/Zomboid folder.
    You can fix this by moving the Zomboid location elsewhere.

    Try going to your Steam Library > Right click Project Zomboid > Properties > Set Launch Options > Type -cachedir=C:\Zomboid > Start the game

  12. It is likely not going to come in the near future. Though, does your app not allow using any of the default Controller buttons? In this case you should be able to use one of the R1 or L1 buttons to select the window and then use the X button to close it.

  13. Thanks, this is fairly unusual, I would recommend you go to the Zomboid folder and delete everything there, including the Saves folder, though you can instead move that folder somewhere else if you have any old saves you want to keep around.

    After that, try verifying your game files.
    Steam Library > Right-click Project Zomboid > Properties > Local Files > Verify Local Files

    Then just try starting the game again, It should fix the Savefile error.

  14. Unfortunately, this logs file is empty, I recommend first starting a game and loading into a new save, then reproducing the issue after that, and then finally shutting down the game. This should create the new logs file which would contain the logs from that game, you have to send the logs after that.

×
×
  • Create New...