Stop Error 0x000000F4

I have been having this problem for a while now, and I can't identify the source of the problem!

My computer gets the BSOD with error 0x000000F4 (0x00000003....), sometimes when under heavy load, sometimes with very little load. It also hangs when left idle for 15 minutes or so...

I use SpeedFan to check temperatures and they seem normal... plus it happens when idle, nothing is overheating

The SMART for my HD says everything is fine... it is a new HD and it doesn't seem to be the cause.

I checked my RAM with Memtest86, no errors, plus my friends PC used it for a while and had no problems.

The CPU was also tested in another machine, no errors.

I have a FOXCONN mobo661MX-03 i believe, everything is integrated (VGA, sound, LAN). I have attached a minidump debug in the hope that someone can point me to the culprit!

Thank you for any help guys!


Debug text:
=======================================================
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Juan\Desktop\Mini021107-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: .sympath[+] srv*C:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sat Feb 10 16:08:15.593 2007 (GMT-4)
System Uptime: 0 days 0:11:58.101
Loading Kernel Symbols
................................................................................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, 8564db28, 8564dc9c, 805f9f88}

Probably caused by : csrss.exe

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

kd> !analyze -v
*******************************************************************************
* *
* 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: 8564db28, Terminating object
Arg3: 8564dc9c, Process image file name
Arg4: 805f9f88, Explanatory message (ascii)

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


PROCESS_OBJECT: 8564db28

IMAGE_NAME: csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: csrss

FAULTING_MODULE: 00000000

PROCESS_NAME: csrss.exe

EXCEPTION_RECORD: f79289d8 -- (.exr fffffffff79289d8)
ExceptionAddress: 75b7cb90
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000000
Parameter[1]: 75b7cb90
Parameter[2]: c000000e
Inpage operation failed at 75b7cb90, 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:
+75b7cb90
75b7cb90 ?? ???

BUGCHECK_STR: 0xF4_IOERR_C000000E

STACK_TEXT:
f7928520 8062c359 000000f4 00000003 8564db28 nt!KeBugCheckEx+0x1b
f7928544 805f9f46 805f9f88 8564db28 8564dc9c nt!PspCatchCriticalBreak+0x75
f7928574 804de7ec 8564dd70 c0000006 f79289b0 nt!NtTerminateProcess+0x7d
f7928574 804ddae1 8564dd70 c0000006 f79289b0 nt!KiFastCallEntry+0xf8
f79285f4 8051d696 ffffffff c0000006 f79289f8 nt!ZwTerminateProcess+0x11
f79289b0 805064c2 f79289d8 00000000 f7928d64 nt!KiDispatchException+0x3a0
f7928d34 804e206b 00c7f248 00c7f268 00000000 nt!KiRaiseException+0x175
f7928d50 804de7ec 00c7f248 00c7f268 00000000 nt!NtRaiseException+0x31
f7928d50 75b7cb90 00c7f248 00c7f268 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
00c7fe9c 00000000 00000000 00000000 00000000 0x75b7cb90


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0xF4_IOERR_C000000E_IMAGE_csrss.exe

BUCKET_ID: 0xF4_IOERR_C000000E_IMAGE_csrss.exe

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

 

Hi, theforceinme. Welcome to Windows BBS!

Please carefully follow all the instructions in this link and then paste your DebugWiz-generated BSOD dump log analysis reports in this thread. The additional information the DebugWiz-generated reports provide might help us narrow down the culprit more quickly.

 

Hi again, theforceinme.

Since you stated you have a new hard drive, is it an IDE (PATA) drive and is it the "C:\" hard drive on your system? If so, you should set the jumper on the back of the new hard drive as "Master" (instead of "Slave ") and it should be connected to the end connector on the IDE cable. If you have another HD on your system in addition to the new HD, then the other HD should be jumpered as "Slave" and connected to the middle connector on the IDE cable.

If the IDE (PATA) hard drives are already correctly jumpered and correctly connected to your IDE cable, then perhaps your IDE cable is faulty and should be replaced.

If the new HD is a SATA drive, connect the hard disk cable to a master channel SATA connector on the mobo. If the SATA drive is already connected correctly, then perhaps the SATA cable is faulty and should be replaced. (I am not intimately familiar with SATA yet so there may be other SATA configuration issues I am not aware of that should be addressed.)

Here's a link to the Microsoft Knowledge Base article that makes me suspect your hard drive may be jumpered incorrectly, connected incorrectly, or the hard drive data cable may be faulty.

• Microsoft KB Article 330100: Connecting a hard disk drive in slave only mode leads to system halt during resume from standby
  

According to the same Microsoft KB article I linked above:

