kadaitcha.cx

Archive for July, 2010

Virtual PC 2007 is free software from Microsoft. You can get both a 32-bit and 64-bit edition here.

For those of you who don’t need a step-by-step walk-through for correctly setting up NAT in a virtual machine (VM), the solution to get NAT working inside the VM is to set the IPv4 DNS server to the virtual gateway’s IP address, 192.168.131.254.

Read the rest of this entry »

Consider the following scenario:

• You have a computer that has Windows 7 preinstalled.
• You start the computer for the first time. Therefore, the Out of Box Experience (OOBE) wizard starts.
• You set the display language to Chinese or to Portuguese.

Note You notice that there are at least two entries for the language that you select.

In this scenario, you experience one or both of the following issues:

• After you restart the computer, the system display language is changed to a random language.
• When you try to restart the computer, the system cannot start and you receive a Stop error that resembles the following:

STOP 0x0000021A

Notes:

• This issue may occur up to several days after you start the computer for the first time.
• These issues may also occur if you use Language Pack Installer (Lpksetup.exe) to manually remove a language pack on a computer that is running Windows 7 Ultimate, or Windows 7 Enterprise, or Windows Server 2008 R2.

»«

When going into hibernate on a Windows 7-based computer, you may encounter the following error message:

STOP 0x000000A0 INTERNAL_POWER_ERROR

This issue can be caused if the size of the Hibernation file is not large enough for the current memory contents loaded on the system.

See the for details.

On a computer that is running Windows Server 2008 R2 or Windows 7, you receive a Stop error message that resembles the following:

STOP: 0x000000B8 (parameter1, parameter2, parameter3, parameter4)
ATTEMPTED_SWITCH_FROM_DPC

• The parameters in this Stop error message vary, depending on the configuration of the computer.
• Not all “0x000000B8″ Stop errors are caused by this problem.

This issue may occur in one of the following conditions:

• The computer is under a heavy load situation.
• The computer is connected to a network that has some connectivity issues.

»«

A computer that is running Windows 7 or Windows Server 2008 R2 may crash when you use some IEEE 1394 devices. Additionally, you may receive a Stop error message that resembles the following:

STOP 0x0000003B (Parameter1, Parameter2, Parameter3, Parameter4)
SYSTEM_SERVICE_EXCEPTION

This issue occurs because of an error in the Microsoft IEEE 1394 driver stack, in which the buffer that is allocated to the driver stack does not initialize correctly.

»«

Consider the following scenario. You have a computer that is running Windows 7 or Windows Server 2008 R2. This computer has a third-party application installed that uses the Windows Filtering Platform (WFP) callout driver. In this scenario, you may receive an error message on a blue screen. This error message resembles the following:

STOP: 0x00000050 (parameter1, parameter2, parameter3, parameter4)
PAGE_FAULT_IN_NONPAGED_AREA

WFP callout drivers are typically used in third-party antivirus and firewall programs.

This problem occurs because of an error in the TCPIP.sys system driver. When the WFP callout driver calls the FwpsReleaseClassifyHandle0 function to free up some system resources, the Stop error occurs.

»«

You enable Driver Verifier, and then you perform stress tests on a computer that is running Windows 7. However, you receive the following Stop error message during the stress tests:

Stop 0x00000050 (parameter1, parameter2, parameter3, parameter4)
PAGE_FAULT_IN_NONPAGED_AREA

Note The parameters in these Stop error messages may vary, depending on the actual configuration.

In some scenarios, the system may stop responding, and you may see some horizontal stripes on the screen.

»«

On a computer that is running Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2, you receive the following Stop error message:

STOP 0x00000050 (parameter1, parameter2, parameter3, parameter4)
PAGE_FAULT_IN_NONPAGED_AREA

The parameters in this error message vary, depending on the configuration of the computer.

Not all “Stop 0×00000050″ errors are caused by this problem. This issue occurs when the Server service handles some SMB requests from some remote computers.

This issue occurs because of a timing issue in the Server service driver. This timing issue involves the operation that adds a new SMB session to the global session table and the operation that closes an SMB session. In this timing issue, the Server service driver synchronizes these operations incorrectly. When this behavior occurs, an SMB session is added to the global session table after the session is deleted. Therefore, an entry in the global session table references freed memory. When the freed memory is accessed, you receive the Stop error message that is mentioned in the “Symptoms” section.

