Rick Selby's Microsoft Windows XP Error Codes Help Page

Outlook 2002 & 2003 Outlook & Outlook Express Import & Export Outlook Express Files Export Outlook Express to Windows Live Mail Hotmail More E-mail Problems

Microsoft Shortcut Key and Office Shortcut Keys Microsoft XP Shortcut Keys

Window Media Player Hyper Links & Shortcuts Printing Favorite Links

"In God" † Prayer Requests † Jesus Help Page † Tribute to Sept. 11, 2001
"Christian" Merchandise † "If You Were The Father"
"Colon-Liver Cancer, God, My Story"

Think Adoption, NOT Abortion
If this site helped you, please make a donation to:

Feeding families around the world…and the corner.

Revelation 3:3 "Remember therefore how thou hast received and heard, and hold fast, and repent. If therefore thou shalt not watch, I will come on thee as a thief, and thou shalt not know what hour I will come upon thee"

"Of the People, by the people, for the people."
Not any more in the USA.
Now it is Of the people, by the government, for the government, big corporations, and rich.

ITS TIME FOR THE PEOPLE TO TAKE BACK AMERICA,
VOTE THE POLITICIANS OUT AND PUT IN GOOD PEOPLE WHO
CAN'T BE BOUGHT BY THE BIG CORPORATIONS AND RICH.
Read More, Politicians Running Wild

Windows XP Error Codes

Site Visitors

To find a topic on this page, Click Edit on the Toolbar, Find (on this page), type in keyword

you will not be able to find drivers for your hardware at this time.

Vista drivers

This is another repeat of XP SP 2.

Three things to remember when you are working with computers.

First thing is "YOU CAN DO IT".
Second take your time, a little mistake can cause a big problem.
Third all answers are only a question away.

TABLE OF CONTENTS

If you are experiencing computer Problems such as slowness, strange icons appearing, tool bars appearing, home page changing, please use one of the following links to check for a virus or trojan.

Panda Virus Free Online Virus Scan
AVG Anti-virus Program (FREE)
- AVG is a great "FREE" program and I used to keep a link to the download but they keep changing it all the time and I can't keep this link up to date so Google "Download AVG Free" to get the download link. SORRY!

ALSO Check the

XP Error Massage Page

if you can't find it here.

XP Error Codes

Installing Errors

Internet Connections Errors

Error 678 Or Error 769
"Error 629, 640, 691 or 734" Error Message When You Try to Connect to Your ISP
Error Message: Error 633 Modem Is Already in Use
Error Message "Error 633" When Starting Broadband Connection

The TCP/IP network transport is not installed

Hibernation Errors

Windows XP Generates a "Stop 0xA0" Error Message During Hibernation

Media Player Error Codes and Solutions

Media Codes

Memory Error

Ntkrnlmp.exe Could Not Be Loaded Error Code 7 Error Message

Misc.

Stop 0x24 or NTFS_FILE_SYSTEM Error Messages
Stop 0xC2
BAD_POOL_CALLER

Outlook Express Errors

Outlook Express error message "Method Not Allowed" and error " 0x800CCC35"
Outlook Express Error 0x800ccc92 (0x800CCC90, Error Number: 0x800CCC92)

Setup Errors

During install, an Error occurs: Error 1335 The cabinet file Data.cab required for this install is corrupt.
Error 2350 When You Installing A Program
The file I386\L_intl.nlf could not be loaded. The error code is 7. As a result, you cannot install Windows
Ntkrnlmp.exe Could Not Be Loaded Error Code 7 Error Message
Error 1311, Source File Not Found
"Error 1304: Error Writing to the File" When You Install Office XP-03 or Office 2000
"Error 1304 Or Error 27000 When You Try To Install Microsoft Plus! Digital Media Edition
Error 1304: Error writing to file X.inf
Error Code: 0x80070002" error message cites license-checking issue after upgrade on Dell computer
"STOP 0x0000001E" Error Message During Windows Setup
A Stop: 0xc000026C or Stop: 0xc0000221 "Unable to Load Device Driver" Error Occurs When You Start Windows XP

Shutdown Errors

Stop 0x000000D1 Error Message When You Turn Your Computer Off

Stop Error Messages

Stop 0x24 or NTFS_FILE_SYSTEM Error Messages
Troubleshoot "Stop 0x0000007B" Errors in Windows XP
Troubleshooting a Stop 0x9F Error in Windows XP
Windows XP Generates a "Stop 0xA0" Error Message During Hibernation
"Stop 0x000000EA" Error Message When You Run Video-Intensive Programs
"STOP 0x000000ED UNMOUNTABLE_BOOT_VOLUME" Error Message During Windows XP Upgrade
Stop 0x000000ED Error Message When Volume on IDE Drive with Caching Enabled Is Mounted
Stop 0x000000D1 Error Message When You Turn Your Computer Off
"STOP 0x0000001E" Error Message During Windows Setup
"STOP: C0000221 Unknown Hard Error" or "STOP: C0000221 STATUS_IMAGE_CHECKSUM_MISMATCH" Error Message Occurs
A Stop: 0xc000026C or Stop: 0xc0000221 "Unable to Load Device Driver" Error Occurs When You Start Windows XP

