Windows error 0x000000DA, 218

Detailed Error Information

EXE_CANNOT_MODIFY_STRONG_SIGNED_BINARY[1]

MessageThe image file %1 is strong signed, unable to modify.
Declared inwinerror.h

This appears to be a raw Win32 error. More information may be available in error 0x800700DA.

SYSTEM_PTE_MISUSE[2]

This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0xDA: SYSTEM_PTE_MISUSE.

HRESULT analysis[3]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.
FlagsSeveritySuccess

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[3][1]
DescriptionThe default facility code.[3][1]
Error Code218 (0x00da)

Possible solutions

1

Performance Issues RDP Session Server 2003

windows
windows-server-2003
rdp

Bug Check 0xDA: SYSTEM_PTE_MISUSE

The SYSTEM_PTE_MISUSE bug check has a value of 0x000000DA. This indicates that a page table entry (PTE) routine has been used in an improper way.

Use WinDBG and the parameters included with the bugcheck to identify the problematic driver. Although you say in your question that you updated your video driver, I see no evidence in your question that the video driver was actually the driver causing the problem.

https://msdn.microsoft.com/en-us/library/windows/hardware/ff560282%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

If the driver that is crashing the kernel is from a 3rd party vendor, contact the vendor and see if there's an update. Or, if the driver belongs to an optional component, then uninstall it. If the driver belongs to Microsoft, then:

¯\_(ツ)_/¯

There is no valid reason or excuse to be deploying Server 2003 at this point in time.

answered on Server Fault Jan 6, 2016 by Ryan Ries
0

Performance Issues RDP Session Server 2003

windows
windows-server-2003
rdp

after a lot of testing, definitely the problem we caused because the image was not captured with Sysprep. We run sysprep and the process of recognition of the HAL allow us to connect to RDP sessions without any problems.

answered on Server Fault Feb 26, 2016 by Jason

Comments

Leave a comment

(plain text only)

Sources

  1. winerror.h from Windows SDK 10.0.14393.0
  2. https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
  3. https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0