|Error code: 0x000000D5|
This problem appears when a driver tries to access a portion of memory that it no longer owns. To fix the problem, identify the driver wither from the BSOD or possibly from the dump file created with the bugcheck. Then, update the driver from the manufacturer, or if a new driver is not available uninstall the application if possible. Note that bad hardware can also cause this problem, so if you just installed new hardware, the problem can be caused by the hardware itself or by the driver.
The following are some examples for this error:
- M314083 - The Win32k.sys driver caused this problem on Windows 2000.
- M870896 - In this case, the Ks.sys driver was the cause of this error on a Microsoft Windows XP Service Pack 2 system.
|Links: M314083, M870896, M980226|
Keywords: error code 0x000000D5 and Bugcheck: Google - Bing - Microsoft - Yahoo
Keywords: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL: Google - Bing - Microsoft - Yahoo
|Feedback: If you have additional details about this error code, please send it to us.|