My Very 1st Blue Screen, now WTF?

[digital_trucker]

Microshaft's 'site has been less than helpful in identifying this, anyone want a try? I got a blue screen and it did a memory dump.

This is what the event viewer says:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000A (0x00000000, 0x00000002, 0x00000001, 0x800683A5). Microsoft Windows 2000 [v15.2195].

Wabbit season! Duck season! AMD season! INTEL season!
Hmmmph--whatever...

 

[Toejam31]

If you get another BSOD, take careful note of all information listed on the screen, and write it down. Don't consider anything you see to be irrelevant ... often, the file that caused the problem will be listed ... although that might not be the case in the Event Viewer.

If it is a driver issue, you may be able to use this tool to locate the problem:

<A HREF="http://support.microsoft.com/default.aspx?scid=kb;EN-US;q244617&GSSNB=1" target="_new">http://support.microsoft.com/default.aspx?scid=kb;EN-US;q244617&GSSNB=1</A>

Without more information about your system, and hearing you describe any recent changes you may have made to the computer, this is the best I can do, for the moment.

You can turn off the memory dumps and the spontaneous restarts by going to:

"My Computer\Properties\Advanced\Startup and Recovery"

and changing your preferences under System Failure. But please be advised, this won't fix the initial problem that caused the error.

Nearly every blue screen I have seen in Win2K has been because of an older driver or a software program that was incompatible with the system. If you can determine the source, you may be able to upgrade the driver or software, and that should take care of the BSOD's.

Toejam31

<font color=red>My Rig:</font color=red> <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=6847" target="_new">http://www.anandtech.com/mysystemrig.html?rigid=6847</A>
____________________________________________________

<font color=purple>"Procrastination on your part does not constitute an emergency on my part."</font color=purple>

 

[digital_trucker]

Actually, it didn't restart itself, it froze. Here's the complete text of the BSOD:

0x0000000A (0x00000000, 0x00000002, 0x00000001, 0x800683A5) Address 800683A5 Base at 80062000, Datestamp 3a24873f - hal.dll

Wabbit season! Duck season! AMD season! INTEL season!
Hmmmph--whatever...

 

[Toejam31]

It sounds like you have a problem with the Hardware Abstraction Layer.

<A HREF="http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q237556" target="_new">http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q237556</A>

Toejam31

<font color=red>My Rig:</font color=red> <A HREF="http://www.anandtech.com/mysystemrig.html?rigid=6847" target="_new">http://www.anandtech.com/mysystemrig.html?rigid=6847</A>
____________________________________________________

<font color=purple>"Procrastination on your part does not constitute an emergency on my part."</font color=purple>