IO Exception : status code = 720112 now Resolve won't start

I was cutting up an edit when I got this error code: "IO Exception : status code = 720112" after exiting I started Resolve again, got the same error code within 5 minutes of editing, and now I can't open Resolve. I saw another post on here saying that they deleted their render cache, but since Resolve won't open I can't delete render cache nor find where it's stored to delete it manually. I've tried everything I could find and it hasn't worked.

Here are the logs:
www(dot)dropbox(dot)com/scl/fo/zcchul8xfdmxbv3x9aa3l/h?dl=0&rlkey=2s7p0orrwcjq6c1ddqs66c8lk

Cache is stored where you set it in Master Settings>Working Folders. Ideally, that should be the first drive you have listed in Preferences>System>Media Storage.

You should know where that is, having set it up manually.

But even if you do know, your only practical option is to delete all the Cache, which isn't always desirable. You can vote for the following feature to make things better.

viewtopic.php?f=33&t=124820

Since I don't remember what I set as the cache folder, my only solution seems to be to delete all the cache, no matter how undesirable...

How do I do that?

Update: Found my CacheClip folder (turns out it was in the default location) and deleted everything in it.

Davinci Resolve still won't start.

[Dwaine Maggart]

The Resolve crash has corrupted your config files.

Your config.dat and .config.data files are bad.

Open File Explorer Options, and on the View tab, enable "Show hidden files, folders and drives".

Also unselect "Hide extensions for known file types".

Then in File Explorer, navigate to this folder:

C:\Users\T\AppData\Roaming\Blackmagic Design\DaVinci Resolve\Preferences

Delete the config.dat, and .config.data files.

Now Resolve should start.

It will recreate the config files with the default starting info. If you had any Preferences modifications made, be sure to reapply those after starting.

If Resolve still doesn't start, send a new Resolve log file.

Thank you! That worked

Is there a way I can know in the future that the config files are corrupted? Or what I did to corrupt them?
Was that what the error code meant?

Thanks again!

[Dwaine Maggart]

I don't know what that error code means. The system had been restarted enough times that the crash logs for the original issue were rotated out.

If Resolve has a similar startup error in the future, you could look at those config files, and if they are 0 size, they are bad.

Gotcha Thank you!