Nemok ha scritto:.....stavolta è un "System Error":
Codice errore 0000009c, parametro1 00000002, parametro2 805366f0, parametro3 f6002000, parametro4 0000017a.
Id evento= 1003
Description Error code <error code>, parameter1 <param 1 value>, parameter2 <param 2 value>, parameter3 <param 3 value>, parameter4 <param 4 value>.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Comments Adrian Grigorof
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. If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.
Error code 0000009c = "MACHINE_CHECK_EXCEPTION" - This indicates that a fatal machine check exception has occurred. See also Q162363.
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. 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.
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.
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.
Windows XP SP1 resolve this issue. See Q317277.
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.
Turned out to be BlackIce v2.9 causing blue screen.
With error code 100000ea, this occured in my case due to a faulty video card
|vba excel: strano errore che costringe a riavviare pc
Forum: Applicazioni Office Windows
Visitano il forum: Nessuno e 13 ospiti