I've tried the above techniques and still no resolution. All I could do was disable error reporting, not the fix I was hoping for.

0

I booted up into safe mode and changed back to the Microsoft XP driver for my video card as in response 3 (I had updated to the Geoforce unsigned driver) and then carried out the procedure as in response 5. Thanks all!!

0

Hello, I have also the same problem... and also a MSI GeForce 2 MX200. I downloaded the latest drivers, but that had no effect. (I already suspected it was my videocard giving problems) I've tried a lot, but when I really carry out what to do to solve this problem, I let you know! Cheers - ;>

0

You might want to try the last know good configuration of windows xp. To do that you should press the F8 key as your system is starting up. Then choose the option for the last know good configuration. If that does not work then boot into windows. Go to start, then run and then type msconfig. Go over to the startup tab.Uncheck everything listed. Then click apply or okay. Close the window. Your computer will ask you to restart. Click restart. Your system will restart. It will say your are using selective startup. Click don't show me this again and then click okay. Still if that does not work. Then you may want to run the repair tool for windows xp. To do this you should boot to the windows xp cd. It will say press enter to install windows now. Then press R to repair. Press R. This process will take several minutes. Let it finish. Take out the windows xp cd and then restart the system. Windows will startup. If it works you shouldn't get the message. Unfortunately,if that step doesn't work then you need to format and reinstall windows from the xp cd.

0

Just a note for the record.. I'm having the same erors in: C:\WINDOWS\Minidump\Mini012202-01.dmp C:\DOCUME~1\Robert\LOCALS~1\Temp\WER2.tmp.dir00\sysdata.xml I also have a GeForce 2 MX200, but i believe this one is a card that was originally in a dell or a gateway. Last install of XP i had up for about 4 months with no probs, but i did upgrade my motherboard from a asus p5b to a asus a7v133 with an athlon xp1600 (haven't flashed BIOS, system reports CPU as a athlon 1.06ghz, don't know if this is correct- the 1600 in athlon 1600 doesn't indicate cpu speed, just a model, haven't had a chance to look up actual cpu speed to see if it's right. My first suspect is video card drivers, if i remember will send a msg here when i update.. Also possible the OEM geforce 2 is some kinda weird piece of junk crap that was specially made for the one computer.. Companies will do anything to save a dime.. What happened was i was playing counterstrike. I refreshed the server list (to get new ping times from the servers) and the system froze with no error, mouse cursor didn't move. I hit ctrl/escape to get back to windows and i saw a blue screen flash with an error, but too fast to read since the system shutdown completely (computer shut off) before i could read. Don't know where that blue screen error is stored in XP..)

0

BTW anyone having this prob install officeXP just after installing winXP? Just ran into others who did.. Also, found this possible fix via deja.. What I did, and posted in another newsgroup yesterday (which two people have emailed me back and said worked for them too) is the following - arrived at more by guesswork and hope than science ;-) * Deleted all the files in the c:\windows\minidump subdirectory * Deleted the whole c:\docume~1\(your logon)\local~1\temp\werl.tm.dir00\ directory (ie the file(s) *and* the directory itself. * Defragmented the hard drive (someone else said this helped; if anyone can explain why, I'd love to know, but maybe just do it because I did and the problem went away). * Disabled hibernation (probably nothing to do with the problem, but I did it anyway) * Ensured the (ACPI) power switch on the PC was configured to do a shutdown (rather than Ask, Standby, etc). * Shut down the PC via the power switch (rather than start menu) - it still seems to do the same controlled shutdown when you have a "soft" power switch anyway. After all this, I rebooted and - for the first time in quite a few days - *didn't* get the spurious "recovered from a serious error" message, and I haven't had it again since. I'm guessing that one of the above actions (or some mysterious combination of them) caused some flag to be cleared which tells the XP shutdown/startup process whether it's doing a "good" one or a "crash/restart" one. I don't yet know how this mechanism works, but the above stuff has definitely worked for at least 3 people who had been suffering from this same problem with XP reporting an error when there wasn't one. [aside: Doing this is way better than turning off that critical error notification/reporting stuff, as I've seen some people recommending and saying they've done. You *do* want to be told when a real crash has happened, and you _do_ want to send the dumps to Microsoft or the problems aren't going to get logged, tallied-up and fixed.]

0

lol, i figured it out....that error report is for an error in internet explorer...i dunno how to fix that but what i did was i went into error reporting and added internet explorer to the list of programs for xp to not report on....i think my stuff will be fine....but microsoft needs to fix the prob with internet explorer

0