In my opinion XP is a deliberate attempt to stop the proliferation of heritage software, or other old programs. Microsoft believes it's time to buy 100% new stuff. And XP is their start on the process of guaranteeing that old programs become totally obsolete and un-runnable.

Right click on 'My Computer' and select 'Properties'. Click on the advanced tab, then the error reporting button. Select the 'Nor Error Reporting' checkbox and turn off the 'But notify me' checkbox. Hit ok. From the system properties window (right click on My Computer and select Properties), stay in the advanced tab, then performance settings, the advanced tab, virtual memory button. Write down your current settings, then select 'no paging file' and press the 'Set' button. Reboot.

Once this is done, make sure the pagefile.sys file doesn't exist in the C:\ directory.

Now just follow the above steps in reverse. Re-enable virtual memory, then error reporting, and reboot. That should fix the problem.

This is only a temporary fix. I have several systems that still have this error pop up. I am still trying to find out what is causing it.

According to rumour the sysdata.xml as far as I'm led to believe is a CPU instruction set glitch between mostly AMD Athlon or Duron processors and Windows XP (of course this is just rumour) - no doubt it will be ironed out in the future.

Windows 98 was OK in it's day but it's now just an ageing old dinosaur that is now in the dark as far as modern-day software is concerned.

The whole licensing debockle demonstrates the true interest of the corporation. The fact that they are designing the os to turn itself off periodically and await a reg-number recharge is way off. Whether the system is in use or in discussion the fact that MS is moving in this direction is abusive.

There isn't a person in the world that would tolerate a car manufacturer selling cars that turns themselves off once a year and await a new reg-code. Even if this was a handy-dandy mechanism to guarantee car maintenance or upgrade or reportage or anything. No one would tolerate that level of post-purchase intrusion.

It is only the fact that Microsoft has a near total monopoly on the os market that allows them to even attempt this bullying of the public.

And the fact is that this presumptive attitude runs very deep in the company and in the code.

There is a 3mb patch now available. Ask your XP system to check for system updates - you'll get a whole lot of security fixes, and this patch on the Microsoft site. In addition, once it's downloaded and installed you will also need to delete the log files from the Windows\Minidump\ folder - it doesn't tell you this as part of the patch.

In the Microsoft Knowledge base, it's Q317277. Here's the url:

Basically they claim that Linksys, NetGear and some SMC NICs have compatibility issues with many of P0G0's games. They said thge only solution that they have found was to use Sun's Java Interpreter.
http://java.sun.com/getjava/download.html

Anyway, I don't mind sending these reports to Microsoft. It gives me the hope (maybe artificial hope) that they will fix it without me having to create the time to do it myself. It's not cost effective.

Side note: I'd like to see a copy of that sysdata.xml file, which seems to disappear before I access it.

The last error report I sent to Microsoft implies that it is an "Error Caused by a Device Driver", but I don't recall any device driver updates being done on my work PC that didn't come directly from Microsoft. I suppose I could check the log of updates for any that were done just prior to March 2002, since Microsoft does track that installation history.

Additional note for "Rik": My PC is a DELL that uses an Intel Pentium 4 CPU, so not all issues of this nature can be rumored as part of an AMD issue.

Of the 3 reports that I have sent to Microsoft, only the first one is at a status of "Researching". Since I have two other similar error report sent for May and July, I figure they may have enough to figure out something, without me spending several weekends doing it myself. If "Researching" turns out to be more than a pacifier, I'll be sure to post the information here.

jon2xxx@hotmail.com since you seem to imply that it might have something to do with Media Player, there was a new security update recently that might address some additional issues. I happened to be using Media Player for just an audio steam (radio) at the time of the last one, and since then have updated it with yesterdays patch. The other months are in question as to if Media Player was even running, but I am sure it's in the dmp file. Does anyone have a interpreter for these dump files?

A few more months and maybe, I'll avoid spending the time finding the issue myself or one of you will send out an automated fix as a virus.

I don't have the time I use to.

Walter

I think that originally, it worked fine, but left you open over the internet. When they fixed it, the "fix" causes the system to crash if any program attempts to access information because the "fix" reads it as and intrusion.

