Stop error 0x00000067

stop error 0x00000067

This bug check indicates that the registry configuration failed. This repair tool can fix common computer errors like BSODs, system freezes and crashes. sprers.eu › › Microsoft › Windows XP. Stop codes display on error screens — the Blue Screens of Death (BSOD). BSOD error code 0x may also show.

Related Videos

How do I fix error 0x00000006

Did you happen to have any CD-Writer software from Adaptec on this system?
I recently upgraded a machine with CD-Creator c to Win and it would
not boot until I disabled the CD-Creator drivers using the Recovery Console.
Aparantly, CD-Creator c is not compatible with Winbut the setup
does not tell you that.

If it is, check this KB article:
sprers.eu?LN=EN
n&FR=0

If that isn't the case, post more of the BSOD and possibly system config and
installed software.

- Matt

> Can you reproduce any more of the BSOD, I'm not familiar with that error
> code.

> Stuart


> > I recently upgraded my Win98 computer to Win I was stupid enough
to
> > not choose the double-boot option. No my computer refuses to start and
> gives
> > the following.

> > STOP Error 0x

> > Please help
> > Sanjay

Terms

General discussion

  • by barry pie · about 18 years, 11 months ago

    The full error code is:

    0x (0x, 0x, 0x, 0x)
    CONFIG_INITIALIZATION_FAILED

    These are win 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, stop error 0x00000067. It appears that it may possibly be related to the registry but I have no confirmation. BTW we do not have ERD&#;s at + cdrun =8 error to the high number of PC&#;s on our network.

    I have attempted windows repairs to no avail. The error even stop error 0x00000067 booting up in safe mode. I&#;m very stuck, please help.

