HELP URGENT : STOP 0X00001E (0XC00005, 0X80520D1F, 0X00000000, 0X00000FF8)

  • Thread starter Thread starter sgupta
  • Start date Start date
S

sgupta

Hi ,

Today Suddenly a blue screen popped up with the following error on
windows 2000 sp4

: STOP 0X00001E (0XC00005, 0X80520D1F, 0X00000000, 0X00000FF8) address
80520D1F BASE AT 80400000 DateStamp 42258bd8-ntoskrnl.exe

Beginning to dump memory

The machine then reboots and give the log in screen. When I log in , it
starts registering then boom! the error come back. BAsically I cannot
log in. Tried safe mode too - as soon as I login same problem.


I desparately need help here. I do not have emergency repair disks.
Someone had suggested to replace ntoskrnl.exe from Driver Cache and/or
from etup disk. Tried that and has not worked. The orignal file is now
back in and I conntinue to get this errror..

any help really appreciated - desperate

viper
 
what happens if you don't login and leave the system at the login screen?
does it still crash after a certain amount of time?
if not, can you connect to the server remotely and see the event log for any
other errors?
from what i'm reading in the resource kit, it looks like a faulty driver
 
no it does not crash when I leave the login screen. However I have not
been able to connect remotely to the laptop. Since I was using a
wireless card while this happened I had disable the lan network to
avoid conflict...

Is there anyway I can enable login access from the repair console. How
would I see the event log remotely anyway? Can I look at it from the
event console?

Any help would be greatly appreciated

thanks

sandeep
 
I meant enaling remote access from the repair console and viewing event
log from repair console

thanks
 
no it does not crash when I leave the login screen. However I have not
been able to connect remotely to the laptop. Since I was using a
wireless card while this happened I had disable the lan network to
avoid conflict...

Is there anyway I can enable login access from the repair console. How
would I see the event log remotely anyway? Can I look at it from the
event console?

Any help would be greatly appreciated

thanks

sandeep

Here are a couple of ways to access the hard disk in order
to read the registry or the event logger (config\*.evt):

- Temporarily install the hard disk as a slave disk in some
other Win2000/XP PC.
- Boot the machine with a Bart PE boot CD (www.bootdisk.com).
To make the CD you need a CD burner, a WinXP Professional
CD and about three hours of your time (but no WinXP licence
number!).
 
This is actually a thinkpad PC so I am somewhat wary about taking the
hard disk out. Is there someway I can copy this files of the disk and
read them on another computer?

throught the repair console I can backup the config directory within
some other directory under windows - the only other thing I needed to
backup was the ntuser.dat which I am not sure I can do

thanks

viper
 
I figured out a way to copy the event files from the disk. However
while the security event file opens the other two - application and
system event logs do not open in the other computer. Says the files are
corrupt. I renamed then on the original disk through the repair disk,
it create new file I copied them again - but no luck - same
corruption..

I think since it crashes it corrupts these files perhaps not sure what
to do now
 
Back
Top