I've been getting an error as well with the sysdata.xml file. My PC is running almost all the time, and sometimes while I'm away, after I come back and turn the screen on, there is the WinXP log-in screen (therefore I know the system must have rebooted). When I log in and Windows comes up, there is the error about Windows recovering from a serious error. When I check the error details, it mentions the sysdata.xml file. When I navigate to Microsoft's site regarding the error, it mentions something about it being a driver problem, but nothing specific yet.

Only in one of the previous posts did I see something mentioned about possibly Java being the problem. Maybe we should all see what we have installed for running Java applets. I recently installed a program that needed the Java 2 environment to be installed, so now it is on my system. I forget which program it was that needed it...Hmmm...I think it was Morpheus 2.0? Anyone else running Morpheus? Or maybe another program that installed Java runtime environment?

I think I'm going to try Sun's Java environment as suggested by that user who tried it with success.

Let me know if anyone else finds a fix.

I tried F8 and also tried to boot up from cd-rom still no luck.

Any other suggestions or advise how to fix this problem.

same error messages..i just bought and built this machine...and I run a business from hom eon it...but oh well..i thought XP would be better...i will give it time..if I still get this message...after a year im back to Win2k

Asus a7v kt133,1Ghz AMD Athlon, 256ram, SB Live, SB Modemblaster (til I upgrade to NIC this weekend) and the part I believe to be the kicker GeForce2 MX400.

Error he's getting is:

C:\WINDOWS\Minidump\Mini092402-05.dmp
C:\DOCUME~1\Home\LOCALS~1\Temp\WER1.tmp.dir00\sysdata.xml

running 1Ghz Athlon 256ram asus A7V GeForce2 MX 400... it´s the same as Rex, it must have something to do with hardware and softwere, i hope microsoft FIX it soon. It happened while experiencing extreme 3d graphics, however some of the games that require 3D accel it works perfectly

Windows XP Pro

What a pain

I have deleted dirs in my documents/temp blah blah, deleted content in windows/minidump and even done all crap to do with the pagefile...nothing works.

I just built my machine three days ago, i have never had this problem ever even with Xp on my old machine, making me think it has to be a hardware issue, new pc is, SOyO Dragron P4X400 Platinum MB, GeForce4 440mx Pny, Ati Tv Tuner VE, 768MB PC 333mhz DDR, Pentium 4 2.53Ghz

Since we had in our Fab a couple of PC that rebootet automatically during test - I investigated the problem and found a solution
The problem was the Graphiccard driver. In generall operation it works, but every once in a while it makes a reboot.

Detailed plan (what to do):

