Windows xp installation error bsod

windows xp installation error bsod

If you are trying to install the Windows XP from scratch on the laptop, please BE SURE that you put the Hard Drive on "Compatibility" mode in BIOS, which was. It seems that some users have encountered a blue screen error message while installing Windows XP. This problem can occur due to many. sprers.eu › Support › Knowledge Base Article.

You can watch a thematic video

Fix \

Windows xp installation error bsod - confirm

Unable to install Windows XP : Blue screen error pops up before "Starting Windows Setup"

I got caught up in a strange problem. It's really annoying me. I'm writing this by logging into ultimate boot cd.

Strange because, it never happened before. Just about a week ago I installed and it installed perfectly fine. (I used a different Windows XP CD & a different DVD drive then).

Now I'm trying to install windows xp pro sp3. When I insert the CD. Everything till "Loading %^[email protected]#[email protected]#$" is fine. Then comes the step "Starting Windows Setup" and then suddenly a Blue Screen pops up.

It says:

A problem has been detected and windows has been shut down to prevent damage to your computer.

Plug & Play detected an error most likely caused by faulty driver.

If this is the first time you've seen this error screen, restart your computer. If this screen appears again, follow these steps.

Check to makes sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching and shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced startup options, and then select safe mode.

Technical Information:

Stop: 00xCA (0X, 0XE, 0XE, 0X)

I did little bit of Googling and found that I need to change the drive configuration from AHCP to IDE (or something like that).

I'm using Intel DGLVG Desktop Board its bios doesn't have any such setting. But there was something related to IDE & SATA. I tried disabling the SATA ports and only enabling the IDE. Even then it didn't work.

I'm using PATA hardisk as Primary Master and DVD COMBO drive as primary slave.

Any suggestions about getting rid of this error?

PS: I'm not technically weak. But I cannot understand what that "Technical Information" in the error is trying to say. If you have anything to say on that please do.

EDIT: The version of BIOS I'm using is (I couldn't find any separate name) VGAA I'm using Intel DGLVG Desktop Board

EDIT 2:

In my BIOS, under Drive configuration there is a setting called "ATA/IDE Configuration". It was set to AUTO by default. When I set to "Legacy". It shows me a new setting called "Legacy IDE Channels" which has the following options:

  1. SATA P0/P2, PATA
  2. SATA P1/P3, PATA
  3. SATA P0/P2, P1/P3
  4. PATA only

I've tried using all four options. None of it solved my problem.

EDIT 3:More info about my computer

It is an old computer with following hardware configuration:

  1. Intel DGLVG Desktop Board
  2. Intel P4 processor
  3. MB ddr RAM.
  4. GB PATA hard disk.
  5. Floppy Disk drive. (it's not connected)
  6. SATA DVD drive
  7. 15" monitor, keyboard, optical mouse.

This is all what my computer has (connected to it). Now, I don't understand which critical hardware can I remove from these?

System was running fine but one day there was a sudden power cut. I don't have a UPS. Immediately when power is back my Windows XP was not letting me login but it was rebooting continuously without showing me the login screen. I thought it was this problem sprers.eu and tried replacing kerneldll (from ultimate boot CD) but even then problem XP rebooting problem was not solved. So, I thought I would format and install new Windows XP. I successfully installed it. Next day again there was power cut and again the same rebooting problem. I again wanted to reinstall XP but now it started showing me this blue screen (STOP ERROR).

I've tried changing every possible setting in the BIOS. When I was using ultimate boot CD, (and now I'm in UBUNTU live CD) one strange observation is previously I had 4 partitio

