Anilrgowda

I am having an annoying problem with my brand new system based on the Asus P4P800 Deluxe motherboard running Windows XP Pro.

It keeps returning me a "Serious Error":

Category: (102)
Event ID: 1003
Company Name: Microsoft Corporation
Date: 09/03/04
File Name: faultrep.dll
File Version: 5.1.2600.1232
Product Version: 5.1.2600.1232
Source: System Error
Error code: 1000008e, parameter1 c0000005, parameter2 80538105, parameter3 b20feb00, parameter4 00000000.


The Windows XP system tells me that it is a problem with a driver, but I can not find any clue to identify it, neither some documentation about that problem.

Could anybody please help me?

------------------

Anilrgowda

Source System
Type Error
Description Error code <error code>, parameter1 <value>, parameter2 <value>, parameter3 <value>, parameter4 <value>.
Things to understand What are the Windows error codes?
Comments Adrian Grigorof (Last update 10/6/2003):
Most of the problems leading to this event indicate faulty hardware, bugs in device drivers or incompatible hardware.

A troubleshooting approach from a newsgroup post: "Boot from CD to start the Recovery Console, then read setuplog.txt, and setupapi.log, to see what happens when it boots.

Another newsgroup posts suggests that this error requires the debugger to look at the parameters of the error. Usually this is some hardware driver failure. Running 'verifier' may identify it. Article Q244617 - How to Use Driver Verifier to Troubleshoot Device Drivers in Windows 2000 may help."

Error code 0000000a = "IRQL_NOT_LESS_OR_EQUAL" - The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS. For additional details see the link to error code 0x0000000a.

Error code 00000020 = "KERNEL_APC_PENDING_DURING_EXIT" - May indicate a bug in a device driver. For additional details see the link to error code 0x00000020.

Error code 00000050 = "PAGE_FAULT_IN_NONPAGED_AREA" - See the link to error code 00000050 for information about what may cause this.

Error code 0000009c = "MACHINE_CHECK_EXCEPTION" - This indicates that a fatal machine check exception has occurred. See also Q162363 and error code 0x0000009c.

Error code 000000ce = "DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERAT IONS" - This indicates that a driver failed to cancel pending operations before unloading. If the driver responsible for the error can be identified, its name is printed on the blue screen.

Error code 000000ea = "THREAD_STUCK_IN_DEVICE_DRIVER" - A device driver is spinning in an infinite loop, most likely waiting for hardware to become idle. This usually indicates problem with the hardware itself, or with the device driver programming the hardware incorrectly. In many cases this is the result of a bad video card or a bad display driver.

Error code 1000007f = "UNEXPECTED_KERNEL_MODE_TRAP_M" - The first parameter displayed on the blue screen specifies the trap number. Trap number 0x00000000, or Divide by Zero Error, may indicate memory corruption. Other hardware problems, or software failures can cause this error. See the the link to Bug Check codes for more explanations about various trap numbers.

Error code 1000008e = "KERNEL_MODE_EXCEPTION_NOT_HANDLED_M" - Most of newsgroup comments about this error point to faulty hardware or drivers. The hardware varies from modems, video cards, USB device to memory or sound cards. Sometimes it proves to be hardware that it is not compatible with Windows XP. Q310740 gives an example of this error occuring when and old Audigy sound card driver is installed.

Error code 100000be = "ATTEMPTED_WRITE_TO_READONLY_MEMORY" - This is issued if a driver attempts to write to a read-only memory segment. If the driver responsible for the error can be identified, its name is printed on the blue screen. A faulty device driver would typically be the cause of that. Also, potential file corruption.

Error code 100000ea = "THREAD_STUCK_IN_DEVICE_DRIVER_M" - This indicates that a thread in a device driver is endlessly spinning. See the information for 000000ea.

Error code 0000007F = "UNEXPECTED_KERNEL_MODE_TRAP" - From a newsgroup post: "According to Q104292, there are two known causes for this error:
- corrupt system files, especially file system files
- mismatched memory or motherboard problem
This error generally occurs during boot, with no parameters specified except the first one. Suggested troubleshooting is to run repair to check for corrupt files, then low-level hardware diagnostics (including diagnosing RAM and the motherboard)." See also the link to error code 0x0000007F.

Error code 0x10000050 = Some information about this type of error can be found via the error code 0x10000050 link.

Ionut Marin (Last update 2/18/2004):
- Error code: 0x00000050 = "PAGE_FAULT_IN_NONPAGED_AREA" - See Q817197.
- Error code: 0x0000001E - See Q820767.
- Error code: 0x000000A5 - See Q831691.

Anonymous (Last update 11/10/2003):
In my case, the error occurred after installing Kingston HyperX KHX3200/512 in a P4C800 and activated performance mode in BIOS. After I disabled Performance Mode, the problem disappeared.

Christian Garbass (Last update 10/17/2003):
Error code 0000007f = "UNEXPECTED_KERNEL_MODE_TRAP" - When I remote controlled a machine with Altiris Carbon Copy 5.8.410 and tried to open a shortcut on the desktop of the controlled machine it caused the machine to hang up and to reboot.

Isd503 (Last update 9/22/2003):
Error code 0000007f = "UNEXPECTED_KERNEL_MODE_TRAP" - This error surfaced on my machine running Windows XP Professional, SP-1. I tried the suggestion of setting the virtual memory to zero and rebooting. After logon, I recreated the page file and the problem dissapeared.

Adrian Florin Moisei (Last update 5/15/2003):
Error code 000000d1 = "DRIVER_IRQL_NOT_LESS_OR_EQUAL". A faulty device driver would typically be the cause of that. See also the comments for event id 1001 from "Save Dump".

Error code 000000c2 = "BAD_POOL_CALLER" - See Q265879 link below.
Error code 00000044 = "MULTIPLE_IRP_COMPLETE_REQUESTS" - See Q196022, Q296734 and Q294876.

PaulD
Windows XP SP1 resolve this issue. See Q317277.

Birol | AKBAY
In my case, this error for a motherboard using Bus Mastering and a NIC that does not support Bus Mastering. When Bus mastering is disabled from BIOS, this type of error went away.

Anonymous
With error code 100000ea, this occured in my case due to a faulty video card.

Charlton Wang
From the net, someone mentioned setting the Virtual memory to 0 and then reboot, delete the pagefile.sys file. Then set the virtual memory back to normal. It worked for me.

Axton
Turned out to be BlackIce v2.9 causing blue screen.

------------------