• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Can't start Win2000 PLEASE HELLLLLPPP!!!!!!!!!!!!!!!!!!!

FOH

Senior member
I have a dual boot system with 98FE and Win2000. I was using 2000 and was looking at my audio settings on my Sound Blaster Live Platinum, when my computer restarted by itself. It went though the startup procedure, then went though a scandisk, then BSOD. It said:



***stop 0x0000001E (0x0000005, 0x804EF92A, 0x00000000, 0x00000000
KMODE_EXCEPTION_NOT_HANDLED
Address 804EF92A base at 80400000, Date Stamp 384d5a86 - ntoskrnl.exe

Beginning dump of physical memory.
Physical memory dump complete. Contact your system administrator or technical support group.



After the BSOD then the computer restarts by itself again and does the same thing, over and over. During the startup procedure I can select to boot into Win98 and it works fine (it is what I am using now). That tells me that the computer hardware is O.K. and it must be in the software. I have tried to start in safe mode, no luck. I have tried to start in last known good configuration, no luck. I have tried all of the different safe modes, no luck.

Any ideas? ----PLEASE HELP!!!!!!----
 
ripped from here win2kfaq


Q. I get the error "NTOSKRNL.EXE missing or corrupt" on bootup.

A. This is usually due to an error in the boot.ini file. The entry for NT is either missing or incorrect. Edit the boot.ini file and check the entry for NT is correct, for example for an IDE disk the entry should look something like

multi(0)disk(0)rdisk(0)partition(2)\winnt="Windows NT workstation"

Check that disk and partition are correct. If you have recently added a new disk or altered the partitions try changing the disk() and partition() values. If you are sure everything is OK, then the actual file may be corrupt so copy NTOSKRNL.EXE off of the installation CD onto the %systemroot%/system32 directory.

You may need to edit the boot.ini if Linux is installed onto a system. During installation DiskDruid (Red Hats disk configuration utility) may create a primary partition (depending on disk configuration) and although the extended NT partition was there first (and at the beginning of the disk), the primary partition affects the numbering of the partition() parameter of boot.ini. Changing it from (1) to (2) (for example) allows the successful boot of NT.


 
I had a similar problem when I upgraded to the Eval copy of W2K I received at a MSDN seminar. I installed W2K over W98, then installed Liveware 3.0 for W2k. Most everything sounded ok, except Flash animation. I have since then done a clean install of W2K and DID NOT download Liveware or any other driver from Creative. The reference drivers that came with W2K work great, so I figured why mess with it. Until Creative comes up with a better set of drivers (I will have different SC by then) I will leave it the way it is. For once Windows comes through with a good driver. My 0.02
 
Boot from the Win2k CD and start setup. Then select "Repair" Then select "Manual Repair". Then let it repair everything.

Bozo 😀
 
i dual boot win98se win2k and just on a random restart i got this same exact error and i can't get rid of it. Basically tried the exact same procedure as FOH and got same results. I can't get to win2k. i ran the repair utility and it didn't correct the problem. is it possible to use the system file checker (sfc.exe) from the repair console? This problem sucks!!
 
Thanks everyone for your replys. I have tried them all with no luck. I still can't get Win2000 to start, just BSOD and then restart by itself. When I did the "repair" from the Win2000 CD, it did find several bad files and replaced them and I thought that would do it. But it didn't, I restarted and same thing.

I have used this computer for about 4 months without adding any hardware or updating any drivers, no change in anything that I can think of. It just stopped and restarted and then BSOD in the middle of doing nothing out of the ordinary. Am I doomed to reformat and reinstall? Would reinstalling instead of repairing Win2000 do any good?
 
if nothing works then i suggest backing up all the files you need from your (win2k partition) winnt folder & documents/settings and goto win98 and re-install it again , it will auto detect a previous installation on win2k and delete that folder and then re-install itself leaving all other files on your partition suc as program files etc...
 
Here is a quick update: I reinstalled Win2000 from Win98. I loaded all my programs and drivers, got everything back to normal. I then went into the Win2000 folders and found all my doucuments and all my email folders still intact, it didn't deleate any of them, but I had two folders for everything. So I copied all the old folders into the new ones, then deleated the old folders and everything seams to be back to normal. 😀

Now the BIG question: Why did this happen and how can I keep it from happening again? 😕 When it happened I was looking at my soundblaster settings. I did that again after the reinstall and nothing happened. I tried clicking on everything to try to make it crash again, no problem, works normal. There must be a reason why Win2000 would, all of a sudden and for no reason, crash so hard that it couldn't even start in safe mode. I switched to Win2000 to get stability, and look what happened!!!! :| :| :|
 
yes...the KMODE_EXCEPTION_NOT_HANDLED error is driver related and basically meant your liveware drivers fecked everything up. a good way to go around that? well, either take out your sound card and look for the driver files that went with liveware(pita!) and erase them. or try booting win2k in safemode and uininstall the soundcard. then when windows loads up again it will detect the soundcard and install reference drivers and viola! youre as good as gold! happened to me too when i installed new drivers for my HPT370. the bios wasnt the latest and the drivers were so it somehow conflicted and gave me a stop error on startup saying how the registry was fecked. so i went in safemode and did exactly that, uninstalled all the new hpt370 drivers and reinstalled the older ones and worked like a charm, same goes for soundblasters, IME

goodluck
loosbrew
 
If I had just installed drivers that would make sense, but I haven't updated, installed, or changed anything in about 4 months and it has been working great. Could it still be confilcts even after that much time of no problems? And after my crash, I couldn't even get into safe mode, and the repair utillity didn't help, so I had to reinstall.
 
Back
Top