MachineCheck: Regs application pop up in event viewer>system

I get this error message as an application pop up in Event viewer(system) any ideas or does anyone know the answer, there is loads of stuff on the internet about it but no one really seems to know what its for.

This is an intel processor so its not an AMD this but it is a pentium 3 600 pga so is a little outdated.

Event Type:      Information
Event Source:      Application Popup
Event Category:      None
Event ID:      26
Date:            28/08/2004
Time:            16:39:44
User:            N/A
Computer:      HOME-TINY
Description:
Application popup:  : Machine Check: Regs

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 08 00 03 00 6c 00   ......l.
0008: 00 00 00 00 1a 00 00 40   .......@
0010: 00 00 00 00 1a 00 00 40   .......@
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........
0028: 00 00 00 00 00 00 00 00   ........


Any ideas anyone it seems to be something that is happening upon start up and doesnt really  cause any errors just would be interested to dsee if anyone can work out what it is.

Cheers Duncan
Simo1Asked:
Who is Participating?
 
zilantyasCommented:
On your machine you must have a application that relies on DirectX like a game, P2P program, multimedia, etc.  

I had this exact problem before and installing DirectX 9.0b corrected the problem for me.  This update is also included with Windows Update (but not part of the Critical Update).

For the update click here:  http://www.microsoft.com/downloads/details.aspx?FamilyID=141d5f9e-07c1-462a-baef-5eab5c851cf5&displaylang=en  

That should do it.  Good luck.
0
 
Simo1Author Commented:
Any ideas why this would only happen to run on start up I don't have any apps running on startup that would use Direct x, that I am aware of .


I have recently installed service pack 2 and don't get this error message anymore.


I am going to check the other pc at my friends which I have just put service pack 2 on and see if it has stopped that machine getting this message and see if that has cured it.

Cheers for your comment I will let you know.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.