English

0x000000F4 on Windows 2003 Server.

There is a number of instances of 0x000000F4 0x00000003 on Windows 2003 Server. A typical error message is the following:

STOP 0x000000F4 (0x00000003, parameter 2, parameter 3, parameter 4) CRITICAL_OBJECT_TERMINATION

Please, check the list of solutions for different cases below.

Opening and closing Multiple Console Applications

STOP 0x000000F4 0x00000003 error may occur on a Windows 2003 Server based computer in Csrss.exe process. when you open and close multiple console applications in a short time span when the computer is running under heavy load.

According to the Microsoft support, this problem is caused by a timing issue that occurs when Windows Server 2003 initializes the console IME process and is solved by the fotfix provided by the Microsoft company. Please, note that the hotfix is supposed to fix only this specific case of 0x000000F4 0x00000003 in windows server 2003.

STOP 0x000000F4 when Clicking or resizing a Window in Windows XP

You may get STOP 0x000000F4 on a Windows XP based computer when all of the following conditions are true:

You have Windows Classic theme applied. The window overlaps another window. You have a a dual-core processor or a hyper-threading processor in your computer.

A supported hotfix is available to fix this specific STOP 0x000000F4:

  • File name: Win32k.sys
  • File version: 5.1.2600.2868
  • File size: 1,839,616
  • Date: 16-Mar-2006
  • Time: 01:43
  • Platform: x86

Japanese version of Windows Server 2003.

0x000000F4 may occur on a Windows Server 2003 based computer when all of the following conditions are true:

  • You are running the Japanese version of Windows Server 2003.
  • You have Windows Server 2003 with Service Pack 1 (SP1) with the subkey HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\GRE_Initialize\SupportLinkedFontConTextOut enabled ( the value of the SupportLinkedFontConTextOut entry is 1.) or the original release version of Microsoft Windows Server 2003 with hotfix 842642 applied.
  • You change the Command Prompt window to full-screen mode after run a command with kanji characters.

The said problem is caused by incorrect processing of the size of the buffer that stores character information for full-screen mode in Windows Server 2003. As a solution, it is recommended to get the latest service pack for Windows Server 2003. In addition, a supported hotfix designed to fix this specific problem is available from the Microsoft company.

Running Hyper-V guest VM in Windows Server 2008

You may get 0x000000F4 0x00000003 error when running Hyper-V guest VM in Windows Server 2008 R2 while under stress when MPIO PathVerify is enabled, provided that you have the following configuration:

  • Windows Server 2008 R2 x64 with Hyper-V Role installed
  • MPIO path verification is enabled
  • Guest VM boot storage (VHD files) on iSCSI storage
  • iSCSI and Multi-Path I/O (MPIO) running

In this scenario, STOP 0x000000F4 0x00000003 is likely to occur after a short network interruption, such as a failover of an iSCSI target controller, while under heavy load. The error is caused by the following sequence of events:

  • Worker queue threads are extensively used by MPIO and iSCSI drivers to queue work items for processing on iSCSI initiator systems.
  • Long delay in worker thread processing that occurs under heavy stress causes disk timer expiration on the guest systems.
  • Disk timer expiration results in removal of the boot drive from the guest system which causes STOP 0x000000F4 0x00000003.

Enabling path verification in in with short PathVerificationPeriod (short path verify intervals) MPIO also increases worker queue thread and the network contention,which aggravates the situation.

To resolve the problem, you’ll have to modify the registry. We won’t explain how to open Regedit and other basics for the person managing Windows 2003 Server is supposed to be an advanced user.

  • Find and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Executive
  • Right-click AdditionalCriticalWorkerThreads value and then choose Modify In the details pane.
  • In the Value data box, if the Base set to Hexadecimal type 10 (or 16 the Base set to Decimal) and then click OK to save the changes.
  • Right-click AdditionalDelayedWorkerThreads value and then choose Modify In the details pane.
  • In the Value data box, if the Base set to Hexadecimal type 10 (or 16 the Base set to Decimal) and then click OK to save the changes.

All the changes will be effective only after reboot.

Please not that PathVerificationPeriod matters only if path verification is enabled. If you are not sure if path verification is enabled, locate the following registry entry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MPIO\Parameters\ and check the setting PathVerifyEnabled. The value may be either 0 (disabled) or 1 (enabled). The default one is disabled.

If PathVerificationPeriod is enabled, lengthen path verify intervals. To do so:

  • Locate HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mpio\Parameters
  • In the value data box for PathVerificationPeriod value type 3C (for Hexadecimal base) or 60 (for Decimal base), and then click OK to save the changes.

Connecting Hard Disk Drive in Slave Only

STOP 0x000000F4 may occur in STOP 0x000000F4 or any later OS when your computer resumes from standby with the KERNEL_DATA_INPAGE_ERROR error message. The problem occurs when the system disk is configured as a subordinate with no other device connected to the same IDE controller channel. The solution for this error is given on 0x000000F4 0x00000003 error page.