Windows Forum

Ask something
Discussion Locked

bugcheck on win 2000

0 helpful
8 replies

by a former member

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a small home network running a 2000 domain controller and a 2000 member server. I recently started having my member server begin rebooting due to a bugcheck.
The actual description stated that the computer has rebooted from a bugcheck. Thebugcheck was 0x00000050. Each time the rest of the error code is somewhat different.
I tried to use the dumpchk.exe command to access the memory dump and minidump that was created but it said dumpchk could not initialize the dump file.
I've triedto do a search on Microsoft's knowledge base, but no luck so far. I'll continue to search for answers.
Does anyone have any ideas that I might try?
Thanks

8 replies

by Former member

I forgot to mention in my original question that I also have the latest service pack 3.

by cshill

Don't dismiss that there may be a hardware problem. If the memory is gone then you get the same type of errors. Check that if you can't find a software solution.

by oliviu

1. Modify the BIOS to disable the fast memory check at startup. Eventualy use a 'Burn-Out' memory test program. It may reveal you have a faulty chip.
2. Try to switch the memory cards between computers.
3. If you have an HP printer use the driver from Microsoft.
4. Apply all the patches recommanded. Use BigFix (www.bigfix.com) to check your system for problems and to recommand the necessary patches.
5. If you applied SP2 or SP3 and then you add new components to the system, the SP should berun again.

More details from you may help also.

by Former member

This question was closed by the author

This discussion is closed to new replies.