I need help. I'm getting the Blue Screen and the "kernel inpage" message.
I Downloaded and install the Debugging Tools from Microsoft and Download and install the debugwiz. I pasted my .dmp file into the program and here are the results: Any ideas?

************************************************** *****************************
*
*
* Bugcheck Analysis
*
*
*
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, 85fa98d8, 85fa9a4c, 805c773e}

Probably caused by : hardware_disk

Followup: MachineOwner
---------

kd> !analyze -v;r;kv;lmtn;.logclose;q
************************************************** *****************************
*
*
* Bugcheck Analysis
*
*
*
************************************************** *****************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited
or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 85fa98d8, Terminating object
Arg3: 85fa9a4c, Process image file name
Arg4: 805c773e, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: 85fa98d8

IMAGE_NAME: hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAULTING_MODULE: 00000000

PROCESS_NAME: csrss.exe

EXCEPTION_RECORD: a9c689d8 -- (.exr 0xffffffffa9c689d8)
.exr 0xffffffffa9c689d8
ExceptionAddress: 75b8ffb9
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000008
Parameter[1]: 75b8ffb9
Parameter[2]: c000000e
Inpage operation failed at 75b8ffb9, due to I/O error c000000e

EXCEPTION_CODE: (NTSTATUS) 0xc000000e - A device which does not exist
was specified.

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The required data was not placed into
memory because of an I/O error status of "0x%08lx".

IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was
specified.

EXCEPTION_STR: 0xc0000006_c000000e

FAULTING_IP:
+75b8ffb9
75b8ffb9 ?? ???

BUGCHECK_STR: 0xF4_IOERR_C000000E

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
!chkimg -lo 50 -d !nt
805c776c-805c7770 5 bytes - nt!NtTerminateProcess

[ 8b ff 55 8b ec:e9 fa cd 31 29 ]
5 errors : !nt (805c776c-805c7770)

FOLLOWUP_IP:
+75b8ffb9
75b8ffb9 ?? ???

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware_disk

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0xF4_IOERR_C000000E_IMAGE_hardware_disk

BUCKET_ID: 0xF4_IOERR_C000000E_IMAGE_hardware_disk

Followup: MachineOwner



I

Run the diagnostic from your hard drive manufacture and also run sfc /scannow



Bugcheck Analysis:
CRITICAL_OBJECT_TERMINATION (f4)

The error 0x000000F4 CRITICAL_OBJECT_TERMINATION may occur if the hard drive with the operating system is installed is set as the slave or secondary drive.

If you havent changed the hard drives, you may want to do some diagnostics on it. Also this from MS Bug Check codes page:

Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION
The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread Crucial to system operation has unexpectedly exited or been terminated.

Cause
Several processes and threads are necessary for the operation of the system. When they are terminated for any reason, the system can no longer function.

It sounds from this that you have some corrupted system files. If you can get to the desktop do a search for drwtsn32. open it up and look at the Application Exception entries. You just need to look at the first part. The most recent will be towards the bottom. See what program is causing it, or if there are different ones. Actually before doing that if you get to the desktop try to run the system file checker. Go to start/run and type in sfc /scannow and let it run. It will repair or replace any corrupted system files.

so yeh.. give a system scancheck a go - sfc /scannow
you may need your winxp cd to do this..


============================

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.
0x000000F5:
0x000000F6: PCI_VERIFIER_DETECTED_VIOLATION
0x000000F7: DRIVER_OVERRAN_STACK_BUFFER
0x000000F8: RAMDISK_BOOT_INITIALIZATION_FAILED
0x000000F9: DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN
0x000000FA:
0x000000FB:

http://www.aumha.org/a/stop.htm


==============================

I ran the Dell diagnostic , which took about 2 hours, and everything passed. I also ran the sfc /scannow and it came back with nothing.

I haven' t ever changed the harddrive so I don't think it could be the slave issue.

I did a complete virus scan with Mcafee and even went online to do a second scan with Trend Micro. No problems there. I also ran Adaware and Search & Destroy for malware/spyware. No problems there either.

I opened up the drwtsn32. but couldn't figure out how to use it. There wasn't an option for Application Exception...keep in mind I an no expert at Windows. I have a basic knowledge of the inner workings. I'll look for a tutorial on the drwtsn32 program online and try that again.

Someone else recommended using the ShellExview to disable all the shell apps on my system. It looks like there are 249 shell apps running on windows. Should I try disabling all of them and then turning them on one at a time until I isolate the one that is crashing. Or am I way off base with this solution?

I always have the option of wiping the hard drive and doing a reinstall...although you know how mush time and trouble that takes. I've also read that that might not fix the problem.

Thanks for your help and if you have any other ideas please advise.

Go to Start/Run and type in:

regsvr32 /i shell32

Click OK.

Restart your computer.

Also please post any further dumps.

Did the Dell diagnostic specifically list tests on your hard drive?

Another .dmp file. This one is different.




Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini090407-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32 \drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Tue Sep 4 14:42:56.796 2007 (GMT-7)
System Uptime: 6 days 22:50:53.359
Loading Kernel Symbols
.................................................. .................................................. ..........................................
Loading User Symbols
Loading unloaded module list
..................................................
************************************************** *****************************
*
*
* Bugcheck Analysis
*
*
*
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {c07ba190, c000000e, f7432642, 3caa9860}

Probably caused by : ftdisk.sys ( ftdisk!FtDiskInternalDeviceControl+51
)

Followup: MachineOwner
---------

