BSOD 312 (GPIO_CONTROLLER_DRIVER_ERROR): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: the GPIO controller driver reported a fatal controller or framework error.

Could be also:
Constant	Type	OS
ERROR_NO_RANGES_PROCESSED	Win32 error	Windows

Previous	Next
WIN32K_HANDLE_MANAGER	KERNEL_SECURITY_CHECK_FAILURE

GPIO_CONTROLLER_DRIVER_ERROR

GPIO controller driver failure

GPIO_CONTROLLER_DRIVER_ERROR is bug check code 0x00000138. The built-in table identifies it as GPIO_CONTROLLER_DRIVER_ERROR; the useful diagnostic question is what Windows component raised the stop and which invariant failed.

This bug check points to a GPIO controller driver or its integration with the Windows GPIO framework. It is usually about interrupt/resource/controller state, not a generic device installation problem.

How to read the parameters

Use the dump to identify the GPIO controller driver and whether the path involves interrupt handling, resource translation, or power transition.
ACPI resource descriptions can be relevant on modern systems.
The stack and device node are more useful than the symbolic name alone.

What to check in the dump

Check the GPIO controller driver version, ACPI firmware tables, SoC/chipset package, and recent BIOS updates.
Look for crashes during sleep/resume, device enumeration, interrupt storms, or GPIO-backed device activity.
Inspect related ACPI and PnP logs before blaming the consumer device attached to the GPIO line.

References

Looking for a different code? Search another status or error code.