Event ID 1003 Source System
| Event ID | 1003 |
| Source | System |
| Type | Error |
| Description | Error code <error code>, parameter1 <value>, parameter2 <value>, parameter3 <value>, parameter4 <value>. |
| English, please! | This information is only available to subscribers. An example of English, please! |
| Concepts to understand |
What is the Nonpaged memory pool? What is an IRQL? What are the Windows error codes? What is the kernel? |
| Comments |
Adrian Grigorof
(Last update 2/2/2009): 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 M244617 - 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 M162363 and Error code 0x0000009c. Error code 000000ce = "DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS" - 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. M310740 gives an example of this error occuring when and old Audigy sound card driver is installed. Error code 000000be = "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 Error code 000000ea. Error code 0000007F = "UNEXPECTED_KERNEL_MODE_TRAP" - From a newsgroup post: "According to M104292, 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. Error code 0x0000004e = PFN_LIST_CORRUPT - While this error points to a corrupt memory structure, some forum posts reported this as happening when Panda Antivirus was conflicting with another antivirus program. Mihai Andrei (Last update 11/8/2008): - Error code: 000000D6 - See M935198 for a hotfix applicable to Microsoft Windows XP. - Error code: 000000D5 (Error code 0x000000D5) - See M935198 for a hotfix applicable to Microsoft Windows XP. - Error code: 0000007F (Error code 0x0000007F) - See M928006 for a hotfix applicable to Microsoft Windows Server 2003. - Error code: 0x00000077 - See the link to Error code 0x00000077 for general information about this error. - Error code: 00000024 - See M910311 for a hotfix applicable to Microsoft Windows Server 2003. - Error code: 0x000000CB - See Error code 0x000000CB. - Error code: 0x000000de (Error code 0x000000de) - See M304208 for a possible solution. - Error code: 0000000A (Error code 0x0000000A) - See M908369. - Error code: 00000027 - See "Symantec Knowledge Base Document ID: 2005062009145248". - Error code: 000000E3 - See M900808 for a hotfix applicable to Microsoft Windows XP. - Error code: 00000020 (Error code 0x00000020) - See M905539. - Error code: 0x0000009C (Error code 0x0000009C) - See M329284, M840551 and the link to "Stop message 0x0000009C". - Error code: 00000019 - See M892260 for a hotfix applicable to Microsoft Windows Server 2003. - Error code: 0x0000007E (Error code 0x0000007E) - See M820362 for a hotfix applicable to Microsoft Windows Server 2003 and Microsoft Windows Small Business Server 2003. - Error code: 000000C2 (Error code 0x000000C2) - See M890756 for a hotfix applicable to Microsoft Windows 2000 and Microsoft Windows Server 2003, and M896674 for a hotfix applicable to Microsoft Windows 2000. - Error code: 0000008E (Error code 0x0000008E) - See M894061, M898542 and M907966 for three hotfixes applicable to Microsoft Windows Server 2003. Also see M903251 and M959252 for additional information about this event. - Error code: 000000D1 (Error code 0x000000D1) - See M892137 for a hotfix applicable to Microsoft Windows 2000, M925922 for a hotfix applicable to Microsoft Windows XP and M894086, M926754 and M931322 for three hotfixes applicable to Microsoft Windows Server 2003. - Error code: 1000007e - From a newsgroup post: "Turns out it was an errant file from the Sonic MyDVD program that I never use. I found this out because whenever it would crash to the blue screen, it mentioned the file tfsnpool.sys. I did a search for that file, checked the properties and found it was put there by Sonic and had something to do with the drive letter. So I renamed the files, which was probably taking a big chance, deleted everything Sonic related and all is well". Also check M330182 for possible causes and a resolution. - Error code: 100000d1 - From a newsgroup post: "In the end it was the pagefile that was corrupted. I selected the no pagefile option under the perfomance menu in system properties, rebooted, and then recreated the pagefile". Anonymous (Last update 1/30/2008): - Error code: 0x000000C4 - This problem might be happening because of Norton AntiVirus. See M325672 for details. Anonymous (Last update 7/10/2007): We ran the free MS memory tester, and 1 stick of RAM was bad. To get the RAM tester follow the link “Windows Memory Diagnostic”. Rhonda Lea Kirk (Last update 5/4/2006): - Error code: 1000007e - This problem occurs only during the use of the CD-DVD player/burner. Microsoft's response to this error: "it's a device driver". Dell's Crash Analysis Tool says the problem is caused by tfsnifs.sys from Sonic. I have found some evidence (Google) that others have had a problem with the Sonic DLA and that by disabling DLA the crashes stop. The current driver version is 5.2 and I am using 4.88 so upgrading to the latest driver may fix this problem. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! Ashkan Abtahi (Last update 1/31/2006): - Error code: 0x000000de (Error code 0x000000de) - Go to Services in Administrative Tools and find the "Remote Procedure Call" (RPC) service. Open it and change it from "Restart the computer" to "Restart the service". This will solve the reboot issue. Ionut Marin (Last update 10/24/2005): - Error code: 0x00000050 = "PAGE_FAULT_IN_NONPAGED_AREA" - See M817197, M894278, M897079, and M903251. - Error code: 0x0000001E (Error code 0x0000001E) - See M820767, M822563, and M898114. - Error code: 0x000000A5 (Error code 0x000000A5) - See M831691 and the link to Error code 0x000000A5. - Error code: 0x000000d1 (Error code 0x000000D1) = "DRIVER_IRQL_NOT_LESS_OR_EQUAL" - See M837432. - Error code: 0x000000c5 = DRIVER_CORRUPTED_EXPOOL - See the link to "Error code 0x000000c5" for details on this error code. - Error code: 0x000000D5 - See M870895 and M870896. - Error code: 0x0000007f (Error code 0x0000007F) - See M870908 and M891722. - Error code: 0x0000000A (Error code 0x0000000A) - See M897079. - Error code: 0x00000076 (Error code 0x00000076) - See M895473. See the link to "Windows XP Stop Errors" and "Stop Messages" for information regarding error codes. Mathias Bachmann (Last update 8/15/2005): - Error code: 0x00000050 (Error code 0x00000050) - In my case, the error was caused by a IRQ/DMA conflict with the parallel port. The Windows-suggested configuration of LPT 1 was E/A 0278-027F, DMA 3, set to "auto" in the Bios. Setting it via Bios manually to DMA 1, E/A 0378-037F, ECP solved the problem. Mickey (Last update 2/7/2005): - Error code: 0x000000EA (Error code 0x000000EA) - If you have a video card with an Intel chipset, update to the latest drivers to resolve this problem. See the link to "Intel Support Solution ID: CS-016497" for additional information on this issue. Tom (Last update 2/7/2005): - Error code: 0x000000d1 (Error code 0x000000D1) - If you have installed Backup Exec 9.0 revision 4454 or Backup Exec 9.1 revision 4691, then see the link to "Veritas Support Document ID: 261728" for information on resolving this problem. Ronald (Last update 10/4/2004): - Error code: 0xc0000005 (Error code 0xc0000005) = STATUS_ACCESS_VIOLATION - My computer started to reboot randomly after I installed Windows XP SP2. After searching the Web, I found this to be related to a new addition in Windows XP brought by SP2, namely Data execution prevention (DEP). If you have hardware or software that does not work properly after the installation of SP2 then deactivate DEP. You do that in the “boot.ini” file with the “/noexecute=AlwaysOff” switch. After I modified the “boot.ini” file accordingly, this problem ceased to reappear. See the link to “Memory Protection Technologies in WinXP SP2” for more details on this issue. Charlton Wang (Last update 8/9/2004): From the net, someone mentioned setting the Virtual memory to 0, reboot and delete the pagefile.sys file. Then set the virtual memory back to normal. It worked for me. See M255205 for information on how to delete the pagefile.sys file in Recovery Console. LHI (Last update 7/21/2004): If you are running on the following hardware: "HP ProLiant DL380 G3", then HP suggests that it can be solved by a BIOS update. See "HP ProLiant DL380 G3 BIOS Update" to get the update. Nougat (Last update 7/13/2004): - Error code: 0xD1 (Error code 0xD1) - See M829120 for a hotfix applicable to Microsoft Windows 2000 and to Microsoft Windows XP. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! Wendi Fisher (Last update 5/16/2004): On my Alienware Area 51 M laptop computer, this error was generated due to a conflict between the Linksys Wireless -G notebook adapter and the native Windows XP wireless manager. If you get this error and you have one of these cards you need to call Linksys tech support and they will walk you through installing the drivers for the card without installing the control utility, which is what conflicts with Windows XP. Anonymous (Last update 5/14/2004): See M322205 for info on how to troubleshoot Hardware and Software Driver problems in Windows XP. 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 M265879 link below. Error code 00000044 = "MULTIPLE_IRP_COMPLETE_REQUESTS" - See M196022, M296734 and M294876. 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. Axton Turned out to be BlackIce v2.9 causing blue screen. PaulD Windows XP SP1 resolve this issue. See M317277. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! Anonymous With Error code 100000ea, this occured in my case due to a faulty video card. |
| Links | M104292, M196022, M244617, M255205, M265879, M294876, M296734, M310740, M317277, M322205, M325672, M329284, M330182, M817197, M820362, M820767, M822563, M829120, M831691, M837432, M840551, M870895, M870896, M870908, M890756, M891722, M892137, M892260, M894061, M894086, M894278, M895473, M896674, M897079, M898114, M898542, M900808, M903251, M905539, M907966, M908369, M910311, M925922, M926754, M928006, M931322, M935198, M959252, Error code 0x0000000a, Error code 0x00000077, Error code 0x000000CB, Error code 0x00000020, Error code 0x0000007F, Error code 00000050, Error code 0x0000007E, Error code 0x000000de, Error code 0x0000009c, Error code 0x000000A5, Error code 0x10000050, Error code 0x000000D1, Error code 0x000000c5, Error code 0x0000008E, Error code 000000C2, Error code 0x000000D5, Error code 0x00000076, Interpreting Bug Check Codes, Windows XP Stop Errors, Symantec Knowledge Base Document ID: 2005062009145248, Stop Messages, HP ProLiant DL380 G3 BIOS Update, Memory Protection Technologies in WinXP SP2, Intel Support Solution ID: CS-016497, Veritas Support Document ID: 261728, Stop message 0x0000009C, Windows Memory Diagnostic |
| Search | Google Web - Microsoft Support - Bing - EventID.Net Queue - More links... |
| Custom search | The custom search information is available to subscribers only. |
| Feedback | Send comments - Notify me when updated |
| Print version |