All Comments

    • Reply To: STOP error 0x

      by maxwell edison · about 18 years, 11 months ago

      In reply to STOP error 0x

      Take a look at this Web site titled, &#;KNOWLEDGE BASE LINKS STOP MESSAGES&#;

      (Cut and paste link):

      sprers.eu

      sprers.eu

      Excerpts from the article:

      STOP Messages literally mean Windows has stopped! These appear only in the NT-based operating systems: Win NT, Winand 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 0xA 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), stop error 0x00000067, 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 stop error 0x00000067 programmers debugging their code. Real-life scenarios of a computer user encountering them are unlikely, so I?ve made error code 1063 mysql 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 Error 036 pawno of STOP Messages
      If you can?t find a specific reference to hasp not found -10 error problem, running through the following checklist stands a good chance of resolving the problem for you, stop error 0x00000067. This checklist is also usually the best approach to troubleshooting some specific Stop messages, such as 0x0A and 0x

      (continued&#;)

      • Reply To: STOP error 0x

        by maxwell edison · about 18 years, 11 months ago

        In reply to Reply To: STOP error 0x

        Examine the ?System? and ?Application? logs in Event Viewer for other recent errors that might give further clues. To do this, launch sprers.eu 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 stop error 0x00000067 software.
        Examine (and try disabling) BIOS memory options such as caching or shadowing.
        NOTE: When a STOP message occurs, Windows can error performing snmp request to 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 scx-4200 lsu error your Win XP pagefile minimum to less than the size of stop error 0x00000067 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, stop error 0x00000067. 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 Stop error 0x00000067 Kit for approaching STOP messages overall.

        (continued&#;)

      • Reply To: STOP error 0x

        by maxwell edison · about 18 years, 11 months ago

        In reply to Reply To: STOP error 0x

        0x CONFIG_INITIALIZATION_FAILED

        0xA: 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 boot manager windows 7 error hardware has been installed, reboot with recovery options set to create a dump file. If the message stop error 0x00000067, 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:

        sprers.eu?url=/library/en-us/w2kmsgs/asp

        sprers.eu

Contact US

INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Thanks. We have received your request and will respond promptly.

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!

  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Stop error 0x00000067 functionality depends on members receiving e-mail. By joining you are opting in to receive essbase error codes 1019003 Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Tek-Tips Posting Policies

Contact US

stop error 0x after installation

stop error 0x after installation

proudusa(MIS)

(OP)

I'm installing windows on a system i'm building.   After the installation i'm getting the blue screen mentioned above.    I've checked the video card (SiS) and NIC (linksys LNE) and both are compatible with 2K.   I'm changed the controller cables.   From what i've been able to find the error message pertains to bad scsi termination (doesn't apply), bad controller (replaced) or something to do with the DIP switches on the drive.

Has anyone else run into this stop error 0x00000067

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

How To Fix CONFIG_INITIALIZATION_FAILED Blue Screen Errors (0x)

ExError Number:Error 0x67
Error Name:CONFIG_INITIALIZATION_FAILED
Error Description:The CONFIG_INITIALIZATION_FAILED bug check has a value of 0x This bug check indicates that the registry configuration failed.
Hexadecimal:0x
Developer:Microsoft Corporation
Software:Windows Operating System
Applies to:Windows XP, Vista, 7, 8, 10, 11

Commonly, corrupt or missing 0x device or kernel mode drivers (or even defective hardware) can cause these "bluescreen" (BSOD) errors to occur when trying to execute a related Windows 10 program function. Ordinarily, installing a new version of the 0x67 file will repair the problem creating the error.


CONFIG_INITIALIZATION_FAILED Errors

Most CONFIG_INITIALIZATION_FAILED errors encountered will be BSOD (Blue Screen of Death) errors, also known as a "STOP" error:

  • "A problem has been detected and Windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: CONFIG_INITIALIZATION_FAILED."
  • ":( Your PC ran into a problem and needs to restart. We’re just collecting some info, and then we’ll restart for you, stop error 0x00000067. If you would like to know more, you can search online later for this error: CONFIG_INITIALIZATION_FAILED."
  • "STOP 0x0A: IRQL_NOT_LESS_EQUAL – CONFIG_INITIALIZATION_FAILED"
  • 0xE: KMODE_EXCEPTION_NOT_HANDLED – CONFIG_INITIALIZATION_FAILED
  • STOP 0x PAGE_FAULT_IN_NONPAGED_AREA – CONFIG_INITIALIZATION_FAILED

The majority of CONFIG_INITIALIZATION_FAILED BSOD errors happen after fresh install of new hardware or software (Windows). Commonly, CONFIG_INITIALIZATION_FAILED errors are seen during the Windows-related hardware or software install process, stop error 0x00000067, while a Microsoft Corporation-related driver is loaded, or during Windows shutdown or startup. Keeping track of when and where your STOP error occurs is a critical piece of information in troubleshooting the sprers.eung when CONFIG_INITIALIZATION_FAILED STOP errors happen is paramount in finding the cause of the Windows-related problems and reporting them to Microsoft Corporation for help.


Origins of CONFIG_INITIALIZATION_FAILED Troubles

CONFIG_INITIALIZATION_FAILED BSOD errors are caused by a variety of firmware, hardware, driver, or software problems. These BSODs can stem from Windows problems, stop error 0x00000067, or issues with Microsoft Corporation-related hardware.

Precisely, CONFIG_INITIALIZATION_FAILED errors stem from:

  • Corrupted, outdated, or wrongly configured device driver (CONFIG_INITIALIZATION_FAILED).
  • Invalid (corrupt) CONFIG_INITIALIZATION_FAILED registry entries related to CONFIG_INITIALIZATION_FAILED / Windows.
  • Malware infestation corrupted CONFIG_INITIALIZATION_FAILED file or associated Windows files.
  • New Microsoft Corporation-related hardware install creating CONFIG_INITIALIZATION_FAILED conflicts.
  • Damaged system files (eg. CONFIG_INITIALIZATION_FAILED) after failed driver or Windows install.
  • CONFIG_INITIALIZATION_FAILED blue screen caused by a damaged hard disk.
  • CONFIG_INITIALIZATION_FAILED STOP error due to memory (RAM) corruption.

Product by Solvusoft


Download Now
WinThruster - Scan your PC for computer errors.

Compatible with Windows 11, 10, 8, stop error 0x00000067, 7, Vista, XP and

Optional Offer for WinThruster by Solvusoft

How to Fix “CONFIG_INITIALIZATION_FAILED” (0x) BSOD Error?

Does your Windows-operated laptop or desktop computer show a blue screen? Does it restart after flashing the message «CONFIG_INITIALIZATION_FAILED» (0x)? Looking for a way to fix 0x "CONFIG_INITIALIZATION_FAILED"?

Causes of The Error

  • There is not enough free space in the hard disk of your computer/laptop. For Windows 10 to operate correctly you need to have from 2 to 10 Gb of free space in your system disk.

  • An incompatible version of BIOS was installed or the firmware was damaged.

  • Device drivers incompatible with the OS were installed.

  • Windows registry stop error 0x00000067 damaged or deleted, or cleaning operations accidentally deleted system keys.

  • Antivirus software or viruses may block system files or delete important registry keys.

  • An error occurred in the work of backup software.

  • It can also stop error 0x00000067 as a result of a Windows update.

Read more how to fix 0x "CONFIG_INITIALIZATION_FAILED" in Windows 10, WindowsWindows ServerWindows 8, Windows Home Serverstop error 0x00000067, Windows 7 (Seven), Windows Small Business Server, Windows ServerWindows Home Server, Windows Vista, Windows XP, WindowsWindows NT.

Here are some ways of eliminating the problem with "CONFIG_INITIALIZATION_FAILED":

Restore Deleted Files

Often BSoD errors cause loss of important files. Files blocked by computer viruses, backup software errors, damaged or overwritten system files, file system errors or bad hard disk sectors – these are only some of the causes that can make your data lost.

Corrections of the corresponding errors will restore the normal operation of your devices, but it does not always restore damaged or lost files. Also, it is not always possible to eliminate an error without formatting the hard disk or clean installation of the operating system, which asus gpu tweak error also involve loss of files.

Download for free and scan your device with the help of Hetman Partition Recovery, stop error 0x00000067. Learn about the program features and step-by-step guide.

Start The Stop error 0x00000067 in Safe Mode

If the error "CONFIG_INITIALIZATION_FAILED" (0x) occurs when loading Windows and blocks any attempts to work with the system, try loading the computer in Safe Mode. This mode is meant for operating system (OS) diagnostics, but OS functions are very limited in autoit _inetsmtpmail error 50 mode. Safe Mode should only be used if the system is blocked otherwise.

In order to start Safe Mode you should do the following:

  1. Go to Start menu and choose Settings.

  2. In the settings window that appears go to Update & Security menu and choose the Recovery tab.

  3. In the tab Recovery find Advanced startup and click the button Restart now.

  4. As your Windows restarts, it will ask you to choose the next step. Choose Troubleshoot.

  5. In the Troubleshoot menu click on Advanced Options and then on Startup Settings.

  6. Then Windows will inform you that the computer can be restarted with the use of additional settings one of which is Enable Safe Mode. Press Restart.

  7. After restarting choose Enable Safe Mode by pressing F4.

How to Boot Windows 10 in Safe Mode

Go to view

How to Boot Windows 10 in Safe Mode (All Methods)

Update a Driver With The Device Manager

Have you installed new hardware to your computer? Are you using a new USB device? These can be the causes for the stop error 0x00000067 "CONFIG_INITIALIZATION_FAILED". If you installed your device driver from the disk you have found in the device delivery package or if you are using a driver which was downloaded from a place other than Microsoft official website, this can be the core of the problem. You will have to update the device driver to fix it.

You can do it manually in the Windows device manager by taking the following steps:

  1. Press Windows button and type device manager on the keyboard.

  2. Choose Device Manager from the list.

  3. View the list of device categories and click on the arrow nest to the category in which your new device falls. The driver can be marked with a yellow triangle./p>

  4. Right-click on the device name and press Update Driver Software.

  5. Then a window of Update Driver Software with two options will appear:

    • Search automatically for updated driver software. Windows will automatically check availability of the best suitable driver for this device.

    • Browse my computer for driver software. Use this option to show the Stop error 0x00000067 where the driver files are kept.

Restart the computer after the driver is installed.

Use sfc /scannow To Check All System Files

Damaged or rewritten system files may cause the error "CONFIG_INITIALIZATION_FAILED". The command sfc finds damaged Windows system files and replaces them.

  1. Press Windows button and enter cmd from the keyboard.

  2. Right-click on CMD and launch it as administrator.

  3. In the command prompt window, type in sfc /scannow and press Enter.

This process may take several minutes.

How to Recover Windows 10 System Files

Go to view

How to Recover Windows 10, 8, 7 System Files (SFC, DISM)

Check for Errors The Disk Where Windows Is Installed By Using The Command chkdsk c: pioneer avh 5700 error-02 blue screen with "CONFIG_INITIALIZATION_FAILED" may be caused by a file system error or by bad sectors in your disk. The command CHKDSK will check stop error 0x00000067 disk for file system errors and bad sectors. Using the setting /f will make the program to automatically correct the detected errors, stop error 0x00000067, and the setting /r allows finding and fixing problem disk sectors. To launch it, follow these steps:

  1. Press Windows, then enter CMD from the keyboard.

  2. Right-click on CMD and launch it as administrator.

  3. In the command prompt window type chkdsk c: /f and press Enter (use the stop error 0x00000067 of the drive where your OS is installed).

Wait until the process is over and restart your computer.

Use The Mode of Compatibility With an Old Version of Windows

A error with the code "CONFIG_INITIALIZATION_FAILED" may be caused by outdated software. If this error occurs after launching a program, then using Windows compatibility mode can help you get rid of the problem. To fix it, do the following:

  1. Find a program executable file (it has .exe extension) and right-click on it.

  2. In the quick menu, select Troubleshoot compatibility.

  3. At the next stage, you will see the window Program Compatibility Troubleshooter. Sharks terrors of the deep 2.0 crzck will have two troubleshooting options to choose from:

    • Try recommended settings. Select this variant to start a test run of the program using recommended compatibility settings.

    • Troubleshoot program. Select this variant to choose compatibility settings based on what problems you have encountered.

  4. After testing the program under various versions of Windows and startup settings save the suitable settings for your program.

How to Run a Program in Compatibility Mode With Windows 10, 8 and 7

Go to view

How to Run a Program in Compatibility Mode With Windows 10, stop error 0x00000067, 8 and 7

Disable Unnecessary Programs in Windows Startup Menu

The software causing "CONFIG_INITIALIZATION_FAILED" (0x) may be written to Windows Startup list so the error occurs immediately after the system starts without any user activity. You can delete programs from Startup by using Task Manager.

  1. Load the computer in Safe Mode.

  2. Right-click on Task Bar and then on Task Manager.

  3. Go to Startup tab.

  4. To delete a stop error 0x00000067 from the startup list select it and disable by clicking Disable in the right lower corner of the window.

Consult Microsoft Support Service

Microsoft offers several solutions to eliminate the blue screen error. "CONFIG_INITIALIZATION_FAILED" (0x) can be fixed with the help of Windows Update or by addressing Windows Support.

  1. Go to Microsoft Support Service.

  2. Enter your error code and message into the search field and follow the directions.

  3. If you don’t find a ready solution as the community where your query can be answered by a certified system stop error 0x00000067 Latest System Updates

    Windows provides updates that extend your driver database and correct errors or security vulnerabilities. Download the latest updates to get rid of the error "CONFIG_INITIALIZATION_FAILED" (0x).

    You can launch Windows Update like this:

    1. Go to Start menu and select Settings.

    2. In the Settings window go to Update and Security tab.

    3. To install the latest Windows updates click on Check for updates and wait until they are found and installed.

    It is recommended to stop error 0x00000067 up automatic download and installation of system updates with the help of Advanced Options.

    To enable automatic system update you need to start Windows Update:

    1. Go to Start menu and choose Settings.

    2. In the Settings window go to the Update and Security menu and select Windows Update. To install the latest Windows updates click on Check for updates and wait until they are found and installed.

    3. Go to Advanced Options and choose the mode of update installation - Automatic.

    Scan The System For Viruses

    The blue screen of death with the error "CONFIG_INITIALIZATION_FAILED" 0x can be caused by computer viruses that infected your system.

    To check the computer for viruses launch your antivirus program.

    Modern antiviruses allow checking both hard disks and RAM. Run a full system scan.

    Test Your RAM

    System memory problems may stop error 0x00000067 errors, loss of data or even make your computer stop working.

    Before you start checking RAM, take it out of the slot on the motherboard and then stick it back again. Sometimes the error "CONFIG_INITIALIZATION_FAILED" can be caused by the memory stick which was set into the slot incorrectly or not tight enough, and sometimes by the slot contacts covered with dust.

    If the above actions did not make things better, you can check your RAM with the means of your operating system – Windows Memory Diagnostic.

    JYou can start this tool in two ways:

    1. With the help of Control Panel:

      Go to Control Panel / System and Security / Administrative Tools. Launch the application Windows Memory Diagnostic.

    2. With the use of Run:

      Launch the Run tool with the combination of keys Windows + R. Type in mdsched and press Enter. The Windows Diagnostic tool will start.

    To start the checking select one of the suggested variants to decide how your RAM will be tested after the computer is restarted.

    If the diagnostic tool finds errors that cannot be corrected, such memory should be replaced (that is, stop error 0x00000067 have to replace the memory stick where errors were found).

    Make a Clean Installation of Windows

    If none of the methods helped you to get rid of "CONFIG_INITIALIZATION_FAILED", stop error 0x00000067, try reinstalling Windows. In order to make a clean installation of Windows you need to create a setup disk or another stop error 0x00000067 which you are going to use to install the OS.

    Start the computer with the setup disk. To do it you may need to change boot priority in BIOS or UEFI for newer computers.

    Following the installer menu stages, specify the disk where you want your Windows installed. You will have to format it then, stop error 0x00000067. If you are stop error 0x00000067 satisfied with the number or size of the local disks they can be deleted and repartitioned.

    Remember that formatting, deleting or partitioning your disks will destroy all files in the hard disk.

    After specifying the disk to install Windows to, the process of copying system files and installing the operating system will start. During the installation, no additional action is required. In the process, the screen will go off for a while several times, and the computer will restart on its own to complete certain stages of installation.

    Depending on the version of Windows at one of the stages you may have to select or enter basic personalization settings, choose how the computer works with networks and select settings of your account or create a new one.

    As the computer loads the desktop, a clean installation of Windows is finished.

    Note. Before you start a clean installation of Stop error 0x00000067 make sure you have drivers for all your hardware and that your files are safe. Download and save drivers to a separate media, stop error 0x00000067, and create a backup copy of important data.

    How to Reset Windows 10 or 8 PC to Factory Default Settings

    Go to view

    How to Reset Windows 10 or 8 PC to Factory Default Settings (All Methods)

    How to Reset Windows 10 or 8 PC If The Operating System Won't Boot

    Go to view

    How to Reset Windows 10 or 8 PC If The Operating System Won't Boot

Stop error 0x00000067 - think

How to Fix “CONFIG_INITIALIZATION_FAILED” (0x) BSOD Error?

Does your Windows-operated laptop or desktop computer show a blue screen? Does it restart after flashing the message «CONFIG_INITIALIZATION_FAILED» (0x)? Looking for a way to fix 0x "CONFIG_INITIALIZATION_FAILED"?

Causes of The Error

  • There is not enough free space in the hard disk of your computer/laptop. For Windows 10 to operate correctly you need to have from 2 to 10 Gb of free space in your system disk.

  • An incompatible version of BIOS was installed or the firmware was damaged.

  • Device drivers incompatible with the OS were installed.

  • Windows registry was damaged or deleted, or cleaning operations accidentally deleted system keys.

  • Antivirus software or viruses may block system files or delete important registry keys.

  • An error occurred in the work of backup software.

  • It can also happen as a result of a Windows update.

Read more how to fix 0x "CONFIG_INITIALIZATION_FAILED" in Windows 10, Windows , Windows Server , Windows 8, Windows Home Server , Windows 7 (Seven), Windows Small Business Server, Windows Server , Windows Home Server, Windows Vista, Windows XP, Windows , Windows NT.

Here are some ways of eliminating the problem with "CONFIG_INITIALIZATION_FAILED":

Restore Deleted Files

Often BSoD errors cause loss of important files. Files blocked by computer viruses, backup software errors, damaged or overwritten system files, file system errors or bad hard disk sectors – these are only some of the causes that can make your data lost.

Corrections of the corresponding errors will restore the normal operation of your devices, but it does not always restore damaged or lost files. Also, it is not always possible to eliminate an error without formatting the hard disk or clean installation of the operating system, which can also involve loss of files.

Download for free and scan your device with the help of Hetman Partition Recovery. Learn about the program features and step-by-step guide.

Start The Computer in Safe Mode

If the error "CONFIG_INITIALIZATION_FAILED" (0x) occurs when loading Windows and blocks any attempts to work with the system, try loading the computer in Safe Mode. This mode is meant for operating system (OS) diagnostics, but OS functions are very limited in this mode. Safe Mode should only be used if the system is blocked otherwise.

In order to start Safe Mode you should do the following:

  1. Go to Start menu and choose Settings.

  2. In the settings window that appears go to Update & Security menu and choose the Recovery tab.

  3. In the tab Recovery find Advanced startup and click the button Restart now.

  4. As your Windows restarts, it will ask you to choose the next step. Choose Troubleshoot.

  5. In the Troubleshoot menu click on Advanced Options and then on Startup Settings.

  6. Then Windows will inform you that the computer can be restarted with the use of additional settings one of which is Enable Safe Mode. Press Restart.

  7. After restarting choose Enable Safe Mode by pressing F4.

How to Boot Windows 10 in Safe Mode

Go to view

How to Boot Windows 10 in Safe Mode (All Methods)

Update a Driver With The Device Manager

Have you installed new hardware to your computer? Are you using a new USB device? These can be the causes for the error "CONFIG_INITIALIZATION_FAILED". If you installed your device driver from the disk you have found in the device delivery package or if you are using a driver which was downloaded from a place other than Microsoft official website, this can be the core of the problem. You will have to update the device driver to fix it.

You can do it manually in the Windows device manager by taking the following steps:

  1. Press Windows button and type device manager on the keyboard.

  2. Choose Device Manager from the list.

  3. View the list of device categories and click on the arrow nest to the category in which your new device falls. The driver can be marked with a yellow triangle./p>

  4. Right-click on the device name and press Update Driver Software.

  5. Then a window of Update Driver Software with two options will appear:

    • Search automatically for updated driver software. Windows will automatically check availability of the best suitable driver for this device.

    • Browse my computer for driver software. Use this option to show the OS where the driver files are kept.

Restart the computer after the driver is installed.

Use sfc /scannow To Check All System Files

Damaged or rewritten system files may cause the error "CONFIG_INITIALIZATION_FAILED". The command sfc finds damaged Windows system files and replaces them.

  1. Press Windows button and enter cmd from the keyboard.

  2. Right-click on CMD and launch it as administrator.

  3. In the command prompt window, type in sfc /scannow and press Enter.

This process may take several minutes.

How to Recover Windows 10 System Files

Go to view

How to Recover Windows 10, 8, 7 System Files (SFC, DISM)

Check for Errors The Disk Where Windows Is Installed By Using The Command chkdsk c: /f

The blue screen with "CONFIG_INITIALIZATION_FAILED" may be caused by a file system error or by bad sectors in your disk. The command CHKDSK will check the disk for file system errors and bad sectors. Using the setting /f will make the program to automatically correct the detected errors, and the setting /r allows finding and fixing problem disk sectors. To launch it, follow these steps:

  1. Press Windows, then enter CMD from the keyboard.

  2. Right-click on CMD and launch it as administrator.

  3. In the command prompt window type chkdsk c: /f and press Enter (use the letter of the drive where your OS is installed).

Wait until the process is over and restart your computer.

Use The Mode of Compatibility With an Old Version of Windows

A error with the code "CONFIG_INITIALIZATION_FAILED" may be caused by outdated software. If this error occurs after launching a program, then using Windows compatibility mode can help you get rid of the problem. To fix it, do the following:

  1. Find a program executable file (it has .exe extension) and right-click on it.

  2. In the quick menu, select Troubleshoot compatibility.

  3. At the next stage, you will see the window Program Compatibility Troubleshooter. You will have two troubleshooting options to choose from:

    • Try recommended settings. Select this variant to start a test run of the program using recommended compatibility settings.

    • Troubleshoot program. Select this variant to choose compatibility settings based on what problems you have encountered.

  4. After testing the program under various versions of Windows and startup settings save the suitable settings for your program.

How to Run a Program in Compatibility Mode With Windows 10, 8 and 7

Go to view

How to Run a Program in Compatibility Mode With Windows 10, 8 and 7

Disable Unnecessary Programs in Windows Startup Menu

The software causing "CONFIG_INITIALIZATION_FAILED" (0x) may be written to Windows Startup list so the error occurs immediately after the system starts without any user activity. You can delete programs from Startup by using Task Manager.

  1. Load the computer in Safe Mode.

  2. Right-click on Task Bar and then on Task Manager.

  3. Go to Startup tab.

  4. To delete a program from the startup list select it and disable by clicking Disable in the right lower corner of the window.

Consult Microsoft Support Service

Microsoft offers several solutions to eliminate the blue screen error. "CONFIG_INITIALIZATION_FAILED" (0x) can be fixed with the help of Windows Update or by addressing Windows Support.

  1. Go to Microsoft Support Service.

  2. Enter your error code and message into the search field and follow the directions.

  3. If you don’t find a ready solution as the community where your query can be answered by a certified system administrator.

Install Latest System Updates

Windows provides updates that extend your driver database and correct errors or security vulnerabilities. Download the latest updates to get rid of the error "CONFIG_INITIALIZATION_FAILED" (0x).

You can launch Windows Update like this:

  1. Go to Start menu and select Settings.

  2. In the Settings window go to Update and Security tab.

  3. To install the latest Windows updates click on Check for updates and wait until they are found and installed.

It is recommended to set up automatic download and installation of system updates with the help of Advanced Options.

To enable automatic system update you need to start Windows Update:

  1. Go to Start menu and choose Settings.

  2. In the Settings window go to the Update and Security menu and select Windows Update. To install the latest Windows updates click on Check for updates and wait until they are found and installed.

  3. Go to Advanced Options and choose the mode of update installation - Automatic.

Scan The System For Viruses

The blue screen of death with the error "CONFIG_INITIALIZATION_FAILED" 0x can be caused by computer viruses that infected your system.

To check the computer for viruses launch your antivirus program.

Modern antiviruses allow checking both hard disks and RAM. Run a full system scan.

Test Your RAM

System memory problems may cause errors, loss of data or even make your computer stop working.

Before you start checking RAM, take it out of the slot on the motherboard and then stick it back again. Sometimes the error "CONFIG_INITIALIZATION_FAILED" can be caused by the memory stick which was set into the slot incorrectly or not tight enough, and sometimes by the slot contacts covered with dust.

If the above actions did not make things better, you can check your RAM with the means of your operating system – Windows Memory Diagnostic.

JYou can start this tool in two ways:

  1. With the help of Control Panel:

    Go to Control Panel / System and Security / Administrative Tools. Launch the application Windows Memory Diagnostic.

  2. With the use of Run:

    Launch the Run tool with the combination of keys Windows + R. Type in mdsched and press Enter. The Windows Diagnostic tool will start.

To start the checking select one of the suggested variants to decide how your RAM will be tested after the computer is restarted.

If the diagnostic tool finds errors that cannot be corrected, such memory should be replaced (that is, you have to replace the memory stick where errors were found).

Make a Clean Installation of Windows

If none of the methods helped you to get rid of "CONFIG_INITIALIZATION_FAILED", try reinstalling Windows. In order to make a clean installation of Windows you need to create a setup disk or another media which you are going to use to install the OS.

Start the computer with the setup disk. To do it you may need to change boot priority in BIOS or UEFI for newer computers.

Following the installer menu stages, specify the disk where you want your Windows installed. You will have to format it then. If you are not satisfied with the number or size of the local disks they can be deleted and repartitioned.

Remember that formatting, deleting or partitioning your disks will destroy all files in the hard disk.

After specifying the disk to install Windows to, the process of copying system files and installing the operating system will start. During the installation, no additional action is required. In the process, the screen will go off for a while several times, and the computer will restart on its own to complete certain stages of installation.

Depending on the version of Windows at one of the stages you may have to select or enter basic personalization settings, choose how the computer works with networks and select settings of your account or create a new one.

As the computer loads the desktop, a clean installation of Windows is finished.

Note. Before you start a clean installation of Windows make sure you have drivers for all your hardware and that your files are safe. Download and save drivers to a separate media, and create a backup copy of important data.

How to Reset Windows 10 or 8 PC to Factory Default Settings

Go to view

How to Reset Windows 10 or 8 PC to Factory Default Settings (All Methods)

How to Reset Windows 10 or 8 PC If The Operating System Won't Boot

Go to view

How to Reset Windows 10 or 8 PC If The Operating System Won't Boot

Contact US

INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Thanks. We have received your request and will respond promptly.

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!

  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Us!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Tek-Tips Posting Policies

Contact US

stop error 0x after installation

stop error 0x after installation

proudusa(MIS)

(OP)

I'm installing windows on a system i'm building.   After the installation i'm getting the blue screen mentioned above.    I've checked the video card (SiS) and NIC (linksys LNE) and both are compatible with 2K.   I'm changed the controller cables.   From what i've been able to find the error message pertains to bad scsi termination (doesn't apply), bad controller (replaced) or something to do with the DIP switches on the drive.

Has anyone else run into this problem?

thanks

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Windows error 0x,

Detailed Error Information

TOO_MANY_SEM_REQUESTS[1]

MessageThe semaphore cannot be set again.
Declared inwinerror.h

This appears to be a raw Win32 error. More information may be available in error 0x

CONFIG_INITIALIZATION_FAILED[2]

This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0x CONFIG_INITIALIZATION_FAILED.

HRESULT analysis[3]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.

FlagsSeveritySuccess

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x)
NameFACILITY_NULL[3][1]
DescriptionThe default facility code.[3][1]
Error Code (0x)

Questions

Disable .rodata indirection for local constants

When i have local data defined inside a function, it gets placed into .rodata section. This means that .text section will contain relative reference (//1) to an absolute address (//2) inside the .text, which in turn points to the data (//3) inside .rodata. int function() { int a[] = {97, [] read more

HTTP Error - Internal Server Error Django on iis Error Code 0x

I'm trying to makedjango web app work on IIS using wfastcgi Following This guide it gave me the error code 0x enter image description here [sprers.eu] and here is my sprers.eu file : <?xml version="" encoding="UTF-8"?> <configuration> <sprers.euver> <handlers> <add name="AccuManager" path="*" verb="*" modules="FastCgiModule" scriptProcessor="E:\projectInnoventiq\accuManager\venv\Scripts\sprers.eu

General discussion

  • by barry pie · about 18 years, 11 months ago

    The full error code is:

    0x (0x, 0x, 0x, 0x)
    CONFIG_INITIALIZATION_FAILED

    These are win 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.

All Comments

    • Reply To: STOP error 0x

      by maxwell edison · about 18 years, 11 months ago

      In reply to STOP error 0x

      Take a look at this Web site titled, &#;KNOWLEDGE BASE LINKS STOP MESSAGES&#;

      (Cut and paste link):

      sprers.eu

      sprers.eu

      Excerpts from the article:

      STOP Messages literally mean Windows has stopped! These appear only in the NT-based operating systems: Win NT, Win , 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 0xA 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 0x

      (continued&#;)

      • Reply To: STOP error 0x

        by maxwell edison · about 18 years, 11 months ago

        In reply to Reply To: STOP error 0x

        Examine the ?System? and ?Application? logs in Event Viewer for other recent errors that might give further clues. To do this, launch sprers.eu 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&#;)

      • Reply To: STOP error 0x

        by maxwell edison · about 18 years, 11 months ago

        In reply to Reply To: STOP error 0x

        0x CONFIG_INITIALIZATION_FAILED

        0xA: 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:

        sprers.eu?url=/library/en-us/w2kmsgs/asp

        sprers.eu

Bug Check 0x CONFIG_INITIALIZATION_FAILED

  • Article
  • 2 minutes to read

The CONFIG_INITIALIZATION_FAILED bug check has a value of 0x This bug check indicates that the registry configuration failed.

Important

This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

CONFIG_INITIALIZATION_FAILED Parameters

1

Reserved

2

The location selector

3

The NT status code

4

Reserved

Cause

The registry could not allocate the pool that it needed to contain the registry files. This situation should never occur, because the register allocates this pool early enough in system initialization so that plenty of paged pool should be available.

Was: Stop error 0x00000067

ACPI XP ERROR
Bash /usr/bin/tail input/output error
49 SERVICE ERROR
COUNTER STRIKE VP4 TERRORIST MISSIONS
stop error 0x00000067

0 Comments

Leave a Comment