I also get the sysdata.xml error, but only when trying to play games, the game will play for around 1 min and then crash. Did not use to have this problem with my old vodoo 3 2000 card, but got a geforce 4 ti4200 and have the problem (also tried radeon 9000) exact same prob. Thinking it has to do with winxp conflicts or something. However, installed another harddrive and put 2000, and the games work perfectly no errors. So if u know how to do it just have two OS on the computer (preferably on two different HD's).

However, I might just install win98 for the games part and xp for the rest. If anyone knows how to fix this problem on xp please email. I have all the updates for xp so that is not the problem. and i have tried the to do a clean install.

I've had 22 minudump errors since January 2002. First 5 were between January and June but after October 22. I got them 15 in one month! But when I installed new videocard (GF4 MX420) and CPU (Celeron 1.2 Ghz) and updated bios (1006) and all the drivers except SP1, the problem disappeared! So it's definitely a hardware problem. Afterwards I've had 2 errors (December 6. and the other one 15 minutes ago while playing BF1942).

I can't say why the errors started to occur October 22. but it happened twice in 10 minutes at best! I installed SP1 December 19 so it didn't have anything to do with minidumps.

My hardware was:

Asus P3B-F ATX
Intel PIII 500 Mhz
Asus V3800 32MB NVidia Riva TNT2
384 MB

New CPU and motherboard:

Celeron II 1.2 Ghz & PowerLeap PL-iP3/T adapter
Creative GeForce4 MX420

First problem I had:
Caused my Excel97 spreadsheets to open with error message stating copy of this file is already open--
C:\Windows\Minidump\Mini120702-01.dmp
C:\Documents and Settings\sherry\Local Settings\Temp\WER1.tmp.dir00\sysdata.xml

Then this last week had:
my IE-vs6 crash when composing and sending emails on Yahoo--
C:\Documents and Settings\sherry\Local Settings\Temp\WER4.tmp.dir00\appcompat.txt

One file mentioned "superbar.dll" but no such file existed on my system.

I researched for suspect "superbar.dll", IE plug-in registered to The LionsPride Enterprises Inc, whose website I can not access. Again relating to those DAMN popup ads or links.

once it crashed, and the blue screen appeared and posted the binary code with {irl not less or equal) i shut it down and came back a few hours, and loaded windows, but when the desktop came up, the send error report appeared with the dump files and the tmp file listed

what the hell is going on, have a fix, the formatting option is exhusted. have another ?

http://support.microsoft.com/?kbid=329293

i delete them (lots of time) but always problem, i decide to reinstall XP but problem during install (during install memory management i believe).
i decide to take off one memory, but same, i take off the battery of CMOS, and reinstall,
after Hard disk auto detection.
Now it works, install fews games, and software, and during game, RESTART automatic.

really bored, since few days all is back in good way. and i don't know the final answer.

to finish i think (kazaa or emule) could be guilty, too much trojan and virus, when u downloading a lot, and when the problem came i was in download progress.

well i hope it will be a happy end for u too.

C:\WINDOWS\Minidump\Mini042203-01.dmp
C:\DOCUME~2\Owner\LOCALS~1\Temp\WER1.tmp.dir00\sysdata.xml

"C:\WINDOWS\Minidump\Mini043003-01.dmp
C:\DOCUME~1\OWNER~1\LOCALS~1

BCCode : d1 BCP1 : 001 BCP2 : 002 BCP3 : 001
BCP4 : BC949E3C OSVer : 5_1_2600 SP : 1_0 Product : 256_1 \Temp\WER2.tmp.dir00\sysdata.xml"

the faults should not lie on the hardware.

1. Run The Sims Vacation (all previous expansions are also installed).
2. Run SimCity 4.
3. Hit the start button on CommView 3.0 (Packet Sniffer).
4. Install Norton SystemWorks 2003 (about 52% into installation).

I reformatted and installed WinXP, then did thing in this order, usually resetting in between each one:
-installed network driver
-installed sp1
-installed INF drivers
-updated USB 2.0
-installed DX9

C:\WINDOWS\Minidump\Mini043003-01.dmp
C:\DOCUME~1\OWNER~1\LOCALS~1

but i didn't post any bad remarks blaming on xp or pc.. but juz posting my bad experiences sharing with others... by the way..
i own 3 Mac G4 and 4 pcs... dell, Hp and 2 diy pcs.. at home.. and a advertising and printing firm.

and if u ever have the $$ to own these many computers.. u will understand how i feel... when have a problematic pc among the working computers. as this problematic pc is usually use by students for printing their graphic work...

C:/WINNT\Minidump\Mini063003-07.dmp
C:/DOCUME~1\Owner\LOCALS~1\Temp\WER16.tmp.dir00/sysdata.xml

C:\WINDOWS\Minidump\Mini072703-03.dmp
C:\DOCUME~1\yogev1\LOCALS~1\Temp\WER2.tmp.dir00\sysdata.xml

"C:\WINDOWS\Minidump\Mini072703-03.dmp
C:\DOCUME~1\yogev1\LOCALS~1\Temp\WER2.tmp.dir00\sysdata.xml" Refers to the files that will be sent to microsoft if you choose to send your error report. To find out the real error, go to your System configuration in the control panel and uncheck the "Restart on Problem" box.

Once you've done this, you'll receive the blue screen, instead of a reboot, and you can get the actual error. In my case, it comes down to the win32k.sys file. In other searches, I've found that it has to do with either bad memory, or memory clock speed set too high if using an off-brand. This causes overheating (not on the processor, so BIOS doesn't show it), and the system reboots.
Some have fixed this by doing the following:

A) Go to www.memtest86.com and download and run the tool provided there. If errors show up replace your ram

B) Slow down your memory clock speed to a step or 2 below your current setting and see if it happens less often. If so, either leave your clock setting low, position a fan on your memory bridge, or purchase name brand memory that is approved by your MOBO manufacturer.

F-Secure is issuing an international alert on a new network worm known as
Lovsan or Msblast. This worm spreads to Windows servers and workstations as
MSBLAST.EXE, using the well-known RPC hole. The worm will launch an attack
against windowsupdate.com on 16th of August.

