Blue Screen Of Death.. Blue Screen Error.. Windows

Many of you have come across a blue screen while trying to install windows xp in your new laptop. This BSOD (Blue Screen Of Death) is due to the fact that your Windows XP does not have the SATA drivers which is required to detect your Hard Disk Drives. The solution to this is to integrate SATA drivers to your winxp CD, the following steps will let you do it.
If you don’t have Floppy Disk Drive especially on a notebook. You still can install Win Xp by Slip streaming SATA driver into WinXp boot cd using nLite.
Materials needed:
1) nLite(download here), a free tool to help you slipstreaming(integrate) your SATA drivers into WinXp installation disk.
2) Extract SATA drivers (Please see the corresponding Laptop models for SATA drivers )
(if you are using Intel chipset Intel 82801GR/GH, 631xESB/632xESB, 82801GHM, ICH8R/ICH9R, 82801HEM SATA RAID Controller, get the drivers from here)
Steps:
1) Get your Windows XP installation disk and copy the contents to a new folder(I named it “WinXp”).
2) Extract the SATA drivers you downloaded into a folder
3) Run nLite->choose “Next”.

4) Now, locate the Windows folder(for me, it’s “WinXp”).
5) Next again and you will come to “Presets”. Ignore this by choosing “Next” again. 6) In “Task Selection”, choose “Drivers” and “Bootable ISO” by high-lighting them. 7) Choose “Insert”->”Single driver” Browse to the SATA driver folder and select either one of the .INF file, I choose “iaahci.inf”. 9) A screen like below will pop-up, make sure it’s “Textmode driver” ( This is the most important step ) and select all of them by holding CTRL+A key and choose “OK” 10) You shall see something like this. Choose “Next” and you will be prompted. 11) Choose “Yes” to start the process. 12) Let it finish and choose “Next”. 13) Finally, you can create your project as ISO image or burn it directly to CD-R under “Mode”. I choose “Direct Burn”. You can put anything for “Label” but not too long. Choose “Burn” and you will be prompted again. 14) Choose “Yes” to burn it to CD-R. Wait for it to finish and choose “Next”
15) Choose “Finish” to exit nLite.
Thats all You can now boot your PC or laptop with this CD and install Windows Xp with out Blue screen showing.
Credits:: http://maxeasyguide.blogspot.com

Windows Error Fix:Stop Error “Stop 0×24 - NTFS_FILE_SYSTEM” with BSOD

This BSOD 0×24 is called as “NTFS_FILE_SYSTEM” and this error normally occurs in Windows Vista or in Windows XP computer systems due to hard disk drive problem's. This Windows stop error indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk drive can induce this particular stop error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing this stop error.

Another possible cause of this “NTFS_FILE_SYSTEM” stop error is the depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this stop error in Windows based computer systems.

To resolve a disk corruption problem:

Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the Windows based computer system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer. Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.The steps for this is given:

• Insert and boot from your Windows Vista DVD or XP CD
• Select the Repair option from the opened menu.
  
• Press the number that corresponds to the correct location for the installation of Windows you want to repair. Typically this will be #1
• Enter in the administrator password when requested
• Now type chkdsk /r
• After that command is completed restart your system and check. if the issue still exist then format and reinstall the operating system.

To resolve a nonpaged pool memory depletion problem:

Either add new physical memory to the Windows based computer (thus increasing the quantity of nonpaged pool memory available to the kernel), or reduce the number of files on the Services for Macintosh (SFM) volume.

Fix a Non Booting Windows Vista Installation

NOTE: Be sure to unplug all un-necessary USB devices (everything except mouse/keyboard) before attempting any of these steps, as crazy as it sounds many people can not get the Windows Vista install CD to recognize their Windows install to repair it unless USB devices are unplugged. Don’t ask me why. Now you’ve unplugged them haven’t you? You better have. Great, lets go.

Go ahead and get out that Windows Vista Boot disk that you have, insert it into your CD drive and then turn on your computer. Hold down “F12″ while booting to open up your “Boot To” menu prompt. Select “CD-ROM” and then continue by pressing enter. Now depending on several random factors Windows Vista could take almost a full 10 minutes to get to the point where it shows its install screen. But seeing as tutorials work outside the constraints of time, let’s just assume you are already there. First you will see a screen that has some time/region info on it, go ahead and click the next button. Now instead of clicking the big shiny button in the middle, go ahead and click down at the bottom left hand side that says, “Repair your computer”. Now you should see an old Windows 95 stylistic menu and a list of all the operating systems the install disk detects. If your list is empty, try waiting a few moments or removing all but your master hard-drive. And if that fails, just go ahead and hit next anyway. Now highlight your Windows Vista OS and click Next. Now it should start up automatic recovery at this point and most problems can be fixed through this method. But if startup recovery cannot fix the problem go ahead and click on the “Command Prompt” option from the System Recovery Options.

Trick: If you know what your problem is, but just can’t get into an explorer view to delete the files or change a setting, such as compressing your bootmgr ;), at the command prompt just type in “notepad” without prompts and then select File>Open and now you will be in a simple explorer and can make changes as necessary. Back to the original solutions.

Now that you are in the command prompt, type the following commands, pressing enter after each line.

1. bootrec /fixmbr
2. bootrec /rebuildbcd
3. bootrec /fixboot
4. bootrec /scanos
5. chkdsk /r

Windows Error Fix:Windows Installer Appears Every Time Start an Application

The Windows Installer is a global application used to install many Microsoft products, including Office 2000,Office XP and Office 2007, and is even available to third-party developers to include with their programs.

