STOP 0x000000F4

[Bob Provencher]

Recently, when adding a new drive to our windows 2003 server, we received
this error when trying to resynch a mirror... we had to rearrange the drives
and resynch a mirror that already existed.

About 30 seconds into the synch, we got the following stop error:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4
(0x00000003, 0x8656cba0, 0x8656cd04, 0x8095aa0e). A dump was saved in:
C:\WINNT\Minidump\Mini020207-01.dmp.

Reasoning this may be a drive issue we tried another drive, and received the
same thing. I'm wondering if this could be a controller issue, but this box
has had a mirror on it for a few years now without incident.

The controller is an MBFastTrak133 Lite.

The drives are WD1200JB.

We're running Windows 2003 Server Std.

Any ideas to explore? I'm wondering if it is a software/driver issue.

bob at aesirsoft dot com

[Glenn LeCheminant]

From the debugger.chm

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.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 The terminating object type:

0x3: Process

0x6: Thread


2 The terminating object
3 The process image file name
4 Pointer to an ASCII string containing an explanatory message

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.

check out http://support.microsoft.com/default...en-us%3b330100

[Bob Provencher]

While it's not stand-alone, it is a slave on the secondary channel, I'll try
make it master.