Help Needed: Blue Screen of Death (Vanity)

1 Oct 2002 | tictoc

[tictoc]

Can a Freeper techie help me out?

My main work PC is on the blink, crashed one day while surfing the net.

I've tried to completely reinstall Windows 2000 in a freshly reformatted system partition. Installation seemed to go well while the screen was blue with white lettering (formating system partition, installing Windows 2000 files from the CD-ROM). Then it changes to a turquoise background. A few times I made it almost all the way through the hardware recognition procedure which follows: but never until completion.

Every time it ends in a Blue Screen of Death but each time with a different error message:

"IRQL_NOT_LESS_OR_EQUAL"

"UNEXPECTED_KERNEL_MODE_TRAP"

"NTFS_FILE_SYSTEM"

"DRIVER_IRQL_NOT_LESS_OR_EQUAL"

"KMODE_EXCEPTION_NOT_HANDLED"

"A device driver has damaged the system memory administration pool"

... and sometimes memory addresses (different each time) and a file name (sometimes ntkrnl or atapi.sys) are indicated.

I've tried everything I know: created four HD floppy disks using MAKEBOOT to boot from drive A:, used the various repair and checking options during initial installation (they work fine), started Windows 2000 in Secure Mode, VGA mode, Debug Mode etc.

It always ends more or less at the same point.

Could this be a faulty RAM chip that only makes itself noticed when "higher memory areas" are accessed? However, during bootup sequence the computer tests the RAM (128 MB) and says "OK".

I've gone into BIOS and disabled all caching and shadowing options, and changed system timings to the slowest values. Nothing seems to help.

Any ideas?

[tictoc]

I'm at my wit's end.

[tacticalogic]

I'd try unplugging all non-essential peripherals, and trying the installation again.

[Mo1]

VOTE THE RATS OUT!!

DONATE TODAY. SUPPORT FREE REPUBLIC

Donate Here By Secure Server

Or mail checks to
FreeRepublic , LLC
PO BOX 9771
FRESNO, CA 93794

or you can use

PayPal at Jimrob@psnw.com
STOP BY AND BUMP THE FUNDRAISER THREAD

[PokeyJoe]

you may have formatted your hard drive, but did you "debug" it.

goto www.bootdisk.com, click on "utilities" on the right side, then scroll down to the section called "cleaners" and you'll find "zap/wipe".

Use zap to reset your hard drive. (it's a little debug script that makes resetting a breeze).

The nice thing about bootdisk, you can download a bootdisk of 98, then install zap/wipe on it. Nice for somebody using 2000 without a copy of win98 available. =)

[AAABEST]

It sounds like a hardware issue.

I've found that persistent blue screens usually wind up being caused by a faulty motherboard, memory or such.

It shouldn't do what it's doing on a fresh install.

Did you reformat the HD? If not, clear your bios and reformat the HD.

[The_Victor]

Look out for incomming Mac rants!

You probably need to go to Micro$loth with this one. Windows internal functions are a mystery even to people as bright as FReepers.

[Blue Screen of Death]

It is not my fault.

[dennisw]

I'll be interested in the answers you get. I had blue screen problems/during re-installion of win2k/ due to a virus. Virus in the boot sector.

If you have a spare hard drive you could try it with your equipement. IOW the problem may reside in your present hard drive.

[Constitution Day]

Help Needed: Blue Screen of Death (Vanity)

Seen this?

[Constitution Day]

Damn, you beat me!! ;)

[w1andsodidwe]

I sounds like a bad hard drive to me.

[lsee]

ROFLOL!!!

[tictoc]

Thanks for the pointer to what appears to be a highly useful site.

I'd like to hold off on wiping the entire disk because I'm hoping to keep the data files in my other partition.

However, if nothing else helps I guess I'll have to bite that bullet :-(

[smith288]

INCOMING!

Linux penguins rumbling to these coordinates!

[dennisw]

If problem is on your HD you might need to do a low level format on it. This procedure is known as writing zeros to the HD. It wipes it clean back to factory fresh. IBM/WestDig/Maxtor have this program on their installation floppy and also available for download on the internet.

[Consort]

What color blue is it?

[tictoc]

Virus in the boot sector.

I have a sneaking suspicion that it might be some such thing.

For what it's worth, the trouble started when I was on Yahoo! Games playing Internet chess. Maybe my opponent somehow reached into my machine via the Java applet to crash it and damage it beyond repair. (I know, I'm paranoid and should seek help.)