It's probably best to access Microsoft Knowledge Base (KB) articles with Internet Explorer. I have found other web browsers (such as Firefox) have trouble rendering Microsoft KB web pages properly. (Microsoft KB pages often do not fully display in Firefox.)

Please let us know if this suggestion works for you (or not).

 

Hey mailman. Thank you for the quick reply and the welcome!

Sorry about not giving enough info, or running the dbgwiz... still fairly new at trying to fix my own PC problems... and entirely new at these debugging things.

My IDE HD jumpers are set to Single Master and I only have one. The HD was connected to the middle connector on the IDE, so I fixed that now. I hope that got it, only a matter of time to tell. I will try to crash it again in the usual ways

Thank you very much for your help. I'll try an return it to someone else if I can fix their issue

- Theforceinme

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

I generated a log file like you asked me, here is the output:

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\Documents and Settings\Juan\Desktop\Mini021107-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*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
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sat Feb 10 16:08:15.593 2007 (GMT-4)
System Uptime: 0 days 0:11:58.101
Loading Kernel Symbols
................................................................................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, 8564db28, 8564dc9c, 805f9f88}

Probably caused by : csrss.exe

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: 8564db28, Terminating object
Arg3: 8564dc9c, Process image file name
Arg4: 805f9f88, Explanatory message (ascii)

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


PROCESS_OBJECT: 8564db28

IMAGE_NAME: csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: csrss

FAULTING_MODULE: 00000000

PROCESS_NAME: csrss.exe

EXCEPTION_RECORD: f79289d8 -- (.exr fffffffff79289d8)
.exr fffffffff79289d8
ExceptionAddress: 75b7cb90
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000000
Parameter[1]: 75b7cb90
Parameter[2]: c000000e
Inpage operation failed at 75b7cb90, 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:
+75b7cb90
75b7cb90 ?? ???

BUGCHECK_STR: 0xF4_IOERR_C000000E

STACK_TEXT:
f7928520 8062c359 000000f4 00000003 8564db28 nt!KeBugCheckEx+0x1b
f7928544 805f9f46 805f9f88 8564db28 8564dc9c nt!PspCatchCriticalBreak+0x75
f7928574 804de7ec 8564dd70 c0000006 f79289b0 nt!NtTerminateProcess+0x7d
f7928574 804ddae1 8564dd70 c0000006 f79289b0 nt!KiFastCallEntry+0xf8
f79285f4 8051d696 ffffffff c0000006 f79289f8 nt!ZwTerminateProcess+0x11
f79289b0 805064c2 f79289d8 00000000 f7928d64 nt!KiDispatchException+0x3a0
f7928d34 804e206b 00c7f248 00c7f268 00000000 nt!KiRaiseException+0x175
f7928d50 804de7ec 00c7f248 00c7f268 00000000 nt!NtRaiseException+0x31
f7928d50 75b7cb90 00c7f248 00c7f268 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
00c7fe9c 00000000 00000000 00000000 00000000 0x75b7cb90


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0xF4_IOERR_C000000E_IMAGE_csrss.exe

BUCKET_ID: 0xF4_IOERR_C000000E_IMAGE_csrss.exe

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

