This seems to be a widespread problem after doing research myself into it. I am going to attach part of a correspondence with someone else whom emailed me asking how I fixed this problem with the sysdata.xml and minidump .dmp file errors on my end with a lot of help from my gaming buddies, LOL. Maybe it will help others since it doesn't seem that it is being addressed properly by tech support agents. If anything is unclear or you need further help feel free to email me.
"I’d be glad to help if I can. I can explain the problem I was having and tell you how I found my solution. But please keep in mind that it may or may not be the answer you need as well.
I too have Windows XP Pro. I had SP1 and SP2 service packs installed. My husband and I had the computer custom made last October. Ever since that time, the computer was experiencing at least one crash per day, rebooting spontaneously and reporting recoveries from serious errors stating the same Minidump and Sysdata.xml files which seem to pertain to this widespread problem. Just recently, I decided to undertake the task of rooting the problem out because I got sick and tired of dealing with it and losing my work. I Googled anything that had to do with sysdata.xml files and read many others reporting the problem and their speculation as to it’s origins.
First, I checked thoroughly for any sign of a virus. Nope, wasn’t it. Then I updated my nVidia graphic card driver. Something different happened, and yet the problem did not entirely go away. The computer was not rebooting all the way anymore and but the monitor was clicking repeatedly to a black screen. Sometimes 5 or more times in a row. So obviously there was still a problem.
Then I thought maybe the CPU motherboard was overheating. So, I downloaded and installed MotherBoard Monitor 5 to check the temps. Had a false alarm on one sensor that was reading off, but eventually, I came to learn that the CPU was normal and not overheating.
Then I read of another speculation somewhere. One which listed the problem source to be a compatibility issue between Windows XP, SP1, SP2 and graphic cards. Ultimately, I can tell you this is truly where the problem originates.
I knew I had to uninstall SP1 and SP2 out of Windows XP. This brought up other issues of security in regards to Internet Explorer which I used and various other programs. So first, I decided to go with another browser altogether. In my case, Mozilla Firefox. But there are other options you may choose. It’s free and so far I haven’t had any problems really. So, I downloaded that (don’t install yet). Then I closed everything I could and uninstalled SP1 and SP2. I then installed Firefox. It will automatically ask to be the default browser, so I said yes. (might have to reboot here…not sure) If you decide to try my method and uninstall SP1 and SP2, Windows auto update should inform you of some critical updates to install if you have the feature enabled…choose the custom install method and inspect the updates...you should install the critical ones. However, it will also include SP1 and SP2 again within the choices to install. You don’t want to reinstall those, so unmark those two and check the “never ask me this again” option so that it won’t keep reminding you of those two updates.
Then, I uninstalled my current nVidia graphic drivers and totally reinstalled using my install disk. (for compatibility issues, I used the disk even if it’s an older version just to be sure)
For the last part, I went into my WINDOWS program folder. I located the folder called “Minidump”, opened it and deleted all files within. Then I located my temporary user folder (TEMP) and deleted it altogether. (upon reboot, XP will make another TEMP folder) Then rebooted. So far, everything has worked and my computer is acting normally for the first time. No more clicking to black screens or rebooting issues and error reports.
Hopefully, this might help. If you have any other questions, feel free to ask and I’ll do my best to answer. I believe that some of the graphic card drivers have not been updated with a fix that addresses this problem and Microsoft hasn’t seemed to be in any hurry to address it as well from what I've read."
Regards,
Rose
