The computer has rebooted from a bugcheck

We have a windows xp computer that will periodically reboot. We adjusted a bios setting that provides more voltage to the computer and have now gone a week without a reboot. The problem occurs periodically. Here are the errors in teh event log.



Event Type:      Information
Event Source:      Save Dump
Event Category:      None
Event ID:      1001
Date:            3/28/2006
Time:            7:11:02 PM
User:            N/A
Computer:      RHONDAPC
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x1000000a (0x00000000, 0x00000002, 0x00000001, 0x8051e106). A dump was saved in: C:\WINDOWS\Minidump\Mini032806-01.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Information
Event Source:      Save Dump
Event Category:      None
Event ID:      1001
Date:            3/18/2006
Time:            10:51:35 AM
User:            N/A
Computer:      RHONDAPC
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x10000050 (0xff308000, 0x00000000, 0xba777ee5, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini031806-01.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Information
Event Source:      Save Dump
Event Category:      None
Event ID:      1001
Date:            3/17/2006
Time:            10:52:30 AM
User:            N/A
Computer:      RHONDAPC
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x10000050 (0xfc80a000, 0x00000000, 0xba777ee5, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini031706-02.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Information
Event Source:      Save Dump
Event Category:      None
Event ID:      1001
Date:            3/17/2006
Time:            10:07:21 AM
User:            N/A
Computer:      RHONDAPC
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x10000050 (0xff28f000, 0x00000000, 0xb818bee5, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini031706-01.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
FASTECHSAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

CallandorCommented:
Have you tried analyzing the minidumps?  See http://www.experts-exchange.com/Operating_Systems/Q_21585874.html

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
speak2abCommented:
Try a repair installaion of your OS (i.e an inplace upgrade). It should stop the problem.
FASTECHSAuthor Commented:
appears to have been a windows update requiring the cpu voltage to be tweaked
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hardware

From novice to tech pro — start learning today.