| Previous | Next |
| KERNEL_WMI_INTERNAL | FATAL_ABNORMAL_RESET_ERROR |
SOC_SUBSYSTEM_FAILURE
The SOC_SUBSYSTEM_FAILURE bug check has a value of 0x0000014B. This indicates that an unrecoverable error was encountered in a System on a Chip (SoC) subsystem.
Important
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
Bug Check 0x14B SOC_SUBSYSTEM_FAILURE Parameters
| Parameter | Description |
|---|---|
1 |
Address of an SOC_SUBSYSTEM_FAILURE_DETAILS structure. |
2 |
Reserved. |
3 |
Reserved. |
4 |
Optional. Address of a vendor-supplied data block. |
Resolution
The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause.
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SOC_SUBSYSTEM_FAILURE (14b)
A SOC subsystem has experienced an unrecoverable critical fault.
Arguments:
Arg1: 9aa8d630, nt!SOC_SUBSYSTEM_FAILURE_DETAILS
Arg2: 00000000, Reserved
Arg3: 00000000, Reserved
Arg4: a126c000, (Optional) address to vendor supplied general purpose data block.
Use the provided nt!SOC_SUBSYSTEM_FAILURE_DETAILS structure to dump the failure data using the dt command and the address provided by Arg1.
2: kd> dt nt!SOC_SUBSYSTEM_FAILURE_DETAILS 9aa8d630
+0x000 SubsysType : 1 ( SOC_SUBSYS_AUDIO_DSP )
+0x008 FirmwareVersion : 0
+0x010 HardwareVersion : 0
+0x018 UnifiedFailureRegionSize : 0x24
+0x01c UnifiedFailureRegion : [1] "F"
Work with SoC vendor to further parse the data, including the optional vendor supplied general purpose data block.
You may want to examine the stack trace using the k, kb, kc, kd, kp, kP, kv (Display Stack Backtrace) command. You can specify the processor number to examine the stacks on all processors.
You can also set a breakpoint in the code leading up to this stop code and attempt to single step forward into the faulting code.
For more information see the following topics:
Crash dump analysis using the Windows debuggers (WinDbg)
If you are not equipped to use the Windows debugger to work on this problem, you can use some basic troubleshooting techniques.
Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing this bug check.
If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
You can try running the hardware diagnostics supplied by the system manufacturer.
For additional general troubleshooting information, see Blue Screen Data.
Requirements
Minimum supported client |
Windows 8 |
Minimum supported server |
Windows Server 2012 |