#Event 1000/1005 Crash Error

7 messages · Page 1 of 1 (latest)

viral blaze
#

One of the more interesting errors I've received from a game crash. Tried on both a NVME and SSD, same PC.

*Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Balatro.exe because of this error.

Program: Balatro.exe
File:

The error value is listed in the Additional Data section.
User Action

  1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
  2. If the file still cannot be accessed and
    • It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
    • It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
  3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
  4. If the problem persists, restore the file from a backup copy.
  5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 0x0*

image.png
viral blaze
next flax
#

I had the same issue - and figured it's an issue on my side not on Balatro side.
For me it was an OSD Driver that was broken and tried to inject himself into my games.
nvoglv64.dll is a openGL Driver of Nvidia - some say it might be a possible fix to reinstall the driver completely.

viral blaze
#

did you solve the error?? any recommendations? I am on a fresh windows 11 installation with freshly updated geforce drivers. @next flax

#

i'm not entirely sure it's an "us" issue if it's something happening on a brand new build

next flax
#

So for me what i did is figure out what exactly is causing it - via the .dll file and googled my ass off until i found a solution.
My solution was to deactivate Nvidias Overlay and the Overlay i have from another software.

viral blaze
#

I did NOT have any overlay activate or running - neither nvidia nor game bar nor anything similar.