Desktop

Ask something
Discussion Locked

WINDOWS 2000 BLUE SCREEN

0 helpful
20 replies

by filipofrank

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I HAVE BEING USEING WINDOWS 2000PRO A WHILE NOW BUT SADENLY IT HUNGED MY PC AND I RESTART , BUT UT WOUNT BOOT TO DESKTOP, THATS THIS BLUE SCREEN KEEPS APPEARING AND STAKES THERE WOUNT GET TO DESKTOP. PLEASE IS THERE ANY WAY TO RECORVER THE SYSTEM APART FROM FORMATTING THE HDD?. I TRIED TO BOOT TO THE SAVE MODE AND STILL I ALSO TRIED TO BOOT TO THE LAST KNOWN GOOD CONFIGURATION BUT ALL IN VAIN.

20 replies

by ann777

Boot to Recovery Console and at the c: prompt, type chkdsk /r

If that finds bad sectors, then you need to replace the hdd. If it fines and fixes errors, you should be fine afterward.

by deeda

What kind of blue screen error do you get? I know just yesterday I had a 2000 machine that came up with the error 0x0000007b Inacessible boot device. After trying to get into safe mode, safe mode command prompt and last know config. we tried a diagnostic test in the BIOS and came to the conclusion that it was a bad hard drive!
hope that helps some! good luck

by mabl

I have the same problem with the ...00007b error. It started after I had put in a second hard drive and then removed it. Until I get a "real" solution I boot with the last working config. Anyone know how to get rid of the second "phantom" drive (wich I no longer have access to)?

by hughesm1

I had a similar problem on an Optiplex GX260 when I set the parallel port to ECP using DMA3; the HDD used the same DMA channel and caused a conflict on bootup. Since then I changed to parallel port setting back to PS/2 and the machine came up normally. Check in the BIOS that other devices such as CD drives etc. aren't using the same DMA channel as the HDD. If so, set those devices to a lower channel.

by matjaz.demsar

Most useful thing to know with bluescreens is "last known user action". most of bluescreens I got (and I got hundreds so far) were results of new software, wrong drivers and so far only a couple because of failed hardware. when you have the stop code, drop by at microsoft technet and search for its explaination. it's useful most of the time... as far as 0x7b is concerned, it is many times a result of changing controller or drive drivers. i haven't recovered from one yet. i tried lots of things,including modifying registry, startup and drivers ( when you select "safe mode" you get to see which drivers/files get loaded and system often hangs in that phase of startup- when loading storage device drivers. in those cases it's best to make a clean install and a recovery disk;)

This discussion is closed to new replies.