Blue screen of death (BSOD, Blue Screen of Death), or sometimes called "blue screen" (bluescreen) alone is the popular term for Microsoft Windows screen displayed when experiencing a system error (or so-called stop error by Microsoft). BSOD of Windows NT, 2000, XP, or Vista is usually more serious than previous Windows. There are several things that causes a BSOD it. Among these tools are not good drivers, memory error, damaged registry or use incompatible DLL files. Various forms contained BSOD on all Windows operating systems since Windows 3.1. BSOD is the replacement for the black screen of death (black screen of death) that appears on the OS / 2 and MS-DOS. In earlier versions of Windows Vista also include red screen of death or the red screen of death, which is used in the boot loader error.
Here's Some Code Blue Screen XP list and solution, hopefully a little help
● Attempted Write To Read only Memory (stop code 0X000000BE)
Usually the problem is due to an error in the driver or service. If the file name and the service mentioned try uninstalling the software or driver (rolling back the driver). And find the appropriate driver with its Operating System.
● Bad Pool Caller (stop code 0x000000C2)
The cause of the problem is similar to the problem of "Attempted Write To Readonly Memory," above. Additionally errors can also be caused by faulty hardware / disability. If this problem occurs when doing an upgrade of Windows, it can be caused by hardware that is not compatible with Windows. Try out hardware problems or find the appropriate driver for Windwos her.
● Data Bus Error (stop code 0x0000002E)
This problem is usually caused no damage / defects in the hardware, usually a memory. In addition to defects in memory could also be due to damage to the motherboard, hard drive, replace the hardware ...
● Driver IRQL Not Less Or Equal (stop code 0x000000D1)
Caused drivers to access the hardware address do not match. It could also be caused by problems such as the 'Attempted Write To Readonly Memory, "above. See a problem "Attempted Write To Readonly Memory" above.
● Driver Power State Failure (stop code 0X0000009F)
Caused not suitable / compatible between "computer's power management" with drivers or services that are running. It happens when the computer is doing "hibernation". If the file name and the service mentioned try uninstalling the software or driver (rolling back the driver). Or try to disable "Windows' support for power management".
● Driver Unloaded Without canceling Pending Operations (stop code 0X000000CE)
The cause of the problem is similar to the problem of "Attempted Write To Readonly Memory," above. See a problem "Attempted Write To Readonly Memory" above.
● Driver Used Excessive PTEs (stop code 0X000000D)
Look at the problem of "No More System PTEs," below.
● Hardware Interrupt Storm (stop code 0X000000F2)
Problems arise when a hardware (USB or SCSI controller) fails to "unleash" an IRQ. Failure is usually caused by a problem in the driver. Besides these problems also can arise because of the two devices use the same IRQ.
● Kernel Data Inpage Error (stop code 0X0000007A)
Problems arise in virtual memory, usually because windows can not read or write data to the swap file. Possible causes include bad sectors, virus, memory defects, or even damage the motherboard.
● Kernel Stack Inpage Error (stop code 0x00000077)
Causes similar to the "Kernel Data Inpage Error," above.
● Exception Not Handled Kmode (stop code 0x0000001E)
Usually the problem is due to an error in the driver or service, konfilk IRQ. If the file name and the service mentioned try uninstalling the software or driver (rolling back the driver). This problem can also be caused due to lack of space on the disk at the time of installation.
● No More System PTEs (stop code 0x0000003F)
The problem arises because Windows is out of Page Table Entries (PTEs). PTEs used to perform mapping RAM. Where the mapping is done by the Virtual Memory Manager (VMM). This problem can also occur when you are using multiple monitors.
If the error is likely to occur, try to increase the allocation for PTEs in Windows as follows: I
• Open the Registry Editor.
• Look in: HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager \ Memory Management
• Double-click on PagedPoolSize, enter the value 0, click OK.
• Then double-click on SystemPages. If you use multiple monitors to enter valuenya 36,000. Furthermore enter valuenya 40,000 if 128MB of RAM or less. If RAM 128MB or more enter valuenya 110 000.
• When finished, click OK, close the Registry Editor and restart the computer. when you're done. The change will take effect when you restart Windows.
● NTFS File System (stop code 0x00000024)
Error caused by a problem reported by Ntfs.sys (the driver functions to read and write NTFS). If you're still using FAT 32 file system, an error message will be similar to that signage (stop code 0X00000023). This problem can be overcome by replacing your hard drive.
Perhaps the RAM is defective / broken. Check temperature of the system, could be due to the system overheating. Use RAM Tester to test the RAM is defective or not, if you still have warranty RMA, can be tested by changing the RAM, or removing a RAM. This problem usually arises because there is also a bug driver, BIOS or hardware problem on. Technical details are listing Page Frame Number (PFN) is corrupt, especially caused by passing bad memory descriptor lists. After the Stop Code there will be 4 hex values: {Parameter 1, Parameter 2, Parameter 3, Parameter 4}.
Parameter 1 indicates the type of violation (other parameters depending on the type of computer)
Head 0x00000001 corrupt list
0x00000002 corrupt input list
0x00000007 Driver has to unlock a specific page more than the in-lock it.
0x0000008F free or blank pages from corrupt head list
0x00000099 Page Table Entry (PTE) or PFN is corrupt
0x0000009A driver tried to clean the page is still locked for IO.
Another solution:
* Make sure all your RAM (if more than one) is the same type of speed. Some motherboards do not support if the speed of RAM is different.
* If a problem arises after adding RAM, try to uninstall the newly added RAM.
* Check RAM is dah kenceng or not, make sure it is "fit" in its socket.
* Make sure the motherboard supports RAM.
* If the problem persists, the problem is likely caused by memory on the video card, try another graphics card.
Use the "Last Known Good Configuration"
1. Reboot the computer.
2. F8 when it will enter the operating system loading screen.
3. Select the Last Known Good Configuration option.
If the problem appears after installing new software, uninstall the software. Update all drivers, BIOS, Graphic Card, Motherboard, Operating System, etc..
Posts
0 comments:
Post a Comment