Video Error Messages

"Stop 0x000000EA" Error Message When You Run Video-Intensive Programs

Update or Upgrade Error Messages

"Error 1603: A Fatal Error Occurred During Installation"

Error Message

When you try to install a Microsoft Windows Installer package, you may receive the following error message

Cause

You may receive this error message if any one of the following conditions is true:
- The folder that you are trying to install the Windows Installer package to is encrypted.
- The drive that contains the folder that you are trying to install the Windows Installer package to is accessed as a substitute drive.
- The SYSTEM account does not have Full Control permissions on the folder that you are trying to install the Windows Installer package to. You notice the error message because the Windows Installer service uses the SYSTEM account to install software

Solution

To resolve this problem, use one of the following, depending on the cause of the problem:
- Install the package to a folder that is not encrypted
  - Use this method if you receive the error message because you try to install the Windows Installer package to a folder that is encrypted
- Install the package to a drive that is not accessed as a substitute drive
  - Use this method if you receive the error message because the drive that contains the folder that you try to install the Windows Installer package to is accessed as a substitute drive
- Grant Full Control permissions to the SYSTEM account. (For Windows 2000 and Windows XP only)
  - Use this method if you receive the error message because the SYSTEM account does not have Full Control permissions on the folder that you try to install the Windows Installer package to.
    - To grant Full Control permissions to the SYSTEM account, follow these steps:
      - On the Windows desktop, double-click My Computer. The My Computer window appears.
      - Right-click the drive that you want to install the Windows Installer package
      - Click Properties.
      - Click the Security tab.
      - On the Security tab, do the following:
        
        If you are using Microsoft Windows 2000, verify that the Name box contains the SYSTEM user account
        
        If you are using Microsoft Windows XP, verify that the Group or user names box contains the SYSTEM user account
        
        If the SYSTEM user account does not appear in the box, follow these steps to add the SYSTEM account to the box:
        
        Click Add. The Select Users or Groups dialog box appears
        
        In the Name field, click SYSTEM
        
        Click Add.
        
        Click OK
        
        In the Permissions section, click to select the Full Control check box under Allow
        
        Click Advanced.
        
        Do the following:
        
        If you are using Windows XP, in the dialog box that appears, click to select the Replace permission entries on all child objects with entries shown here that apply to child objects check box for the SYSTEM account
        
        Click OK
        
        If you are not using Windows XP, in the dialog box that appears, click to select the Reset permissions on all child objects and enable propagation of inheritable permissions check box for the SYSTEM account
        
        Click OK.
        
        Note: If you receive a security message, click Yes
        
        Wait for the operating system to apply the permissions that you have selected to all child folders.
        
        Run the Windows Installer package

Windows XP Generates a "Stop 0xA0" Error Message During Hibernation

When you try to hibernate a Windows XP-based computer, you may receive a "Stop 0xA0" error message on a blue screen.

To resolve this problem, obtain the latest service pack for Windows XP

"Stop 0x000000EA" Error Message When You Run Video-Intensive Programs

Error Message

When you run a video-intensive program, such as a movie or a video game, you may receive one of the following stop error messages and bugcheck information:
Note that the four parameters after the stop code may be different.

Cause

This problem occurs because your computer has an Nvidia video card installed that uses the Nv4.sys video driver.
To see if your system is using one of these drivers use the following procedure: .
- Open Device Manager.
- Under the Display Adapters icon, click to highlight the display adapter, right-click it, and then click Properties.
- Under the Driver tab, press the Driver Details button to view the driver names.
- If you have multiple display adapters, repeat these steps for each adapter.
If you have multiple Adapters in your system, it may be necessary to capture a memory dump and have it analyzed by Microsoft Product Support to determine which video adapter driver is at fault.

Resolution

To resolve this problem, obtain an updated driver by contacting your video card manufacturer, or visit the following Nvidia Web site:

Stop 0x000000ED Error Message When Volume on IDE Drive with Caching Enabled Is Mounted

Error Message

When you use volumes that use the NTFS file system on integrated device electronics (IDE) drives with caching enabled, you may receive the following error message during startup:
The normal recovery process in such a case is to run the chkdsk /r command from Recovery Console, and then continue. On OEM versions of Windows XP, the Recovery Console may not be accessible. If this fix has not been included in the OEM build of Windows XP, you may not be able to enter Recovery Console and run the chkdsk /r command for recovery.

Cause

