Question about PC Desktops

1 Answer

System will not boot after a windows32 config error

Posted by on

1 Answer

  • Level 3:

    An expert who has achieved level 3 by getting 1000 points

    Superstar:

    An expert that got 20 achievements.

    All-Star:

    An expert that got 10 achievements.

    MVP:

    An expert that got 5 achievements.

  • Master
  • 3,940 Answers

At a minimum, you have a Windows system file error, but very possibly you may be having a hard drive problem.  If you have them available, run diagnostics on the hard drive (Many systems have a link on the F12 or F8 menus, some in the BIOS, and some on resource or support CDs that come with the system.
Assuming the drive passes diagnostics and you have you XP CD handy, boot to the CD, select R to enter Recovery Console.  From there, RUN:  CHKDSK /P and see if you can repair the file system and make the system boot again.  If that fails, boot to the Recovery Console again, run FIXBOOT   If that fails, boot to the Recovery Console again, run FIXMBR
If all those attempts fail, then you can attempt a repair install of XP

Posted on Oct 12, 2008

Add Your Answer

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

1 Answer

Have an hp pavilion 513n that will not boot up. says " . . . windows32/system/config is corrupt or missing" I don't have a restore disc and can't get to a dos prompt


OK if you are using XP and you have a installation disc click this link, if you are using windows 7 and you have a installation disc click this link. Hope it will help you

Jul 04, 2011 | HP Pavilion 513n (P9850A#ABA) PC Desktop

Tip

System Restore Via Recovery Console


<br /> Ever encountered a problem with your computer wherein it gives you an error page saying that a certain file in the registry is missing or corrupt? Unfortunately, with this kind of error, there are times that you are not able to boot into the OS, and therefor you are not able to do a system restore. <br /> If you are using Windows 7 or Vista, you may initiate System Restore via booting into "Repair My Computer" which you can choose via the Advanced Boot Options of Windows. However, what do you do if this does not work, or you are using Windows XP. <br /> Fortunately, there is still a way to be able to restore your system. This involves manually doing the system restore via the recovery console (for XP), and recovery environment (Vista and 7). The only thing that you will need is the OS CD. <br /> Once you have successfully booted into the Recovery Console, type in the commands below and make sure that you press "ENTER" after each line. <br /> <br /> C:\WINDOWS] cd \ C:\] attrib -h-s "system volume information" C:\] Cd "system volume information" C:\system volume information] cd _resto~1 ..._resto~1] dir --- this should list several rp folders [short for restore points] just select second to the last or any of your choice other the the last rp folder ..._resto~1] cd rp# ...rp#] cd snapshot ...snapshot] dir --- the 5 hive files are shown in this format: _registry_machine_software _registry_machine_security _registry_machine_system _registry_machine_sam _registry_user_.default Syntax [Command filename location] ...snapshot] copy _registry_machine_software c:\windows\system32\config\software ...snapshot] copy _registry_machine_system c:\windows\system32\config\system ...snapshot] copy _registry_machine_security c:\windows\system32\config\security ...snapshot] copy _registry_machine_sam c:\windows\system32\config\sam ...snapshot] copy _registry_user_.default c:\windows\system32\config\default ...snapshot] exit <br /> After this, you just need to restart your computer and it should be working fine.

on Jul 25, 2011 | PC Desktops

Tip

Boot problems and their possible causes & resolutions


Symptoms:
Black screen
"Invalid Partition Table"
"Error loading operating system"
"Missing operating system"


Cause:
Corrupt Master Boot Record (MBR)

Resolution:
Boot into Recovery Console and run "fixmbr" to repair the MBR

--

Symptoms:
"A disk read error occurred"
"NTLDR is missing"
"NTLDR is compressed"


Cause:
Corrupt boot sector

Resolution:
Boot into Recovery Console and run "fixboot" to repair the boot sector

--

Symptoms:
"BOOT.INI is missing or corrupt"
"Boot device inaccessible"
"Windows could not start because the following file is missing or corrupt:
<Windows root>\system32\hal.dll"


Cause:
BOOT.INI missing, corrupt or out of date as a partition has been inserted

Resolution:
Boot into Recovery Console and run "bootcfg /rebuild" to repair the BOOT.INI

--

Symptoms:
"Windows could not start not start because the following file is missing or corrupt:
\WINDOWS\SYSTEM32\CONFIG\SYSTEM"


Cause:
Corrupt/missing system hive