Recommended: ASR Pro

  • 1. Download and install ASR Pro
  • 2. Launch the program and select your language
  • 3. Follow the onscreen instructions to complete the setup process
  • Click here to fix your computer now with this fast

    It seems that some users have encountered a blue screen error message while installing Windows XP. This problem can occur due to many factors. Let&#;s discuss this now. This usually happens due to data corruption on the hard drive. Unfortunately, before starting the computer, make sure that all hard drive cables are properly connected. If buyers have installed new hardware, try uninstalling it and restarting the computer to see if the error returns.

    Recommended: ASR Pro

    Is your computer running slow and sluggish? Are you worried about losing your important files and data? Then look no further than ASR Pro � the ultimate solution for fixing all of your Windows-related issues. This powerful software will repair common errors, protect your system from disaster, and optimize your PC for maximum performance. So don't wait any longer � download ASR Pro today and enjoy a smooth, speedy, and worry-free computing experience!

  • 1. Download and install ASR Pro
  • 2. Launch the program and select your language
  • 3. Follow the onscreen instructions to complete the setup process

  • I tried to install Windows XP on my Acer system. I called my first boot device a concept album and my second boot device a hard drive. The system boots from the CD and DVD and reports that the installer is reloading files. And after that, you will immediately get a blue screen, as the message says. I can&#;t move anymore. The message says that the installation will not continue if it happens frequently the first time&#; Check the computer for viruses&#; Run chkdsk -f&#; .and so on&#; sprers.eu

    Ask someone for help me to solve this problem. How can I install Windows? Is it possible? I have experience waiting for your reply&#;..

    of 15 views

    March views

    How do I install windows with a blue screen?

    Disable secure sprers.eu Legacy sprers.eu available, enable sprers.eu USB boot if sprers.eu the device by inserting the boot disk in the first fragment of the boot sprers.eu the BIOS conversions, reboot the system and it may want to boot from the installation media.

    You should be here because you&#;ve probably experienced the known BSOD several times when installing Windows XP using a USB key. Show two ways to buy Windows XP entirely via USB, especially if you created a bootable USB using WinToFlash.

    1. Enter BIOS and simply enable SATA Combo mode. This backlight is not available in older technologies. On older computers, just enable the Legacy IDE.

    3. If you are still getting this blue screen loading, we need to change sprers.eu during the USB drive.

    4. To do this, you need to download, configure and run TinyHexer.

    5. Copy here the full code from everything youdividing to the last number and insert it into TinyHexer. Be sure to select the hex text on the subpage and click OK.

    8. Be sure to select the Workstation ID and the sprers.eu file.

    ten. Copy the new &#;sprers.eu&#; based on booting the Windows XP bootable USB and replace ntdetect sprers.eu with the new one.

    blue screen on install windows xp

    You should now be able to install Windows XP via USB.

    Why Windows XP is not installing?

    SCAN YOUR COMPUTER FOR VIRUSES. REMOVE ANY NEWLY INSTALLED HARD DISK OR HARD DISK CONTROLLER. CHECK THE HARD DRIVE TO BE SURE IT IS PROPERLY SET UP AND STOPPED. RUN CHKDISK /F TO CHECK FOR DISK DAMAGE, THEN RESTART YOUR COMPUTER.

    I created this tech blog in to write about processes. I needed to repair client systems and the network. Now I will write some tips and instructions to help others solve any technical problems they may encounter.

    Can I install Windows XP in ?

    Windows XP still working? The best solution is yes, but it&#;s more risky. To help you, we usually describe a few tips that will keep Windows XP safe for the long haul. According to Market Chunk research, a lot comes from all the users who still use it on their devices.

    Click here to fix your computer now with this fast

    Pantalla Azul Al Instalar Windows Xp
    Blauw Scherm Bij Installatie Van Windows Xp
    Tela Azul Na Instalacao Do Windows Xp
    Niebieski Ekran Podczas Instalacji Systemu Windows Xp
    Bla Skarm Pa Installation Av Windows Xp
    Ecran Bleu Lors De L Installation De Windows Xp
    Schermata Blu Su Installa Windows Xp
    Bluescreen Bei Windows Xp Installieren
    윈도우 Xp 설치시 블루스크린
    Sinij Ekran Pri Ustanovke Windows Xp

    If you install Windows XP on a modern system, you may experience a blue screen error. This article will help you fix this.

    Cause

    I do not have a modern computer and I have never encountered a blue screen error when booting into the Windows XP installer.

    When I used VirtualBox to create a new virtual machine with a version of Windows 7, then attach the ISO file of Windows XP to install, I got this error. Of course, if I create a new virtual machine with a version of Windows XP, it will work. So what&#;s the difference here? I noticed that VirtualBox uses Controller for Windows 7 as SATA and Windows XP as IDE. Okay, now I will change the Controller for Windows 7 to IDE, I try again and it works. Windows XP will not work if I set the controller to SCSI.

    Blue screen when installing Windows XP

    From the test steps and the information I have found, the cause of this error is in the Controller type.

    How to fix

    Windows XP does not support drivers so that computers can interact with devices that are attached to SATA and SCSI controller (not sure about SCSI). The simplest way is to change the Controller type in the BIOS to Compatibility or IDE. I&#;m not sure about the settings in the BIOS, but the AIO Boot supports installing Mass Storage drivers when installing Windows XP. This means that the Windows XP installer will be able to interact with the USB and hard disk via the SATA/RAID/SCSI port. If you plug in USB , plug it into port

    AIO Boot uses the Windows XP installation method from WinSetupFromUSB. And the DPMS tool is extracted from Easy2Boot. DPMS contains and supports automatic installation of Mass Storage drivers before installing Windows. You can read more about DPMS at the author&#;s website.

    Using DPMS:

    1. Download sprers.eu and copy the file to /AIO/Tools/DPMS. Then defrag the file to make sure it can be used by Grub4dos.
    2. From the Grub2 main menu, press to access the Windows XP/ Setup menu.
    3. You will see a menu to enable the option &#;Auto-detect and use F6 SATA/RAID/SCSI Driver&#;, or use plus Firadisk. If you disable this option, drivers will not be installed. If your ISO file is integrated with the Mass Storage driver, you should disable this option. This option will be remembered for future uses.
      Windows XP Mass Storage Driver - SATA/RAID/SCSI

    After enabling this option, you can boot into the Windows XP installation. Now the blue screen error is gone when using SATA ports.

    How to fix blue screen when installing Windows XP

    If you are still experiencing a blue screen error, your system may be too new while the driver is not up to date to support it. Please contact me, then I will update the driver or contact the author of Easy2Boot.

    Solving BSOD Issues During Windows XP Installation

    Blue Screen of Death (BSOD) which sometimes occurs during Windows installation or just after Windows installation can be particularly annoying, especially when you don't understand its cause or what to do about it.

    This article explains in detail why does Blue Screen of Death occur during Windows XP installation and how to solve Stop 0xB (Stop 7B, INACCESSIBLE_BOOT_DEVICE) error.

    1. Why BSODs occur during Windows XP Installation

    BSOD (Blue Screen of Death) means that Windows Kernel has encountered an error it could not handle. For example:

    Usual reasons for BSOD during Windows XP installation: lack of proper storage drivers, faulty hardware or the minimum system requirements for Windows XP are not met.

    2. Decoding BSODs

    BSODs usually contain the name of failed driver or Windows component (sprers.eu in this example), error description (PAGE_FAULT_IN_NONPAGED_AREA), stop code afer "*** STOP: " (0x in this example) and other information.

    The most important things to note are error description and corresponding stop code.

    3. Stop 0xB (INACCESSIBLE_BOOT_DEVICE): What does it mean

    When Windows starts, it must load its Kernel into the memory. To do this, Windows must read the Kernel from the disk. In order to read the disk, Windows must load disk driver first. But disk driver can't be loaded before Kernel is already in the memory.

    It's a kind of chicken-and-egg problem.

    To solve it, Windows temporarily (only during boot time) is using different way to access the boot disk — not via usual driver, but via BIOS interface (Interrupt 13h). BIOS Interrupt 13h is slow, and incompatible with multitasking, so it is used only to read portion of the operating system from boot disk. Other disks are never read this way.

    During the boot process, in order to remount boot filesystem in read/write mode, to reopen the registry in read/write mode, to load the rest of drivers, and to perform other necessary boot tasks, Windows switches from old BIOS interface for accessing the disk to native (driver) interface for accessing the disk. This switching allows disk access to be faster and more reliable, thus new way to access the disk is used until complete shutdown of the OS.

    If this switching is impossible for some reason, then Windows Kernel fires error 0xB (INACCESSIBLE_BOOT_DEVICE).

    Usual reason why this switching might be impossible is a lack of driver: disk controller driver, or maybe bus (miniport) driver. There are also situations when the driver is present but contains bugs and needs to be upgraded in order to work.

    The most probable reason why you are getting error 0xB (INACCESSIBLE_BOOT_DEVICE) is SATA disk controller configured in AHCI mode, which is supported by BIOS interrupt 13h, but requires special driver from motherboard vendor in order to work in Windows. Detailed discussion of this topic can be found in this article.

    There's also official Microsoft documentation of this error.

    4. Other stop codes

    0xA (IRQL_NOT_LESS_OR_EQUAL),
    0xD1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL),
    0xE (KMODE_EXCEPTION_NOT_HANDLED), 0xC5 (DRIVER_CORRUPTED_EXPOOL), 0xE (KERNEL_MODE_EXCEPTION_NOT_HANDLED)
    One of your drivers contains bugs (name of failed driver may be helpful, but not necessary indicates the source of the problem). Try upgrading/disabling drivers for your devices starting from most unreliable/rare devices. Unplugging devices for the time of Windows Installation also may help. On fully installed Windows this error is usually caused by buggy antivirus/firewall software.
    0x (FAT_FILE_SYSTEM),
    0x (NTFS_FILE_SYSTEM)
    May be related to unreliable hard disk: surface wear-out, bit rot etc. Also check SATA connectors aren't loose.
    0x (VIDEO_TDR_ERROR) This one is related to the driver of your video card.
    0xC (MACHINE_CHECK_EXCEPTION),
    0x (WHEA_UNCORRECTABLE_ERROR),
    0xE (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED),
    0xF (UNEXPECTED_KERNEL_MODE_TRAP),
    0x (PAGE_FAULT_IN_NONPAGED_AREA),
    0xF4 (CRITICAL_OBJECT_TERMINATION)
    It's recommended to test memory with MemTest86+ (here is a local copy). Also disable overclocking if you are using it. This recommendation also applies to all error codes listed above in this section.

    5. Professional kernel dump analysis

    If BSOD occurs after Windows installation, it usually creates dump file in C:\Windows\MiniDump (except the case when BSOD is caused by system disk failure). These dumps can be later copied, archived, sent by email and analyzed by trained professional using Microsoft tools. Here's official documentation on this topic: Analyzing a Kernel-Mode Dump File.



    Windows XP Blue Screen Troubleshooting

    This article is for Microsoft Windows XP.
    Click below to change the operating system.

    Table of Contents:

    1. What Is a Blue Screen Error?
    2. Troubleshooting Common Blue Screen Error Messages
      1. 0xED and 0xB
      2. 0x
      3. 0xE and 0xE
      4. 0x
      5. 0xD1
      6. 0xC
      7. 0xEA
    3. Using the Windows Debugger
    4. Restore the Operating System to Factory Settings

    This article describes what Blue Screen errors are, why they occur, how to recognize them, and how to resolve some of the more common error messages.


    Topic 1: What Is a Blue Screen Error?

    When Windows encounters certain situations, it halts and the resulting diagnostic information is displayed in white text on a blue screen. The appearance of these errors is where the term "Blue Screen" or "Blue Screen" has come from.

    Blue Screen errors occur when:

     
    • Windows detects an error it cannot recover from without losing data
    • Windows detects that critical OS data has become corrupted
    • Windows detects that hardware has failed in a non-recoverable fashion
    • The exact text displayed has changed over the years from a dense wall of information in Windows NT to the comparatively sparse message employed by modern versions of Windows. (Figure 1)

    A problem has been detected and Windows has been shut down to prevent damage
    to your computer.
    UNMOUNTABLE_BOOT_VOLUME
    If this is the first time you've seen this error screen,
    restart your computer. If this screen appears again, follow
    these steps:
    Check to be sure you have adequate disk space. If a driver is
    identified in the Stop message, disable the driver or check
    with the manufacturer for driver updates. Try changing video
    adapters.
    Check with your hardware vendor for any BIOS updates. Disable
    BIOS memory options such as caching or shadowing.
    If you need to use Safe Mode to remove or disable components, restart
    your computer, press F8 to select Advanced Startup Options, and then
    select Safe Mode.

    Technical Information:
    *** STOP: 0xED(0x80FD0, 0xCC, 0x, 0x)

    Figure 1: Sample Blue Screen Error

    Back to Top


    Topic 2: Troubleshooting Common Blue Screen Error Messages

    Stop 0xED (UNMOUNTABLE_BOOT_VOLUME)

    Stop 0xB (INACCESSIBLE_BOOT_DEVICE)

    These two errors have similar causes and the same troubleshooting steps apply to both of them. These stop codes always occur during the startup process. When you encounter one of these stop codes, the following has happened:

    1   The system has completed the Power-On Self-Test (POST).


     

    2   The system has loaded NTLDR and transferred control of the startup process to NTOSKRNL (the kernel).


     

    3   NTOSKRNL is confused. Either it cannot find the rest of itself, or it cannot read the file system at the location it believes it is stored.
    When troubleshooting this error, your task is to find out why the Windows kernel is confused and fix the cause of the confusion.
    Things to check:

    • The SATA controller configuration in the system BIOS If the SATA controller gets toggled from ATA to AHCI mode (or vice versa), then Windows will not be able to talk to the SATA controller because the different modes require different drivers. Try toggling the SATA controller mode in the BIOS.
    • RAID settings You may receive this error if you've been experimenting with the RAID controller settings. Try changing the RAID settings back to Autodetect (usually accurate).
    • Improperly or poorly seated cabling Try reseating the data cables that connect the drive and its controller at both ends.
    • Hard drive failure Run the built-in diagnostics on the hard drive. Remember: Code 7 signifies correctable data corruption, not disk failure.
    • File system corruption Launch the recovery console from the Windows installation disc and run chkdsk /f /r.
    • Improperly configured sprers.eu (Windows XP). If you have inadvertently erased or tinkered with the sprers.eu file, you may receive stop code 0x7B during the startup process. Launch the recovery console from the Windows installation disc and run BOOTCFG /REBUILD

    Back to Top


    STOP 0x (NTFS_FILE_SYSTEM)

    This stop code indicates the NTFS file system driver encountered a situation it could not handle, and is almost always caused by 3 things:

    • Data corruption on the disk
    • Data corruption in memory
    • The system completely running out of memory (this typically only happens on heavily-loaded servers)

    Things to check:

    1   Reseat the memory and all drive data cables to eliminate data corruption issues stemming from poorly or improperly seated hardware.


     

    2   Run a complete memory and hard drive diagnostic. The quick test will not be thorough enough here. You need to run the full system diagnostic.


     

    3   If those diagnostics pass, run a full file system check from the Recovery Console (chkdsk /f /r) to detect and (potentially) fix any corrupted data.


     

    4   If none of the above solves the issue, reinstall Windows.


     

    5   If that does not fix the issue, replace the hard drive.

    Back to Top


    STOP 0xE (SYSTEM_THREAD_EXEPTION_NOT_HANDLED)

    STOP 0xE (KERNEL_MODE_EXCEPTION_NOT_HANDLED)

    These two errors indicate that a program running in the kernel encountered an unexpected condition it could not recover from. They have identical troubleshooting and resolution steps, and you will probably need to use the Windows Debugger to find out what caused the error.

    Things to check:

    • If the Blue Screen message mentions a driver or library file, figure out what driver or application that file is part of and update or disable it.
    • Update the system BIOS to the latest available revision.
    • Uninstall any recently installed programs, and roll-back any recently installed drivers.
    • Run diagnostics on the computer's memory.

    Back to Top


    STOP 0x (PAGE_FAULT_IN_NON_PAGED_AREA)

    This stop code means the system tried to access a nonexistent piece of memory, almost always due to:

    • A driver trying to access a page of memory that is not present
    • A system service (ex. virus scanner) failing in an exceptional way
    • Faulty or incorrectly seated memory
    • Corrupted data on the hard drive

    Use the Windows Debugger to pinpoint the exact cause of these errors.

    Things to check:

    1   If the Blue Screen error mentions a driver or library file, figure out what driver or program the file is a part of and either upgrade to the latest version or uninstall the driver or program.


     

    2   If the error happens during the startup process, try booting to the Last Known Good Configuration.


     

    3   If the error started appearing after a program or driver was installed, uninstall that program or driver.


     

    4   Try running a full hard drive and memory diagnostic after reseating the memory and hard drive data cables.

    Back to Top


    STOP 0xD1 (DRIVER_IRQL_NOT_LESS_THAN_OR_EQUAL_TO)

    This stop code indicates a driver tried to access a certain area of memory when it should not have, meaning there is a flaw in the driver itself. The goal of your troubleshooting is to find that driver and either disable or replace it. Use the Windows Debugger to troubleshoot this error.

    Without the debugger, you are limited to uninstalling/updating/rolling back the driver that contains the driver file the Blue Screen mentions.

    Back to Top


    STOP 0xC (STATUS_CANNOT_LOAD_REGISTRY_FILE)

    This stop code indicates the Registry has been corrupted.

    Things to check:

    1   Try to boot to the Last Known Good Configuration.


    2   If that fails, you will have to try and restore the registry files manually. The process for doing so is fairly complex and described in the Microsoft KB Article: "How to recover from a corrupted registry that prevents Windows XP from starting" Article ID:  

    Back to Top


    STOP 0xEA (THREAD_STUCK_IN_DEVICE_DRIVER)

    This Blue Screen error indicates that a device driver-almost always a video card driver-is stuck waiting for something (usually a hardware operation) to happen. Most of you have probably seen nv4_sprers.eu associated with this Blue Screen.

    Things to check:

    1   Ensure the video drivers are updated to the latest Dell version.


     

    2   The system BIOS is fully up-to-date.


     

    3   If both the video driver and the system BIOS are fully up-to-date, check with the manufacturer for recent driver updates.


     

    4   As a last resort, try exchanging the video card.

    Reinstalling Windows is not likely to prevent this error from reoccurring.

    Back to Top


    Topic 3: Using the Windows Debugger

    The Windows Debugger is one of the primary tools used by Microsoft software developers and support staff to analyze and resolve errors that result in memory dumps, and it's available for you.

    The Windows Debugger is a powerful tool with many useful applications, but for this article, we are only interested in its ability to analyze memory dump files generated by blue screen errors to determine the cause of the error.
    Before you can use the tool, keep in mind the following:

    • The Windows Debugger is not a native Windows tool. You must download and install the application (15 MB) from the Microsoft web site. Administrator access is required to install the tool.
    • The Debugger requires some minor customization before use.
    • The Debugger can take anywhere from 30 seconds to two minutes to fully analyze a memory dump.

    To use the tool, follow these steps:

    1      Download and install the Windows Debugger from the Microsoft Web Site .

    Note: If you use Google to search for "windows debugger," the first link returned will be the Windows Debugger home page.

     


    2      Once installation completes click Start, click All Programs, click Debugging Tools for Windows, then click WinDbg to open the debugger.


    3      Configure the symbol path used by the debugger to turn addresses in the memory dump file into meaningful location names: expand the File menu, select Symbol File Path, type "SRV*c:\debug_symbols*sprers.eu" in the dialog box then click OK.


    4      Open a minidump file: expand the File menu, select Open Crash Dump, select the desired dump file and click Open.

    Note: The system usually stores minidump files in either: C:\WINNT\Minidump\ or C:\Windows\Minidump\. The files will be named sprers.eu, where MM is the month, DD is the day, and YY is the year in which the dump file was created. NN is the sequence the dump files were created in if multiple dumps were generated on the same day (the first crash dump on a given day will be numbered 01, the second 02, etc.).

     


    5      The debugger will open the dump file and give a brief description of what caused the system to crash (Figure 2).

    Note: The first time you use the Debugger to open and dump file on a system, it will take a few minutes to download symbol information in the background before it returns any information

    SLN_en_US__1dump1
    Figure 2: Windows Debugger

     
    SLN_en_US__2SG_Caption1 Suggested command for the Debugger's command line
    SLN_en_US__3SG_Caption2 Stop code from the blue screen (F is the same as 0x7F)
    SLN_en_US__4SG_Caption3 What Windows thinks caused the crash (sprers.eu in this example, you'll sometimes see things like memory_corruption

    6      When it returns this preliminary analysis, the Debugger tells you how to dig deeper. Type "!analyze -v" in the command line (kd>) field at the bottom of the window and press the Enterkey to have the WinDbg perform a detailed analysis of the file.

    Note: The results will be lengthy, and you may have to scroll vertically within the Debugger's window to locate all the pertinent information

    SLN_en_US__5dump2
    Figure 3: Analyze the Results

    SLN_en_US__2SG_Caption1 A detailed explanation of the stop code (in the example, you can see that the kernel encountered an EXCEPTION_DOUBLE_FAULT (8), or an error while trying to process an error)
     

    SLN_en_US__7dump3
    Figure 4: Further Analysis of the Results

    SLN_en_US__2SG_Caption1 The bug check code (notice in the example it includes the number 8, indicating the double fault)
    SLN_en_US__3SG_Caption2 The number of times the system has crashed with this exact error (typically 1)
    SLN_en_US__4SG_Caption3 The bucket in which Windows has categorized the crash
    SLN_en_US__11SG_Caption4 The stack trace at the time the system crashed, with the most recently called procedure on top (you can see in the example the system crashed while processing a request from the IDE controller)
     

    SLN_en_US__12dump4
    Figure 5: Additional Analysis

    SLN_en_US__2SG_Caption1 The name of the module the system was in when it crashed. On an actual system, the module name is a link you can click to receive some useful information about the module, who created it, how old it is, etc

    Back to Top


    Topic 4: Restore the Operating System to Factory Settings

    If clean boot troubleshooting cannot identify the issue, it may be necessary to restore your computer to factory settings. To restore your computer's operating system and software to the original factory settings, launch the link below:
    Launch the Microsoft Windows Reinstallation Guide

    Back to Top


     

    Site: sprers.eu windows xp installation error bsod

    Fix Blue Screen of Death (BSoD) Errors in Windows XP

    This guide shows you how to fix blue screen of death errors (or BSoD errors) for Windows XP.

    Contents

    If you see a blue screen error, but Windows XP restarts immediately and you can&#;t read the error text, follow these instructions to disable the Automatically restart option:

    1. Right-click on My Computer
    2. Go to Properties
    3. Go to the Advanced tab
    4. At the Startup and Recovery section, click the Settings button
    5. At the System failure section, make sure the &#;Automatically restart&#; option is unchecked
    6. Click OK

    If you can&#;t boot into Windows, try booting into Safe Mode, follow the instructions above and then restart your computer again. To boot Windows XP in Safe Mode, follow these steps:

    1. Restart your computer
    2. Press before the Windows logo appears
    3. Use the arrow keys and select &#;Safe Mode&#; from the boot menu
    4. Press

    0xED (UNMOUNTABLE BOOT VOLUME)

    UNMOUNTABLE_BOOT_VOLUME

    The 0xED blue screen error code is most commonly known as UNMOUNTABLE_BOOT_VOLUME. We covered how to fix UNMOUNTABLE_BOOT_VOLUME in Windows XP already.

    For situations where the UNMOUNTABLE_BOOT_VOLUME error windows xp installation error bsod caused by incorrect or outdated information regarding the Windows partition in the boot configuration files (sprers.eu or the BCD) for NTLDR or BootMGR, Easy Recovery Essentials can normally recreate the boot configuration with the correct settings and parameters to allow for Windows to boot correctly:

    1. Download Easy Recovery Essentials from here. Choose your Windows version (XP, Vista, 7 or 8) before you go to download
    2. Burn the windows xp installation error bsod. Follow these instructions on how to burn the bootable ISO image very carefully, windows xp installation error bsod, as making a bootable CD can be tricky!
    3. Boot into Easy Recovery Essentials
    4. Choose Automated Repair option and click Continue

      Easy <b>Windows xp installation error bsod</b> Essentials Automated Repair

    5. Choose your Windows installation drive&#;s letter (usually C:\) and click Automated Repair
    6. Wait for Easy Recovery Essentials to complete the process

      Easy Recovery Essentials Repair Complete

    7. Once the process is complete, click Restart

    0xB (INACCESSIBLE BOOT DEVICE)

    The blue screen error 0xB has the windows xp installation error bsod INACCESSIBLE_BOOT_DEVICE.

    The 0xB error

    This error appears if your computer is infected 800 vpn error boot-sector virus, there is an issue with a device driver or an issue with a piece of hardware. Other issues may also cause this error to show up.

    Follow these instructions to fix this error in Windows XP:

    Fix #1: Remove viruses

    If your computer is infected with a boot-sector virus, run an antivirus scan and remove all viruses from your computer to possibly fix the error.

    If you don&#;t have an antivirus scanner, use the Virus Scanner of our recovery disk Easy Recovery Essentials that you can burn to any CDs, DVDs or USBs and run the scan:

    1. Download Easy Recovery Essentials from here
    2. Burn the image, windows xp installation error bsod. Follow these instructions on how to burn the bootable ISO image very carefully, as making a bootable CD can be tricky.
    3. Boot Easy Recovery Essentials
    4. Choose Virus Scanner

      Easy Recovery Essentials Virus Scanner

    5. Wait for the scan to complete

      Easy Recovery Essentials Virus Scan Complete

    Fix #2: Run chkdsk

    You can run the command to check if the boot volume is corrupted. To do so:

    1. Insert the original Windows XP installation disk
    2. Boot from the CD. Press any key when the &#;Press any key to boot from CD&#; message appears
    3. Press to open Recovery Console
    4. Type in the administrator password and hit
    5. When Command Prompt has loaded, type the following command:

      chkdsk /r
    6. Press
    7. Restart your computer

    Fix #3: Recover the Windows XP registry

    Follow the instructions from the Windows could not start: CONFIG\SYSTEM error guide on how to recover the registry of a Windows XP system.

    The instructions mentioned there are the same you need to perform for the 0xB error.

    Fix #4: Check or remove hardware

    If you installed a new hardware piece, remove it and restart your computer.

    Check that all hard disk cables are connected properly.

    Fix #5: Reboot into Last Known Good Configuration

    The Windows xp installation error bsod Known Good Configuration mode can solve issues caused by an incorrect or misconfigured driver. This Windows mode forces your computer to use a previously saved version of the Windows registry.

    To do so, follow these steps:

    1. Restart your computer
    2. Start tapping repeatedly before the Windows XP logo appears, but after the BIOS screen (the screen with your manufacturer logo and/or system information)
    3. When the boot options list screen appears, windows xp installation error bsod, choose &#;Last Known Good Configuration (Advanced)&#;
    4. Press

    Fix #6: Reconfigure the sprers.eu

    A misconfigured sprers.eu can be the cause for the 0xB error.

    To rebuild the sprers.eu using Easy Recovery Essentials, follow the instructions:

    1. Download Easy Recovery Essentials from here. Choose your Windows xp installation error bsod version (XP, Vista, 7 or 8) before you go to download
    2. Burn the image. Follow these instructions on how to burn the bootable ISO image very carefully, as making a bootable CD can be tricky!
    3. Boot into Easy Recovery Essentials
    4. Choose Automated Repair option and click Continue

      Easy Recovery Essentials Automated Repair

    5. Choose your Windows installation drive&#;s letter (usually C:\) and click Windows xp installation error bsod Repair
    6. Wait for Easy Recovery Essentials to complete the process

      Easy Recovery Essentials <a href=Error smtp 500 5.5.2 Complete">

    7. Once the process is complete, click Restart

    0x (NTFS FILE SYSTEM)

    A blue screen error with the error code as 0x indicates an issue with the NTFS file system. This is usually caused by data corruption on your hard disk.

    The 0x error

    To fix this error try the following methods:

    Method #1: Check or remove hardware

    Make sure that all disk cables are connected properly before booting your computer. If you installed new hardware, try to remove it and restart your computer to see if the error appears again.

    Method #2: Run the chkdsk command

    The chkdsk utility, available on your Windows XP installation CD can detect and potentially fix corrupted data.

    1. Insert and boot from the CD
    2. Press to go to the Recovery Console
    3. Type in the administrator password
    4. Hit
    5. Type the following command, in Command Prompt: chkdsk /f /r
    6. Press
    7. Restart

    More information about this error is available in the windows xp installation error bsod 0x&#; guide.

    If the above methods do not work, try reinstalling Windows XP or replace the hard disk.

    0xE (SYSTEM THREAD EXCEPTION NOT HANDLED)

    0xE

    The 0xE error

    A blue screen error with the code as &#;0xE&#; (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) can be caused by any of the following:

    • Insufficient hard disk space
    • Your BIOS might be incompatible with Windows XP
    • The video adapter driver isn&#;t compatible with Windows XP
    • The device drive is misconfigured or damaged
    • Issues with the &#;sprers.eu&#; file

    Try these tips to fix this error:

    • Make sure you have enough hard disk space, windows xp installation error bsod. It&#;s very common for the 0xE error to appear because of insufficient space on the disk.
    • Try updating your BIOS software. Contact or search your computer manufacturer&#;s website on how to windows xp installation error bsod BIOS.
    • Temporarily remove any drivers you recently installed. Remove any unsigned drivers (not digitally signed by Microsoft) if the cause isn&#;t any of the recently installed drivers.

    0xE (KERNEL MODE EXCEPTION NOT HANDLED)

    The blue screen error with &#;0xE&#; as the error code and &#;KERNEL_MODE_EXCEPTION_NOT_HANDLED&#; as the error name (not necessarily displayed) can be caused by a RAM memory module that is faulty or incompatible with Windows XP.

    0xE

    To fix this error, try these methods:

    Method #1: Remove new RAM modules

    Remove any RAM modules you&#;ve recently added to your system. Then, restart your computer and try again.

    Method #2: Uninstall new software or drivers

    If 0xE appeared after installing a new piece of software or a device driver, try removing the software and restart your system to see if the error disappears.

    Method #3: Update BIOS

    Search on your computer manufacturer&#;s website on how to update your BIOS.

    0x (PAGE FAULT IN NONPAGE AREA)

    The blue screen error with the code &#;0x&#; (PAGE_FAULT_IN_NONPAGED_AREA) can be caused by corrupted data on the hard disk, incompatibility of the installed display adapter drivers with Windows XP, or other causes.

    The 0x error

    To repair your computer from this error, try the following fixes:

    Fix #1: Boot into the Last Known Good Configuration mode

    The Last Known Good Configuration mode can solve issues caused by an incorrect or misconfigured driver. To boot into this mode, follow these steps:

    1. Restart your computer
    2. Press repeatedly before the Windows XP logo appears
    3. Choose &#;Last Known Good Configuration (Advanced)&#; from the boot options menu
    4. Press

    Fix #2: Remove any new installed software or drivers

    If the error showed up after you installed a new software or a device driver, remove it from your system and try again.

    Fix #3: Check the hard disk cables

    Make sure all your hard disk cables are connected properly.

    0xD1 (DRIVER IRQL NOT LESS THAN OR EQUAL TO)

    The blue screen error with the code &#;0xD1&#; and name as &#;DRIVER_IRQL_NOT_LESS_THAN_OR_EQUAL_TO&#; can be caused by a faulty driver.

    0xD1

    Microsoft released an update for Windows XP Service Pack 2 (SP2) users that have the 0xD1 error:

    Download update #KB

    Follow the instructions from the &#;Install Instructions&#; section on how to install the update.

    If #KB doesn&#;t fix the error, try uninstalling any new device drivers you may recently installed on your system.

    0xC

    The blue screen error with the code &#;0xC&#; (sometimes with these names displayed along: STATUS_CANNOT_LOAD_REGISTRY_FILE, windows xp installation error bsod, UNKNOWN_HARD_ERROR, {Registry File Failure}) is caused by a misconfigured registry (a registry hive file can&#;t be loaded properly).

    A hive is a group of keys (and subkeys) and values in the registry.

    0xC

    You can fix the 0xC error by trying any of the following methods covered below:

    Method #1: Run the chkdsk /p command

    You need your original installation CD for this procedure. When you have the CD ready, follow these steps:

    1. Insert the CD
    2. Boot into the CD
    3. Press for Recovery Console
    4. Type in the administrator password
    5. Hit
    6. Type the following command in Command Prompt: chkdsk /p
    7. Press
    8. Restart

    Method #2: Boot to the Last Known Good Configuration

    You can boot into Windows XP&#;s Last Known Good Configuration mode by doing these steps:

    1. Restart your computer
    2. Press repeatedly before the Windows XP logo appears
    3. Choose &#;Last Known Good Configuration (Advanced)&#;
    4. Press

    Method #3: Recover the registry

    Follow the instructions from the Windows could not start: CONFIG\SYSTEM error guide on how to recover the registry of a Windows XP system.

    0xEA (THREAD STUCK IN DEVICE DRIVER)

    The blue screen error with the code &#;0xEA&#; and the name &#;THREAD_STUCK_IN_DEVICE_DRIVER&#; that a video card driver (most likely) is stuck in a loop.

    0xEA

    To fix this error, try any of the following fixes.

    Fix #1: Install the latest driver

    Make sure your video adapter has the latest driver available installed. If it&#;s not, remove the current driver, restart your computer, install the latest driver available from the manufacturer&#;s website and then restart your computer again.

    Fix #2: Adjust Hardware Acceleration

    To adjust the acceleration, follow these steps:

    1. Click Start
    2. Click Control Panel
    3. Click Display
    4. At the Settings tab, windows xp installation error bsod, click Advanced and then click on the Troubleshoot tab
    5. Move the Hardware Acceleration slider to None
    6. Click the Enable write combining option to make it unchecked
    7. Click OK
    8. Click OK again

    More Information

    Linked Entries

    Support Links

    Applicable Systems

    This Windows-related knowledgebase article applies to the following operating systems:

    • Windows XP (all editions)

    Propose an edit

    Address: Jakarta Indonesia.


  • What is the error code/message?
    Dan

  • Toolbox windows-xp-pro-l
    Dear

    I have been already checked.

    manish
  • There are a few reasons why I do not like laptops.
    And that is one of them.
    They are ornery little critters with weird hardware.
    When buying a new laptop these days, you should ask the vendor is it
    downgradable to XP.
    And they should give you a downgrade CD that can install XP, and the
    unique drivers.
    These days, getting the latter may be harder, as MS strives to eliminate
    every previous version of their software(s) from the planet.
    Have you gone to the Acer web site to download all the necessary XP
    drivers (AND ADVICE) ?


  • iRQL-NOT-LESS-OR-EQUAL
    Stop: 0xx(0x,0xD,0x,0xF4)

  • I have had similar problems when I install the raw XP with no service pack included. When I used a disk that includes SP 2, I have no problems. Some of these issues are related to new hardware windows xp installation error bsod is not supported on XP with no service pack. Hope that helps.

  • You said that installing Windows 7 is working - but when you install Windows XP did you re-format the partitions (or recreate at least the system partition).
    Another thing to check - Windows 7 is creating a "special" (system) partition at MB size that may interfere with Windows XP installation - you should delete that partition if you are installing Windows XP.

    Another things to check - in the Microsoft article: sprers.eu the "Error occurs during the installation of Windows XP" section.

    And as Mike Enos suggested - try install windows with SP2 or SP3 already included.

  • is laptop getting too hot?
  • WinXP on i3? That's not a very good ideea, XP will not know how to deal with your processor and your system will not work in its full performance. I recommend to go for w7, it will know how to deal correctly with your hardware.

    What version of xp did you try to install? with SP2, SP3?



  • What do you base that comment on?
    Regards, windows xp installation error bsod,
    Hank Arnold

    MVP (Windows Server - Directory Services)
    sprers.eu

    From: mircea_luca via windows-xp-pro-l [mailto:[email protected]]
    Sent: Monday, August 09, AM
    To: Hank Arnold
    Subject: RE:[windows-xp-pro-l] Blue screen when installing Win XP on new laptop

    Posted by mircea_luca (Net admin)
    on Aug 9 at AM Mark as helpful


    WinXP on i3? That's not a very good ideea, XP will not know how to deal with your processor and your system will not work in its full performance. I recommend to go for w7, it will know how to deal correctly with your hardware.

    What version of xp did you try to install? with SP2, windows xp installation error bsod, SP3?



  • it is very simple: winxp it is too old to know how to deal with (lets remmember dual core, SATA and other new technoolgy). It will work, of course, but you will not have the best of that tech.
    maybe i am wrong, but i saw a big difference using the same hardware and diff OS (xp vs w7) both on All the tests error pl/sql sql statement ignored did where on my own computer, and i know very well how it works on xp and how it works on w7 for ex. not to mention the linux, where my system worked very fine and surprise: it was very fast comparing with XP (i don't want to argue here which is best linus vs win, all i want is to explain that a newer OS can release the true power that come from the newer hardware).

  • Even if you manage to install XPyou will have no supporting drivers for the Laptop e.g display etcGo for winXP is becoming Ancient and its being weeded out fastchipset companies and microsoft are like done with it because of competitors like apple who are sinking their teeth into their marketbefore with any new computer you could downgrade but now even with Apple machinesdowngrading aint an option
    Go Windows 7 its an sprers.eu appreciate what the ancient softwares have done for us But we need to improve the future

  • Toolbox windows-xp-pro-lWhat??? "the cd from which you installing have been already used in a system in which virus is there " and this is going to matter How?
    I have never in my life heard so much
    Cheers Gazza
  • I agree with gazza - what a load of crap - it's a cd-ROM - ROM means 'READ ONLY' memory. A virus (or anything else for that matter) cannot possibly infect a 'real' pressed OS installation CD. The only way that the install cd could be infected is if it isn't a proper pressed CD, but rather a user burnt copy and the burning was done from an infected machine at the time of writing. But if it is a proper factory pressed CD then the Blue Screen arises because of a low-level problem during the install - maybe problems writing to the hard disk or a bad hw probe or whatever. A blue screen arises when the OS (or OS installer) encounters a situation that it cannot resolve. If cody error mitsubishi mr-s12 is the case, do try installing another OS, windows xp installation error bsod. I would recommend a latest version of Linux - why? Because Linux is (usually by default, or optionally can be made to be) VERY MUCH MORE VERBOSE on screen during installation and you get loads of 'logs' which you can examine and various tools to help sort problems. Also, the Linux CLI (Command Line Interpreter) which can be used during install is very much more powerful than the install script of Windows. Linux will also do a more 'thorough' installation - i.e. installing not just the OS, but a whole bunch of applications (e.g. Open Office) as well - so that you can better judge if an installation went OK. You also have more say over the 'format' of the disk - i.e. dual boot (if Windows or some OS is already on the drive), partitioning options, etc. The MS way is just to bulldozer over almost everything and to install just the OS on drive C: - it doesn't respect other OS's (often even if they are MS OS's) - the Windows installation is really kind of evil - that's why people put Windows on 1st and then install Linux (or whatever) in a multi-boot environment - because Windows is such a 'destructive' install.

    You could try booting from a system CD or system floppy (if you have one) and running 'FDISK' - to delete all the existing partitions on the drive. You may have to use a Linux version (or some 3rd party one) if there are any partitions that are non-Windows. Once the hard disk is totally all unassigned space (i.e. no partitions), then you can either create a primary (bootable) partition and reinstall XP - or just let XP do it for you during installation gmake[1] error 2 then you lose control over how the hard disk is to partitioned).
    HTH,
    Allan



    From: [email protected]
    To: [email protected]
    Subject: Re: [windows-xp-pro-l] Blue screen when installing Win XP on new laptop
    Date: Mon, windows xp installation error bsod, 9 Aug +

    Posted by Gazza (Technical Officer)
    on Aug 9 at AM Mark as helpful
    Toolbox windows-xp-pro-lWhat??? "the cd from which you installing have been already used in a system in which virus windows xp installation error bsod there " and this is going to matter How?
    I have never in my life heard so much
    Cheers Gazza
  • I disagree with you premise of switching to linux. The user wants xp, and it's our responsibility to help get there.
    Correct, a genuine install cd isn't infected, but remember the 'windows black' version? Had every driver imagined, windows xp installation error bsod, and every spyware too. Totally bootleg.
    I would start with bios settings, especially the hard drive settings. Play with the options. Hey, it doesn't work now, so what can you do? take it back to sata.

    From: allan_mee via windows-xp-pro-l [mailto:[email protected]]
    Sent: Monday, August 09, PM
    To: Highstreet, Jeff
    Subject: RE: [windows-xp-pro-l] Blue screen when installing Win XP on new laptop

    Posted by allan_mee
    on Aug 9 at PM Mark as helpful


    I agree with gazza - what a load of crap - it's a cd-ROM - ROM means 'READ ONLY' memory. A virus (or anything else for that matter) cannot possibly infect a 'real' pressed OS installation CD. The only way that the install cd could be infected is if it isn't a proper mac os boot0 error CD, but rather a user burnt copy and the burning was done from an infected machine at the time of writing. But if it is a proper factory pressed CD then the Blue Screen arises because of a low-level problem during the install - maybe problems writing to the hard disk or a bad hw probe or whatever. A blue screen arises when the OS (or OS installer) encounters a situation that it cannot resolve. If that is the case, do try installing another OS. I would recommend a latest version of Linux - why? Because Linux is (usually by default, or optionally can be made to be) VERY MUCH MORE VERBOSE on screen during installation and you get loads of 'logs' which you can examine and various tools to help sort problems. Also, the Linux CLI (Command Line Interpreter) which can be used during install is very much more powerful than the install script of Windows. Linux will also do a more 'thorough' installation - i.e. installing not just the OS, but a whole bunch of applications (e.g, windows xp installation error bsod. Open Office) as well - so that you can better judge if an installation went OK. You also have more say over the 'format' of the disk - i.e. dual boot (if Windows or some OS is already on the drive), partitioning options, etc. The MS way is just to bulldozer over almost everything and to install just the OS on drive C: - it doesn't respect other OS's (often even if they are MS OS's) - the Windows installation is really kind of evil - that's why people put Windows on 1st and then install Linux (or whatever) in a multi-boot environment - because Windows is such a 'destructive' install.

    You could try booting from a system CD or system floppy (if you have one) and express gate error code 8c000002 'FDISK' - to delete all the existing partitions on the drive. You may have to use a Linux version (or some 3rd party one) if there are any partitions that are non-Windows. Once the hard disk is totally all unassigned space (i.e. no partitions), then you can either create a primary (bootable) partition and reinstall XP - or just let XP do it for you during installation (but then you lose control over how the hard disk is to partitioned), windows xp installation error bsod.
    HTH,
    Allan



    From: [email protected]
    To: [email protected]
    Subject: Re: [windows-xp-pro-l] Blue screen when installing Win XP on new laptop
    Date: Mon, 9 Aug +

    Posted by Gazza (Technical Officer)
    on Aug 9 at AM Mark as helpful
    Toolbox windows-xp-pro-lWhat??? "the cd from which you installing have been already used in a system in which virus is there " and this is going to matter How?
    I have never in my life heard so much
    Cheers Gazza
  • I hope that I didn't tell the user to switch from XP to Linux (because that's not my place to). What I hope I said is '** I F** the XP installation does NOT work - and if it's a bona-fide XP CD, then try installing Linux as Linux is quite simply more helpful in these kind of problematic areas. If Linux does install ok then the user now windows xp installation error bsod that the drive and the rest of the PC is ok and that XP *should* actually install ok and can c00002la fatal system error the user can do XP's usual destructive install (getting rid of the said Linux). The reason I suggested doing a Linux install (temporarily) is that Linux has the advantages that I mentioned plus it's 'free' and, additionally, there are many Linux User Groups (LUGs) who help people with installation problems.
    Allan



    From: [email protected]
    To: [email protected]
    Date: Mon, 9 Aug
    Subject: RE: [windows-xp-pro-l] Blue screen when installing Win XP on new laptop

    Posted by broken-pc (PC Technician)
    on Aug 9 at PM Mark as helpful
    I disagree with you premise of switching to linux. The user wants xp, and it's our responsibility to help get there.
    Correct, a genuine install cd isn't infected, but remember the 'windows black' version? Had every driver imagined, and every spyware too. Totally bootleg.
    I would start with bios settings, especially the hard drive settings. Play with the options. Hey, it doesn't work now, so what can you do? take it back to sata.

    From: allan_mee via windows-xp-pro-l [mailto:[email protected]]
    Sent: Monday, August 09, PM
    To: Highstreet, Jeff
    Subject: RE: [windows-xp-pro-l] Blue screen when installing Win XP on new laptop

    Posted by allan_mee
    on Aug 9 at PM Mark as helpful


    I agree with gazza - what a load of crap - it's a cd-ROM - ROM means 'READ ONLY' memory. A virus (or anything else for that matter) cannot possibly infect a 'real' pressed OS installation CD. The only way that the install cd could be infected is if it isn't a proper pressed CD, but rather a user burnt copy and the burning was done from an infected machine at the time of writing. But if it is a proper factory pressed CD then the Blue Screen arises because of a low-level problem during the install - maybe problems writing to the hard disk or a bad hw probe or whatever. A blue screen arises when the OS (or OS installer) encounters a situation that it cannot resolve. If that is the case, do try installing another OS. I would recommend a latest version of Linux - why? Because Linux is (usually by default, or optionally can be made to be) VERY MUCH MORE VERBOSE on screen during installation and you get loads of 'logs' which you can examine and various tools to help sort problems. Also, the Linux CLI (Command Line Interpreter) which can be used during install is very much more powerful than the install script of Windows. Linux will also do a more 'thorough' installation - i.e. installing not just the OS, but a whole bunch of applications (e.g. Open Office) as well - so that you can better judge if an installation went OK. You also have more say over the 'format' of the disk - i.e. dual boot (if Windows or some OS is already on the drive), partitioning options, etc. The MS way is just to bulldozer over almost everything and to install just the OS on drive C: - it doesn't respect other OS's (often even if they are MS OS's) - the Windows installation is really kind of evil - that's why people put Windows on 1st and then install Linux (or whatever) in a multi-boot environment - because Windows is such a 'destructive' install.

    You could try booting from a system CD or system floppy (if you have one) and running 'FDISK' windows xp installation error bsod to delete all the existing partitions on the drive. You may have to use a Linux version (or some 3rd party one) if there are any partitions that are non-Windows. Once the hard disk is totally all unassigned space (i.e. no partitions), then you can either create a primary (bootable) partition and reinstall XP - or just let XP do it for you during installation (but then you lose control over how the hard disk is to partitioned).
    HTH,
    Allan



    From: [email protected]
    To: [email protected]
    Subject: Re: [windows-xp-pro-l] Blue screen when installing Win XP on new laptop
    Date: Mon, 9 Aug +

    Posted by Gazza (Technical Officer)
    on Aug 9 at AM Mark as helpful
    Toolbox windows-xp-pro-lWhat??? "the cd from which you installing have been already used in a system in which virus is there " and this is going to matter How?
    I have never in my life heard so much
    Cheers Gazza
  • whew! confusing aren't we?Ok, new laptop? Did it come with Win7? You installed Win7? Win7 works, but you can't install XP? Yes, first of all you need to know if that laptop will even work with XP. There are some machines, windows xp installation error bsod, NEW machines that are NOT made to work with XP. If the windows xp installation error bsod is only new to you and not NEW, then maybe there is hope for youwhen you try, what happens first? Can you boot the cd? When the cd boots, does it say it is trying or is installing the files it needs to run? Then does it ask you which partition to put XP on? That is VERY important. If you want to run 2 operating systems you need to have a second partition to put it on. Did you follow step by step instructions that the CD gave you? What kind of blue screen is it? Did you get the blue screen after the XP installed and you windows xp installation error bsod a XP splash screen and THEN the blue screen? That has happened to me and I fixed itboot error or corrupted file, sometimes upon installation. Can be fixed by
    carefully trying again and reformatting drive completelyworks.

    It is very hard to give the correct answer if we do not know what happened. We need the error codea blue screen does not mean the laptop is dead or needs anythingjust some help to fix the corrupted files that did not install correctlyI saved a BSOD just last week that said is was "uncorrectable"then when I fixed itit said "the file has been corrected"LOLneed more input(in mechanical voice)Peace!

  • Toolbox windows-xp-pro-lDear

    xp Sp3
    now it working but there is some problem of graphics driver i downloaded the driver of access site but it is not working, windows xp installation error bsod. The model of Laptop is:

    Acpire

    so how can I install the other graphic driver.

    Regards
    Manish Arya
  • Toolbox windows-xp-pro-lDear All


    Thank A LOT OF YOU.

    NOW The Problem Is Solved.

    Regards
    Manish Arya

  • What was the solution? It might help others.

    Regards,
    Hank Arnold

    MVP (Windows Server - Directory Services)
    sprers.eu

    From: manish via windows-xp-pro-l [mailto:[email protected]]
    Sent: Tuesday, August 10, AM
    To: Hank Arnold
    Subject: Re: [windows-xp-pro-l] Blue screen when installing Win XP on new laptop

    Posted by manish
    on Aug 10 at AM Mark as helpful


    Toolbox windows-xp-pro-lDear All


    Thank A LOT OF YOU.

    NOW The Problem Is Solved.

    Regards
    Manish Arya

  • Toolbox windows-xp-pro-lDear Hank


    The solution was very simple. In Bios changed the HDD mode "AHCI To IDE" .

    Thanks a lot of Kohar.


    Regards
    Manish Arya

  • You can use a "nLite" to build a custom installation CD:
    sprers.eu

  • Hello!
    This problem may be happen because WinXp doesn't have correct driver for HD
    controller.
    You can try change type of HD controller in BIOS.
    Good Luck

  • go to acer laptop website and download the graphic driver because any other sites caused virus


    Mohamed Reluwan.M.A.

  • Dear All,
    Try to download only Laptop Drivers which is available for your model. If
    you try other desktop graphic drivers it will be downloaded but it doesn't
    display the results what you are looking for and it will create problem by
    fixing errors in .dll files into your machines and then if you try to
    uninstall, uninstall will not be proper. So choose graphic driver to
    your Laptop model.
    Reply

    Thanks & Regards,
    sprers.euaran
    Mobile: +91
    Email: [email protected]


    *
    [email protected]*

  • try by changing sata settings tp ATA in bios
    Regards,
    Reddy
  • Hi Mohamed, I agree with you to go to Acer website (if the laptop is
    Acer) but to say ANY other sites caused virus is a bit over the top.
    I would be a bit more careful with your responses because you are
    insinuating that the Acer site is the only safe site. (Trying to be
    polite here)
    This is your opinion only.
    Cheers Gazza.

  • Have you try installing sata controllers using F6 option during xp instalation. must download from the correct vendors of the ID controllers then procceed. It will prompt you to apply the controller driver.

  • Change the BIOS settings

    SCSI are Disable OR Enable.

  • It is occurring the following situations:
    1. RAM problem (check with the new ram)
    2. While booting from XP ?press F6? insert bootable usb floppy drive which is having booting files. You can download from online based on your model.
    3. In bios settings ?disable the SCSI

    Best Regards
    sprers.euwilliams
  • Try to add sata driver in yours installation setup through nlite software
    its freeware
    PRADEEP SHARMA

    "The Dream is not what u see in sleep ! Dream is the thing which does not
    let you sleep.!!!"

  • Hi
    You say that it is a new laptop, if so have you checked that the laptop is compatible with Windows XP. One of the reasons Microsoft bring out a new operating system is that the hardware has moved beyond a point at which it can remain stable and canon mp160 carriage error take advantage of the newer features of the hardware.
    As much as I love and have fond memories of Windows XP and earlier operating systems we must bite the bullet so to speak and move on
    Just my $ worth
    Regards Greg