kd> !analyze -v;r;kv;lmtn;.logclose;q
************************************************** *****************************
*
*
* Bugcheck Analysis
*
*
*
************************************************** *****************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically
caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed
because
a filesystem failed to make forward progress.
Arguments:
Arg1: c07ba190, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000000e, error status (normally i/o status code)
Arg3: f7432642, current process (virtual address for lock type 3, or
PTE)
Arg4: 3caa9860, virtual address that could not be in-paged (or PTE
contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was
specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

TRAP_FRAME: a69eda5c -- (.trap 0xffffffffa69eda5c)
.trap 0xffffffffa69eda5c
ErrCode = 00000010
eax=00760018 ebx=86539008 ecx=00000000 edx=0000000c esi=865c9cd8
edi=00000000
eip=f7432642 esp=a69edad0 ebp=a69edb24 iopl=0 nv up ei pl zr na
pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010246
ftdisk!FtpReferenceDependantVolume:
f7432642 53 push ebx
.trap
Resetting default scope

LOCK_ADDRESS: 80551360 -- (!locks 80551360)
!locks ffffffff80551360

Resource @ nt!PiEngineLock (0x80551360) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be
corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be
corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x80551360
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 80511f39 to 804f8aef

STACK_TEXT:
a69ed930 80511f39 0000007a c07ba190 c000000e nt!KeBugCheckEx+0x1b
a69ed960 80512a5f 81748a7c c07ba190 f7432642
nt!MiWaitForInPageComplete+0x1c7
a69ed9e0 8051bfa0 c07ba190 f7432642 c07ba190 nt!MiDispatchFault+0x2b5
a69eda44 8053f90c 00000008 f7432642 00000000 nt!MmAccessFault+0x7b4
a69eda44 f7432642 00000008 f7432642 00000000 nt!KiTrap0E+0xcc
a69edacc f742951f 865c9cd8 86539008 00000000
ftdisk!FtpReferenceDependantVolume
a69edae4 804edfe3 865c9c20 86539008 00000000
ftdisk!FtDiskInternalDeviceControl+0x51
a69edaf4 f7810bd3 86594b38 8604bc00 00000000 nt!IopfCallDriver+0x31
a69edb24 f781197e 865c9c20 8655dc68 86574940
PartMgr!PmQueryDependantVolumeList+0x83
a69edb6c f7811e8a 8656bc28 8588fb94 8588fc30
PartMgr!PmBuildDependantVolumeRelations+0xd5
a69edb98 f781200d 8656bc28 c00000bb 8588fc54
PartMgr!PmQueryRemovalRelations+0x7f
a69edbd4 804edfe3 8656bb70 8588fb78 a69edc54 PartMgr!PmPnp+0x17c
a69edbe4 80587021 00000003 865c9128 a69edc7c nt!IopfCallDriver+0x31
a69edc10 804f5b89 8656bb70 a69edc30 a69edc7c nt!IopSynchronousCall+0xb7
a69edc58 80587ff2 00000003 86574940 00000001
nt!IopQueryDeviceRelations+0x45
a69edc80 80588bb1 00000000 00000003 00000001 nt!IopProcessRelation+0xfa
a69edca8 8058e424 86574940 00000003 a69edd18
nt!IopBuildRemovalRelationList+0x41
a69edd34 8058ebf0 a69edd70 806d0778 e11badd8
nt!PiProcessQueryRemoveAndEject+0x262
a69edd50 8058ed49 a69edd70 86384310 8055a3fc
nt!PiProcessTargetDeviceEvent+0x2a
a69edd74 80533fe6 86384310 00000000 8644da70 nt!PiWalkDeviceList+0xfd
a69eddac 805c4cce 86384310 00000000 00000000 nt!ExpWorkerThread+0x100
a69edddc 805411c2 80533ee6 80000001 00000000
nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
ftdisk!FtDiskInternalDeviceControl+51
f742951f eb31 jmp ftdisk!FtDiskInternalDeviceControl+0x84
(f7429552)

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: ftdisk!FtDiskInternalDeviceControl+51

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ftdisk

IMAGE_NAME: ftdisk.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3b7d8419

FAILURE_BUCKET_ID: 0x7a_c000000e_ftdisk!FtDiskInternalDeviceControl+5 1

BUCKET_ID: 0x7a_c000000e_ftdisk!FtDiskInternalDeviceControl+5 1

Followup: MachineOwner

Both dumps are pointing to your hard drive.

If you have not backed up your important data I would ASAP.

Did you note if the Dell Diagnostic specifically addressed your hard drive?

See if you can ID the manufacturer in the Device Manager:

right click My Computer then click Manage then Device Manager:

here click the + before Disk drives: what is listed?

You might as well run Check Disk as well as seen in my next post.

Try running Check Disk:

Go to start Run... and type: cmd

Then type: chkdsk /f

You will be told the volume is in use do you want to run chkdsk on next boot? Type: Y and reboot.

I did the regsvr32 /i shell32 thing also. Then I rebooted. Just letting you know...I ran the chkdsk /f yesterday and it came back fine. I'll try it again today and get back to you. Also, I'm running the HD diagnostic again. I did it yesterday as well and everything passed.

Okay... the device manager says that my hard drive is a Samsung MP0402H. By the way, the Computer in question is a Dell Inspiron B120 Notebook.

I ran the chkdsk again and it passed. I ran just the hard drive diagnostics and all tests passed.

Although... it hasn't crashed today at all and I've backed everything up.

Any more ideas?