if you've gotten the blue screen, that means it's a windows issue not hardware. you will need to elaborate a lot more plus run a gauntlet of system tests.
generally ntoskrnl errors on blue screens which are coupled with involuntary reboots require immediate virus scans.
it is the core kernel (or deployment workhorse) which initially loads win2k and then calls upon the remainder of the GUI boot process, while continuing to run in the background to support win explorer and app launches.
this is simply the definition.
now what to check for is in the event viewer in admin tools.
sounds like your hardware is quite adequate.
in event viewer you'll see the red x and the time the error occured. this will give you some insight into what happened. you could have a virus, a program you aren't aware may not be compatible with 2k or just a corrupt windows system (general term i know, but then again, this is microsoft we're talking about)
if you can elaborate more on events leading up to the reboot or blue screen, i can help you further.
-Orpheum