.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 Tagged ‘stop 0×0000001e’

“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.

Error Message: STOP 0×00000001e KMODE_EXCEPTION_NOT_HANDLED in Win32k.sys

Symptoms
When you restart your computer, you may receive the following error message:

STOP 0×0000001e KMODE_EXCEPTION_NOT_HANDLED in win32k.sys
or

STOP 0xC000021A {Fatal System Error}The Windows Logon Process terminated unexpectedly.
Resolution
This behavior can occur if you downloaded the Backdoor.NTHack virus from a remote host into your computer. This virus is initiated by the Dl.bat file in the InetPub\Scripts folder.
As a result, both the Firedaemon.exe and Sud.exe files are installed on the computer as well as the Os2srv.exe and Mmtask.exe files, which along with the Sud.exe and Index.exe files are run as services.

“STOP 0×0000001E” Error Message During Windows Setup

Symptoms
When you run Windows XP Setup, you may receive an error message similar to the following:

STOP: 0×0000001E (0×80000003, 0xBFC0304, 0×0000000, 0×0000001)
[bugcheck code] ([1] [2] [3] [4])
Resolution
This behavior can occur if you restart your computer during or after the Windows Setup process, and if any of the following conditions are true:There is insufficient disk space on the drive on which you installed Windows.There is an outdated or incompatible third-party driver (or drivers) installed on your computer — for example a faulty video driver.There are system BIOS incompatibilities.

“STOP 0×0000001E KMODE_EXCEPTION_NOT_HANDLED” Error Message from Aspi32.sys

Symptoms
When you are using Windows XP, the following error message may be displayed:

STOP 0×0000001E KMODE_EXCEPTION_NOT_HANDLEDThe STOP screen lists Aspi32.sys as the source of the STOP error.
Resolution
This behavior can occur if an older version of the Advanced SCSI Programming Interface (ASPI) layer is installed on your computer. By default, Windows XP does not include ASPI support.

“STOP 0×0000001E KMODE_EXCEPTION_NOT_HANDLED in NTOSKRNL.EXE” Stop Error Message After You Install PcAnywhere

Symptoms
After you install Symantec Corporation’s pcAnywhere on a computer that runs Windows 2000 Professional, when you restart the computer it may stop responding. You may also receive the following stop error message:

STOP 0×0000001E KMODE_EXCEPTION_NOT_HANDLED in NTOSKRNL.EXE When you try to restart your computer, you receive the same stop error message again. The computer cannot complete the startup procedure.
Resolution
To resolve this issue, you must disable the AW_HOST and AW_HOST32 drivers, and then remove pcAnywhere from your computer. After you have removed pcAnywhere, contact Symantec Corporation to obtain the Windows 2000 pcAnywhere patch before you reinstall the software on your computer.
To disable the AW_HOST and AW_HOST32 drivers on your computer, follow these steps: Start your computer by using the recovery console. To do this, follow these steps: Start the computer from the Windows 2000 CD. At the “Welcome to Setup” screen, press R. Press C to repair a Windows 2000 installation by using the recovery console.When you are prompted by the recovery console, type the number of the Windows 2000 installation that you want to repair, and then press ENTER.Type the Administrator password, and then press ENTER.
For additional information about the recovery console, click the following article numbers to view the articles in the Microsoft Knowledge Base:
229716?(http://support.microsoft.com/kb/229716/EN-US/) Description of the Windows 2000 Recovery ConsoleType disable aw_host, and then press ENTER.Type disable aw_host32, and then press ENTER. Note: If AW_HOST32 is not present on your computer you will receive an error message. This is expected behavior and will not affect this procedure.Type exit, and then press ENTER to quit the recovery console.After you have disabled the AW_HOST and AW_HOST32 drivers, remove pcAnywhere from your computer. To do this, follow these steps: Click Start, point to Settings, and then click Control Panel.Double-click Add/Remove Programs.In the list of currently installed programs, click Symantec pcAnywhere, and then click Change/Remove.Follow the on-screen instructions to remove pcAnywhere, and then restart your computer.After you have removed pcAnywhere from your computer, contact Symantec to obtain the Windows 2000 pcAnywhere patch. After you install the patch, reinstall pcAnywhere.
For information about how to contact Symantec Corporation, visit the following Microsoft Web site:
http://support.microsoft.com/gp/vendors/en-us(http://support.microsoft.com/gp/vendors/en-us) The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.