0x000000F4: CRITICAL_OBJECT_TERMINATION
(Click to consult the online MSDN article.)
One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function. Specific causes are many, and often best resolved by a careful history of the problem and the circumstances of the error message. One user, who experienced this on return from Standby mode on Win XP SP2, found the cause was that Windows was installed on a slave drive; compare KB 330100.
Solution:
PRB: Connecting a Hard Disk Drive in Slave Only Mode Leads to System Halt During Resume From Standby
Article ID
:
330100
Last Review
:
July 22, 2004
Revision
:
1.0
This article was previously published under Q330100
On this Page
SYMPTOMS
CAUSE
RESOLUTION
MORE INFORMATION
SYMPTOMS
A Windows XP-based computer stops responding during resume from standby, and you receive the following KERNEL_DATA_INPAGE_ERROR stop error message:
0x0000007a (e163a3e4,c000000e,bf8e9313,0697f860)
This problem occurs on a system where Windows XP is installed on a hard disk that is configured as a subordinate ("slave"), and no other device is connected to the same IDE controller channel (primary or secondary).
CAUSE
This behavior may occur when you use Windows XP with some motherboards. Microsoft is researching this problem and will post more information in this article when the information becomes available.
RESOLUTION
Microsoft recommends that you use one of the following methods to resolve this behavior:
•
Configure your Disk drive as Master only.
- or -
•
Connect another device as a Master, such as another disk drive or CD-ROM or DVD.
MORE INFORMATION
Steps to Reproduce the Behavior
1.
Set Hard Disk jumper to Slave mode.
2.
In BIOS power management, set BIOS to S1 or S3 (STR).
3.
Install Windows XP Professional with Service Pack 1.
4.
Power on the system.
5.
Set computer to Standby.
6.
Try to resume the system; the system stops responding.
Source:
http://aumha.org/win5/kbestop.php