Because of the write-pattern optimization in IDE disk drives, the caching routines sometimes write data out of order to keep drive write speeds at the fastest possible level depending on where data is located on the disk. This opens a timing window where the NTFS disk system could have critical tables damaged if a write is not finished. Microsoft has recommended in the past that caching on IDE drives be turned off on programs with somewhat critical data that is stored on the disk or for situations that allow the slight drop in overall speed. Programs with critical data may need to use SCSI drives, which have better control of data transactions.

Resolution

To resolve this problem, obtain the latest service pack for Windows XP.
To resolve this problem, obtain the following update from the Microsoft Windows Update Web site:

Stop 0x000000D1 Error Message When You Turn Your Computer Off

Error Message

When you shut down your computer that has one or more universal serial bus (USB) devices attached to it, you may receive the following error message on a blue screen:

Resolution

To resolve this problem, obtain the latest service pack for Windows XP.
The English version of this fix should have the following file attributes or later:

"STOP: C0000221 Unknown Hard Error" or "STOP: C0000221 STATUS_IMAGE_CHECKSUM_MISMATCH" Error Message Occurs

Error Message

You may receive any of the following STOP error messages:
-or-
-or-

Cause

This problem can occur if the file that is described in the error message is corrupted. The following files are checked for integrity when Windows starts: "
- All driver files (except those that are loaded by the system loader to start the computer)"
- All dynamic-link libraries (DLLs), including User, Graphics Device Interface (GDI), Shell, Kernel, Ntdll, Crtdll, and so on.
This problem can occur if you install an inappropriate driver for your hardware.

Resolution

To resolve this issue, either obtain a new copy of the corrupted file or reinstall Windows. If continue to receive any of the error messages that are described in the "Summary" section of this article after you reinstall Windows, a hardware or network problem may exist.

Outlook Express Error 0x800ccc92 (0x800CCC90, Error Number: 0x800CCC92)

Error Message

You may get the following error message

Solution

Check your Outlook Express settings, making sure that the POP3 and SMTP servers are entered correctly, and that your full username and password are correct.
If you are still having problems, it could be that your password has somehow become corrupted.
Try creating a new profile.
If the new profile works you can import E-mail messages from old profile to new profile, then delete old profile.

Troubleshooting a Stop 0x9F Error in Windows XP

Error Message

STOP 0x0000009F DRIVER_POWER_STATE_FAILURE

Resolution

To resolve the error and prevent the error from recurring, update or remove the offending driver. This error can occur because of a device driver, but it can also occur because of a file system filter driver (for example, a driver that is installed by an anti-virus, remote control, or backup program).
To isolate the driver that is causing the error, follow these steps:
- Check to make sure that your computer and all installed devices are on the Hardware Compatibility List (HCL). You can view the HCL at the following Microsoft Web site:
- Check for drivers that are not designed for use with Windows. You can use the Sigverif.exe tool to do this.
- Check for driver updates that may be available for your hardware.
- Update any software that uses filter drivers (for example, anti-virus, remote control, and backup software).
- Remove any non-critical devices and software to help isolate the device or software that is causing the error.
- Install Windows in a new folder. Add drivers one by one, and restart the computer after each addition, to try to locate the driver that is causing the error.

Windows XP Generates a "Stop 0xA0" Error Message During Hibernation

Error Message

When you try to hibernate a Windows XP-based computer, you may receive a

Cause

If an integrated device electronics (IDE) time-out occurs during the hibernation process, the Atapi driver does not wait long enough for the primary IDE drive to come online.

Resolution

To resolve this problem, obtain the latest service pack for Windows XP.

Error Message: System Restore Cannot Run Until You Restart the Computer

Error Message

System Restore cannot run until you restart the computer. Please restart the computer, and then run System Restore again.

Resolution

To resolve this issue, restart the computer. If the error still occurs, search the hard drive for the presence of the Wininit.ini file, and then rename it. To do so, follow these steps:
- Restart your computer in Safe or DOS Mode.
- Click Start
- Point to Search
- Click For Files or Folders.
- In the Named box, type
- In the Look in box, click Local hard drives
- Click Find Now.
- Right-click the Wininit.ini file,
- Click Rename
- Type
- Click OK.
- Close the Find Files window, and then run System Restore again.
If the previous steps do not resolve the problem, run the following command to repair the damaged portions of your registry:

Encrypt Your Data to Keep It Safe
Encrypting Folders

To encrypt a file or folder

Open Windows Explorer
Click Start
Point to All Programs
Point to Accessories
Click Windows Explorer
Right-click the file or folder that you want to encrypt
Click Properties.
On the General tab, click Advanced.
Select the Encrypt contents to secure data check box.
Files or folders that are compressed cannot also be encrypted. If you encrypt a compressed file or folder, that file or folder will be uncompressed.
Files marked with the System attribute cannot be encrypted, nor can files in the systemroot directory structure.

To decrypt a file or folder

Open Windows Explorer.
Right-click the encrypted file or folder
Click Properties.
On the General tab, click Advanced.
Clear the Encrypt contents to secure data check box.

