reinstalling win2k...

[cmdavid]

nobody in operating system forum is helpin me out so i figured id post here where I know somebody is knowledgeable to help...

I can't boot into win2k cause of some stop error.. is there anyway to reinstall it w/out deleting everything on that drive?? here's how my computers set up..

c: winME

e: win2k...

ive got setup booting off the win2k cd in dos mode but I don't see an option to re-install win2k.. ive tried all the fix methods (recvovery, emergency repair) and they don't fix the problem.. I don't know DOS well enough to remove the files that are causing the stop error, which I can't really see because the stop error screen only shows for a split second before my computer restarts again... help...

 

[SnoopCat]

are u having the problem where win2k loads up to "2 bars" and just hangs?

 

[Barrak]

When you go to reinstall there should be an option to repair an existing instalation, (or something like that). That will do a reinstall without loosing files. But if you already tried this.... Dont think there is anything else you can do to save it. There are programs around that can read NTFS (lost and found) and possibly save your files. I wish you luck

 

[luv2chill]

"some stop error" isn't very helpful.

What is the exact STOP message? Once you post that, I can give you some suggestions. Also, expanding on SnoopCat's question, how far into the win2k boot process does it throw the STOP error?

l2c

 

[lowtech1]

Can you boot to safe mode and try Last Known Good Boot.

Also try check disk at prompt: chkdsk c: /f

Or try to run Recovery Console.

 

[cmdavid]

it goes through the entire boot process before the stop error comes up...the progress bar loads up all the way.. and then the light blue screen is supposed to come up when it asks for password, thats when the stop screen comes up... .i think the stop error is 0x0000001E, which I know has to do with drivers.. only problem is that I haven't installed any drivers recently....but like i said.. the stop error screen only flashes for a split second before my computer restarts...

 

[lowtech1]

Boot into safe mode and select manual boot devices to find out which device is cuprit, then boot into safe mode and uninstall the violating device.

 

[cmdavid]

can't boot into safe mode tried that.. also tried last known configuration... doesnt work.... verified that stop error is 0x0000001E by staring at the screen trying to catch the split second... any other suggestoins... any way to reinstall it from winME or no??

 

[luv2chill]

Well, first off, can you boot successfully into safe mode? If so, once you boot up, right click on My Computer and go to Startup and Recovery settings and disable Auto-restart. Then reboot and let the boot process run so you can see the exact stop error.

If that's not possible (make sure to try both safe mode and safe mode with networking. Sometimes one works while the other doesn't.

OK, so assuming that you can't get into safe mode and you're reasonably sure that it's Stop 0x0000001E, here's what the win2k resource kit has to say about the problem:

Hardware Incompatability: First make sure that any new hw instlled is listed on the Win2k Hardware Compatability List.

Buggy device driver or system service: In addition, a buggy device driver or system service might be responsible for the error. Hardware issues, such as memory conflict and IRQ conflicts can also generate this error.

If a driver is listed by name within the Stop msg, disable or remove that driver. Disable or remove any drivers or services that were recently added.

If the problem is associated with win32k.sys, the source of the error might be a 3rd part remote control program. If such sw is installed, the service can be removed by starting the system using the Recovery Console and disabling the offending system service.

...

Disabling the memory caching of the BIOS might also resolve the error. You also need to run hw diagnostics, especially the memory scanner, supplied by the system manufacturer.
----

That's a start, but try hard to read the whole error off the BSOD before it reboots... it will usually give you the name of the driver or service that caused the Stop.

l2c

 

[luv2chill]

nix the safe mode stuff (took me too long to type it all!) but make sure that safe mode with networking doesn't work either.

Reboot a bunch of times and focus your eyes on a different section of the top line on the screen until you read it all... well the hex values aren't all that important, but look for a name of a device driver or service. I can get you into the recovery console to disable the offending driver, but you have to know which one.

l2c

 

[cmdavid]

alright.. ill try to find the exact offending driver.... if I don't get back to you tonight could you help me out tomorrow though luv2chill?? I appreciate your help.... thanks...

 

[luv2chill]

Yeah no problem. Believe me the only reason I know any of this is because I've been there. I was so determined to not have to reinstall everything that I went out and bought the win2k resource kit and learned the recovery console.

Will it likely be tomorrow? If so, pls. let me know. If you find it tonight I'll stay up and help you. Otherwise I'm going to bed.

l2c

 

[cmdavid]

yeah.. itll probably be tomorrow... thanks agian.. I'll pm you tomorrow and bump this thread when I have time to do this.. thanks a lot...

 

[luv2chill]

OK... night

l2c

 

[cmdavid]

alright.. took a video camera and recorded the stop error on my screen and then put it up on tv and paused it so that I could see everything.... I pmed you the stop page luv2chill

 

[cmdavid]

anybody know how to fix error 0x0000001E with ntoskrnl.exe as corrupted file...

I can get into the recovery console but don't know what to do from there...

 

[luv2chill]

YGPM... good idea about the camera BTW... I was going to suggest that.

l2c

 

[cmdavid]

<< YGPM... good idea about the camera BTW... I was going to suggest that.

l2c >>


yeah thanks... it was still hard cause it was for just barely a split second and the reaction time for pressing the pause button wasn't exact so it was still pretty tough to get it paused on the screen...

 

[lowtech1]

Run recovery console

 

[cmdavid]

<< Run recovery console >>



I know how to do that.. but what do i do once im there.. here's my stop error page.. there's a problem w/ the kernel apparently...

STOP 0x0000001E (0xC000005, 0x805064B5, 0x0000000)
KMODE_EXCEPTIOIN_NOT_HANDLED
***ADDRESS 805064B5 base at 80400000 DateStamp 384d9b17 -ntoskrnl.exe

 

[SinNisTeR]

me and my friend were installin win2k into his system and we were getting errors left and right. we didnt know what was wrong, we removed each device from the comp trying every combination. i finally found out what the problem was...it was the RAM!!

he has hever had a problem with the ram b4, it was cuz it was incompatible with his new mobo, he bought crucial to replace his generic and it works perfect now, he uses his old ram in his linux box...it works perfect too, go figure

 

[lowtech1]

.

 

[lowtech1]

Reboot system from CD or the 4 boot disk, then select Recoveryl, once your there you can select reinstall or fix restore system.

 

[Nevo]

First, determine what drivers you changed/installed/whatever between the last time the system successfully booted and the time that it didn't.

Knowing which driver(s) to suspect is key.

Boot to the W2K CD.

Choose Repair.

Choose Recovery Console.

Type 1 and hit Enter.

Enter the admin password.

Type the command listsvc

Write down the drivers you suspect might be causing the problem exactly as they appear.

Disable the driver(s), one at a time, with the command disable drivername

Attempt to boot the machine and see if the BSOD goes away.

Repeat as necessary.

Given the stopcode parameters, DVD drivers or CD burning drivers are likely culprits.

 

[cmdavid]

thanks nevo for the help but I've already done all that and disabling the drivers from the recovery console isn't working because they automatically re-enable themsevles after I try an boot up and i get the stop error again.. then i go into Recovery console again, and the drives and services that i just disabled are enabled again to their original state.. (boot, manual, auto.. etc)... then i tried scanning pretty much through my entire winnt folder in the recovery console and chaning the names of the .dll files mostly that i thought were causing the problems so that when windows looked for these files it wouldn't find them and would jsut skip them... that didnt work either....

now im looking for a software that somebody mentioned that can recover files from an NTFS disk while running off a FAT32 disk... anybody know of any software like this?? thanks in advance..