Larian Studios Forums Divinity - Original Sin Divinity Original Sin - Beta Beta 1.0.231.0 - Win7 BSOD/save file corruption?

Neat little trick happened after my first hour messing with the beta. After quitting the game, my Win7 system crashed to a blue screen, and I was forced to restart Windows. Yet when I now restart D:OS, even though my save file made just before quitting still appears intact in the correct hard drive location (C:\Users\(My Name)\My Documents\Larian Studios\Divinity Original Sin\Savegames), the save no longer appears in the in-game save list, and the main menu "Continue" and "Load" options are grayed out. I played several alpha versions for many hours on this same computer, and never had this problem.

The Windows Event Viewer recorded two errors around the time of the problem:
1) (Steam Client Service) Error: Failed to poke open firewall
2) Faulting application name: EoCApp.exe, version: 1.0.231.0, time stamp: 0x533d56c9;
Faulting module name: EoCApp.exe, version: 1.0.231.0, time stamp: 0x533d56c9;
Exception code: 0xc0000005

Has anyone had a similar problem, and/or could give some advice? Thanks!

So the latest save game folder appears to have the same files, of about the same sizes, as your other saves? The save folder should contain a Global.lsb file, SaveName.bmp (not essential) and SaveName.lsb, as well as a LevelCache folder containing several lsb files for specific regions (ie CharacterCreation, Cyseal, Homestead).

Was the latest save folder renamed, or marked as read-only or anything like that after the BSOD? If the SaveName folder isn't the same as the SaveName.lsb file in the folder it will not show up in the save.

Thanks Raze - yes, all those files are in the save folder, which is about 15MB; I'd only been playing for about an hour when I made the save. The file names haven't changed and are consistent, but the folder/files (and in fact every folder/file on my C: drive) are marked as "Read-only." But I'm not sure whether or not they were marked as such before the problem as well, and whenever I try to "unset read-only" attribute for the save folders/files (or any other folders/files), the attribute is simply re-applied when I re-check the folder properties afterwards.

(This also didn't work: http://support.microsoft.com/kb/256614)

OK, I started a new save, which I can now load without problems both before and after restarting D:OS - and the new save folder is also marked as "Read-only," so that's apparently not the problem. I guess the earlier Win7 BSOD crash somehow corrupted the old save?

It's pretty frustrating, since I didn't experience such crashes with any alpha version, and I don't want to spend too much time in the beta if I'm just going to end up corrupting all my save files like this later on.

You need to just have files selected if you want to check if any are marked as read-only. Since Vista, I think, MS change the behaviour so that if a folder is selected, the Properties will just put a square in the attribute box, indicating that didn't check the folder contents. You can click the box to cycle through read-only (checkmark), not read-only (empty) and unknown (solid square), and for the first 2, have the option to apply the changes to the folder, subfolders and files.

If you still have the old save, could you zip it and email it to supportdos@larian.com, with a description of the problem? Someone said yesterday that mailbox was full, so you could use the general support address instead: support@larian.com.
The D:OS support tool would create a report.zip file containing system info, crash reports and your saved games (to reduce the file size you could delete the new saves and any old working saves from the zip, since they are not relevant to the problem).

By the way, a blue screen is often caused by more serious issues (e.g. hardware or faulty drivers) than bugs/crashes in some application.

If it happens again, you might want to find out more about the bluescreen's error code - there are bluescreen viewers that can be used to read out the files Windows creates in such a case and you can check the error codes in lists that are available online.

Thanks El Zoido - it hasn't happened again (and I haven't seen anyone else here with BSOD issues), so I'll probably need to look into my setup if it does.

And Raze - thanks for the info on Larian support. I actually did start messing with the D:OS Analysis Tool, so if it happens again and I can't find another solution to the file corruption, I'll give it a shot.