Error Message: Error 633 Modem Is Already in Use

Error Message

This behavior may occur when another device with a driver that is incompatible with Windows XP is in conflict with the modem. For example, this problem can occur with outdated Palm Pilot software.
When you try to use your modem on a Windows XP-based computer, you may receive an error message similar to the following:

Solution

In safe mode, remove all the modem drivers, and then restart the computer.
Windows will redetect the modem.
Click Start
Click Control Panel
Click Add or Remove Program.
Click the incompatible software, for example, Palm Desktop and Synchronization Software
Click Change/Remove
Follow the steps to remove the software.

Error Message "Error 633" When Starting Broadband Connection

Error Message
- When you attempt to make a broadband connection, you may receive the following error message:
Solution
- To resolve this behavior, you must disconnect the existing broadband connection to establish the new connection. You must only have one broadband connection that is active.

"Error 629, 640, 691 or 734" Error Message When You Try to Connect to Your ISP

161986

Error Messages

When you attempt to connect to your Internet service provider (ISP), you may receive one of the following error messages:
- Error 691: The computer you are dialing in to cannot establish a Dial-Up Networking connection. Check your password, and then try again.
- Error 691: Access was denied because the user name and/or password was invalid on the domain.
- Error 734: The PPP link control protocol was terminated.
- Error 629: The port was disconnected by the remote machine.
- Error 640: A NetBIOS error has occurred.

Cause

This behavior can occur if any of the following conditions are true:
- The settings for your dial-up connection to your ISP are configured incorrectly
- The dial-up connection's security option is incorrectly configured to use the Require secured password setting
- Your ISP's Point-to-Point Protocol (PPP) server is not functioning properly
- You type an incorrect user name or password

Solution

To resolve this issue (or issues), use the following methods, as necessary, in the order presented. After you finish each method, check to see whether you can connect to your ISP successfully.
Note: You must be logged on as an administrator or a member of the Administrators group to complete these procedures. If your computer is connected to a network, network policy settings may also prevent you from completing these procedures.
Verify Your User Name and Password
- Make sure that the CAPS LOCK key has not been accidentally pressed and engaged
- Click Start
- Point to Connect To
- Click your dial-up connection
- In the Connect dialog box
- Verify that your user name and password are correct
- Click Dial
Verify the Phone Number
- Verify that you are using the correct phone number to connect to your ISP
Allow Unsecured Password
- Configure your dial-up connection to your ISP to allow an unsecured password
- To do this, follow these steps
  - Click Start
  - Click Control Panel
  - Click Network and Internet Connections
  - Click Network Connections
  - Click your dial-up connection
  - Click Change settings of this connection under Network Tasks
  - Click the Security tab
  - Verify that Typical (recommended settings) is selected
  - In the Validate my identity as follows box, verify that Allow unsecured password is selected
  - Click the Options tab
  - Click to clear the Include Windows logon domain check box (if it is selected)
  - Click OK twice
Lower the Connection Speed
- If phone-line noise or other interference is an issue, you may be able to connect to your ISP by lowering your connection speed
- To lower your connection speed, follow these steps
  - Click Start
  - Click Control Panel
  - Click Network and Internet Connections
  - Click Network Connections
  - Click your dial-up connection
  - Click Change settings of this connection under Network Tasks
  - Click the General tab
  - Click your modem in the Connect Using box
  - Click Configure
  - In the Maximum speed (bps) box, click 9600
  - Click OK twice
- If you are able to connect at a lower speed, or if phone-line noise is such that you cannot connect, request that the phone company check the phone lines
Disable Hardware Flow Control
- Disable the Hardware Flow Control feature in your dial-up connection to your ISP
- To do this, follow these steps
  - Click Start
  - Click Control Panel
  - Click Network and Internet Connections
  - Click Network Connections
  - Click your dial-up connection
  - Click Change settings of this connection under Network Tasks
  - Click the General tab
  - Click your modem in the Connect Using box
  - Click Configure
  - Click to clear the Enable Hardware Flow Control check box
  - Click OK twice
Disable Modem Error Control
- Disable the Modem Error Control feature in your dial-up connection to your ISP
- To do this, follow these steps
  - Click Start
  - Click Control Panel
  - Click Network and Internet Connections
  - Click Network Connections
  - Click your dial-up connection
  - Click Change settings of this connection under Network Tasks
  - Click the General tab
  - Click your modem in the Connect Using box
  - Click Configure
  - Click to clear the Enable Modem Error Control check box
  - Click OK twice
Disable Modem Compression
- Disable the Modem Compression feature in your dial-up connection to your ISP
- To do this, follow these steps
  - Click Start
  - Click Control Panel
  - Click Network and Internet Connections
  - Click Network Connections
  - Click your dial-up connection
  - Click Change settings of this connection under Network Tasks
  - Click the General tab
  - Click your modem in the Connect Using box
  - Click Configure
  - Click to clear the Enable Modem Compression check box
  - Click OK twice