Resolution:
1. Boot into Recovery Console and run "chkdsk C: /f" to check the system disk for errors and fix them, then reboot.
2. If the error continues and System Restore is enabled, copy the system hive from the last restore point into \WINDOWS\SYSTEM32\CONFIG
3. If the error continues, copy the system hive from \WINDOWS\REPAIR into \WINDOWS\SYSTEM32\CONFIG
4. If the error continues, perform a repair installation by booting from the Windows installation media


--

Symptoms:
"Windows could not start because of a computer disk hardware configuration problem.
Could not read from the selected boot disk, Check boot path and disk hardware."


Cause:
Boot volume (with Windows folder) is not accessible as defined in BOOT.INI

Resolution:
Check the boot volume is accessible

--

Symptoms:
Dual-boot 32-bit Windows and 64-bit Windows system reports "NTOSKRNL.EXE is corrupt" trying to boot into 64-bit Windows

Cause:
System volume contains an older boot loader than the boot volume requires - e.g. XP SP2 installed after XP x64

Resolution:
Copy NTDETECT.COM and NTLDR from XP x64 installation media to the root of the system volume

on May 03, 2010 | PC Desktops

1 Answer

Stack overflow at line 598


Stacks are reserved memory that programs use to process hardware events. A stack overflow occurs when there is not enough space in memory to run the hardware interrupt routines. To resolve these behaviors, you can modify the "STACKS=" line in the Config.sys file, eliminate terminate-and-stay-resident program (TSRs), and eliminate hardware conflicts.

When Windows delivers an error message that is related to an internal stack overflow, there is not enough space in memory either set aside or available to handle the calls that are made to the computer hardware. There are several things to consider when you troubleshoot this behavior:
  1. The Config.sys startup file may not be properly configured for the Windows installation. Use the following values: STACKS=64,512 ;(this is the maximum allowed)
    FILES=60
    BUFFERS=40 If you are using the dual-boot capabilities in Windows, the Config.sys and Autoexec.bat files may not contain the correct configuration to run Windows. When you are dual-booting between Windows 3.x and Windows, these files may not have been renamed back to Config.dos and Autoexec.dos.

    Examine the Config.sys file to determine if files such as Himem.sys or Emm386.exe are loaded from a folder other than the Windows folder. If so, boot Windows by using the Safe Mode Command Prompt Only option. Rename the Config.sys file to Config.dos and the Autoexec.bat file to Autoexec.dos, and then restart your computer.
  2. Some TSRs may be interfering with Windows. Disable any non-boot device drivers in the Config.sys and Autoexec.bat files. If you install from Windows 3.x and you receive a stack overflow error message, check the Win.ini and System.ini files for non-Windows-based programs or drivers that are loading.
  3. There may be an incompatible hardware configuration. Check the port and IRQ settings of the network adapter, sound card, and modem. Make sure that there are no COM2/COM4 or COM1/COM3 conflicts and that no devices are sharing IRQs. Disable or remove conflicting devices.
  4. The computer may need a BIOS upgrade. Check the BIOS version and contact the manufacturer of your computer for information about a BIOS upgrade.

Hope this helps. Please rate my response.
Thanks.
Have a good day

Dec 28, 2010 | Microsoft PC Desktops

1 Answer

OptiPlex 760 PC Desktop: Boots with this error: Windows could not start bec...


reinstall windows xp pro. in different folder
and keep all the files

May 18, 2010 | Dell OptiPlex 760 PC Desktop

4 Answers

My desktop shut down and is asking me to re install a 32 windows file. What is this and how do I fix it?


Hi, This normally means that a windows file from the system32 folder is missing or corrupt. You will have repair that by using your operating system cd and go to repair when prompted. If this does not work you may have to install a clean copy of your operating system.

Apr 10, 2010 | HP Pavilion a1220n (A1220NED904AA) PC...

1 Answer

\windows\system32\config\system


If your computer doesn't boot and displays this error your registry is corrupt and likely our HDD may be failing. Backup your files if you have important data by using a live disc such as Ultimate Boot CD and follow the steps here to fix your problem.Let me know if I can be of more help

Nov 10, 2008 | PC Desktops

Not finding what you are looking for?
PC Desktops Logo

Related Topics:

131 people viewed this question

Ask a Question

Usually answered in minutes!

Top PC Desktops Experts

joecoolvette
joecoolvette

Level 3 Expert

5660 Answers

Brian Sullivan
Brian Sullivan

Level 3 Expert

27725 Answers

Les Dickinson
Les Dickinson

Level 3 Expert

18297 Answers

Are you a PC Desktop Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...