This post come from Brian Higgins, former Third Tier staff member.
Brian ran into an issue for which he could find no public information about yet. This issue appears to be quite similar to the known issue with Windows 8 and some video drivers. Since Windows 8 and Server 2012 share much of the same code this isn’t surprising but this is first known documented case.
The server would BSOD after logging off an RDP session (most of the time). After lots of digging I identified from a nearly identical issue someone was having with Windows 8 that the (likely) culprit was the video driver. This server was a brand new Dell R720 server, and while all the “important” drivers had been updated when it was setup a week ago, the video card had not gotten any second thought and was running the default windows driver (who updates the video card driver on a Hyper-V Host?). A update to the correct driver from Dell’s website (which was major 3 version numbers newer) appears to have solved the issue.
In the event log was:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 4/19/2013 5:53:58 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SERVER2012.contoso.local
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ab (0×0000000000000001, 0×0000000000001160, 0×0000000000000000, 0x000000000000002b). A dump was saved in: C:\Windows\MEMORY.DMP.
And an Analysis of the minidump showed:
TAG_NOT_DEFINED_405: Uspf
BUGCHECK_STR: 0xAB_Uspf
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: win32k
FAULTING_MODULE: fffff960000b4000 win32k
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT_SERVE
So if you run into Server 2012 that is suffering BSOD you may want to start by making sure that you update the video driver.
—
So who wrote this blog and what do they do for a living anyway?
We’re Third Tier. We provide advanced Third Tier support for IT Professionals.
Get Support
Blog
Twitter
Facebook
LinkedIN