Disable Software Compression
- Disable the Software Compression feature in your dial-up connection to your ISP
- To do this, follow these steps
  - Click Start
  - Click Control Panel
  - Click Printers and Other Hardware
  - Click Phone and Modem Options
  - On the Modems tab, click the modem that you want to configure
  - Click Properties
  - Click the Advanced tab
  - Click Change Default Preferences
  - In Data Connection Preferences, click Disabled in the Compression list
Disable LCP Extensions
- You may have trouble connecting to your ISP if your ISP's Point-to-Point Protocol (PPP) server does not support Link Control Protocol (LCP) extensions. LCP extensions include a Callback option, a Time Remaining feature, and Identification packets as defined in RFC 1570. Contact your ISP to determine whether you should disable LCP extensions.
- To disable LCP extensions, follow these steps
  - Click Start
  - Click Control Pane
  - Click Network and Internet Connections
  - Click Network Connections
  - Click your dial-up connection
  - Click Change settings of this connection under Network Tasks
  - On the Networking tab, click Settings
  - Click to clear the Enable LCP extensions check box
Disable IP Header Compression
- You may experience issues logging on to your ISP if you are using IP header compression (also known as Van Jacobson, or VJ, header compression)
- To disable IP header compression, follow these steps
  - Click Start
  - Click Control Panel
  - Click Network and Internet Connections
  - Click Network Connections
  - Click your dial-up connection
  - Click Change settings of this connection under Network Tasks
  - On the Networking tab, click Internet Protocol (TCP/IP)
  - Click Properties
  - Click Advanced
  - Click to clear the Use IP header compression check box
  - Click OK
No Message for User Name and Password
- If you do not receive a message for your user name or password when you attempt to connect to your ISP
- Follow these steps
  - Click Start
  - Click Control Panel
  - Click Network and Internet Connections
  - Click Network Connections
  - Click your dial-up connection
  - Click Change settings of this connection under Network Tasks
  - Click the General tab, click your modem in the Connect Using box
  - Click Configure
  - Click the Options tab
  - Click to select the Prompt for name and password, certificate, etc. check box
  - Click OK
Mutual Authentication
- You may experience issues logging on to your ISP if your ISP's PPP server is using mutual authentication. Dial-Up Networking does not support mutual authentication. Contact your ISP to determine whether your ISP's PPP server uses mutual authentication. For additional information about modem or dialing problems, read the article below in the Microsoft Knowledge Base

Error 1304 Or Error 27000 When You Try To Install Microsoft Plus! Digital Media Edition

Error

When you try to install Microsoft Plus! Digital Media Edition, you may receive one of the following error messages:
- Error 27000. Plus! Digital Media Edition Installation Wizard cannot complete this installation. No changes were made to your computer. To install Plus! Digital Media Edition at a later time, run the wizard again.
- Error 1304. Error writing to file C:\documents and settings\all users\documents\my music\photostory.wpl. Verify that you have access to that directory. Error 1606. Could not access network location INSTALLDIR

Cause

This problem may occur if the Administrators Group does not have write access to the All Users/ Documents folder.

Solution

To resolve this problem, the Administrators Group must have write access to the All Users/ Documents folder
To give the Administrators Group write access, follow these steps
- Start your computer by using an administrator account
- Open a command prompt
- To Open a Command Prompt
- Click Start
- Click Run
- Type in the box
- Click OK
- The command prompt will appear
- At the command prompt type the following
- Press Enter
- When you read the prompt Are you sure (Y/N)?, press Y
- Then type cacls.exe "%ALLUSERSPROFILE%\Documents" /G System:F
- Press Enter
- When you read the prompt Are you sure (Y/N)?, press Y
- Then type cacls.exe "%ALLUSERSPROFILE%\Documents" /G BUILTIN\Users:R
- Press Enter.
- When you read the prompt Are you sure (Y/N)?, press Y
- Reboot

Error 1304: Error writing to file X.inf

Solution

Click Start
Click Search
Click For Files And Folders
In the Search For Files Or Folders Named field type the following and don't forget the asterisk (*) because it acts as a wild card
Type C:\WINDOWS\INF in the Look In field
Check the Advanced Options box
Remove the check from the Search Subfolders
Expand the View menu
Click Details
Click Search Now
After the search is finished expand the View menu
Expand Arrange Icons
Click By Size
Scroll through the results list until you find the first 0 KB size file
Click the entry to highlight it
Hold down the Shift key and scroll down to the last 0 KB size files and click the first entry
Check to make sure you didn't select a 1KB or larger entry
Once you're sure that only 0 KB size files are highlighted
Click Delete
Reboot and you should be able to install

Error 1311, Source File Not Found

Try one of the following solutions

