.NET Questions and Solutions

As a software engineer, I focus on .NET, especially asp.net, C#, WCF and so on, and I am also very interested in Search Engine Optimization.

Entries for June, 2011

“0×0000003B” Stop error on a terminal server in Windows Server 2008

Symptoms
Consider the following scenario:
You install the Terminal Services role on a computer that is running Windows Server 2008.You connect to this terminal server, and then you perform some window-related operations in a terminal server session.
For example, you open and then close some windows in the terminal server session.In this scenario, the computer may restart unexpectedly. Additionally, you receive a Stop error message that resembles the following:

STOP 0×0000003B (parameter1, parameter2, parameter3, parameter4)
SYSTEM_SERVICE_EXCEPTION
Notes
The parameters in this Stop error message may vary, depending on the configuration of the computer.Not all the “Stop 0×0000003B” Stop errors are caused by this issue.

Resolution
This issue occurs because the Rdpwd.sys driver does not check whether a returned list is NULL or not.
When the returned list is NULL, the Rdpwd.sys driver accesses the wrong memory location. Therefore, an access violation exception occurs.

“0×0000001E” Stop error when you perform disk I/O-intensive operations on dynamic disks in Windows Server 2008 or in Windows Server 2008 R2

Symptoms
Consider the following scenario:
You have a computer that is running Windows Server 2008 or Windows Server 2008 R2.You set up a software RAID5 volume on the computer by using dynamic disks.You perform some disk I/O-intensive operations on the volume.
For example, you use Distributed File System (DFS) Replication to replicate files.In this scenario, you receive a Stop error message that resembles the following:

STOP 0×0000001E (parameter1, parameter2 , parameter3 , parameter4)
KERNEL_MODE_EXCEPTION_NOT_HANDLED
NotesThe parameters in this Stop error message vary, depending on the configuration of the computer. Not all “Stop 0×0000001E” error messages are caused by this issue.
Resolution
This issue occurs because of an error in the Volmgrx.sys driver.

What Are Fatal Exception Errors

Symptoms
When you attempt to shut down your computer, start Windows, or start a program in Windows, you may encounter error messages that are similar to:

A fatal exception XY has occurred at xxxx:xxxxxxxx Fatal exception errors are codes that are returned by a program in the following cases: Access to an illegal instruction has been encountered Invalid data or code has been accessed The privilege level of an operation is invalid When any of these cases occurs, the processor returns an exception to the operating system, which in turn is handled as a fatal exception error. In many cases the exception is non-recoverable and the system must either be restarted or shut down, depending upon the severity of the error.
In the sample error message that is listed above, XY represents the actual processor exception from 00 to 0F. (Note that the “h” that is listed after the 0E, 0F, and so on, in the explanations below is frequently omitted from the error message.) The xxxx:xxxxxxxx value represents the enhanced instruction pointer to the code segment; the 32-bit address is the actual address where the exception occurred.
Windows does not cause these errors, but has the exception-handling routine for that particular processor exception, which displays the error message.
NOTE: This article is primarily for informational use. Click the following link to go to the “Troubleshooting Fatal Exception Errors” section of this article:

Unknown Software Exception When Application Calls OpenGL

Symptoms
An unknown software exception occurs when applications call OpenGL. WhenWindows NT attempts to shutdown the computer, a bluescreen appears.
Resolution
To correct this problem, install the latest U.S. Service Pack for WindowsNT version 3.51.