COMMON BSOD IN WINDOWS VISTA THEIR CAUSES & SOLUTION Continued.....:

·         Stop code 0X000000F2 : Hardware Interrupt Storm
Causes :    This error occurs when a hardware device (such as a USB or SCSI con-troller) fails to
                  release an  IRQ,  a condition typically caused by a buggy driver or firmware. This error
                  can also appear if two devices are incor-rectly assigned the same IRQ.
Solution : Check the New Hardware attach to the System are not given the same IRQ, it is
                  recommended that the New Hardware are to be added one by one after the system
                  assign the IRQ.

·         Stop code 0X0000007B : Inaccessible Boot Device
Causes :    You may see this error during Windows startup if Windows cannot read data from the
                  system or boot partitions. Faulty disk controller drivers are often to blame, but this
                  problem can also be caused by hard disk errors, or even a corrupted boot.ini file, this
                  also occur incomplete or  incompatible installation of Operating System or installing
                  multiple OS.
Solution :  If all is well with your drivers and your drive, and you haven’t been messing with
                  theboot.ini file (such as while installing multiple operat-ing systems), check your
                  system BIOS settings. If you encounter this message while upgrading to Windows
                  Vista, it may mean that one or more  devices in your system are not compatible with
                  Vista. Try disconnecting unnecessary devices, or at least look for updated drivers and
                  firmware. Also, disable any antivirus software you may have  running.

·         Stop code 0X0000007A : Kernel Data Inpage Error
Causes :    This error implies a problem with virtual memory, most often in the case that Windows
                  wasn’t able to read data from—or write data to—the swap file. Possible causes include
                  bad sectors, a virus, improper SCSI termination, bad memory, or physical damage to
                  the motherboard.
Solution : Check the Hard Drive and memory also the Motherboard.

·         Stop code 0X00000077 : Kernel Stack Inpage Error
Causes :    This error implies a problem with virtual memory, most often in the case that Windows
                  wasn’t able to read data from—or write data to—the swap file. Possible causes include
                  bad sectors, a virus,  improper SCSI termination, bad memory, or physical damage to
                  the motherboard.
Solution : Check the Hard Drive and memory also the Motherboard

·         Stop code 0X0000001E : Kmode Exception Not Handled
Causes :    A faulty driver or service is sometimes responsible for this error, as are memory and
                  IRQ conflicts, and faulty firmware. This error can also be caused if you run out of disk
                  space while install-ing an application or if you run out of memory while using a buggy
                  application with a memory leak.
Solution : If the name of a file or service is specified, try uninstalling the software (or  rolling back
                  the driver if it’s an upgrade). If the Win32k.sys file is mentioned in the message, the
                  cause may be third-party remote control software.

·         Stop code 0X00000079 : Mismatched Hal
Causes :    The currently installed Hardware Abstraction Layer (HAL) must match the type of
                  computer on which Windows Vista is installed, or you may see this error. For example,
                  if you use a HAL intended for a dual-processor system on a single-processor
                  motherboard, Windows may not start. This error can also be caused by out-of-
                  dateNtoskrnl.exeor Hal.dll files, so if you’ve recently attempted to repair these files on
                  your system, look for backups of the original versions.
Solution : The best way to correct problems with the HAL is to reinstall Windows Vista.

·         Stop code 0X0000003F : No More System PTEs
Causes :    This error usu-ally means that Windows has run out of PTEs. Aside from the usual
                  assortment of faulty drivers and services that can cause all sorts of problems, this
                  error can also occur if you’re using mul-tiple monitors.

Solution : If you find that you’re experiencing this error often, you can increase Windows’
                 allocation of PTEs with this procedure:
                  1.         Open the Registry Editor.
                  2.         Then expand the branches to HKEY_LOCAL_MACHINE\SYSTEM\
                              CurrentControlSet\Control\Session Manager\Memory Management.
                  3.         Double-click thePagedPoolSize value, enter 0 for its value data.
                  4.         Click OK.
                  5.         Next, double-click the SystemPages value. If you’re using multiple monitors,
                              enter a value of 36000 here. Otherwise, enter 40000 if you have 128 MB of
                              system RAM or less, or 110000if you have more than 128 MB of RAM.
                  6.         Click OK
                  7.         Close the Registry Editor .
                  8.         Restart the System.

·         Stop code 0X00000024 : NTFS File System
Causes :    This is caused by an problem reported by Ntfs.sys, the driver responsi-ble for reading
                  and writing NTFS volumes. If you’re using the FAT32 filesystem, you may see a similar
                  message (with stopcode 0X00000023). Causes include a faulty IDE or SCSI controller,
                  improper SCSI termina-tion, an overly aggressive virus scanner, or errors on the disk
Solution : Try testing it with Chkdsk. To investigate further, open the Event Viewer(eventvwr.msc)
                  and look for error messages related to SCSIor FASTFAT (in the Systemcate-gory), or                             
                  Autochk (in the Application category).

·         Stop code 0X00000050: Page Fault In Nonpaged Area
Causes and Solution : Similar to “Attempted Write To Readonly Memory (stop code 0X000000BE),”
                  earlier in this list.