A few people have emailed me recently for a solution to a serious error that occurs on every boot up that happened to me a few months ago. I have no solution to this, sorry. It was suggested to me that i try to disable synching time with the internet. This did not help. It initially happened when another user of my PC did something so i don't know exact details. This then caused an error every boot up. The same person that caused the initial error, managed to screw something up again and get another error WHILE WORKING ON THE PC - NOT AT BOOT UP. Following this, the boot error disappeared. So my suggestoin to those experiencing this error is to try and reproduce the original error that began your troubles. Sorry i couldn't be more use!

Saw this daily dump and thought I'd chime in ... What is happening is that when "bad" drivers are installed, or an app crashes the system, it creates a "minidump" much like it used to in Win2K. Sometimes, these minidumps are not cleaned off the system at the next reboot. So what happens is System Restore detects that a minidump was created and stops creating System Restore points and alerts the OS about the problem. Hence the error message. The quick fix as I have seen it is: Right click "My Computer" and select Properties. Click on the System Restore tab at the top. Check the box labeled "Turn off System Restore". Click Apply, then OK. Then restart the system. Then go back into that same screen, and uncheck that box. Restart the system. No more error message! :) Hope this helps...

I had this error on bootup (twice) on Tuesday, having last used my PC on Sunday. I don't recall ever seeing any kind of error message on Sunday, which, by the way, is when the MiniDump is date-stamped. On Sunday I installed one or two old (Win95 era) applications, AND did a Windows Update, including the Security fixes from around Feb 13th. Is it likely that something in the Update triggered this saga? Is there any way retrospectively to find, even the .exe, which triggered the original error? My WinXP computer is almost new (~10 hours use?) so there shouldn't have been time for much to go wrong yet?! Andrew "If it ain't broke, don't fix it."