DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2550576 - Last Review: May 16, 2011 - Revision: 1.0

SYMPTOMS

After enabling Driver Verifier (Verifier.exe) and restarting the machine, the following STOP error may occur during the "Applying Computer Settings" startup phase:

   *** STOP: 0x000000C4 (0x0000000000000000,0x0000000000000000,0x0000000000000000,0x0000000000000000)

CAUSE

When Driver Verifier (Verifier.exe) is enabled on the tcpipreg.sys driver, the STOP 0xC4 occurs following a NULL length memory allocation.

RESOLUTION

There are two possible resolutions:

1. Disable Driver Verifier        

a. Boot the machine into Safe Mode

b. Run verifier.exe and choose "Delete existing settings"

 *or*

2. Remove the registry key that can cause the null-byte allocation (verifier can remain enabled)

a. Boot the machine into Safe Mode

b. Run regedt32.exe

c. Find the following registry key, and if the Data value is empty, remove the registry key.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces\<your-adapter-interface>

Name: IPAddress
Type: REG_MULTI_SZ
Data:

NOTE: If the Data is non-NULL, then this is not the cause of this STOP error and the IPAddress registry value should not be deleted. If IPAddress shows no Data value, then delete the IPAddress entry and restart the machine.

MORE INFORMATION

This problem has only been observed after the machine's TCP/IP configuration has been changed from a static IP address to a dynamic address with DHCP, which leaves an empty value for the IPAddress registry key for the network interface.

NOTE: If the computer is configured to reboot automatically following a failure (within Computer / Properties / Advanced system settings / Startup and Recovery Settings / Automatically Restart checkbox enabled), the STOP error may never appear on the display before the restart occurs. Instead, the machine will restart and display the option for booting Windows into Safe mode.  If no dump file is created, the only indication of the failure may be a Critical error logged to the System Event log:

   Event ID: 41
   Source:   Kernel-Power
   General:  The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped
             responding, crashed, or lost power unexpectedly.


Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

APPLIES TO
  • Windows 7 Service Pack 1
  • Windows Server 2008 R2 Service Pack 1
Keywords: 
KB2550576
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support