eax=ffdff13c ebx=8564db28 ecx=00000000 edx=8564db10 esi=8564db28 edi=85610838
eip=8053331e esp=f7928508 ebp=f7928520 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
nt!KeBugCheckEx+0x1b:
8053331e 5d pop ebp
ChildEBP RetAddr Args to Child
f7928520 8062c359 000000f4 00000003 8564db28 nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo])
f7928544 805f9f46 805f9f88 8564db28 8564dc9c nt!PspCatchCriticalBreak+0x75 (FPO: [Non-Fpo])
f7928574 804de7ec 8564dd70 c0000006 f79289b0 nt!NtTerminateProcess+0x7d (FPO: [Non-Fpo])
f7928574 804ddae1 8564dd70 c0000006 f79289b0 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ f7928584)
f79285f4 8051d696 ffffffff c0000006 f79289f8 nt!ZwTerminateProcess+0x11 (FPO: [2,0,0])
f79289b0 805064c2 f79289d8 00000000 f7928d64 nt!KiDispatchException+0x3a0 (FPO: [Non-Fpo])
f7928d34 804e206b 00c7f248 00c7f268 00000000 nt!KiRaiseException+0x175 (FPO: [Non-Fpo])
f7928d50 804de7ec 00c7f248 00c7f268 00000000 nt!NtRaiseException+0x31
f7928d50 75b7cb90 00c7f248 00c7f268 00000000 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ f7928d64)
WARNING: Frame IP not in any known module. Following frames may be wrong.
00c7fe9c 00000000 00000000 00000000 00000000 0x75b7cb90
start end module name
804d7000 806eb100 nt ntoskrnl.exe Tue Mar 01 20:59:37 2005 (42250FF9)
806ec000 8070c380 hal halaacpi.dll Wed Aug 04 01:59:05 2004 (41107B29)
bf800000 bf9c1180 win32k win32k.sys Wed Oct 05 20:05:44 2005 (43446A58)
bf9c2000 bf9d3580 dxg dxg.sys Wed Aug 04 02:00:51 2004 (41107B93)
bff50000 bff52480 framebuf framebuf.dll Wed Aug 04 03:56:31 2004 (411096AF)
f6b14000 f6b37000 Fastfat Fastfat.SYS Wed Aug 04 02:14:15 2004 (41107EB7)
f6c27000 f6c78480 srv srv.sys Mon Aug 14 06:34:39 2006 (44E051BF)
f6e35000 f6e38280 ndisuio ndisuio.sys Wed Aug 04 02:03:10 2004 (41107C1E)
f7149000 f7160480 dump_atapi dump_atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f7161000 f71cfa00 mrxsmb mrxsmb.sys Fri May 05 05:41:42 2006 (445B1DD6)
f71f8000 f7222a00 rdbss rdbss.sys Fri May 05 05:47:55 2006 (445B1F4B)
f7223000 f7244d00 afd afd.sys Wed Aug 04 02:14:13 2004 (41107EB5)
f7245000 f7265f00 ipnat ipnat.sys Wed Sep 29 18:28:36 2004 (415B3714)
f7266000 f728dc00 netbt netbt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f728e000 f72e5d80 tcpip tcpip.sys Thu Apr 20 07:51:47 2006 (444775D3)
f72e6000 f72f8400 ipsec ipsec.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f7319000 f732c780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 02:07:04 2004 (41107D08)
f73d1000 f73d3900 Dxapi Dxapi.sys Fri Aug 17 16:53:19 2001 (3B7D843F)
f73f5000 f7428200 update update.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7429000 f7459100 rdpdr rdpdr.sys Wed Aug 04 02:01:10 2004 (41107BA6)
f745a000 f746ae00 psched psched.sys Wed Aug 04 02:04:16 2004 (41107C60)
f746b000 f7481680 ndiswan ndiswan.sys Wed Aug 04 02:14:30 2004 (41107EC6)
f7482000 f74a4e80 USBPORT USBPORT.SYS Wed Aug 04 02:08:34 2004 (41107D62)
f74a5000 f74c7680 ks ks.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f74c8000 f74ca580 hidusb hidusb.sys Fri Aug 17 17:02:16 2001 (3B7D8658)
f7510000 f752a580 Mup Mup.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f752b000 f7557a80 NDIS NDIS.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f7558000 f75e4480 Ntfs Ntfs.sys Wed Aug 04 02:15:06 2004 (41107EEA)
f75e5000 f75fb780 KSecDD KSecDD.sys Wed Aug 04 01:59:45 2004 (41107B51)
f75fc000 f761b780 fltMgr fltMgr.sys Mon Aug 21 05:14:57 2006 (44E97991)
f761c000 f7633480 atapi atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f7634000 f7659700 dmio dmio.sys Wed Aug 04 02:07:13 2004 (41107D11)
f765a000 f7678880 ftdisk ftdisk.sys Fri Aug 17 16:52:41 2001 (3B7D8419)
f7679000 f7689a80 pci pci.sys Wed Aug 04 02:07:45 2004 (41107D31)
f768a000 f76b7d80 ACPI ACPI.sys Wed Aug 04 02:07:35 2004 (41107D27)
f76d9000 f76e1c00 isapnp isapnp.sys Fri Aug 17 16:58:01 2001 (3B7D8559)
f76e9000 f76f3500 MountMgr MountMgr.sys Wed Aug 04 01:58:29 2004 (41107B05)
f76f9000 f7705c80 VolSnap VolSnap.sys Wed Aug 04 02:00:14 2004 (41107B6E)
f7709000 f7711e00 disk disk.sys Wed Aug 04 01:59:53 2004 (41107B59)
f7719000 f7725200 CLASSPNP CLASSPNP.SYS Wed Aug 04 02:14:26 2004 (41107EC2)
f7729000 f7733e80 uagp35 uagp35.sys Wed Aug 04 02:07:43 2004 (41107D2F)
f7739000 f7744f80 sisidex sisidex.sys Thu Oct 17 03:14:44 2002 (3DAE6364)
f7749000 f7752080 SISAGPX SISAGPX.sys Thu Jul 17 21:58:19 2003 (3F17543B)
f7779000 f7783380 imapi imapi.sys Wed Aug 04 02:00:12 2004 (41107B6C)
f7789000 f7795180 cdrom cdrom.sys Wed Aug 04 01:59:52 2004 (41107B58)
f7799000 f77a7080 redbook redbook.sys Wed Aug 04 01:59:34 2004 (41107B46)
f77a9000 f77b5e00 i8042prt i8042prt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f77b9000 f77c5880 rasl2tp rasl2tp.sys Wed Aug 04 02:14:21 2004 (41107EBD)
f77c9000 f77d3200 raspppoe raspppoe.sys Wed Aug 04 02:05:06 2004 (41107C92)
f77d9000 f77e4d00 raspptp raspptp.sys Wed Aug 04 02:14:26 2004 (41107EC2)
f77e9000 f77f1900 msgpc msgpc.sys Wed Aug 04 02:04:11 2004 (41107C5B)
f77f9000 f7802f00 termdd termdd.sys Wed Aug 04 01:58:52 2004 (41107B1C)
f7809000 f7812480 NDProxy NDProxy.SYS Fri Aug 17 16:55:30 2001 (3B7D84C2)
f7819000 f7827100 usbhub usbhub.sys Wed Aug 04 02:08:40 2004 (41107D68)
f7839000 f7841700 netbios netbios.sys Wed Aug 04 02:03:19 2004 (41107C27)
f7869000 f7871d80 HIDCLASS HIDCLASS.SYS Wed Aug 04 02:08:18 2004 (41107D52)
f7889000 f7898900 Cdfs Cdfs.SYS Wed Aug 04 02:14:09 2004 (41107EB1)
f7959000 f795f200 PCIIDEX PCIIDEX.SYS Wed Aug 04 01:59:40 2004 (41107B4C)
f7961000 f7965900 PartMgr PartMgr.sys Fri Aug 17 21:32:23 2001 (3B7DC5A7)
f7969000 f796dde0 PxHelp20 PxHelp20.sys Thu Sep 23 20:24:24 2004 (41536938)
f7999000 f799d280 usbohci usbohci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f79a1000 f79a7800 usbehci usbehci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f79a9000 f79b0e00 sisnic sisnic.sys Wed Jul 10 04:39:32 2002 (3D2BF2C4)
f79b9000 f79ba000 fdc fdc.sys unavailable (00000000)
f79c1000 f79c7000 kbdclass kbdclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f79e1000 f79e5880 TDI TDI.SYS Wed Aug 04 02:07:47 2004 (41107D33)
f79f1000 f79f5580 ptilink ptilink.sys Fri Aug 17 16:49:53 2001 (3B7D8371)
f7a01000 f7a05080 raspti raspti.sys Fri Aug 17 16:55:32 2001 (3B7D84C4)
f7a09000 f7a0ea00 mouclass mouclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7a19000 f7a1e000 flpydisk flpydisk.sys Wed Aug 04 01:59:24 2004 (41107B3C)
f7a31000 f7a36200 vga vga.sys Wed Aug 04 02:07:06 2004 (41107D0A)
f7a41000 f7a45a80 Msfs Msfs.SYS Wed Aug 04 02:00:37 2004 (41107B85)
f7a51000 f7a58880 Npfs Npfs.SYS Wed Aug 04 02:00:38 2004 (41107B86)
f7a69000 f7a6f180 HIDPARSE HIDPARSE.SYS Wed Aug 04 02:08:15 2004 (41107D4F)
f7a89000 f7a8d500 watchdog watchdog.sys Wed Aug 04 02:07:32 2004 (41107D24)
f7ae9000 f7aec000 BOOTVID BOOTVID.dll Fri Aug 17 16:49:09 2001 (3B7D8345)
f7aed000 f7aef500 sisperf sisperf.sys Tue Aug 20 05:19:07 2002 (3D62098B)
f7b75000 f7b77f80 mouhid mouhid.sys Fri Aug 17 16:47:57 2001 (3B7D82FD)
f7b79000 f7b7b580 ndistapi ndistapi.sys Fri Aug 17 16:55:29 2001 (3B7D84C1)
f7b9d000 f7ba0c80 mssmbios mssmbios.sys Wed Aug 04 02:07:47 2004 (41107D33)
f7bd1000 f7bd3280 rasacd rasacd.sys Fri Aug 17 16:55:39 2001 (3B7D84CB)
f7bd9000 f7bdab80 kdcom kdcom.dll Fri Aug 17 16:49:10 2001 (3B7D8346)
f7bdb000 f7bdc100 WMILIB WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7bdd000 f7bde700 dmload dmload.sys Fri Aug 17 16:58:15 2001 (3B7D8567)
f7bdf000 f7be0480 speedfan speedfan.sys Sun Sep 24 09:28:47 2006 (4516880F)
f7be5000 f7be6100 swenum swenum.sys Wed Aug 04 01:58:41 2004 (41107B11)
f7beb000 f7bec280 USBD USBD.SYS Fri Aug 17 17:02:58 2001 (3B7D8682)
f7bef000 f7bf0f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 16:49:37 2001 (3B7D8361)
f7bf3000 f7bf4080 Beep Beep.SYS Fri Aug 17 16:47:33 2001 (3B7D82E5)
f7bf7000 f7bf8080 RDPCDD RDPCDD.sys Fri Aug 17 16:46:56 2001 (3B7D82C0)
f7bfd000 f7bfe100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7ca1000 f7ca1d00 pciide pciide.sys Fri Aug 17 16:51:49 2001 (3B7D83E5)
f7ca2000 f7ca3000 siside siside.sys Tue Mar 25 05:50:44 2003 (3E802674)
f7ca3000 f7ca3680 giveio giveio.sys Wed Apr 03 22:33:25 1996 (316334F5)
f7d73000 f7d73b80 Null Null.SYS Fri Aug 17 16:47:39 2001 (3B7D82EB)
f7d76000 f7d76f80 avgclean avgclean.sys Mon Aug 21 18:55:15 2006 (44EA39D3)
f7e2e000 f7e2ed00 dxgthk dxgthk.sys Fri Aug 17 16:53:12 2001 (3B7D8438)
Closing open log file c:\debuglog.txt

 

