%SystemRoot%\System32\regsvr32 %SystemRoot%
\System32\urlmon.dll
(It's one line with no enter)
and press Enter.

Then, Input

%SystemRoot%\System32\regsvr32 %SystemRoot%\System32\mshtml.dll

and press Enter.

Same way, input

%SystemRoot%\System32\regsvr32 %SystemRoot%\System32\shdocvw.dll

and

%SystemRoot%\System32\regsvr32 %SystemRoot%\System32\browseui.dll

and

%SystemRoot%\System32\regsvr32 %SystemRoot%\System32\msjava.dll

(Each time, you'll see a message box.)

Then, reboot your computer and check it out.
Well, If anyone solve the problem in this method, please inform us.

i put that on 2 notepad and saved it as appcompat, i just dont no whr 2 save it! ne body out thr no? if so plz email me!

Q. I get this message: "C:\WINDOWS\Minidump\Mini080102-01.dmp C:\DOCUME1\user\LOCALS1\Temp\WERD.tmp.dir00\sysdata.xml BCCode : 1008e BCP1 : C005 BCP2 : EEAE21C8 BCP3 : EE68BB84 BCP4 : 00 OSVer : 5_1_2600 SP : 0_0 Product : 768_1." Do you know what it means?

C:\DOCUME~1\Owner\LOCALS~1\Temp\WER250.tmp.dir00\appcompat.txt

IT KILLS/FIXES spyware..and that is what was wrong with mine, it was only happenning with Internet Explorer when I opened more than one instance of it at the same time.

anyways..TRY IT!!

There are several methods to resolve this issue. Follow the instructions in the first section. If the problem is not resolved, proceed to the next
section.

I. Resize the Swap File
When a serious error occurs, by default the system dumps the system state to the swap file for later retrieval. However, it is possible that the swap file is not properly cleaned up and the system thinks that it is rebooting from a crash. To resolve this, you will need to resize the swap file:

1. Click the Start button.
2. Right click the My Computer menu option, and then click Properties on the context menu that appears.
3. Click the Advanced tab, and then click the Settings button in the Performance section. The Performance Options window appears.
4. Click the Advanced tab, and then click the Change button in the Virtual Memory section. The Virtual memory window appears.
5. Click Custom Size, and then record the Initial Size and Maximum Size.
6. Set the Initial Size and Maximum Size to the same value as the amount of RAM that is installed in the system.
7. Click Set and then click OK. The system will advise you to restart the computer.
8. Click OK.
9. Click OK at the Performance Options window. The system prompts you to restart the computer.
10. Click Yes.

After the system has restarted, repeat the above steps to restore the original Initial Size and Maximum Size values for your swap file.

II. Delete the Minidump Files and the Sysdata.xml File

When a serious error occurs, by default the system writes out a miniature memory dump along with an XML description of the system status (which notes the program at fault and other pertinent system data) that can be uploaded to Microsoft. If this data is not correctly closed out, the system may present a Serious Error screen upon boot. To resolve this problem, perform
the following steps:

1. Click the Start button.
2. Right click the My Computer icon, and then click Explore on the context menu that appears.
3. Browse to the c:\Windows\Minidump directory.
4. Delete everything located in this directory.

NOTE : You will need to be able to view hidden and system files and the system should not be hiding protected operating system files.

5. Browse to the c:\Documents and Settings folder.
6. Search for the following file: sysdata.xml file.
7. Delete all instances (you may find more than one) of this file.
8. Click the Start button, click Turn off the computer, and then click Restart.

III. Disable the Automatically Restart setting

This attacks the same class of Serious Errors that resizing the swap file fixes, but it tries to ensure that the errors do not happen beforehand.
However, this does not help to rid the persistent Serious Error message after the fact.

1. Click the Start button.
2. Right click the My Computer icon, and then click Properties on the context menu that appears.
3. Click the Advanced tab and then click the Settings button in the Start-up and Recovery section.
4. Click to remove the check next to Automatically Restart checkbox and then click OK.
5. Click OK. The system will no longer automatically restart after a Serious Error message appears.

IV. Disable Memory Dumps\

This option totally disables memory dumps altogether, which may help fix some persistent Serious Error messages. To disable memory dumps, perform the following steps:

After months of troubleshooting this problem I have finally managed to identify and resolve it on my PC. It was the most frustrating issue I have ever encountered with my PC. Although I knew the problem wasn't hardware based, out of complete frustration, I even went so far as to RMA my mobo (A7N8X), Video card (Radeon 9700), HDD 80 gig Maxtor and memory (Mushkin pc3500 2x512 dual channel) to no avail. I had reformatted my HDD uncountable times, reinstalling everything in an attempt to isolate the occurance. I finally managed to narrow it down and avoid the problem completely.

The issue is caused by a video driver conflict with Windows Media Player 9. It can result after Media Player 9, the codec update or the critical patch that becomes available once you have installed media player 9 is downloaded. I am referring to the 3 seperate Media player downloads off of the Windows update site. I have not be able to narrow it further than that as the error happens sporatically and I have encountered the problem at various points when installing any of the 3 mentioned downloads.

ALSO, if you are using Adaware or some other Spyware removal software, a new Windows Media Player 9 registry entry gets reconized by spyware detection programs. Pay very close attention, as deleting it WILL create the problem, if you haven't already begun experiencing it by simply downloading media player and it's updates.

By avoiding Media Player 9 and all of its updates you can steer clear of the Appcompat.txt issue. That's what I have chosen to do and I have not run into the problem since. If you do download Media Player 9 and use Spyware removal software, DO NOT delete the new registry entry it creates and you should not have any problems.

I hope this helps the many people out there who have been struggling with this issue, like me, for far too long! Please post any successes or failures as I am curious if my resolution to the issue will work for everyones situation.

C..documents\owner\locals~1\temp\werd.tmp.dir00\appcompat.txt.

I tried some of the fixes above but it seems removing the Yahoo companion from add and remove programs actually did the trick.

Okay, lets review what works and what doesn't work in fixing the problem.

Doesn't Work - Removing Yahoo Companion
- Creating a new user
- Reinstalling windows
- Spybot
Work - NOTHING

i found creating a new user acoount did work - providing it is called something other than your original (eg old problem 1 called HOME, create new one called FAMILY)

C:\DOCUME~1\Master\LOCALS~1\Temp\WER53.tmp.dir00\appcompat.txt