Stop error on win2k

[samarth]

I have a dual booting system with win2k and win98. Win2k just rebooted by itself today morning and is giving me a blue screen with the message that there is a stop error. I can still boot to 98. What is this message about and how can i get rid of it.
thanks

note: I cant boot to win2k anymore.

 

[Slikkster]

by any chance you don't have Windows 98 and Windows 2000 on the same partition, do you? That's always a no-no because they will share the same Program Files folder and several other sub-folders of it, creating havoc.

Can you use the "Last known good configuration" option when booting into Windows 2000?

Last known good configuration boot Win2k

If you keep getting the blue screen, post whatever gibberish you can from it here...as much as possible so it can be tracked down.

 

[samarth]

they are not on the same partition
the error is this
Stop error 0x0000000A and then it has some other memory location and says that there is a fault at ntoskernel.exe

 

[samarth]

these are the things i tried but nothing has worked
1. use the restore previous good setup from the advanced bootup menu
2. get into the win2k installation setup program and use the repair operation to reinstall all the files for the OS
3. I can get into win2k using safe mode but then there is not much i can do while in safe mode. I can also bootup 98 perfectly fine.
If it helps, both os's are on different partitons but both are fat32 partitions. They are also on the same physical drive.

 

[Slikkster]

Here's Microsoft's info on this error:

Windows 2000 Stop Errors FAQ

Can you recall installing any new devices recently before this happened? Maybe you didn't log onto 2000 after having installed someting in 98 awhile earlier or something? Any new drivers?

It may not help, but you can use windows 98's "msconfig.exe" while in 2000's Safe Mode to disable some programs that are running at startup...it will give you a few errors when running it because win2k doesn't use autoexec.bat nor config.sys...just click OK and let it get to the startup section and then disable programs.

You can also access device manager in Win2K in Safe mode and disable any devices you think might be hurtin ya. The Microsoft Page above says it's the third line of the blue screen memory message that gives you an indication of what driver is causing the problem. Take a look at it. You'll be interested in scrolling down the page about 3/4's of the way till you get to the "Stop Errors After Installation"...the first part of the info has to do with Stop Errors while installing 2K.

Ran across one MS page on Stop Errors in 2000 that said motherboards with older VIA chipsets could have this problem, but sounds like this is something that cropped up on you all of the sudden.

 

[samarth]

this is the exact error on the blue screen if it helps

stop: 0x0000000A (0x00000000, 0x00000002, 0x00000001, 0x8042d5b4)
Address 8042d5b4, base at 80400000, date stamp: 384D9B17 - ntoskrnl.exe

 

[SendTrash]

I say....
REFORMAT and REINSTALL!!!.. lol

 

[Slikkster]

Here's what I would try next:

If you have a "VGA Mode" option in your Windows 2000 Boot Menu, try that one. It loads with standard VGA drivers vs. your videocard's normal drivers. Video drivers can cause Stop Errors on bootup. If you don't have a "VGA Mode" option on your Windows 2000 Boot Menu at bootup, do this from Win98:

Go to the c:\ folder. Right-click on "boot.ini" and choose "Properties". Remove the checkmark for "Read-Only". Now, close the properties and doubleclick on the boot.ini file to edit it. Find your entry for Windows 2000 Professional. It should end with the switch "/fastdetect".

You want to replace "/FASTDETECT" with "/BASEVIDEO /SOS" (all of this without quotes). "/BASEVIDEO /SOS" will load VGA drivers and ALL other normal drivers, which is different from Safe Mode which only loads limited drivers. "SOS" will list the names of the drivers as they load, so should there be a problem with a particular driver, it should be the last one on the list that's loading. Now, it could also be the next driver on the list at startup that's causing the problem, and if that's the case, it won't show on the list of loading drivers. However, you can find the order of driver loading by booting up in SAFE MODE in Win2K and going to Regedit.exe, then going to the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Control\ServiceGroupOrder


Make sure there's a space between the "O" in /BASEVIDEO and the "/" that preceeds "SOS".

 

[dkk]

or maybe that nt kernel file is corrupted? just a thought

 

[Slikkster]

that's the right idea, but if you look earlier, he said he restored all system files. Since it works in safe mode, it's most definitely a driver, and I'd bet a dollar to a donut it's a video thing. But, we shall see.

 

[jasonlee123]

Ill match your dollar and raise you a twinkie that its a video thing.:|:|

 

[samarth]

If you have a "VGA Mode" option in your Windows 2000 Boot Menu, try that one. It loads with standard VGA drivers vs. your videocard's normal drivers. Video drivers can cause Stop Errors on bootup. If you don't have a "VGA Mode" option on your Windows 2000 Boot Menu at bootup, do this from Win98:
I did the VGA mode thing, then there was a screen which just showed it loading bunch of files but then it would keep freezing at some point. I tried this 3 times. I tried the repair again form the setup menu and it worked this time. just weird.
but thanks for your help
samarth

 

[Slikkster]

Glad it worked out for ya in the end.