Re: stop error 0x00000067
From: joe (joe.rhoades_at_cae.com)
Date: 03/02/04
- Next message: Simon Lew: "Delete Registry Recovery message"
- Previous message: Simon Lew: "Registry Recovery"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 2 Mar 2004 08:41:55 -0800
Problem seems to be corrected. I dis-assembled computer
laptop looking for battery to reset bios, couldn't find it
so re-assembled and bios was reset when booted. Computer
booted into Win2000 and then went black screen. Cycled
power and error returned. Then went into safe mode and
selected last known working config and then it booted and
has worked ever since. Thanks, for the help, JR
>-----Original Message-----
>In microsoft.public.win2000.registry Bill Peele [MS]
wrote:
>
>> --------------------
>> From: "joe" <joe.rhoades@cae.com>
>> Subject: Re: stop error 0x00000067
>> Date: Tue, 24 Feb 2004 03:39:50 -0800
>> Lines: 23
>> Newsgroups: microsoft.public.win2000.registry
>>
>> The error is stop: 0x00000067(0x00000004, 0x0000000E,
>> 0x00000000, 0x00000000)
>> config_initialization_failed
>> OS is Windows 2000 professional
>> --
>>
>> Joe,
>>
>> This is one of those blue screens that can have
multiple causes.
>> I have seen this message caused by bad RAM, but you
said switching
>> out the RAM has not helped. I have seen it caused by
the System
>> and/or Software registry hives being corrupted. If we
can get to
>> Recovery Console we could try replacing these registry
hives with
>> backups or if we have to the original copies from when
Windows
>> 2000 was installed. I have also seen this message be
caused by
>> hardware drivers, especially drivers for SCSI
controllers where
>> the driver version does not match the firmware version
on the
>> controller.
>>
>> What was the last thing done on the system before the
blue screen
>> started?
>>
>> Bill Peele
>> Microsoft Enterprise Support
>>
>> This posting is provided "AS IS" with no warranties,
and confers
>> no rights. Use of included script samples are subject
to the terms
>> specified at http://www.microsoft.com/info/cpyright.htm
>>
>> Note: For the benefit of the community-at-large, all
responses to
>> this message are best directed to the newsgroup/thread
from which
>> they originated. Attachment decoded: untitled-2.txt
>> ------=_NextPart_0001_1E01F711
>> --------------------
>> From: "joe" <joe.rhoades@cae.com>
>> Subject: Re: stop error 0x00000067
>> Date: Tue, 24 Feb 2004 03:39:50 -0800
>> Lines: 23
>> Newsgroups: microsoft.public.win2000.registry
>>
>> The error is stop: 0x00000067(0x00000004, 0x0000000E,
>> 0x00000000, 0x00000000)
>> config_initialization_failed
>> OS is Windows 2000 professional
>> --
>>
>> Joe,
>>
>> This is one of those blue screens that can have
multiple causes.
>> I have seen this message caused by bad RAM, but you
said switching
>> out the RAM has not helped. I have seen it caused by
the System
>> and/or Software registry hives being corrupted. If we
can get to
>> Recovery Console we could try replacing these registry
hives with
>> backups or if we have to the original copies from when
Windows
>> 2000 was installed. I have also seen this message be
caused by
>> hardware drivers, especially drivers for SCSI
controllers where
>> the driver version does not match the firmware version
on the
>> controller.
>>
>> What was the last thing done on the system before the
blue screen
>> started?
>
>This is speculation:
>
>If nothing else (a long shot here), record BIOS setting,
un-plug the
>system and either remove the battery for some minutes or
use a jumper
>to reset-to-defaults the BIOS. I've heard that certain
auto-
>configuration settings at the hardware level might be
correupt and
>causing various problems. "Last resort" perhaps. No
guarantees.
>YMMV and FWIW. Hey, it's just a theory AFAIK.
>
>.
>
- Next message: Simon Lew: "Delete Registry Recovery message"
- Previous message: Simon Lew: "Registry Recovery"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