"The IT security industry has been waiting in horror for a new major worm to
appear since the RPC/DCOM hole was found on the 16th of July", says Mikko
Hypponen, Director of Anti-Virus Research at F-Secure. "Now it's here".

First sample of this worm was received to F-Secure Anti-Virus Research Labs
at 20:22 GMT on 11th of August, 2003. The worm spreads in a 6176 byte
executable named MSBLAST.EXE to Windows 2000 and Windows XP systems unless
recent Windows security patches have been applied.

The worm will scan addresses in the internet to locate vulnerable Windows
machines. Once found, it will copy itself over and modify the system so the
worm will be executed every time the machine is started. The worm will keep
on replicating from every infected machine.

The Lovsan worm contains these texts:

I just want to say LOVE YOU SAN!!
billy gates why do you make this possible ? Stop making money and fix your
software!!

"There seems to be clear attack routine in the worm", observes Hypponen. On
the 16th of August the worm will start a distributed denial-of-service attack
against the windowsupdate.com server. "If our initial spreading data is
correct and the worm continues to spread fast, the attack might take down the
whole Windows Update service".

QUESTIONS AND ANSWERS ON THE LOVSAN WORM

Q: What makes this worm special?
A: It spreads using the MS03-026 DCOM/RPC hole, "Buffer Overrun In RPC
Interface" - which is one of the most common security holes in the world
right now.

Q: When was it found?
A: First sample of this worm was received to F-Secure Virus Research Labs at
20:22 GMT on 11th of August, 2003.

Q: How does it spread?
A: If an unprotected machine is connected to the internet, the worm will
access it directly with connections to TCP port 135 and infect it remotely.
The user sees nothing.

Q: Which Windows platforms are vulnerable?
A: At least Windows 2000 and Windows XP. It seems that Windows NT 4 and
Windows 2003 might be affected, but this has not yet been confirmed either
way.

Q: Does Microsoft have a patch to close this hole?
A: Yes, at http://www.microsoft.com/technet/security/bulletin/MS03-026.asp

Q: How many machines it could infect?
A: There are potentially tens of millions of machines to infect. For
reference, Slammer worm only had around 100,000 potential SQL servers to
infect and even Code Red had less than 2 million machines IIS web servers.
Then again, most of the workstations with the RPC hole are behind firewalls.

Q: Could it get behind firewalls?
A: In several ways. There might holes in the firewall rules, or people might
make direct unfiltered connections from behind the firewall (with modems or
WLAN). Or somebody might just carry an infected laptop to the company
premises.

Q: Will there be different versions of this worm?
A: Most likely there will be several variants, yes.

Q: What kind of emails does this worm send?
A: None. This is not an email worm. It never sends any emails.

Q: Is this a 'Warhol' worm?
A: No. It has no hitlist and it doesn't spread as fast as for example the
Slammer worm did in February 2003.

Q: Does it do direct damage to infected machines?
A: No. But it does try to take down windowsupdate.com after midnight local
time on 16th of August.

Q: Where is this worm from?
A: We don't know.

Detailed technical description of the worm as well as screenshots are
available in the F-Secure Virus Description Database at
http://www.f-secure.com/v-descs/msblast.shtml

F-Secure Anti-Virus can detect and stop the Lovsan worm. F-Secure Anti-Virus
can be downloaded from http://www.f-secure.com

Free firewall here;

http://www.pcflank.com/sygate.html

Removal tool here

I've just bought a new Dell Latitude laptop, with all the stuff--ATI video card, Pentium 4, 30 gig, and the only things I've loaded onto it other than those of the manufactorer are DivX, MS Office, and a few DVD ripping freewares that I have deleted since.

Now, when trying to watch a DVD in either WinDVD or Windows Media Player, I also get the dreaded app.txt message like the others in this forum. The .avi files work perfectly, but the .vob off the DVDs don't work. The perplexing thing is that they DID work before I installed a program for screen capturing, but even after I removed it, the players don't work for DVDs.

Please reply to my post. I am a student who needs her computer running properly before she leaves for college. Any information is very appreciated.

BCCode : d1 BCP1 : 00 BCP2 : 002 BCP3 : 00

BCP4 : 00 OSVer : 5_1_2600 SP : 1_0 Product : 256_1

Please, if you have a solution send me an email .

Check here for the thread

http://www.annoyances.org/exec/forum/winxp/t1031315908

