**URGENT** STOP 0x0000001E in ntoskrnl.exe

[John7]

Hi,

System was fine, no changes, no new installs, then suddenly ...
When booting system, rightafter logging in I get this:
STOP ERROR 0x0000001E
(0xC0000005, 0x8051C8B7, 0x00000000, 0x00000FF8)
KMODE_EXCEPTION_NOT_HANDLED
ntoskrnl.exe datestamp 3df90c0d
Happens when logging in with 2 different admins.
Memtest86 checked RAM => OK.
Can't enter Repair Console because original driver floppy (after F6)
for the mirrored HD's causes:
\win_2000\hpt3xx.sys caused unexpected fault a(4096)
at line 1211 in F:\nt\private\ntos\boot\setup\oemdisk.c.
Surface scanned floppy => OK.
ERD floppy available but need to figure out how to use it.
Tape available but 40GB disk is 1 partition, so restoring is difficult.

System:
Windows 2000 Pro, SP3, Windows Update status unknown.
AMD Duron 1200, 256MB, mirrored 40GB, Dawi DC-100 RAID,
Abit KG7 m/b, OnStream ADR30GB tape, LiteOn 32x CDRW.

Except for a faulty Software Registry Hive nothing seems likely so far.
No Terminal Services used. No installs in last 6 months.

I'd like to check disks first but how?
All suggestions are welcome.

QUICK HELP IS HIGHLY APPRECIATED !!!


TIA,
John7

 

[John7]

Hi,

System was fine, no changes, no new installs, then suddenly ...
When booting system, rightafter logging in I get this:
STOP ERROR 0x0000001E
(0xC0000005, 0x8051C8B7, 0x00000000, 0x00000FF8)
KMODE_EXCEPTION_NOT_HANDLED
ntoskrnl.exe datestamp 3df90c0d
Happens when logging in with 2 different admins.
Memtest86 checked RAM => OK.
Can't enter Repair Console because original driver floppy (after F6)
for the mirrored HD's causes:
\win_2000\hpt3xx.sys caused unexpected fault a(4096)
at line 1211 in F:\nt\private\ntos\boot\setup\oemdisk.c.
Surface scanned floppy => OK.
ERD floppy available but need to figure out how to use it.
Tape available but 40GB disk is 1 partition, so restoring is difficult.

System:
Windows 2000 Pro, SP3, Windows Update status unknown.
AMD Duron 1200, 256MB, mirrored 40GB, Dawi DC-100 RAID,
Abit KG7 m/b, OnStream ADR30GB tape, LiteOn 32x CDRW.

Except for a faulty Software Registry Hive nothing seems likely so far.
No Terminal Services used. No installs in last 6 months.

I'd like to check disks first but how?
All suggestions are welcome.

QUICK HELP IS HIGHLY APPRECIATED !!!


TIA,
John7

Managed to get passed the RAID driver floppy problem (F6).
Got into Recovery Console, Chkdsk /r found errors and fixed them
but the problem remains. Still STOP 0x0000001E.

John7

 

[Pegasus \(MVP\)]

Hi,

System was fine, no changes, no new installs, then suddenly ...
When booting system, rightafter logging in I get this:
STOP ERROR 0x0000001E
(0xC0000005, 0x8051C8B7, 0x00000000, 0x00000FF8)
KMODE_EXCEPTION_NOT_HANDLED
ntoskrnl.exe datestamp 3df90c0d
Happens when logging in with 2 different admins.
Memtest86 checked RAM => OK.
Can't enter Repair Console because original driver floppy (after F6)
for the mirrored HD's causes:
\win_2000\hpt3xx.sys caused unexpected fault a(4096)
at line 1211 in F:\nt\private\ntos\boot\setup\oemdisk.c.
Surface scanned floppy => OK.
ERD floppy available but need to figure out how to use it.
Tape available but 40GB disk is 1 partition, so restoring is difficult.

System:
Windows 2000 Pro, SP3, Windows Update status unknown.
AMD Duron 1200, 256MB, mirrored 40GB, Dawi DC-100 RAID,
Abit KG7 m/b, OnStream ADR30GB tape, LiteOn 32x CDRW.

Except for a faulty Software Registry Hive nothing seems likely so far.
No Terminal Services used. No installs in last 6 months.

I'd like to check disks first but how?
All suggestions are welcome.

QUICK HELP IS HIGHLY APPRECIATED !!!


TIA,
John7

