IT Employment

General discussion


Contending with BSOD

By kcav ·
Normally, 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 harddisk 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 putting boards 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, 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 physicalsectors 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

Related Discussions

Related Forums