Weird XP glitch

[Jon P. Inghram]

Running XP Pro SP1, and for the life of me I cannot figure out why when I get a BSOD (due to a buggy demo crashing) I no longer get the "The system has recovered from a serious error" window when it reboots. I've tried it with and without the Error Reporting option on (with critical error notification box checked) and it seems to make no difference. I'm also not seeing the crash logged the in the event viewer, before it'd leave an actual error event also, but now it only leaves the Save Dump event.

If a application crashes in a "normal" manner it pops up the window like it's supposed to and records an application error in the application log just fine.

[VJ]

Strange...
I sometimes get 'the system has recovered from a serious error', but never saw a blue screen before that...
Serious! Occasionally: the system boots, I try to log on, this logon failes, windows resets, boots again and then shows this error.


Jörg

[Jon P. Inghram]

I found a work around for my issue, when it crashes it puts a "dumprep 0 -k" command in the startup list, but for whatever reason it doesn't actually work. If I type the command line in exactly the same as it is in the registry it properly run and puts the window up and also logs the crash in the event log. Windows is so fun to troubleshoot.

[Goc]

Windows is so fun to troubleshoot.

LOL

[leech]

I've seen the "System has recovered from a Serious Error" on several different computers. And this after a complete shutdown and after the computer is not on for a few days, and booted back up it says this. No sign of a crash or anything.

Kind of like last night. Windows just locked up, I wasn't even doing anything on it. Had no programs (except the IM's) and it locked. Then when I reset the computer, it froze when running chkdsk. (I have Fat32 on my drive, so it runs that when it doesn't shut down properly). Then I rebooted yet again, ran chkdsk again and then it worked. Lousy windows. Yup, <i>so</i> fun to troubleshoot...

Leech

[Kurt]

It's usually a memory timing problem. It can _look_ to run fine though. Or you have a bad memory chip on the DIMM.

PS: it's not as if it's always the fault of the system...