You're very welcome. Thanks for the additional details and information about what you discovered.

Please let us know after awhile whether or not the 0xF4 BSODs appear to have stopped for good. I crossed my fingers hoping your IDE cable connection fix solves your issue.

 

Hey, mailman! Wow, you hit the nail on the head with this. I waited longer to make sure... no BSOD since the cable switch. I can only shake my head at how silly this seems after fixing

Thank you very much for the advice!

 

Hi, theforceinme.

Thanks for following up! I'm glad your issue seems to be fixed.

I decided to include this discussion in this thread so others with the same or similar problem (or others who want to learn more about analyzing BSOD dump data) might be able to benefit from it.

I searched the Microsoft Knowledge Base (as I often do) for 0x000000F4 and discovered the KB article with a reference to the STOP error: 0x000000F4 (0x00000003....) which exactly matches the error you posted (and also applies to Windows XP, according to that Microsoft KB article).

Upon reading that KB article which states, "This problem occurs on a computer in which Windows XP or a later operating system is installed on a hard disk that is configured as a subordinate and no other device is connected to the same IDE controller channel (primary or secondary). ... " and remembering you posted you have a new hard drive, I initially suspected you had it jumpered as "Slave ".

After thinking about it some more, I recalled from my "tinkering" with my PC over the years since the "DOS days" that the Master IDE drive should be connected to the end connector on the IDE cable. Therefore, I edited my message to include that detail.