Unfortunately, Windows Installer is fraught with bugs, one of which is its tendency to appear every time you start applications like Microsoft Office (or some other third party software programs) and begin a re-installation or reconfiguration process. All you'll see is the "Please Wait" screen, followed by a progress bar. The problem is related to the This feature will be installed when required option (sometimes called "Install on Demand"), used when installing some applications. In essence, Windows Installer starts to install a "feature" when it is needed, even though it may be already installed.

Unfortunately, but not surprisingly, Microsoft will not acknowledge that there is a serious flaw in their installer software. Here are the solutions we've come up with so far:

Solution 1:

• Reinstall the application in question, and don't choose the This feature will be installed when required for any of the optional components.

However, this may not solve the problem (which is the very bug we're talking about). We're currently looking for a way to fix the problem properly, but in the mean time, here's how to turn off the "feature:"

Solution 2

• Open the Group Policy Editor by selecting Run from the Start Menu, and typing gpedit.msc. (If the file is missing, run mmc.exe instead. Then, select Add/Remove Snap-in from the Console menu, click Add, and double-click Group Policy. Click Finish, then Close, then Ok.)
• Expand the following branches:
  Local Computer Policy \ Computer Configuration \ Administrative Templates \ Windows Components \ Windows Installer
• Double-click Disable Windows Installer to your right, click Enabled, and choose Always from the list. Click Ok when you're done.
• The change will take effect immediately. If you added a snap in, as described above, you don't need to "save changes to the console."
• Note: If you encounter an error about the Administrator Policy the next time you try to install an application, you'll have to re-enable the Windows Installer temporarily.

Solution 3 (for Office 2000 only):

• Run the Registry Editor (Regedit.exe) from Windows.
• Expand the branches to HKEY_CURRENT_USER\ Software\ Microsoft\ Office\ 9.0\ Common.
• Delete the UserData value on your right, and close the Registry Editor.
• The next time you start an Office application, it will ask for your username, but shouldn't bother you again.

To Fix “Black Screen on Resuming Hibernation” on Multiprocessor Computer Running on Windows Vista or Windows XP- KB951126

If you’ve a multiprocessor (32 processors) computer system running Windows Vista or Windows XP, you might have faced problems, when you tries to resume the computer from hibernation (S4), in this scenario, the computer stops responding on a black screen.

A supported hotfix is now available from Microsoft to fix this issue. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing.

Generally marked with the reference Blue Screen of Death(or BSOD), the stop errors causing the operating system to shut down, or restart the machine in order to prevent damage, and the critical system errors in Windows have reached a status of ubiquity and even managed to spawn derivations such as the Black Screen of Death.

Used in reference with the Reduced Functionality Mode introduced in Windows Vista as a direct result of the Windows Genuine Advantage mechanism detecting a non-genuine copy of the operating system, the Black Screen of Death is in fact a multifaceted labeled which can successfully be used for both Vista SP1 and XP SP3. According to Microsoft, both Vista and XP, updated with SP1 and SP3 respectively, are susceptible under the right configuration to enter into a coma and prevent any access from the end user.

“Consider the following scenario, you have a multiprocessor computer that is running Windows Vista or Windows XP, the computer has exactly 32 processors and you resume the computer from hibernation (S4),” Microsoft said. The Redmond company revealed that, in this case, either XP SP3 or Vista SP1 running on multiprocessor machines will stop respond and present the user with a black screen. The Black Screen of Death is displayed upon the resume from hibernation action. Such a process will successfully block Vista SP1 and XP SP3, the operating systems requiring a restart in order to regain functionality.

Windows Vista Can't Log In: "The system could not access the Credential Manager Server"

Credential Manager is a new SSO solution that Microsoft offers in Windows Server 2003 and Windows XP and also in Windows Vista. It's based on a secure client-side credential-caching mechanism.Single sign-on (SSO) is an approach that attempts to reduce the time users spend performing logon tasks and the number of passwords users must remember. The Open Group, an international vendor and technology-neutral consortium dedicated to improving business efficiency, defines SSO as the "mechanism whereby a single action of user authentication and authorization can permit a user to access all computers and systems where that user has access permission, without the need to enter multiple passwords". The Windows 2000 (and earlier) requirement that users must reenter the same credentials whenever they access resources on the same Internet or intranet server can be frustrating for users, especially when they have more than one set of credentials. Administrators often must cope with the same frustration when they have to switch to alternative credentials to perform administrative tasks.

When you are trying to logon to Windows vista computer,you will get an error message says "The system can not access the Credential Manger Server" .Also when you are tried logging on to Windows Vista with the local admin account, but it tells that it is disabled, and tried again by disconnecting the Windows Vista computer from the network and then trying to logon, but get the error message, "The server is not responding properly. Verify that the Credential Manager server is properly installed on the target server."

HERE'S WHAT YOU DO TO RID YOURSELF OF THIS PROBLEM IN WINDOWS VISTA.(For HP laptop)

Login to Windows Vista as a local administrator in SAFE MODE by hit F[8] before the boot process starts .Then go to services and DISABLE everything that starts with HP.

Reboot the system. Hit F[10] while it's starting and disable the security settings (the second column halfway down). You'll have to configure a password to do it for some reason.

Anyway, then you should be able to login on the local admin in NON-SAFEMODE.

Then go Windows vista START- > HP PROTECTTOOL SECURITY MANAGER - >Credential Manager -> SETTINGS and DISABLE CREDENTIAL MANAGER. If you want disable the multifactor authentication (by enabling password only) under Credential Manager -> MULTIFACTOR AUTHENTICATION.