FreeRepublic , LLC
PO BOX 9771
FRESNO, CA 93794
STOP BY AND BUMP THE FUNDRAISER THREAD
Posted on 10/01/2002 6:33:19 AM PDT by 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?
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. =)
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.
You probably need to go to Micro$loth with this one. Windows internal functions are a mystery even to people as bright as FReepers.
Seen this?
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.)
It's always good to know the root causes.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.