event id 1003

[Jonny]

I recently purchased a new computer and it has windows xp professional installed on it and it will randomly restarts, normally when i am playing a game, and when i log back on it says the system has recovered from a serious error. When i check the error in event viewer it says:

date: the date occured
time: the time occured
source: system
type: error
event ID: 1003
user: N/A
Computer: DAVID


Error code 1000008e, parameter1 c0000005, parameter2 804edcc5, parameter3 f5218a8c, parameter4 00000000.

0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 38 30 34 65 64 63 63 35 804edcc5
0040: 2c 20 66 35 32 31 38 61 , f5218a
0048: 38 63 2c 20 30 30 30 30 8c, 0000
0050: 30 30 30 30 0000




I have no idea what this means or how to rectify it, any help would be grewatly appreciated.

Computer specs are:
AMD Duron 900
GeForce2 mx 400 - latest drivers installed
512mb RAM
Windows XP Pro SP1
Realtek 10MBps Network card - i know its old but it was free!
Onboard AC97 sound
40x Generic CD-ROM
PS/2 mouse and keyboard

[ESALADUANE]

This often means that you have hardware (or drivers) that is incompatible with XP. Have you added or replaced anything to your computer since you bought it? Did you go to Windows Update and download all the Critical or relevant Updates?

[Jonny]

I have the latest drivers from nvidia installed, the mouse, keyboard and network card are just using generic drivers from windows xp driver base, i have installed the latest via 4in1 drivers and the latest update for the onboard sound but im not sure if the sound drivers installed properly.

Even if i do not use the sound drivers but they are installed incorectly can they still cause errors?

You said that it could be a hardware issue as well, could this be the network due to it being so old?

[ESALADUANE]

Yes, the Network card is the first place I'd look for a cause of the problem.

[Jonny]

Thank you, i will purchase a new network card and try that.

Could the sound drivers be causing errors as well? Should i get a new sound card?

When i tried to uninstall the audio drivers it went through the uninstalling process and said that it had finished it sucsessfully but the drivers didnt actually uninstall.

[Jonny]

I have installed a new network and sound card and even bought some new new speakers, i downloaded the new realtek drivers from realtek and installed them but i keep getting the errors and restarts.

What is going on? Can anybody help me please

[FGTH]

Do a search for Error code 1000008e and you'll find a slew of messages from people asking for assistance.

I only counted the problems that were almost identical.

I've noticed that the majority of these errors occurred over the past three months.

Please be aware that this has only been with Windows XP platforms.

SEQUENCE OF MICROSOFT UPDATES FOR XP (PROBLEMS SURFACED AFTER Microsoft's Decemember 19, 2003 issue of Security Update Q811114)

May 01, 2004 Update for Windows Media Player 9 Series (KB837272)
April 13, 2004 Intel network software update released on February 10 2004.
April 13, 2004 Critical Update for IntelliType Pro and IntelliPoint on Windows XP (KB834840)
April 13, 2004 Security Update for Windows XP (KB835732)
April 13, 2004 Security Update for Windows XP (KB828741)
April 13, 2004 Security Update for Windows XP (KB837001)
April 13, 2004 Critical Update for Internet Explorer 6 Service Pack 1 (KB831167)
April 13, 2004 Cumulative Security Update for Outlook Express 6 Service Pack 1 (KB837009)
February 15, 2004 Security Update for Windows XP (KB828028) Automatic update
February 04, 2004 Cumulative Security Update for Internet Explorer 6 Service Pack 1 (KB832894)
January 14, 2004 Security Update for Microsoft Data Access Components (KB832483)
December 19, 2003 Q811114: Security Update (Windows XP or Windows XP Service Pack 1)

SEQUENCE OF REPORTED PROBLEMS
Date: 01-07-04
http://www.computing.net/gaming/wwwboard/forum/768.html

Date: 01-19-04
http://www.mcse.ms/archive57-2004-2-298018.html

Date: 01-24-04
http://www.debugmode.com/forums/post.php?action=reply&fid=23&tid=795&repquote=2938

Date: 02-15-04
http://forums.viaarena.com/messageview.cfm?catid=13&threadid=51878

Date: 03-09-04
http://www.experts-exchange.com/Oper..._20912978.html

Date: 03-21-04
http://forums.anandtech.com/messageview.cfm?catid=34&threadid=1274894&FTVAR_MS GDBTABLE=&STARTPAGE=4

Date: 04-01-04
http://forums.windrivers.com/showthr...&mode=threaded

SUSPECTED CONCLUSION
1) Recent Microsoft updates have bugs causing this common error
2) There's a new virus infecting XP computers
I haven't changed anything other than installing the Microsoft Updates.

I started seeing this error on my computer last week, just after the May 1 Update issued by Microsoft.

Normally this would be assigned to hardware/driver errors, but the high number occurrences exclusively on XP platforms reduces this probability.

I run my computer behind a Firewall with up-to-date virus protection.

Many people have also reported sasser and variants of the sasser infecting their computers with a huge spike in numbers over the last 3 weeks.

One way to slow down sasser is to disable system restore.

Right now, I'm waiting for Microsoft to release a new update.