Windows 10: BSOD due to GPIO_CONTROLLER_DRIVER_ERROR (138)

I need some pointers to where I can further look to understand my issue.

My Surface Laptop (1st. Gen, i7 - running Build 2004) is crashing randomly due to GPIO_CONTROLLER_DRIVER_ERROR. Upon examining the crash dump running WinDBG, the msgpioclx module appears to be at fault. I read a few MDSN entries on what gpio is, but I do not find relevant info on the crash. I guess the main thing I want to know is whether I am dealing with a software/firmware issue or hardware, and if I can fix it on my end or not.

Below is the output of WinDBG:

Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\vizio\OneDrive\Desktop\MEMORY.DMP] Kernel Bitmap Dump File: Full address space is available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff805`06c00000 PsLoadedModuleList = 0xfffff805`0782a310 Debug session time: Wed Sep 23 12:21:21.722 2020 (UTC - 7:00) System Uptime: 0 days 0:07:13.480 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......................... Loading User Symbols Loading unloaded module list ................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff805`06ff3ea0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8503`a080f850=0000000000000138 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* GPIO_CONTROLLER_DRIVER_ERROR (138) This bugcheck happens when the GPIO class extension driver encounters a fatal error. Arguments: Arg1: 0000000000000005, On-Soc GPIO interrupt operation failed. Arg2: ffffffffc000000d, NTSTATUS. Arg3: ffffab0ec09dc310, GPIO device extension. Arg4: ffff8503a080f8a0, GPIO interrupt parameters. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2764 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-PJKFRTG Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 3024 Key : Analysis.Memory.CommitPeak.Mb Value: 80 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 BUGCHECK_CODE: 138 BUGCHECK_P1: 5 BUGCHECK_P2: ffffffffc000000d BUGCHECK_P3: ffffab0ec09dc310 BUGCHECK_P4: ffff8503a080f8a0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System STACK_TEXT: ffff8503`a080f848 fffff805`1e7eac2f : 00000000`00000138 00000000`00000005 ffffffff`c000000d ffffab0e`c09dc310 : nt!KeBugCheckEx ffff8503`a080f850 fffff805`1e7ea1aa : 00000000`00000000 ffffab0e`c30aa001 ffffab0e`c09dc310 00000000`00000000 : msgpioclx!GpiopDeferredUnmaskRequestHandler+0x3b3 ffff8503`a080f920 fffff805`1e7ee984 : 00000000`00000002 00000000`00000004 00000000`00000401 00000000`00000000 : msgpioclx!GpiopUnmaskInterrupt+0x3a2 ffff8503`a080f9c0 fffff805`070cb494 : ffffab0e`c095b000 00000000`00000002 ffffe301`e0480180 fffff805`07845300 : msgpioclx!GpioHubUnmaskInterrupt+0x44 ffff8503`a080f9f0 fffff805`07093230 : 00000000`00000401 00000000`00000002 ffffffff`ffffffff 00000000`00000000 : nt!HalpHandleMaskUnmaskSecondaryInterrupt+0xa8 ffff8503`a080fa20 fffff805`07107733 : ffffab0e`c3a15080 ffff8503`a080fac0 00000000`00000000 00000000`00000118 : nt!HalpUnmaskInterrupt+0x10ac20 ffff8503`a080fa60 fffff805`070af9a9 : ffffe301`e0480180 fffff805`07845360 fffff805`06fc9b80 ffffab0e`c3a150c8 : nt!IopPassiveInterruptWorker+0x1b3 ffff8503`a080fae0 fffff805`06e66dd5 : ffffab0e`bba94040 fffff805`06fc9b80 fffff805`07845360 000fa4ef`bd9bbfff : nt!IopPassiveInterruptRealtimeWorker+0xe5e29 ffff8503`a080fb10 fffff805`06ffb4f8 : ffffe301`e0480180 ffffab0e`bba94040 fffff805`06e66d80 00000000`00000000 : nt!PspSystemThreadStartup+0x55 ffff8503`a080fb60 00000000`00000000 : ffff8503`a0810000 ffff8503`a0809000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 SYMBOL_NAME: msgpioclx!GpiopDeferredUnmaskRequestHandler+3b3 MODULE_NAME: msgpioclx IMAGE_NAME: msgpioclx.sys STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 3b3 FAILURE_BUCKET_ID: 0x138_msgpioclx!GpiopDeferredUnmaskRequestHandler OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {8e573638-d253-79c5-5f7a-87b961f6d314} Followup: MachineOwner --------- 0: kd> lmvm msgpioclx Browse full module list start end module name fffff805`1e7e0000 fffff805`1e812000 msgpioclx # (pdb symbols) C:\ProgramData\Dbg\sym\msgpioclx.pdb\8941CD7972904D5FEC1A1616BD757F221\msgpioclx.pdb Loaded symbol image file: msgpioclx.sys Mapped memory image file: C:\ProgramData\Dbg\sym\msgpioclx.sys\491CB74932000\msgpioclx.sys Image path: \SystemRoot\System32\Drivers\msgpioclx.sys Image name: msgpioclx.sys Browse all global symbols functions data Image was built with /Brepro flag. Timestamp: 491CB749 (This is a reproducible build file hash, not a timestamp) CheckSum: 0002DE50 ImageSize: 00032000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Information from resource tables: 0: kd> !gpiokd.clientlist Dumping Hub List at 0xfffff8051e7fc5c0: GPIO Extension: 0xffffab0ec09dc310 [ \_SB.PCI0.GPI0 ] [ \Device\GPIO_1 ] 0: kd> !gpiokd.bankinfo GPIOKD: Bank address could not be found! 0: kd> !gpiokd.gpioext ACPI: Extension Address could not be found 0: kd> !gpiokd.pintable GPIOKD: Pin table address could not be found!
submitted by /u/momofuku18
[link] [comments]

:)

 

BSOD- atikmpag.sys

This is most likely due to an installation/upgrade error with ATI driver's. I suggest doing DriveSweeper and the following:

• Drivesweeper all drivers & in Safe Mode
• Unistall all drivers that aren't used in DriveSweeper (CCC Profiler Updates, MSI AfterBurner, anything related to ATI that use's it's drivers.)
• After you do this, the first thing you need to do is go into Device Manager and Unistall your ATI Drivers

Once your done, restart the PC and then try installing the latest drivers.


I had several issues with this in the past, but I overcame it with logical reasoning and whenever I have a driver issue, I just use these steps and I always overcome the problem.

Best of luck! *Toast :toast:

 

BSOD due to DPC_Watchdog_Violation

I have done some of the steps suggested and it seems the BSOD goes away in general but it's still consistently triggered by one activity, downloading via qBitorrrent. It happens consistently, with the same error code, DPC watchdog violation

Here's my new MiniDump file: 012618-31203-01.rar

Are there any more clues as to why this specific application consistently trigger the BSOD? I've tried other similar application like uTorrent but it still triggers BSOD regardless of which application I use.

Thank you again for your help.

 

BSOD due to DPC_Watchdog_Violation

I have done some of the steps suggested and it seems the BSOD goes away in general but it's still consistently triggered by one activity, downloading via qBitorrrent. It happens consistently, with the same error code, DPC watchdog violation

Here's my new MiniDump file: 012618-31203-01.rar

Are there any more clues as to why this specific application consistently trigger the BSOD? I've tried other similar application like uTorrent but it still triggers BSOD regardless of which application I use.

Thank you again for your help.