During install, an Error occurs: Error 1335 The cabinet file Data.cab required for this install is corrupt.

Solution

Method 1: Change the Memory Settings for Installation
To change the memory settings for installation, follow these steps:
- Click Start
- Click Run
- In the Open box type
  - Click OK
  - On the BOOT.INI tab, click Advanced Options.
  - In the BOOT.INI Advanced Options dialog box, select the /MAXMEM= check box
  - Change the setting to 256 (or lower if your computer has less RAM).
  - Click OK to close the BOOT.INI Advanced Options dialog box.
  - In the System Configuration Utility dialog box, click Apply.
  - Click OK to close the System Configuration Utility dialog box.
  - Click Restart to the following message
  - After you restart your computer try installing again
  - After you finish installing, clear the /MAXMEM= check box.
Method 2: Install by Using a Flat Folder
To install by using a flat folder, follow these steps:
- Clean boot your computer.
- Save a flat copy of the CD-ROM to your computer's hard disk.
- To do this, follow these steps:
  - Start Windows Explorer.
  - To do this, right-click Start and then click Explore on the Startup Programs shortcut menu.
  - Create a new folder at the root of a hard disk volume, and then name it "Flatfile" (for example, C:\Flatfile ).
  - Browse to the drive that contains the CD-ROM, and then copy the entire contents of the CD-ROM into the C:\Flatfile folder.
  - To do this, follow these steps:
    - In Windows Explorer, click the CD-ROM icon (or DVD-ROM icon) containing the CD-ROM.
    - On the Edit menu, click Select All.
    - Paste all the files into the new folder.
    - To do this, drag the selected items on the right side of the Explorer window into the C:\Flatfile folder on the left.
    - Note: If there are errors during the copy process, this can indicate problems with the CD-ROM (media), a dirty CD-ROM drive, or a problem with your hard disk.
  - Restart your computer the way that you typically do, and then install from the C:\Flatfile folder onto your hard disk.

Error 2350 When You Installing A Program

Error Message

When you try to install a program, Setup may stop running, and you may receive an internal error 2350.

Solution

Follow these steps to update Windows Installer or to re-register the installer.
Note: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps
- Insert the installation CD in the CD-ROM drive or DVD-ROM drive
- When the Windows Installer dialog box appears, click Cancel
- Click Start
- Point to Search
- Click For Files or Folders
- In the Search Results dialog box, type one of the following file names in the Search for files or folders named box
  - If you are running Microsoft Windows 98 or Microsoft Windows Millennium Edition (Me), type instmsi.exe
  - If you are running Microsoft Windows NT, Microsoft Windows 2000, or Microsoft Windows XP, type instmsiw.exe
- In the Look in list, click the drive that contains the installation CD
- Click Search Now
- To install the updated Windows Installer, double-click one of the following files in the drive (letter):\Files\Support\ folder, where drive is the drive that contains the installation CD:
  - If you are running Windows 98 or Windows Millennium Edition, double-click Instmsi.exe
  - If you are running Windows NT, Windows 2000, or Windows XP, double-click Instmsiw.exe
- When the installation is complete, restart your computer
- Install program
Re-register the window installer
- Enter the following commands from a command prompt:
  - msiexec /unregister
  - Press the Enter Key
  - msiexec /regserver
  - Press the Enter Key
- If this fails to resolve your problem try performing the following steps:
  - Unregister Windows Installer:
    - Enter the following commands from a command prompt:
      - msiexec /unregister
    - Rename the following files from the command prompt: Msi.dll, Msiexec.exe, and Msihnd.dll (by changing the names to msi.dll.bak, msiexec.exe.bak and msind.dll.bak respectively.)
    - Restart Windows
    - Install the Windows Installer service again (InstMSI.exe)
    - I have noticed one thing - most people who have this problem are using NAV

Stop 0x0000007B or "0x4,0,0,0" Error

Error Messages

When you restart your computer, you may receive one of the following error messages:
- STOP: 0x0000007B Inaccessible Boot Device
- Setup has encountered a fatal error that prevents it from continuing. Contact your software representative for help. The following status codes will assist them "0x4, 0, 0, 0"

Cause

This problem may occur if one or more of the following conditions exists:
- Your computer is infected with a boot sector virus.
- A device driver required by your boot controller is not configured to start at boot time or is corrupt. If during a WINNT /B installation no mass storage device was detected.
- A resource conflict exists between the boot controller and another controller in the system or between SCSI devices.
- Drive translation is not being performed or was changed.
- The boot volume is corrupt and cannot be mounted by Windows NT.
- Information in the Windows NT registry about which device drivers load at start up is corrupt.
- If this error occurred during Windows NT Setup while reading Windows NT Setup floppy disk 2, you may have the Drive Swapping option enabled in your computer BIOS.
- Using winnt /b as the installation method may present a timing issue for the disk controller. The controller is not given enough time to respond and identify itself and is therefore detected incorrectly or not at all.
- If you run Setup from a bootable SCSI CD-ROM drive, you receive a STOP 7B error message because Setup does not allow you to add a third-party SCSI driver when you boot from the SCSI CD-ROM.