[Focault's Pendulum]

(I know, I'm paranoid and should seek help.)

It's always good to know the root causes.

[I_Love_My_Husband]

Tictoc, I'm not a techie (but I'm married to a puter guy), however, whenever I've gotten BSOD it's because I don't have enough RAM. You say you've got 128...imho, it's NOT large enough.

[Falcon4.0]

It might be that you are not setting the partition to NTFS type file system. My source comfirm that you need NTFS partitioning for Windows 2000. Check all your partitions as your system might be trying to load critical files on a non NTFS partition.

[tictoc]

Thank you for the tip but I did choose NTFS, as previously installed, instead of FAT.

[ResistorSister]

Have you ever installed 2000 before?

If yes. Did you install it on the same machine/hard drive that you are trying to setup today?

[AAABEST]

Virus in the boot sector.

You can try going to DOS and typing "FDISK /MBR". Sometimes that will take care of a corrupt master boot record.

[ChadGore]

Linux: The ultimate windows service pack.

[dennisw]

It might be that you are not setting the partition to NTFS type file system. My source comfirm that you need NTFS partitioning for Windows 2000.
________________

I have always installed on NTFS part but I'm pretty sure you can install it on FAT32. There are good reasons for doing this. In dual boot mach. win2k is not visible when you boot to win98 if installed on NFTS.

HOWEVER/// Win2k and it's files are visible from win98 if installed on FAT32 partition.

[tictoc]

Yes to both questions. The BSOD occurred before the present reinstallation attempts.

[FreetheSouth!]

This type of error is most likely a hardware error. Check these items:

Check the CPU fan. By that I mean the fan on the processor itself (a failed CPU fan can cause this type error from excess heat)

Does the BIOS allow you to check voltage output from the power supply? (A power supply with an over/under voltage can cause the system to fail to load and/or run properly)If not, barrow a known good power supply from another system and try loading 2000 again.

Does this motherboard have a VIA chipset? If so, replace with an Intel chipset motherboard. I’ve had no end of trouble with Via boards that would work for a year or more then just go walkabout on me.

[RedBloodedAmerican]

check your fr mail.

[jude24]

That, or delete the partition. Theres a little program out there called "delpart."

2 years ago, Office 2k had an undocumented bug that really trashed my system when the install crashed. Only way I could fix it was to delete the partition and reinstall the OS from scratch.

[tictoc]

You can try going to DOS and typing "FDISK /MBR".

Thank you.

How and when do I get to a DOS prompt? I hit the F8 key during Windows 2000 bootup sequence, attempting to get "Secure Mode with Prompt", but did not get a DOS prompt that way.

[Askel5]

Hysterical ... how long have you been waiting for this thread?!?

[RedBloodedAmerican]

no dos in win2k. use a win98 diskette.

[RedBloodedAmerican]

after that, i suggested he write zeroes to the drive. gateway has a nice utility for doing that.

[tictoc]

I have no doubt that Linux is a superior OS but I am only an intermediate-level computer user not an expert. In addition, I require 100% of M$ Office software and files to work as under Windows for the purpose of being able to exchange files with clients, 99% compatibility is not enough for me.

Have read mixed reviews regarding Windows emulators and/or Star Office and am not willing to take the risk.

[RedBloodedAmerican]

He needs to work on his computer, not toy around with it ;o)

[Askel5]

check your fr mail.

No fair ... not on this thread. Folks will really hate you if they think you have "secret" Microsoft knowledge you can't share with the masses who are saddled with this secondrate also-ran OS.

[RedBloodedAmerican]

I am not sure about the advice I fr mailed, it was not an MS fix, just what I would try if it were me. AAABEST said the first thing, as well, except I said format /mbr. Then write zeroes, and need a win98 diskette (no dos in win2k) Thats about it. Plus a said some mean things about you :) (just kidding)

[w1andsodidwe]

My source comfirm that you need NTFS partitioning for Windows 2000

Not true. You can run with FAT32.

[js1138]

Do you by any chance have an IBM drive?

[tictoc]

Drive C: is MAxtor 7000A/AP series drive. Drive E: is an ancient Seagate but contains no system files. Also have CD drive and a CD/RW drive.

[RedBloodedAmerican]

you can go fat on win2k, but ntfs is more secure.

[js1138]

during bootup sequence the computer tests the RAM (128 MB) and says "OK".

I've seldom seen the boot test find a faulty RAM card. There's a downloadable utility called "TuffTest" that'll wring out the memory.

The last time I had this many errors on boot, it was the hard disk, which had to be low-level formatted. You have to get the disk repair utility from the manufacturer's web site. There's no such thing as a generic low-level format utility.

[RedBloodedAmerican]

http://www.maxtor.com/en/support/downloads/maxblast_plus_ii.htm

[JSpears]

Sounds to me like a hardware problem.....

This can be frustrating...but...

1) Remove as many devices installed in your ISA and PCI slots that are not absolutely needed..ie...one usually only needs a video card....no modem card, no sound card, etc.

2) Perform an install.....if the install is successful, then you have isolated the hardware problem to inteface cards...

3) If the install in 2) was unsuccessful, then there is a
hardware problem not associated with the interface cards...
one can assume that the video card is ok since you can see the install GUIs...

[ResistorSister]

NTFS is preferred.

[FourtySeven]

Mark for home use....I always get good tech things on threads like this...

[Ranxerox]

Try this web site for NT/2000 tips and troubleshooting. Scroll down and look under the "Installation" link. There are some subtle issues which could point you in the right direction, without reformatting your drive.

http://www.ntfaq.com

[absalom01]

I'm afraid that PokeyJoe is right in his advice to you. The error messages are (distressingly familiar and) telling you that the install program does not like your disk controllers and drivers. I don't know enough about the guts of the w2k install program and ntfs, but for some reason it seems that a mere re-format does not remove all traces of the previous install. (This little gem first showed up, to my knowledge, in WinME, and has been added as a part of the Redmond feature set for all time.)

Fixes: 1. try the utility mentioned by PokeyJoe
2. use fdisk or cfdisk supplied on most Linux install disks (no, you don't have to install Linux to ouse it.)
3. If you want to save the data on your other partintions, go to Fry's spend 80 bucks and buy a new disk (or salvage an old disk from a dead box, and "clean it" as above.) Install your OS on the new (or cleaned drive). To keep windows from trying to boot to your old partition, you can:
a) put it on a separate "channel" (ie, ide1 vs ide0) and set your bios accordingly or;
b) jumper the old drive to the "slave" setting and leave it on the current channel.

You can then mount your old partitions and get access to the data.

Repeat once a year.

Or, you can install Linux now, and save yourself the trouble next year ;-)

[Hot Tabasco]

This has happened to me a few times. I would suggest you do what I did. Not knowing an "alt" from an "Esc", I simply went out and bought a new computer each time. I now have a closet full of used computers and a maxed out credit card. Hope nothing happens to thsssssssssssssss....FSSSSSST!!!!......

[brianl703]

If you motherboard allows you to change it, make sure that the CPU voltage is correct. Too low will make it work, but not reliably.