»«

On a computer that is running Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2, you may receive the following Stop error message:

0x000000D5 (parameter1, parameter2, parameter3, parameter4)
DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL

This behavior occurs when you perform a Windows Logo Kit (WLK) test on the computer.

»«

Consider the following scenario:

• You share an optical drive on a server that is running Windows Server 2008 R2, and then you insert a DVD disc into the drive.
• You use a network connection to access the disc from a client computer that is running Windows 7 or Windows Server 2008 R2.
• You run an application or transfer some data from the shared DVD disc.

In this scenario, the client computer crashes and you receive a Stop error message that resembles the following:

0x000000D5 (parameter1, parameter2, parameter3, parameter4)
DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL

Note This issue usually occurs if the running process of the application or the data transfer process takes more than 30 minutes.

»«

When you try to perform a native boot from a virtual hard disk (VHD), the operation fails, and you receive the following Stop error message:

A problem has been detected and Windows has been shut down to prevent
damage to your computer. An initialization failure occurred while attempting
to boot from a VHD. The volume that hosts the VHD does not have enough free
space to expand the VHD.

Stop: 0x00000136 (0x00000000, 0xc0000007f, 0x000000, 0x000000)

Note The second parameter of the bug check is ”0xc000007f - STATUS_DISK_FULL.”

This problem occurs when you use a VHD that has been configured as a dynamically expanding VHD. When you perform a native boot, a dynamically expanding VHD is expanded to its maximum size. This Stop error occurs because the volume that hosts the VHD does not have sufficient free space to expand the VHD past that boundary.

See the  for details.

Consider the following scenario:

• You have a computer that is running Windows 7 or Windows Server 2008 R2.
• During the startup process of the computer, you insert a Secure Digital (SD) card. This SD card uses the PCI-Express (PCI-E) bus.
• After the computer finishes the startup process and the desktop appears, you remove the SD card.

In this scenario, the computer crashes and then you receive a stop error message on a blue screen. This stop error message resembles the following:

STOP: 0x000000D1 (parameter1, parameter2, parameter3, parameter4)
DRIVER_IRQL_NOT_LESS_OR_EQUAL

»«

Consider the following scenario:

• A computer is running Windows Server 2008 R2 or Windows 7.
• The IPSec tunnel is configured on a network by using IPv6 transition technologies, such as Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) or IPv6 over IPv4 (6to4).
• The RequireinClearout mode is enabled on the IPSec tunnel.

Note This option is only valid on computers that are running Windows 7 or Windows Server 2008 R2.

In this scenario, the computer restarts unexpectedly and you receive the following error message:

STOP: 0x000000D1 (parameter1, parameter2, parameter3, parameter4)
DRIVER_IRQL_NOT_LESS_OR_EQUAL

When an outgoing clear text packet is sent by using the IPSec tunnel, an access violation occurs. This behaviour triggers the error message that is mentioned in the “Symptoms” section.

»«

Assume that you have a computer that is running Windows 7 or Windows Server 2008 R2. The Advanced Configuration and Power Interface (ACPI) BIOS on this computer contains a namespace object that is not a PCI device. However, Windows assumes that the device is a PCI device incorrectly. Therefore, if Windows tries to access the PCI configuration space for the device, you receive a “STOP 0x000000D1″” error message.

This issue occurs because of an error in the Acpi.sys system driver. The Acpi.sys system driver sets an incorrect value for the affected device. This causes the system to try to access the PCI configuration space for the device. However, the device is not a PCI device and the PCI configuration space does not exist.

»«

You attach a 1394 device to a computer that is running Windows 7 or Windows Server 2008 R2. In this scenario, the computer may crash after you resume the computer from sleep or from hibernation. Additionally, you may receive the following Stop error message:

STOP: 0x000000D1 (parameter1, parameter2, parameter3, parameter4)
DRIVER_IRQL_NOT_LESS_OR_EQUAL

»«

Windows based computers listed in the applies to section may display one of the following error messages on a blue screen:

STOP: 0x00000076 (0xY,0xY,0xY,0xY) PROCESS_HAS_LOCKED_PAGES

STOP: 0x000000CB (0xY,0xY,0xY,0xY) DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS

This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

(http://support.microsoft.com/kb/256986) Description of the Microsoft Windows Registry

See the  for details.