Here is a little light reading on Stop errors:
http://support.microsoft.com/default.aspx?scid=kb;en-us;130802
http://aumha.org/win5/kbestop.htm

 

[Chris Croughton]

Managed to get passed the RAID driver floppy problem (F6).
Got into Recovery Console, Chkdsk /r found errors and fixed them
but the problem remains. Still STOP 0x0000001E.

If it's true that "nothing has changed" (and I'd be rich if I had a
pound for each time I've heard that one!) then the most likely cause is
hardware, probably memory going/gone bad. That would be the first thing
I'd try.

Chris C

 

[John7]

If it's true that "nothing has changed" (and I'd be rich if I had a
pound for each time I've heard that one!) then the most likely cause is
hardware, probably memory going/gone bad. That would be the first thing
I'd try.

Chris C

No hardware or software was changed. Because the mouse hung my friend
turned off power. This might have damaged files / registry.
All safe boot modes (F8) crash rightafter logon (incl. Last Known Good).

In Recovery Console tried to save ntoskrnl.exe and ddl cache version to
floppy
for comparison but Recovery Console can't write to floppies (Christ, WHY?).
Have nothing to compare SP3 version of ntoskrnl.exe against?!
How to figure out if files are still intact?

Problem is all help docs assume windows is still operational, while this one
crashes rightafter logon so I cannot start any corrective action there.

GETTING DESPERATE :-(

John7

 

[Chris Croughton]

No hardware or software was changed. Because the mouse hung my friend
turned off power. This might have damaged files / registry.
All safe boot modes (F8) crash rightafter logon (incl. Last Known Good).

Including command line?

In Recovery Console tried to save ntoskrnl.exe and ddl cache version to
floppy
for comparison but Recovery Console can't write to floppies (Christ, WHY?).
Have nothing to compare SP3 version of ntoskrnl.exe against?!
How to figure out if files are still intact?

So have you tried the memory? How about booting from your install CD
and checking the files from there? What data do you have on there which
isn't backed up (you do backups, don't you?), if you re-install?
Incidentally, data should always be put onto a different drive or
partition in case you need to vape the system area...

Problem is all help docs assume windows is still operational, while this one
crashes rightafter logon so I cannot start any corrective action there.

It could be a driver problem, or hardware. Or it could be total
corruption needing a re-install.

Chris C

 

[Simon Elliott]

No hardware or software was changed. Because the mouse hung my friend
turned off power. This might have damaged files / registry.
All safe boot modes (F8) crash rightafter logon (incl. Last Known Good).

In Recovery Console tried to save ntoskrnl.exe and ddl cache version to
floppy
for comparison but Recovery Console can't write to floppies (Christ, WHY?).
Have nothing to compare SP3 version of ntoskrnl.exe against?!
How to figure out if files are still intact?

Problem is all help docs assume windows is still operational, while this one
crashes rightafter logon so I cannot start any corrective action there.

GETTING DESPERATE :-(

John7

Quickest way to get the machine working again might be a duplicate
install of Windows and then recover back from the tape I understand you
to have.

 

[John7]

Thx Chris for responding.

Including command line?

Yes, same story !

So have you tried the memory?

Yes, ran docmem for several hours, no prob.

How about booting from your install CD and checking the files from there?

That's what I am about to do next.

What data do you have on there which

My friend's business files. He's kinda nerveous now.

isn't backed up (you do backups, don't you?), if you re-install?

Last backup was 9 days ago. As a LAST resort I will restore
the tape to the all-in-one partition. He will lose 9 days of work.
Problem is the tape drive mfg went bankrupt, so NO support.
And ... disk has to be wipped first to install win2K from fresh,
then restore tape on top of it. If it succeeds fine but if it fails he
looses all data! I may need to break the mirrored array
(2 x 40GB in RAID 1) to backup data first. Another thing I
need to figure out. No easy path either.

Incidentally, data should always be put onto a different drive or
partition in case you need to vape the system area...

True, but this is the situation we are facing now.

It could be a driver problem, or hardware. Or it could be total
corruption needing a re-install.

I just can't come closer to problem|cause. All solutions require a
running OS which we don't have and Recovery Console is limited.

 

[John7]

Thx Simon,

Quickest way to get the machine working again might be a duplicate
install of Windows and then recover back from the tape I understand you
to have.

