Article ID: 290101 - Last Review: January 15, 2006 - Revision: 1.2 Error Message: An Interrupt Storm Has Caused the System to Hang
This article was previously published under Q290101 SYMPTOMS
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 CAUSE
This problem can occur if any of the following behavior occurs:
RESOLUTION
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. 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. MORE INFORMATION
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 of this article. Technical information about the parameters in a bugcheck message:
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
