so far its been couple of hours without BSOD or rez flickering

i haven't tested workshelf or nextart backups yet (nexststart didnt cause any problems before, but its a very light config), but since i clean reinstalled my graphics drivers updated both gom and klite, if it works we wont know what was it

Sometimes figuring out a cause is not as important as actually fixing the problem eheh

Example, the instability I told you about on the new Windows 11 PC. Would I like to know what was actually causing it? Of course. But do I REALLY care? Nah, it was a random thing, so all that matters is that it stopped

In your case memory would be a very likely culprit given the way WritePrivateProfileString works (there's a reason it's slow) and the size of the backup.

well, if its faulty ram, it should still be under warranty so i can get it replaced.

if its something else in my system it'll come back and bite me in the ass sooner or later

if it was gom/codecs thing that were causing the crash, chance of someone else stumbling into the same issues are minor

hmm, interesting, updated gom and codecs, new ram, and still got an error

any ideas?

edit: 2 times in a row with GOM open but paused, then no crash after i closed GOM, then after that not even restart helped, only when i killed some of the apps running did it succed

Doh.

Long shot, but do you have more than one drive?

If so, let's try backing up to another drive. First make a manual backup specifying the new destination folder in the other drive - after this manual backups AND automatic backups should remember the new folder location.

Let's see if you still get an error when backing up into a different drive.

And if that doesn't work we will have to wait until after the official release of v22.5 for me to be able to mess with the backup code. That's not the kind of thing you want to accidentally scr*w up.

good catch, ssd+hdd, and to make it more complicated i used symbolic link to put backup folder which is on hdd in winsteps folder on ssd
gonna test now

edit: Both tests to SSD (C:) and HDD (D:) crashed

Ah well...

Out of curiosity, how long does it usually take there for a backup to finish?

its long, but i couldnt tell you if its about a minute or a couple of minutes. dont think its more than 2 or 3 tho

nextstart is fast, but that isnt supprising its only 64 kb, vs 261 for the workshelf, as i only have few things set up in nextstart

Strange. Backup of WorkShelf here takes less than 15 seconds, and the backup file has a size of 219KB, so not too far off from your 260KB backup.

Maybe the problem is in how long it takes for the backup to finish in your system?

now i had several successful backups in a row, and i guess my mind was playing tricks on me, bc using stopwatch they last about 30 secs. will update when i manage to trigger a crash

So no more crashes, I guess?

they are still happening, but i had some other, offline issues to deal with

they dont seem to be memory related bc i have new ram installed and i stabilised my system. could be something in the registry maybe? i should do a windows reinstall but so not feeling up to it