IT Employment

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 -

Isn't plug n play great?

by djent In reply to Contending with BSOD

This is one of the many reasons i choose to stay at NT4 SP6a. I dont find manual driver installation to be problem, in fact I much prefer it. When the hardware config is set it stays till I change it and if I wish to change hardware I can do so at will instead of endless detection loops and HW found prompts. I have found MS PNP to notoriously unreliable, causing more OS crashes then any other single reason. My next upgrade will probably be to Linux given to gross weight of the current MS OS's and EULA baggage. There are some that may call me a fool for not upgrading but I am content with a stable system that works for me instead of me working for it. The same is true for applications, My choice of office suits is Corel, the "features'" added to MS office since 97 are of nominal value to me and I have been a Wordperfect user since V3 that ran from a floppy disk.

Collapse -

Avoiding detection loops

by kcav In reply to Isn't plug n play great?

I wanted to install LINUX on my server, but there was no driver available for the RAID card I have, so I decided to say with Windows. That may only be for a little while longer.

Collapse -

How to prepare Win2k boot floppies?

by kcav In reply to Avoiding detection loops

Problem: Can not reach Repair facility in Windows 2000. When I boot from hdd,Setup stalls on the Screen that says, Starting Windows". When I boot from CDRom, I get Blue Screen that says, device inaccessible. I can boot to DOS. Disk diags say, hard disk is OK. My problem is file corruption, but can not read/write to NTFS disks from DOS. Is there a way to make a Windows 2000 floppy boot disk?

Collapse -

Other things may be the cause.

by LordInfidel In reply to Contending with BSOD

My experience with 2K has been, it is very stable as long as the platform undrneath it is stable.

That being said, The #1 cause of the BSOD in 2k is memory. The slightest bad bit will throw 2k into a tail spin. It is very touchy.

When you get the BSOD, look at the top of it. It will generally tell you what file has created the error.

You may want to do the following.

1- Before removing/replacing/adding, make a backup of the system state (ntbackup/backup/systemstate) this needs to be done to the HDD.

2- Create an ERD (ntbackup/create erd)

3- Install the recovery console
(Put in the 2K cd,open a cmd prompt, cd to %cd-rom%\i386 , type winnt32 /cmdcons press enter, follow the instructions)

Alot of times the file thatis corrupt will be from the os, (NTLoader.dll is a big offender). The recovery console will allow you to get into the file system and replace/add files.

You will need to know the admin U/P to your machine.

Collapse -

This is a test

by kcav In reply to Other things may be the c ...

Two attempts to post a reply failed. This is a tets of the posting mechanism.

Collapse -

Command Console

by kcav In reply to This is a test

You suggested that I setup Command Console, and fix corrupt files from it. That is what I want to do. However, I'm stuck in DOS. From DOS I can't read dynamic disks formatted with NTFS 5.

I downloaded NTFSDOS Pro. When I get it installed o a floppy disk, it is suppose to allow me to read NTFS from DOS. But I have mounted, spnned, and Stripped disks. I don't know if it will work?

Related Discussions

Related Forums