Computer shutdown unexpectedly

[Guest]

My computer just shutdown out of the blue and when it did a blue screen came
up. Saying something about driver problems. the Stop # was:

0x0000000A (0x01C24F5F, 0X000000FF, 0X00000000, 0X804D954B)

If anyone knows how to fix this it would very much appreciated. Thanks.

 

[Kelly]

Hi Sam,

By default when WinXP encounters a system failure, it reboots without
warning. The setting that controls this can be changed:

Control Panel/System/Advanced/Settings (Startup & Recovery)/System
Failure/Uncheck-Automatically Restart.

You can use Event Viewer to view and manage the event logs, gather
information about hardware and software problems, and monitor Windows
security events.

To view the event log: Administrative Tools/Event Viewer or
Start/Run/eventvwr.

To review Shutdown Event Tracker data, Open Event Viewer. Click System Log,
scroll to the Event column, and find entries with the number 1075.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q308427

And also:

Go to Start/Run/Msinfo32/Hardware Resources, Components/Problem Devices and
Software Environment/Windows Error Reporting.

Go to Help and Support/Pick a Task (left side)/Use Tools to view.../(left
pane)My Computer Information/(right pane)View the status of my system
hardware and software/Hardware/Update and Troubleshooters.

How to Troubleshoot Hardware and Software Driver Problems
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q322205

Try running the DirectX Tool: Start/Run/Dxdiag, Lower Hardware Acceleration
(Display/Settings/Advanced/Troubleshoot/Hardware Acceleration). Check
System Info for problematic issues: Start/Run/Msinfo32/Hardware Resources
and Components/Problem Devices and Software Environment/Windows Error
Reporting.

Report Error's to Microsoft automatically

Start/Run/gpedit.msc/Computer Configuration/Administrative
Templates/System/Error Reporting. Right click Report Errors/Properties.
Check off Enable and then check off, Do not display links to any MS provided
more information web sites. Apply, ok.

Added Suggestions:

How to Perform a Clean Boot in Windows XP
How to Use Clean Boot Troubleshooting for Windows XP
How to Troubleshoot By Using the Msconfig Utility in Windows XP
http://www.kellys-korner-xp.com/xp_conflicts.htm

How to Recover from a Corrupted Registry that Prevents Windows XP from
Starting
http://support.microsoft.com/default.aspx?scid=KB;en-us;q307545

How to Disable a Service that Prevents Windows XP from Booting
http://support.microsoft.com/support/kb/articles/q244/9/05.asp

Good luck, Sam and keep us posted. )

 

[Steven Litvintchouk]

My computer just shutdown out of the blue and when it did a blue screen came
up. Saying something about driver problems. the Stop # was:

0x0000000A (0x01C24F5F, 0X000000FF, 0X00000000, 0X804D954B)

If anyone knows how to fix this it would very much appreciated. Thanks.

Did you install SP2? Ever since I installed SP2, I've had exactly these
kinds of problems. So I was forced to uninstall it.

 

[S.Sengupta]

http://support.microsoft.com/?kbid=314063
regards,
ssg MS-MVP
pronetworks.org

My c

omputer just shutdown out of the blue and when it did a blue screen came

 

[w_tom]

Various software code is not permitted to access other
memory areas. This protection feature is why NT does not
crash like Windows 9x when bad application software is
loaded. Message suggests that error came from a software
driver. The software was in memory location 804D954B. Either
the memory location (memory chip) was corrupted or the driver
is defective (maybe responding improperly due to peripheral
problem). Assuming the driver's code is OK, then it provides
an idea where in hardware to start running manufacturer's
comprehensive diagnostics. However if you recently loaded a
driver for new or upgraded hardware, then there lies a 'usual
suspect'. Rest of the error message was also important
information. We cannot use it because you did not provide it.

Further information would be obtained from the system
(event) logs and from Device Manager. Often the system was
seeing this problem previously and recorded further
information about this problem. You do want to review those
as well, if for no reason, to understand why we really no long
want XP to stop dead on failure and to learn how to locate
future failures before they become serious.