Apparent Bugcheck caused by Transcoder

Plex Media Server
1

Server Version#: 1.32.0.6973
Player Version#: N/A
Win 10 x64 Version 22H2 Build 109045.2913

Today was the second time in 2 days that a bugcheck associated with Plex Transcoder has occurred.

I have the Debug Log but do not see anyway to attach it.

Here is the winDbg output for the bugcheck:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffc008d9fbe028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000100153, Low order 32-bits of the MCi_STATUS value.

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 4811

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 4854

Key  : Analysis.IO.Other.Mb
Value: 6

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 20

Key  : Analysis.Init.CPU.mSec
Value: 2124

Key  : Analysis.Init.Elapsed.mSec
Value: 24141

Key  : Analysis.Memory.CommitPeak.Mb
Value: 92

Key  : Bugcheck.Code.DumpHeader
Value: 0x124

Key  : Bugcheck.Code.KiBugCheckData
Value: 0x124

Key  : Bugcheck.Code.Register
Value: 0x124

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

FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc008d9fbe028

BUGCHECK_P3: b6000000

BUGCHECK_P4: 100153

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: Plex Transcoder.exe

STACK_TEXT:
ffffa8802c686938 fffff8020fab785a : 0000000000000124 0000000000000000 ffffc008d9fbe028 00000000b6000000 : nt!KeBugCheckEx
ffffa8802c686940 fffff8020da815b0 : 0000000000000000 ffffc008d9fbe028 ffffc008d73f73a0 ffffc008d9fbe028 : nt!HalBugCheckSystem+0xca
ffffa8802c686980 fffff8020fbb9b3e : 0000000000000000 ffffa8802c686a29 ffffc008d9fbe028 ffffc008d73f73a0 : PSHED!PshedBugCheckSystem+0x10
ffffa8802c6869b0 fffff8020fab9181 : ffffc008d9f90070 ffffc008d9f90070 ffffc008d73f73f0 ffffc008d73f73a0 : nt!WheaReportHwError+0x46e
ffffa8802c686a90 fffff8020fab94f3 : 0000000000000003 ffffc008d73f73f0 ffffc008d73f73a0 0000000000000003 : nt!HalpMcaReportError+0xb1
ffffa8802c686c00 fffff8020fab93d0 : ffffc008d72b3e78 0000000000000001 ffffa8802c686e00 0000000000000000 : nt!HalpMceHandlerCore+0xef
ffffa8802c686c50 fffff8020fab8915 : ffffc008d72b3e78 ffffa8802c686ef0 0000000000000000 0000000000000000 : nt!HalpMceHandler+0xe0
ffffa8802c686c90 fffff8020fabb0d5 : ffffc008d72b3e78 0000000000000000 0000000000000000 0000000000000000 : nt!HalpHandleMachineCheck+0xe9
ffffa8802c686cc0 fffff8020fb10bf9 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!HalHandleMcheck+0x35
ffffa8802c686cf0 fffff8020fa0c8ba : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0x9
ffffa8802c686d20 fffff8020fa0c577 : 0000000000000000 0000000000000000 00000132db315a98 0000000000000000 : nt!KxMcheckAbort+0x7a
ffffa8802c686e60 00007ff84ce5cbe3 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277
0000001b048ff620 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff8`4ce5cbe3

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_PROCESSOR_CACHE_IMAGE_AuthenticAMD.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d6c4d869-cd29-1e48-0267-5766712959d2}

2

Hi there. I asked our expert to take a look and they say this is a kernel bug mostly in your AMD driver. Have you updated the driver recently? Do you get the same error in earlier PMS builds?

3

The current AMD graphics driver is version 31.0.14051.1000 and was installed on 4/23/2023.

Now that I have reason to examine the system log I see that bugcheck 0x0101 has been occurring since 4/25/2023. Another bugcheck, 0x0124, has also occurred multiple times between 2/23/2023 and 4/22/2023 but the MEMORY.DMP file is overwritten each time so there are only the details provided in Event Viewer available, such as:

(EventID Qualifiers=16384 )1001(/EventID)

(Version)0(/Version)

(Level)2(/Level)

(Task)0(/Task)

(Opcode)0(/Opcode)

(Keywords)0x80000000000000(/Keywords)

(TimeCreated SystemTime=2023-04-22T13:51:56.2848407Z /)

(EventRecordID)7738(/EventRecordID)

(Correlation /)

(Execution ProcessID=0 ThreadID=0 /)

(Channel)System(/Channel)

(Computer)Media-Server(/Computer)

(Security /)

(/System)

(EventData)

(Data Name="param1 ")0x00000124 (0x0000000000000000, 0xffffb205283ad028, 0x00000000b6000000, 0x0000000000100153)(/Data)

(Data Name="*Param2 ")C:\Windows\MEMORY.DMP(/Data)

(Data Name="param3 ")9c4e2588-c1b4-4773-8a14-7db08fa5470d(/Data)

(/EventData)

(/Event)

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.