General discussion


Contending with BSOD

By kcav ·
I run Windows 2000. Sometimes, usually after changing hardware and rebooting, instead of loading Windows 2000 I get a Blue Screen, or else the Windows Setup routine will freeze before finishing the job of loading Windows 2000. In either case, the only access I have to my system is to boot to DOS from a floppy disk. When I do, I can run disk diagnostics from the A drive. Usually this tells me my disks are physically OK. If not, I know what to do. But most of the time, I find my hard disk drives are electro-mechanically OK. At this point I could run FDISK. But if I do I destroy the contents of my drives. So what I have been doing is, I disconnect all my peripheral devices and remove the PCI cards, then I try to boot my system. Sometimes it loads Windows 2000 from my hard drive. Other times it will not. When this happens, I place my Windows Installation disk in the CD-ROM drive, and boot from it. Then I run Repair. This usually works. Once I am back in Windows 2000 I start puttingboards back-in, one at a time, and rebooting after making each change.

It seems to me if I had device drivers that I could place in a DOS config.sys file, I would have a number of worthwhile alternatives. For example, I could run CHKDSK and Scandisk on my drives. Or maybe I could load event logs into a text editor, and determine which files are corrupt. Then maybe I could replace them from a backup. Or maybe instead of using a text editor I could use a program that reads the physical sectors and find and replace a corrupt program. And I suspect the Master File Table. It seems to me this approach would be quicker and easier than what I have been through.

Has anyone faced a similar problem? What do you do when faced with the BSOD?You don't take boards out do you? Please advise what should I do?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Contending with BSOD

by TheChas In reply to Contending with BSOD

Since it looks like you posted this in both Q&A and the discussion center, I'll repeat my comment to your discussion.

For most hard drives, you do not need a driver for the drive itself.
For SCSI or other drive controllers (except the built-in IDE) you will need the driver for the controller card.

If a hard drive was setup using drive overlay software (EZ-Drive) you need to boot in a manor that allows the overlay program to run.

Since you are running W2K, I assume the drives are NTSF. You need a utility for DOS to access NTSF drives.
Check out

For CD-ROM drivers, check out or
I believe that both have CD-ROM GOD. This is a file that fits on a floppy and has drivers for most CD-ROM drives.

Next, how do you go about changing the hardware? I seldom get blue screens or other issues.

You must remove the old hardware from device manager, then any related software from add/remove programs.
Then shutdown and swap in the new device.

If you are getting regular BSOD with W2K, you have some software or setup problems.

Are all device drivers W2K versions?
Are you running older software?
Are you running serious game software?
Do you have a lot of programs that run in the system tray, or in the backround?
Is your hardware near the minimum system requirements for W2K?
Esspecially RAM and free HDD space!


Collapse -

by kcav In reply to Contending with BSOD

Poster rated this answer.

Collapse -

by kcav In reply to Contending with BSOD

This question was closed by the author

Related Discussions

Related Forums