Crashing the Connection: How to Fix BSOD 0x000000CF – TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE
BSOD error 0x000000CF, with the message "TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE", is a Windows stop codetriggered when a device driver attempts to access memory incorrectly in a Terminal Server (Remote Desktop Services) environment.
What Is BSOD Error 0x000000CF?
BSOD error 0x000000CF, with the message "TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE", is a Windows stop codetriggered when a device driver attempts to access memory incorrectly in a Terminal Server (Remote Desktop Services) environment. This error indicates that the driver was improperly ported to a terminal server scenario and is referencing memory in a way that is not supported in multi-user sessions.
Essentially, it’s a driver compatibility issue, often related to legacy or misconfigured drivers that are not designed to work in Terminal Services environments.
Key Causes of Error 0x000000CF
Incompatible or Poorly Ported Drivers
A driver has been written or modified incorrectly for Terminal Services.
Common in third-party print drivers or remote-access tools.
Misconfigured Remote Desktop Services (RDS)
Improper RDS setup or unsupported driver interactions with session memory.
Faulty Kernel-Mode Components
Drivers attempting to access memory not mapped to them in the RDS memory model.
Outdated or Corrupted Drivers
Especially in virtual environments using shared drivers.
Improper Use of Memory Reference APIs
Code in the driver misuses memory reference calls (like MmGetSystemAddressForMdlSafe).
Conflicting Software
Endpoint security tools, remote administration software, or thin client systems misbehaving.
Symptoms of This BSOD
Sudden system crashes during or after login via Remote Desktop.
Crashes when using remote printers or other redirected devices.
Blue screen displaying: "TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE"
Windows becoming unbootable in multi-user or remote session mode.
Step-by-Step Guide to Fix BSOD 0x000000CF
Step 1: Boot into Safe Mode
If you're stuck in a BSOD loop, you need to access Safe Mode:
Boot into the Windows Recovery Environment (WinRE).
Check for warnings or errors under: Applications and Services Logs → Microsoft → Windows → TerminalServices-LocalSessionManager
Avoid Unnecessary Third-Party Tools in RDS
Especially remote support tools, printing optimizers, or USB virtualization software.
Final Thoughts
The 0x000000CF BSOD is a niche but critical error affecting Terminal Server environments. It's almost always rooted in incompatibly designed or outdated drivers. The good news? With the right tools and steps, it's highly fixable and preventable.
Don’t let a rogue driver crash your entire RDS deployment—audit your driver stack, stay updated, and choose software that's made for multi-user environments.
Support.Com Can Help!
If you’re still having trouble, consider reaching out to Support.Com for a personalized solution to all technical support issues.