| 5:50 am on Jan 10, 2011 (gmt 0)|
Have you looked to see if there are any third party cloning apps that may have taken the system hostage?
Try running [vssadmin list providers] from a prompt, and if you see any, remove that application.
Bad memory? memtest.
| 4:16 pm on Jan 10, 2011 (gmt 0)|
Thanks, only Microsoft Software Shadow Copy provider V1.0, which is what I would have expected.
I suspect the error orginally occurred over some bad blocks on the HD. I cloned the HD and replaced it with a new one and the same error continues.
| 2:09 am on Jan 11, 2011 (gmt 0)|
1. Go to windows Device Manager
2. Click "view" and select "show hidden devices"
3. Scroll down to "storage volumes"
4. Click on the plus to expand.
5. Click on each one listed and right click and uninstall. (you will get a message on some staying to reboot before it takes effect. Select no until you do them all.)
7. Wait till windows automatically reinstalls devices. Will prompt to reboot again.
| 5:29 pm on Jan 19, 2011 (gmt 0)|
Thanks, sadly, that didn't work.
| 11:02 am on Jan 21, 2011 (gmt 0)|
Programs can crash as a result of bad (or unexpected) data.
It's not a blue screen but my version of Delphi can crash on startup if a configuration file (that it maintains) is dodgy. The first time this happened, it took me a while to figure out what the problem was but the solution was simple - revert to a backup of said dodgy file.
Assuming that a simple "restore" hasn't solved the problem, I would run scandisk first (without with a surface scan) and then look for dodgy files starting with anything that appears oversized.
Logically, if this problem is new but the configuration of the system is old then bad data is the most likely cause. However, it is precisely because of problems of this sort that I only update my computers infrequently (so that I am concious of changes).
| 12:32 pm on Jan 21, 2011 (gmt 0)|
It's VSS that's causing the crash. That's what it's telling me.
If only there was a way to restore VSS without having to do a complete system restore.
| 7:56 pm on Jan 21, 2011 (gmt 0)|
|It's VSS that's causing the crash. That's what it's telling me. |
Not my area of expertise, but I believe that with a BSOD all you can be confident of is that the address at which the error occurs is mapped to the specified module. That can be a lot less than you think, for instance...
Would you immediately associate a BSOD in VFAT.SYS with file encryption software (I won't say which one).
I had a quick look to see if there was anything useful out there with regard to the "bad pool header" error - all I would say is ignore advice to run a registry cleaner. The likelihood of that fixing the problem is vanishingly small. If you use one routinely anyway I suppose running it one more time would do no harm (or as a last resort before a reinstall).