Jay,
In order to determine the root cause of the Stop 0xA, you will need to use a
debugger to analyze the dump file.
You can download our "Debugging Tools for Windows" package from the
following web site:
http://www.microsoft.com/whdc/ddk/de...g/default.mspx
After you install the debugger (Windbg), you will need to configure the
symbol server location:
http://www.microsoft.com/whdc/ddk/de...g/symbols.mspx
For more information on how to troubleshoot Stop 0xAs, please refer to the
following article:
165863 Troubleshooting "Stop 0x0A" Messages in Windows 2000 and Windows NT
http://support.microsoft.com/?id=165863
Jeff Patterson
Microsoft Support
This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.
"Jay Erdman" <(E-Mail Removed)> wrote in message
news:03b101c3a309$23990590$(E-Mail Removed)...
> Computer using Windows 2000 reboots without warning.
> Event log shows Event ID 1001. Source: Save Dump
> Gives following message:
>
> The computer has rebooted from a budcheck. The bugcheck
> was: 0x0000000a (0xfffffffc, 0x00000001,0x80464b66).
> Microsoft Windows 2000 [v15.2195]. A dump was save in
> C:\WINNT\Minidump\Mini110403-03.dmp.
>
> Does anyone know how to fix this problem? Thanks.