[windows_errors] [What_Error_Messages_Really_Mean_WinXP] Er Msg:An Interrupt Storm Has Caused the System to Hang:
- From: "albertj809" <albertj809@xxxxxxxxx>
- To: What_Error_Messages_Really_Mean_WinXP@xxxxxxxxxxxxxxx
- Date: Sun, 16 Nov 2003 02:03:55 -0000
An Interrupt Storm Has Caused the System to Hang:
This info is for Windows XP,Home & Pro,Advanced Server,Ltd.Edition.
You may have Symptoms like this.
Your computer may hard hang, "It may be completely frozen and
unresponsive", and you may receive the following error message.
STOP: 0x000000F2 (0xFCA7C55C, 0x817B9B28, 0x817D2AA0, 0x00000002)
An interrupt storm has caused the system to hang.
Address FCA7C55C base at FCA72000, Datestamp 3A72BDEF - ACPI.sys
Possible Cause:
This problem can occur if any of the following behavior occurs.
A hardware device does not release its interrupt signal after being
instructed to do so by the device driver.
A device driver ignores the interrupt signal that had been initiated
from its hardware and the device driver does not instruct its
hardware to release the interrupt signal.
A device driver claims the interrupt signal even though the
interrupt signal had not been initiated from its hardware. (This
behavior can only occur when multiple devices are sharing the same
interrupt request (IRQ).
The Edge/Level Control Register (ELCR) is set incorrectly.
The ELCR interrupt-triggered devices share an IRQ (for example, a
COM port and Peripheral Component Interconnect [PCI] small computer
system interface [SCSI] controller).
A Remedy for this:
To work around this problem, examine the fourth parameter in the
error message.
If the parameter is "0x00000001", the module pointed to is very
likely the source of the problem.
Either the driver is corrupt or missing; or the hardware is
malfunctioning.
If the fourth parameter is "0x00000002", the module pointed to is
the first interrupt service routine (ISR) in the chain.
This module is not guaranteed to be the source of the problem.
Please Note:
A computer that experiences this problem repeatedly may have devices
that are on the same IRQ as the one for which the module is a
driver.
In the preceding scenario, trouble-shoot the same IRQ that the
Advanced Configuration and Power Interface (ACPI) feature uses.
Some More Info:
An interrupt storm is defined as a level-triggered interrupt signal
that remains in the asserted state.
When a bugcheck occurs, it locates the module for which the ISR on
the storming IRQ resides, and then displays the error message as
listed in the Symptoms section above.
Here's some of the Tech info about the parameters in a bugcheck
message.
Parameter 1: The address of the ISR (or the first ISR in the chain)
that is connected to the storming interrupt vector.
Parameter 2: The ISR context value.
Parameter 3: The address of the interrupt object for the storming
interrupt vector.
Parameter 4: The parameter is 0x1 if the ISR is not chained, or 0x2
if the ISR is chained.
====================================================================
Albert 290101
I'm still scratching my head.
====================================================================
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~The End~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/67folB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, send an email to:
What_Error_Messages_Really_Mean_WinXP-unsubscribe@xxxxxxxxxxxxxxx
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Other related posts:
- » [windows_errors] [What_Error_Messages_Really_Mean_WinXP] Er Msg:An Interrupt Storm Has Caused the System to Hang:
