kadaitcha.cx

Posts Tagged ‘PAGE_FAULT_IN_NONPAGED_AREA’

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.

»«