check here for some kb articles

http://support.microsoft.com/?kbid=329052#appliesto

http://support.microsoft.com/default.aspx?scid=kb;en-us;329293

http://support.microsoft.com/default.aspx?scid=kb;en-us;827663

check here for a document on pre SP2 patches

http://www.gc.peachnet.edu/www/wbeck/Patches/XP_Patches_Ver1.4.doc

I have an MSI motherboard, and I found somewhere that the problem had to do with an old BIOS version. So, I just downloaded the updated BIOS version, and flashed the motherboard with it.

I think the problem lays in that the new XP updates are not compatible with older BIOS versions.

D:\WINDOWS\Minidump\Mini10302-01.dmp
D:\DOCUMENT~1\CHRIST~1.ROO\LOCALS~1\Temp\WER4.tmp.dir00\sysdata.xml

Not with the other blue screen problems, but who knows, maybe they are related.

Has anyone found a solution? If so can you Please give me the steps how to fix it or I'll have no hair left lol

After it reboots it comes up with this error.

Windows has recoved from a serious error

C:\WINDOWS\Minidump\Mini110303-01.dmp
C:\DOCUME~1\LORSYS~1.STU\LOCALS~1\Temp\WER1.tmp.dir00\sysdata.xml

mini*.dmp and sysdata.xml ...etc plus random reboots.

I've tried everything suggested all over the internet, have tried updating all device drivers, tried replacing the graphics card, replaced the Hard Disk, replaced the RAM, have done about a total of 5 fresh installations in winXP. Spent hours changing settings, page file settings, erasing user accounts, creating user accounts... Getting a bit bored of the error now. It's been going on for almost a month and I'm at a loss as to how to diagnose or solve the problem. Everyone suggests something different and it never solves it. I'm an experienced system builder, and have never come across this persistant kind of problem before. I have tried erasing minidump folders, no effect. The CPU and all temps are nominal (around 30^C).. if anyone thinks they know a solution, I'm all ears.

My specs:

AK39N motherboard (shuttle)
Athlon XP2200
512 DDR400 RAM
PNY Verto Deforce4 MX 440 Graphics card
120GB Maxtor HD

As I've said, I've replaced hard disk, graphics card + ram but to no effect, so it seems unlikely to be any of these components. Unless it's some evil combination that's causing the problem. This error occurs on each winXP fresh installation, and also after I update to all hotfixes.

Any help greatly appreciated. Thanks,

1) It's a p4 3Ghz
2) I originally installed Windows XP Home on thesystem and when i was testing it it all came up clear
3) Was placed on site with no problems
4) a Web-Table was purchased and installed,
5) For the installation the system had to be updated to the Pro version, which was supplied, it was after then that the Minidump Error occured.
6) I updated all the ncessary files, all hardware drivers were updated to the latest version and all the service packs were installed.
7) All the hardware in the machine is brand new and has been prior bench-tested for problems

Thanks for everyone who wants to help!!

http://support.microsoft.com/default.aspx?scid=kb;en-us;318023

Anyway, I am no expert in this but I got a suggestion from a friend of mine….
- Buy a new Power Supply - he said…. So I did.
And it actually worked.
But now, after some time (two months or so) the damn problem is back.
I don’t know why.
My friend who gave me this tip hasn’t got the problem again. So maybe it’s just me….!?
So why don’t u guys try it? A new Power Supply is not very expensive. And it may work.

I get the crash and reboot with the error:
C:\WINDOWS\Minidump\Mini10302-01.dmp
C:\DOCUMENT~1\Your Name\LOCALS~1\Temp\WER4.tmp.dir00\sysdata.xml

However it only occurs when Emule is running, and always about 15 minutes after I launch it.
I've tried so many suggestions but no success.

I don't think it's a fault with emule as other ppl have experienced it with various software etc.. Seems to me that there is something in certain software that is causing the problem with XP..

Although i'm now going back to win2k ... by far the easiest solution.

I'v tried to clear all temp files etc..

But the problem still appears. Microsoft says it's a sounddriver problem, and that i must get the updates.
But i'v got al the update from Creative Labs.
(Soundblaster Live 5.1 digital)

So this is not the solution.

I'm going to try to delete the pagefile mentioned earlier.

If anyone has the same problem, i will return here for anwsers.

Thanks..