Re: *DESPERATE* STOP 0x0000001E in ntoskrnl.exe

From: Chris Croughton (chris_at_keristor.org)
Date: 05/04/04 

Date: Tue, 4 May 2004 16:42:47 +0100

On Tue, 4 May 2004 15:22:08 +0200, John7
   <nosp@mm.com> wrote:

> "Chris Croughton" <chris@keristor.org> wrote in message
> news:slrnc9eoog.667.chris@ccserver.keris.net...
>> On Tue, 4 May 2004 02:10:01 +0200, John7
>> <nosp@mm.com> wrote:
>>
>> > "John7" <nosp@mm.com> wrote in message
>> > news:c769el$925$1@news5.tilbu1.nb.home.nl...
>> >
>> > 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.
>
> 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

Relevant Pages

  • Re: *DESPERATE* STOP 0x0000001E in ntoskrnl.exe
    ... >> pound for each time I've heard that one!) ... > Have nothing to compare SP3 version of ntoskrnl.exe against?! ... It could be a driver problem, or hardware. ... corruption needing a re-install. ...
    (microsoft.public.win2000.hardware)
  • Re: SYSTEM DISK FREEZES WITH HEAVY IO ON DISK
    ... hardware to keep up with obselence and efficiency. ... With servers a re-install is a major task -- and I would assume Microsoft ... Look, I have another post, asking for help wht SP3 server update fails. ... Some how the drivers or setup are not compatible when I switched to Intel ...
    (microsoft.public.windows.server.sbs)
  • Re: SYSTEM DISK FREEZES WITH HEAVY IO ON DISK
    ... I would also argue that 2 years is all you should expect from your hardware and that you should always upgrade after that. ... As to the OS, especially SBS, it really isn't that hard to re-install. ... You can also migrate the domain over from one server to the next by building the new one beside the old. ... With servers a re-install is a major task -- and I would assume Microsoft ...
    (microsoft.public.windows.server.sbs)
  • Re: WinXP Pro SP3 Blue Screen when ejecting CD
    ... I did re-install the chipset drivers when loading XP Pro. ... Any stop code to decode with a Bill Gates super decoder ring? ... Start by running hardware diagnostics on the memory and the hard drive. ...
    (comp.sys.hp.hardware)
  • Re: Update now asks for CD
    ... you can re-install as many times as you need on the same hardware. ... you may have to phone Microsoft to activate the ... "Jess" wrote in message ...
    (microsoft.public.officeupdate)
Loading