You should apply any patches for the OS that might be out there (especially if they mention they are related to Terminal Server or RDP). You should also probably contact Microsoft support.
The crash dump looks like the crash is happening in the RDP driver.
Even if the winoac.exe application is passing bad data to win32k.sys (the display subsystem) that results in the crash, device drivers are never supposed to crash the system - they should detect and handle the problem appropriately, even if it means the application crashes. The driver should never crash, so MS should take an interest in this so they can fix it.
Unless Smartware has developed their own drivers it should never be possible for a user mode application to bluescreen a windows NT server.
So, ignoring all that information, you are either looking at a buggy device driver - step 1 - find and install any updates for drivers on the system, OR the hardware is beginning to fail. even bug free drivers might need to throw a bug check when the actual hardware they depend on is failing.
win32k.sys is the kernel driver side of the win32 subsystem, not specifically a display driver at all. However the call stack does implicate that something related to drawing crashed, so, perhaps starting with updating the systems video drivers - or replacing the video card if its not onboard might help.
发布评论
评论（2）
您应该为可能存在的操作系统应用任何补丁（特别是如果它们提到它们与终端服务器或 RDP 相关）。 您或许还应该联系 Microsoft 支持人员。
故障转储看起来崩溃发生在 RDP 驱动程序中。
即使 winoac.exe 应用程序将错误数据传递给 win32k.sys（显示子系统）导致崩溃，设备驱动程序也不应该导致系统崩溃 - 它们应该检测并处理问题适当地，即使这意味着应用程序崩溃。 驱动程序永远不应该崩溃，因此微软应该对此感兴趣，以便他们可以修复它。
You should apply any patches for the OS that might be out there (especially if they mention they are related to Terminal Server or RDP). You should also probably contact Microsoft support.
The crash dump looks like the crash is happening in the RDP driver.
Even if the
winoac.exeapplication is passing bad data to win32k.sys (the display subsystem) that results in the crash, device drivers are never supposed to crash the system - they should detect and handle the problem appropriately, even if it means the application crashes. The driver should never crash, so MS should take an interest in this so they can fix it.除非 Smartware 开发了自己的驱动程序，否则用户模式应用程序永远不可能蓝屏 Windows NT 服务器。
因此，忽略所有这些信息，您要么正在查看有缺陷的设备驱动程序 - 第 1 步 - 查找并安装系统上驱动程序的任何更新，要么硬件开始出现故障。 即使没有错误的驱动程序也可能需要在它们所依赖的实际硬件出现故障时进行错误检查。
win32k.sys 是 win32 子系统的内核驱动程序端，根本不是专门的显示驱动程序。 然而，调用堆栈确实暗示与绘图相关的某些内容崩溃了，因此，也许从更新系统视频驱动程序开始 - 或者更换视频卡（如果没有板载）可能会有所帮助。
Unless Smartware has developed their own drivers it should never be possible for a user mode application to bluescreen a windows NT server.
So, ignoring all that information, you are either looking at a buggy device driver - step 1 - find and install any updates for drivers on the system, OR the hardware is beginning to fail. even bug free drivers might need to throw a bug check when the actual hardware they depend on is failing.
win32k.sys is the kernel driver side of the win32 subsystem, not specifically a display driver at all. However the call stack does implicate that something related to drawing crashed, so, perhaps starting with updating the systems video drivers - or replacing the video card if its not onboard might help.