Windows Forum

Ask something
Discussion Locked

STOP error 0x00000067

0 helpful
3 replies

by barry pie

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

The full error code is:

0x00000067 (0x00000004, 0x00000007, 0x00000000, 0x00000000)
CONFIG_INITIALIZATION_FAILED

These are win 2000 PC's, fully updated wrt patches, all cloned from a master (identical hardware). PC's are constantly generating the above error when they had previously worked (6 PC's in 1 week)

I cannot find anything useful on microsoft support. It appears that it may possibly be related to the registry but I have no confirmation. BTW we do not have ERD's due to the high number of PC's on our network.

I have attempted windows repairs to no avail. The error even prevents booting up in safe mode. I'm very stuck, please help.

3 replies

by maxwell edison

Take a look at this Web site titled, "KNOWLEDGE BASE LINKS STOP MESSAGES"

(Cut and paste link):

http://aumha.org/win5/kbestop.php

http://tinyurl.com/o73i

Excerpts from the article:

STOP Messages literally mean Windows has stopped! These appear only in the NT-based operating systems: Win NT, Win 2000, and Win XP. Most are hardware issues. STOP messages are identified by an 8-digit hexadecimal number, but also commonly written in a shorthand notation; e.g., a STOP 0x0000000A may also be written Stop 0xA. Four additional 8-digit hex numbers may appear in parentheses, usually unique to your computer and the particular situation.

If a message is listed below (see link), but has no articles or explanation (nothing but its number and name), post a request on the AumHa Forums asking about it. STOP messages of this type are rare, obscure, and usually only of interest to programmers debugging their code. Real-life scenarios of a computer user encountering them are unlikely, so I?ve made it a lower priority to document them here; but we?ll be happy to address this in the Forum (which also will tip me off that I should add more to this present page).

General Troubleshooting of STOP Messages
If you can?t find a specific reference to your problem, running through the following checklist stands a good chance of resolving the problem for you. This checklist is also usually the best approach to troubleshooting some specific Stop messages, such as 0x0A and 0x50.

(continued...)

by maxwell edison

Examine the ?System? and ?Application? logs in Event Viewer for other recent errors that might give further clues. To do this, launch EventVwr.msc from a Run box; or open ?Administrative Tools? in the Control Panel then launch Event Viewer.
If you?ve recently added new hardware, remove it and retest.
Run hardware diagnostics supplied by the manufacturer.
Make sure device drivers and system BIOS are up-to-date.
However, if you?ve installed new drivers just before the problem appeared, try rolling them back to the older ones.
Open the box and make sure all hardware is correctly installed, well seated, and solidly connected.
Confirm that all of your hardware is on the Hardware Compatibility List. If some of it isn?t, then pay particular attention to the non-HCL hardware in your troubleshooting.
Check for viruses.
Investigate recently added software.
Examine (and try disabling) BIOS memory options such as caching or shadowing.
NOTE: When a STOP message occurs, Windows can create a debug file for very detailed analysis. To do this, it needs a workspace equal to the amount of physical RAM you have installed. If you resize your Win XP pagefile minimum to less than the size of your physical RAM, you will get an advisory message that your system may not be able to create a debugging information file if a STOP error occurs. My advice is to go ahead with this change if you want, but simply remember the limitation so that you can change it back if you need to troubleshoot STOP messages. Some general troubleshooting principles are suggested in the Resource Kit for approaching STOP messages overall.

(continued...)

by maxwell edison

0x00000067: CONFIG_INITIALIZATION_FAILED

0x0000005A: CRITICAL_SERVICE_FAILED

(Click to consult the online MSDN article.)
A critical service failed to initialize while starting the LastKnownGood control set. If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Hardware Compatibility List to verify that the hardware and its drivers are compatible with your version of Windows. If Windows is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message recurs, press F8 and select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk.

MSDN Article:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/w2kmsgs/1195.asp

http://tinyurl.com/o73y

This discussion is closed to new replies.