Solution

To resolve this problem try the following solutions. Not an easy error to solve.
- Method 1
  - Check any diskettes for viruses that may have been used in the computer since the last time you were able to successfully restart Windows NT
  - Note: You may need to use more than one brand of virus detection software to detect and remove various viruses
  - If a virus has infected the Windows NT computer and a virus detection program cannot remove the virus and repair the system, you will have to reinstall Windows NT
- Method 2
  - Windows NT requires a mini-port driver to communicate with the boot controller.
  - If the device driver is corrupt or incompatible with your controller, you can replace it by copying a new drive to the %systemroot%\system32\drivers folder or through the Emergency Repair process.
  - On computers running on a SCSI controller or ATAPI enabled systems, SCSIPORT.SYS and DISK.SYS (Windows NT 4.0 only) device drivers are also required to successfully boot.
  - If you attempt a "WINNT /B" installation, you may receive a STOP 0x7B before mass storage detection takes place.
  - To work around this, when the computer reboots after the initial file copy, press F6 as soon as "Setup is inspecting your computers hardware configuration" is displayed.
  - This will allow you to add a mass storage device at the very beginning of text mode setup.
    - Article-Id: 125933
      - Title: STOP 0x0000007B: Inaccessible Boot Device After Removing CD-ROM
    - Article-Id: 164471
      - Title: Replacing System Files Using a Modified Emergency Repair Disk
- Method 3
  - If an IRQ or I/O port address conflict exists between your boot controller and another controller in the system, Windows NT will either hang or stop with the Stop 0x0000007B error message.
  - If you recently added new hardware, remove the new hardware or re-configure it so it does not conflict with the resources of any other installed controllers.
  - Check the SCSI chain for proper termination.
  - Remove any non-essential SCSI devices or check to ensure each SCSI ID is unique.
    - Article-Id: 102651
      - Title: Required Settings for Adaptec 1510 SCSI Host Adapter
- Method 4
  - The Windows NT Boot partition must exist within the first 1024 cylinders of the boot device
  - This is due to restrictions of the INT-13 BIOS call used to start the operating system.
  - Check your CMOS settings for LBA support on IDE based systems, or your SCSI controllers BIOS settings for enabling drive translation for drives greater than 2GB
    - Article-Id: 114841
      - Title: Windows NT Boot Process and Hard Disk Constraints
- Method 5
  - If the file system is corrupt and Windows NT cannot mount the boot volume during start, move the drive to another machine running Windows NT and run the CHKDSK command on that drive.
  - Alternately, attempt to create a parallel installation of Windows NT on the drive in a separate directory.
  - The Windows NT Setup program checks the integrity of the volume prior to copying files and may fix some problems.
- Method 6
  - If the SYSTEM Hive in the Windows NT registry is corrupt, it may prevent Windows NT from loading the Mini-port device driver required by the boot controller.
  - To resolve this problem, use one of the following methods:
    - Start from the three Windows NT setup disks and use the Repair utility.
    - When prompted, select to inspect registry files, and then only replace the System Configuration Registry hive
    - This hive contains information about which device drivers and services start during start up.
    - Install a parallel copy of Windows NT into a separate directory, and then use Registry Editor to modify the System hive in the Windows NT registry to correct the invalid or missing information
  - Article-Id: 165748
    - Title: How to Disable a Service or Device that Prevents NT from Booting
- Method 7
  - Many computers are equipped with a 5.25-inch and a 3.5-inch floppy diskette drive in one single unit.
  - When you install Windows NT on a computer with this floppy drive unit, the STOP 0x7B error message may appear during Setup while Windows NT Setup disk 2 is being read.
  - To resolve this problem, disable the Drive Swapping option in your system BIOS.
  - For information about correcting this problem, see the following article in the Microsoft Knowledge Base:
    - Article-Id: 126423
      - Title: STOP: 0x0000007B "Inaccessible_Boot_Device" During Setup Disk2
- Method 8
  - Install using the three boot floppies, a bootable CD, winnt or winnt32.
  - Install the device driver recommended by hardware vendor if one is available
- Method 9
  - Install using the three boot floppy disks.
  - Install the device driver recommended by hardware vendor if one is available

Stop 0x24 or NTFS_FILE_SYSTEM Error Messages

Symptoms

When you run Windows 2000, you may receive either of the following error messages:
- Stop 0x00000024
- NTFS_FILE_SYSTEM CAUSE This issue can occur if a problem occurred within the Ntfs.sys file. The Ntfs.sys file is the driver file that enables your computer to read and write to NTFS partitions. Damage in the NTFS file system, damaged portions of your hard disk, or damaged SCSI or IDE drivers can also cause this issue