(Thanks to a "geek friend" who helped me along in those early days with replacing hard drives, motherboards, CPUs, etc., I have always upgraded my computer hardware a little at a time. I have never bought an completely new desktop PC since my first "386" computer back in the late 1980's, if I recall the date correctly. My geek friend is the person I credit for letting me know about the "proper" IDE cable connection.)

Both. See the paragraphs above and below.

Yes.

Usually I first use the information in this 4-page article, Network World: "How to solve Windows system crashes in minutes" (specifically the last paragraph of page 3 and all of page 4). Therefore, I look at the BSOD dump analysis data for the "IMAGE NAME:..." line for a possible suspect.

Since your BSOD "IMAGE NAME:..." points to csrss.exe which is a Windows XP protected system file (instead of a 3rd party driver, for example), I felt that was a dead-end. (After looking at several BSOD dumps over the last several months and reading expert advice from BSOD experts, it seems Windows XP protected system files are rarely, if ever, the culprit.)

Since csrss.exe seemed to be a dead-end, I then proceeded to search the Microsoft KB for the string from your STOP error (0x000000F4) to see if they have any information regarding your error.

Sometimes it is also helpful to search the KB for the other parameter strings included in the parentheses of the STOP error.

I hope this information helps you (and others who may want to learn more about troubleshooting BSOD errors).

DISCLAIMER: I am NOT a BSOD expert. Therefore, you can take my advice with a grain of salt if you wish.

Experts: Please feel free to correct any misconceptions I may have portrayed in this thread (or any other thread).