"Disk access failed repeatedly." Related to "Found an application state backup" notification

[HadToRegister]

OK, so since the Disk access failed repeatedly" message has come back, I've found that it will continue to come back every couple of minutes UNTIL you Dismiss the Blue "Found an application state backup RESTORE/DELETE" notification by clicking the White X in the notification. Once you do that, it will go away, so apparently that Disk Access Problem has something to do with backing up the state of Vortex, by either being unable to write a backup, or overwrite a backup, or reading a backup or something else, but it will keep attempting whatever it's doing until you shut down the Notification by clicking the X.

[Guest deleted34304850]

nice find. that is a really weird and odd error message if it's related to the application state. i mean, if it's a problem with the backup as you suggest, then thats an issue with the backup not your entire disk!

[Tannin42]

Error messages like these occur in response to an error from the operating system which then unfortunately get filtered through the middleware we're using (node.js in our case but it wouldn't be fundamentally different with Qt or .NET) and the information value can only diminish for every layer the message goes through.

But fundamentally: Vortex doesn't do some weird tests that might fail and then decide it can't write, it literally just goes "Windows, give me the content of file x" or "Windows, write data y to file x" and that then fails with an error message that hopefully explains why.

Meaning that if Vortex tells you a disk access failed, that is a fact. The reason/cause might be muddied, by the middleware or Vortex itself but not the fact that Vortex can't access a file it's supposed to be able to access (the error message you're reporting implies a hardware or filesystem defect but I'm not willing to bet that's actually the case).

 

Further, I'm pretty sure what you're describing as the solution is a red herring. The notification is a fire-and-forget message we generate once on startup, it being there does not trigger any further disk accesses, dismissing it only makes the notification disappear until the next time you start Vortex. I don't see how it could have any further effect.

[HadToRegister]

Error messages like these occur in response to an error from the operating system which then unfortunately get filtered through the middleware we're using (node.js in our case but it wouldn't be fundamentally different with Qt or .NET) and the information value can only diminish for every layer the message goes through.

But fundamentally: Vortex doesn't do some weird tests that might fail and then decide it can't write, it literally just goes "Windows, give me the content of file x" or "Windows, write data y to file x" and that then fails with an error message that hopefully explains why.

Meaning that if Vortex tells you a disk access failed, that is a fact. The reason/cause might be muddied, by the middleware or Vortex itself but not the fact that Vortex can't access a file it's supposed to be able to access (the error message you're reporting implies a hardware or filesystem defect but I'm not willing to bet that's actually the case).

 

Further, I'm pretty sure what you're describing as the solution is a red herring. The notification is a fire-and-forget message we generate once on startup, it being there does not trigger any further disk accesses, dismissing it only makes the notification disappear until the next time you start Vortex. I don't see how it could have any further effect.

 

 

I've reported this problem before. as I've said, I have tested my disk multiple times with ChkDsk, and PerfectDisk, both found ZERO errors, also S.M.A.R.T. reports that my disks are fine.

When I get errors like this I will also download multiple disk checking programs and use them "Just in case", the problem might be with the program, however my disk have ZERO ERRORS.

 

So, why is it, that Disk Checking Utilities running on Windows, are reporting what Windows says about my Disks, as being perfectly fine, but only Vortex with Middleware is reporting one of them as faulty?

 

SOMEBODY has to be reporting incorrectly.

[Guest deleted34304850]

Error messages like these occur in response to an error from the operating system which then unfortunately get filtered through the middleware we're using (node.js in our case but it wouldn't be fundamentally different with Qt or .NET) and the information value can only diminish for every layer the message goes through.

But fundamentally: Vortex doesn't do some weird tests that might fail and then decide it can't write, it literally just goes "Windows, give me the content of file x" or "Windows, write data y to file x" and that then fails with an error message that hopefully explains why.

Meaning that if Vortex tells you a disk access failed, that is a fact. The reason/cause might be muddied, by the middleware or Vortex itself but not the fact that Vortex can't access a file it's supposed to be able to access (the error message you're reporting implies a hardware or filesystem defect but I'm not willing to bet that's actually the case).

 

Further, I'm pretty sure what you're describing as the solution is a red herring. The notification is a fire-and-forget message we generate once on startup, it being there does not trigger any further disk accesses, dismissing it only makes the notification disappear until the next time you start Vortex. I don't see how it could have any further effect.

i'd be troubled by any layer of software that interprets an error accessing a file (read or write) that then reports the access issue as a possible/potiential complete disk failure.

in terms of the middleware being used, is this considered to be working as designed?

[HadToRegister]

Yes, I'm necroing, but I didn't want to keep making thread after thread addressing this.

This message ("Disk access failed repeatedly." Related to "Found an application state backup"), does not show up when managing the Witcher 3, just Skyrim AE so far.

More importantly, the PC this that Vortex is installed, is the same PC I regularly do Video and Audio editing in a DAW and Video Editing Software, using Reaper, Sound Forge, Acid Pro, Vegas Pro, et al, and My Audio and Video, renders, records, and plays back just fine, so this leads me to the conclusion that there is something in the Base Package of whatever Vortex is built on, that is having a problem, because Vortex is the only program that complains about this. Even chkdsk and other disk tools don't complain.

Because if the error message was right, I would be experiencing Lost Frames, Audio Dropouts, Rendering Errors and a myriad of other things in my Audio and Video Projects which sometimes rely on multiple Virtual Instruments STREAMING From and Back to the Hard Drives, which would make any Audio and Video work impossible.

[Guest deleted34304850]

hello mate,

since tannin moved on there's been no dev interaction here. i guess they don't come here any more?

so, the only road left to you is on github, where i sent so many error reports and improvement suggestions that simply disappeared. i don't know if anyone will see this, or respond about it.

i still find it strange that there is software out there that interprets a failed file access as a potential hard disk failure. that's just nuts.