Solution

Interpret the error message
The stop error is followed by four parameters defined in order of appearance:
- Source file and line number.
- Optionally contains the address of the exception record.
- Optionally contains the address of the context record.
- Optionally contains the address where the original exception occurred.
- Note:
  - All stop errors due to problems with NTFS or FAT have encoded in their first parameter the source file and the line number within the source file that generated the stop error
  - The high 16 bits (the first four hexadecimal digits after 0x) identify the source file number, and the lower 16 bits (the last four hexadecimal digits of the parameter) identify the source line in the file where the stop occurred.
Check Event Viewer for error messages from SCSI, FASTFAT (the System Log), or Autochk (the Application Log) that might help determine the device or driver that is causing the error
Try disabling any virus scanning programs, backup programs, or disk defragmenter tools that constantly monitor your computer, and if possible, run hardware diagnostics tools supplied by your computer manufacturer
Run chkdsk /r to detect and resolve any file system structural damage
Depletion of non-paged pool memory can cause this issue
If you create a Services for Macintosh (SFM) volume on a large partition (7 gigabytes or larger) with a large number of files (at least 100,000) while the AppleTalk driver Apf.sys is running, the indexing routine consumes a large amount of non-paged pool memory
If the non-paged pool memory is completely depleted, this error can cause your computer to stop responding (hang)
Note:
- However, if the amount of available non-paged pool memory is very low during the indexing process, another kernel-mode driver requiring non-paged pool memory can also cause this issue
- To resolve this issue, increase the amount of installed RAM to increase the quantity of non-paged pool memory available to the kernel, or reduce the number of files on the SFM volume.
- Any corrupted system or data volume that is using NTFS can cause this error message
- If you receive a "stop 0x24" error message when you restart the computer or when you try to run Setup or Recovery Console, you may not be able to determine the cause of the problem by using the steps outlined above
- Instead, use one of the following methods to resolve the corrupted NTFS volume
  - FAT or FAT32 File System
- If your system partition is using the FAT or FAT32 file system, disconnect or turn off any data disks that contain NTFS volumes
- If you can determine which NTFS volume is causing the boot problem, use the following steps:
  - Make sure the drive that contains the corrupted NTFS volume is disconnected, and then start Windows by using Safe mode
  - Rename the %SystemRoot%\System32\Drivers\Ntfs.sys file to Ntfs.old,
  - Shut down the computer
  - Reconnect the drive that contains the corrupted NTFS volume.
  - Restart the computer, and then run the following command on the corrupted NTFS volume:
  - After you use the Chkdsk tool to repair the corrupted NTFS volume, rename %SystemRoot%\System32\Drivers\Ntfs.old to Ntfs.sys
  - Shut down and restart the computer
NTFS File System
- If your system partition is using the NTFS file system, it is possible that the system partition is corrupted and is causing the "stop 0x24" error message.
  - To determine if this is the case, disconnect or turn off all other data disks that contain NTFS volumes
  - After you determine which disk contains the corrupted NTFS volume, move the disk to another Windows 2000-based computer that is running on the FAT or FAT32 file system, or install Windows 2000 on a disk that contains the FAT or FAT32 file system
  - Use the steps that are outlined in the "FAT or FAT32 File System" section
- Using Recovery Console on a Single Drive Computer
  - If your computer contains only a single NTFS volume and no additional Windows 2000-based computers or hard disks are available to use for the previously described methods, you can boot from the four Setup disks to run the Chkdsk tool with the Ntfs.sys driver disabled
  - To repair a NTFS volume by using Recovery Console:
    - Start the computer by using a Microsoft Windows 95/98 startup disk with CD-ROM support (or from another computer with a CD-ROM drive, insert the Windows 2000 installation CD-ROM).
    - Change to the CD_ROM:\Support\Bootdisk folder, and then run Makeboot.exe or Makebt32.exe to create the four Windows 2000 Setup disks.
    - Using Notepad, modify the Txtsetup.sif file on the first Setup disk you created in step 2:
      - In the [FileSystems.Load] section, locate the line that begins with "ntfs."
      - Insert a semicolon (;) at the beginning of the line, as shown in the following example:
        [FileSystems.Load]
        fat = fastfat.sys
        ;ntfs = ntfs.sys
      - Save your changes.
      - Start the computer that is experiencing the "stop 0x24" error message by using the four Setup disks
      - When the Welcome to Setup dialog box is displayed, press F10 to start Recovery Console
      - Run the following command to repair the corrupted NTFS partition:
        chkdsk driveletter: /p
      - Type exit to quit Recovery Console
      - Restart the computer
      - If none of these methods work, you may have to delete, re-create, and format the corrupted NTFS partition, and restore the partition from your last good backup of the volume.

DISCLAIMER: The information provided on ALL of these pages is provided as-is. No warranty is provided or implied. Use at your own risk.
Privacy Policy, About Me