Last backup was 9 days ago. As a LAST resort I will restore
the tape to the all-in-one partition. He will lose 9 days of work.
Problem is the tape drive mfg went bankrupt, so NO support.
And ... disk has to be wipped first to install win2K from fresh,
then restore tape on top of it. If it succeeds fine but if it fails he
looses all data! I may need to break the mirrored array
(2 x 40GB in RAID 1) to backup data first. Another thing I
need to figure out. No easy path either.

 

[Pegasus \(MVP\)]

Thx Chris for responding.


Yes, same story !


Yes, ran docmem for several hours, no prob.
there?

That's what I am about to do next.


My friend's business files. He's kinda nerveous now.



Last backup was 9 days ago. As a LAST resort I will restore
the tape to the all-in-one partition. He will lose 9 days of work.
Problem is the tape drive mfg went bankrupt, so NO support.
And ... disk has to be wipped first to install win2K from fresh,
then restore tape on top of it. If it succeeds fine but if it fails he
looses all data! I may need to break the mirrored array
(2 x 40GB in RAID 1) to backup data first. Another thing I
need to figure out. No easy path either.


True, but this is the situation we are facing now.
this

I just can't come closer to problem|cause. All solutions require a
running OS which we don't have and Recovery Console is limited.

Boot the machine with a WinXP CD (http://www.nu2.nu/pebuilder/#download),
then save your client's important files. To manufacture the CD, you need
a WinXP Professional CD (no key required!) and a CD burner.

When finished, remind your client that the interval between
backups must reflect his business needs. If a loss of 9 days'
worth of data hurts then the interval is clearly too long.

 

[Guy Harrison]

Thx Simon,



Last backup was 9 days ago. As a LAST resort I will restore
the tape to the all-in-one partition. He will lose 9 days of work.
Problem is the tape drive mfg went bankrupt, so NO support.
And ... disk has to be wipped first to install win2K from fresh,
then restore tape on top of it. If it succeeds fine but if it fails he
looses all data! I may need to break the mirrored array
(2 x 40GB in RAID 1) to backup data first. Another thing I
need to figure out. No easy path either.

Why not just put another disk in it? A working w2k on new disk should be
able to access the raid. You also lose nothing in an attempt to restore
from tape to the new disk. Either it works or it doesn't. One thing's for
sure: stop trying to write to current disks if data is that important. Have
them mirrored first, or do it yourself (eg suitable unix and 'dd'). A scsi
card can be handy in these circumstances - a drive attached to it can
typically be made to boot prior to the internal ones.

Btw, tell friend about keyboard shortcuts: ctrl-alt-del,alt-s,r,CR for
instance to avoid future repetitions.

 

[Peter G Sheppard]

Last backup was 9 days ago. As a LAST resort I will restore

the tape to the all-in-one partition. He will lose 9 days of work.
Problem is the tape drive mfg went bankrupt, so NO support.
And ... disk has to be wipped first to install win2K from fresh,
then restore tape on top of it.

Take his hard drive out, put it in another working 2k/xp machine, and copy
the important data from it to the good machine. Then you can reinstall his
if needs be.

 

[Clint Sharp]

Last backup was 9 days ago.

Stupid. Almost makes you want to lose the data to teach him a lesson.

As a LAST resort I will restore
the tape to the all-in-one partition. He will lose 9 days of work.
Problem is the tape drive mfg went bankrupt, so NO support.

Not necessarily a problem, but he's going to have one hell of a time
replacing his tapes.

And ... disk has to be wipped first to install win2K from fresh,
then restore tape on top of it.

Why? Get a new drive and restore to that.

If it succeeds fine but if it fails he
looses all data! See above.
I may need to break the mirrored array
(2 x 40GB in RAID 1) to backup data first. So do it!
Another thing I
need to figure out.

Errm, disconnect one drive? The whole point of a mirror set is that one
drive can disappear and the system carries on until you replace the
failed drive.

No easy path either.

First thing, stop messing around with critical data. One wrong move and
it's gone.
Remove the 'RAID' controller and drives, stop messing about with it
until you are in a position to do so safely.

Build a fresh W2k install (Pro or Server) on a new drive using the
motherboard controller, make sure it all works.

Re-install the 'RAID' controller with one disk from the mirror set, make
sure the system boots from the newly built drive (you may need to change
the BIOS settings) and install the drivers if asked to.

You should then be able to see the drive and recover the data to some
kind of reliable medium (make more than one copy and verify them to be
certain).

Pray the stop error you see isn't a 'RAID' controller hardware error or
the data format used by the 'RAID' isn't proprietary.

Learn lessons from this.

1. Regular backups prevent your arse from falling out.

2. Don't bugger around with things you don't understand if it's business
critical, learn on non critical stuff first or find a professional.

3. Don't rely on toy hardware for business critical stuff, I see nothing
in your hardware list that I would let near a server, let alone inside
one. It's often cheaper to buy a name brand server you can get support
on than find out the hard way you can't get spares or support for
something you need running today.

 

[Chris Croughton]

Yes, same story !

Er, how then did you get to run chkdisk?

Yes, ran docmem for several hours, no prob.

I don't know docmem, I was referring to swapping it out.

My friend's business files. He's kinda nerveous now.

And he doesn't have daily backups? Oy veh.

Last backup was 9 days ago. As a LAST resort I will restore
the tape to the all-in-one partition. He will lose 9 days of work.

See above.

Problem is the tape drive mfg went bankrupt, so NO support.

When? And he hasn't replaced it with something current? How valuable
are these files if it wasn't worth updating the backup system and hasn't
done a backup for 9 days?

Out of interest, where are the backups kept and have you ever done a
restore from them? I've seen a load of cases where it's "Oh yes, we do
backups regularly" and then when they need them they find that the write
was fine but the tape can't be read (or it doesn't have everything they
need on it).

