Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hi...
I have a major problem with Win2k all of a sudden. Yesterday, while running Power DVD, I got a blue screen stop error. OK, reset, now I can't get into Win2k at all.The stop error says:
STOP: 0x0000001E (0xC0000005, 0x8050604B5, 0x00000000, 0x00000000) KMODE_EXCEPTION_NOT_HANDLED
Address-8050604B5
Base-80400000
DateStamp 39760637- ntoskrnl.exeAccording to the WIn2k support tools and the MS KB site:
This is a Windows 2000 Executive character-mode STOP message. It indicates that a kernel-mode exception was not handled. The second parameter in the parameter list is the memory address at which the unhandled exception occurred. Usually, the exception address pinpoints the driver/function that caused the problem. A common problem is 0x80000003, which means a hard-coded breakpoint or assertion was hit but the system started \\NODEBUG
Now at this point, I'm totally lost. I can't boot into safe mode or anything. I've done a system repair off of the CD, tried renaming the ntoskrnl.exe file and extracting it from the CD, nothing seems to do any good.
I don't believe this is a service or device driver that can be disabled to allow me to boot.
I'm running a dual boot 98se/2k machine so I have access to the files etc., but don't know what else to look for. I've run scandisk from 98 looking for invalid dates etc. Done a complete virus scan,(it's clean)
I would like to avoid a clean install if possible.
Sys info:
k62-500
256mb
2 hd
cd-rw
ls-120Any ideas out there? Any advice would be greatly appreciated. Thanx in advance.

Hello Dennis...I had similar problems
Go to microsoft's site and at the search put recovery console...there you are going to find the explanation of the commnads that related with this console.
After that if you have bootable win2k cdrom boot with that and enter repair and repair console(not the emergency repair). I hore you remember your admin password...
then at the command prompt put the foolowing commands to disable some adaptec services...
I had to say that my problem was related with direct cd and easy cd creator:type: disable cdr4vsd
disable cdrpwd
disable cdudf
let me know if it is going to help you
da@engineer.com

Oh..and try another RAM stick if you have a spare! Win9x can tolerate bad RAM (like bad parity bits and stuff like that), but because of the protected/security model, Win2k won't allow such things. I have seen STOP errors caused by bad RAM sticks!

![]() |
GSNW
|
Recovery Console
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |