blue screen of death! - Tilted Forum Project Discussion Community

pornisbadforyou · 01-18-2005, 11:47 AM

Okay, so about a few weeks ago I started getting a blue screen of death every 3-4 days or so with the following info:

KERNEL_DATA_INPAGE_ERROR

Stop: 0x0000007A (0xC030D8614, 0xC000000E, 0xF7619BA6, 0x0D0SA860)

and then it mentioned this file: atapi.sys

So after the second or third time this happened, I completely reformatted the computer and reinstalled windows and noticed I started having the problem again.

Except now I'm getting a variety of errors..

I got this beauty:

CRITICAL_OBJECT_TERM

Stop: 0x000000F4

then I would come home to find that my computer couldn't find a boot drive a few times.

I would reboot a few minutes later and it would boot up fine.

Then today, I just got this one:

KERNEL_DATA_INPAGE_ERROR

Stop: 0x0000007A

relating to this file: pciidex.sys

I am coming to the realization that something in my laptop is totally fucked. Possibly the cd-rom drive? the hard drive? the motherboard?

Any input would be a huge help, because I'm clueless here. I'm not the biggest computer savvy dude, but I kinda know my way around. Any help would be greatly appreciated.

Thank you!!

pornisbadforyou · 01-18-2005, 11:51 AM

Oh.. and I have a Dell Inspiron 8200.

I'm running Win XP with Service Pack 2 (although the errors occurred before AND after i installed SP2 after reformatting.)

zero2 · 01-18-2005, 12:24 PM

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

pornisbadforyou · 01-18-2005, 02:20 PM

pardon my ignorance, but to do all that involves taking apart my laptop, correct?

cyrnel · 01-18-2005, 02:35 PM

It does sound like you have a hardware problem creeping up. Possibly the hard drive. If it runs for some period of time you could install a SMART monitoring utility to check condition.

Any number of utils would work. For short-term checkups I tend towards <a href="http://www.sofotex.com/SpeedFan-download_L4655.html">speedfan</a> since it also monitors temperatures.

It would also be worth running Dell's diagnostics overnight. I'm not familiar with their current stuff but you probably have it in the laptop firmware or on one of the install CD's.

Do you notice anything common happening before the crashes? Will it crash just idling or is it only during use or transition (warming up, moving, etc.)?

01-18-2005, 11:47 AM	#1 (permalink)
pornisbadforyou Crazy Location: virginia	blue screen of death! Okay, so about a few weeks ago I started getting a blue screen of death every 3-4 days or so with the following info: KERNEL_DATA_INPAGE_ERROR Stop: 0x0000007A (0xC030D8614, 0xC000000E, 0xF7619BA6, 0x0D0SA860) and then it mentioned this file: atapi.sys So after the second or third time this happened, I completely reformatted the computer and reinstalled windows and noticed I started having the problem again. Except now I'm getting a variety of errors.. I got this beauty: CRITICAL_OBJECT_TERM Stop: 0x000000F4 then I would come home to find that my computer couldn't find a boot drive a few times. I would reboot a few minutes later and it would boot up fine. Then today, I just got this one: KERNEL_DATA_INPAGE_ERROR Stop: 0x0000007A relating to this file: pciidex.sys I am coming to the realization that something in my laptop is totally fucked. Possibly the cd-rom drive? the hard drive? the motherboard? Any input would be a huge help, because I'm clueless here. I'm not the biggest computer savvy dude, but I kinda know my way around. Any help would be greatly appreciated. Thank you!!

01-18-2005, 11:51 AM	#2 (permalink)
pornisbadforyou Crazy Location: virginia	Oh.. and I have a Dell Inspiron 8200. I'm running Win XP with Service Pack 2 (although the errors occurred before AND after i installed SP2 after reformatting.)

01-18-2005, 12:24 PM	#3 (permalink)
zero2 Junkie	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

01-18-2005, 02:20 PM	#4 (permalink)
pornisbadforyou Crazy Location: virginia	pardon my ignorance, but to do all that involves taking apart my laptop, correct?

01-18-2005, 02:35 PM	#5 (permalink)
cyrnel Adequate Location: In my angry-dome.	It does sound like you have a hardware problem creeping up. Possibly the hard drive. If it runs for some period of time you could install a SMART monitoring utility to check condition. Any number of utils would work. For short-term checkups I tend towards <a href="http://www.sofotex.com/SpeedFan-download_L4655.html">speedfan</a> since it also monitors temperatures. It would also be worth running Dell's diagnostics overnight. I'm not familiar with their current stuff but you probably have it in the laptop firmware or on one of the install CD's. Do you notice anything common happening before the crashes? Will it crash just idling or is it only during use or transition (warming up, moving, etc.)?