And ... disk has to be wipped first to install win2K from fresh,

Get a new disk. Disable the current ones (or make them read-only) so
they don't get even more corrupt first. Restore to the new disk. Or
even easier, find a machine with Win2k (or XP, although that can be
touchy about hardware changes) and put one of your existing drives in
that and pull the data off it.

then restore tape on top of it. If it succeeds fine but if it fails he
looses all data! I may need to break the mirrored array
(2 x 40GB in RAID 1) to backup data first. Another thing I
need to figure out. No easy path either.

Duh, if it's only mirrored (not striped) then it's easy, just unplug one
of the drives. That's the point of RAID 1.

For all you know it may be your RAID controller which is the problem, so
try plugging one of the drives into the ordinary controller.

True, but this is the situation we are facing now.

Then you/he have learnt something for next time.

I just can't come closer to problem|cause. All solutions require a
running OS which we don't have and Recovery Console is limited.

You don't have any other machines? What about the one on which you're
typing this?

Chris C

 

[John7]

I was able to fix the problem.
Thanx guys for all your support!

Backupped RAID1 disks separately to another system.
Data on Primairy RAID1 disk appeared damaged.
Secundairy RAID1 disk appeared OK.
Odd, they were different, probable due to switching off
at an inappropriate moment.
Surface check both disks : OK. Drive fittness checks : OK.
I disabled mirroring relation ship between drives.
Made old secundairy disk (was OK) the new primary.
Made old (bad) primary the new secundairy disk and
rebuild the array. System was fine again.
As a precaution I updated the raid drivers and
reminded friend again about CTRL-ALT-DEL.
After checking he found no errors so far (1.5 wk ago).

Cheers,
John7

 

[soaringink]

Managed to get passed the RAID driver floppy problem (F6).
Got into Recovery Console, Chkdsk /r found errors and fixed them
but the problem remains. Still STOP 0x0000001E.[/vbcol]

If it's true that "nothing has changed" (and I'd be rich if I had a
pound for each time I've heard that one!) then the most likely cause
is
hardware, probably memory going/gone bad. That would be the first
thing
I'd try.

Chris C [/B]

An error like this 0x1E (0xc0000005, 0x8051e981, 0x00000000, 0x00000FF8)
has been plaguing me as well. Though I cant say I changed nothing. I
moved a Duron out and an Athlon in...though the Duron now repsonds in the
exact same way.

Current Configuration:
Windows 2000SBS Svr Pk 4 w/ Exchange
Duron 950
512Mb DDR 2100
2x40Gb Western Digital (Mirror)
ECS K7S5A board
Promise Fasttrack TX2000
8Mb PCI Video
CDROm

With my Windows 2000 SBS we have some other distinctive commonalities. I
was not able to log in as administrator (STOP 0x1E) but could with user
account after the machine sat (off) all night. Then the very next boot I
could only get to log-in screen and it would crash after ANY account tried
to log in. I also got an error when trying to load the RAID floppy to get
to Recovery Console. Mine was at line 1044 in the same NT\private\ntos...
blahblah. The Duron CPU was the only part flagged in some performance
reports with regards to hardwarethreads since I built this machine. Do
you think our Durons have found their graves?