Razer Core X (Intel JHL6340 / Alpine Ridge), RTX 4070 Ti
Windows 11
Previous mainboard: Ryzen AI 9 HX 370
The same enclosure, GPU and cable ran fine on the HX 370 board on my old framework 13. That’s the only thing I changed.
Error detail
Bugcheck 0x124, arg1 0x4 = PCIe error source. !errrec gives a fatal Data Link Protocol Error at 2d:01.0, the downstream switch port inside the enclosure. Event Viewer floods with WHEA-Logger ID 17 corrected errors from the same device.
Tried, no change
New Thunderbolt cable
ASPM off
VT-d disabled
GPU reseated, contacts clean, nothing obstructing inside the enclosure
Under Linux
Same errors, at idle, with no Nvidia driver loaded. The two bridge ports differ:
2c:00.0 (upstream, across the cable): CESta clean, LaneErrStat: 0
2d:01.0 (downstream, to the GPU): BadDLLP+, LaneErr at lane: 0 1 2 3
The catch
The HX 370 board also has these error bits set (checked with my old framework 13). It just doesn’t crash, and doesn’t log them. The main difference is that the Series 3 board turns it fatal within a minute but the hx370 runs games with the egpu under load indefinitely.
Has anyone got a TB3 eGPU working on a Series 3 board? Happy to share the minidump or full lspci -vv.
Just a quick clarification, in case readers think it is important. You mention you’re running BIOS 3.2, but the docs suggest the latest release is 3.0.2. Is that just a typo?
On another note, I notice that the above-linked page has a Windows Driver Bundle - is that worth installing?
Coolio. Other things to try - does the machine port you use make a difference? Also, could you try a USB-booted Linux distro? This might help point to, or rule out, a driver problem.
I have the same issue. I upgraded from a framework 12th gen to the framework 13 pro Ultra X7 358H. I have the razer core x with a 3070 and windows 11. Under no load it is fine. but anything heavy like loading a game or a gpu burn test it crashes anywhere from immediately up to 5 minutes. Giving me the same 0x124 bug check. The only thing I done different in troubleshooting is I removed every driver I could and reinstalled the framework driver pack but it didn’t help.
more dump
15: kd> !errrec ffff9d0fec420028
===============================================================================
Common Platform Error Record @ ffff9d0fec420028
-------------------------------------------------------------------------------
Record Id : 01dd4cbe294e7c25
Severity : Fatal (1)
Length : 1232
Creator : Microsoft
Notify Type : PCI Express Error
Timestamp : 9/25/2026 7:22:19 (UTC)
Flags : 0x00000000
===============================================================================
Section 0 : PCI Express
-------------------------------------------------------------------------------
Descriptor @ ffff9d0fec4200a8
Section @ ffff9d0fec4201c8
Offset : 416
Length : 208
Flags : 0x00000001 Primary
Severity : Fatal
Port Type : Downstream Switch Port
Version : 1.1
Command/Status: 0x0407/0x0010
Device Id :
VenId:DevId : 8086:15da
Class code : 030400
Function No : 0x00
Device No : 0x01
Segment : 0x0000
Primary Bus : 0x2d
Second. Bus : 0x00
Slot : 0x0000
Dev. Serial # : 0abbc029a5c9a000
Express Capability Information @ ffff9d0fec4201fc
Device Caps : 00008020 Role-Based Error Reporting: 1
Device Ctl : 2117 ur FE NF CE
Dev Status : 0015 ur FE nf CE
Root Ctl : 0000 fs nfs cs
AER Information @ ffff9d0fec420238
Uncorrectable Error Status : 00000010 ur ecrc mtlp rof uc ca cto fcp ptlp sd DLP und
Uncorrectable Error Mask : 00000000 ur ecrc mtlp rof uc ca cto fcp ptlp sd dlp und
Uncorrectable Error Severity : 00062010 ur ecrc MTLP ROF uc ca cto FCP ptlp sd DLP und
Correctable Error Status : 00000080 adv rtto rnro DLLP tlp re
Correctable Error Mask : 00008000 adv rtto rnro dllp tlp re
Caps & Control : 00000004 ecrcchken ecrcchkcap ecrcgenen ecrcgencap FEP
Header Log : 60701001 2e00000f 00000001 f6cdf800
Root Error Command : 00000007 FEN NFEN CEN
Root Error Status : 00000054 MSG# 00 FER nfer FUF mur UR mcr cer
Correctable Error Source ID : 2d,01,00
Correctable Error Source ID : 2d,01,00
===============================================================================
Section 1 : PCI Express
-------------------------------------------------------------------------------
Descriptor @ ffff9d0fec4200f0
Section @ ffff9d0fec420298
Offset : 624
Length : 208
Flags : 0x00000000
Severity : Fatal
Port Type : Legacy Endpoint
Version : 1.1
Command/Status: 0x0006/0x0010
Device Id :
VenId:DevId : 10de:2488
Class code : 018000
Function No : 0x00
Device No : 0x00
Segment : 0x0000
Primary Bus : 0x2e
Second. Bus : 0x00
Slot : 0x0000
Dev. Serial # : 0000000000000000
Express Capability Information @ ffff9d0fec4202cc
Device Caps : 10008de1 Role-Based Error Reporting: 1
Device Ctl : 2917 ur FE NF CE
Dev Status : 0009 UR fe nf CE
Root Ctl : 0000 fs nfs cs
AER Information @ ffff9d0fec420308
Uncorrectable Error Status : 00100000 UR ecrc mtlp rof uc ca cto fcp ptlp sd dlp und
Uncorrectable Error Mask : 00000000 ur ecrc mtlp rof uc ca cto fcp ptlp sd dlp und
Uncorrectable Error Severity : 00462030 ur ecrc MTLP ROF uc ca cto FCP ptlp SD DLP und
Correctable Error Status : 0000a000 ADV rtto rnro dllp tlp re
Correctable Error Mask : 00008000 adv rtto rnro dllp tlp re
Caps & Control : 00000014 ecrcchken ecrcchkcap ecrcgenen ecrcgencap FEP
Header Log : 04000001 0000000f 2e020000 f7f7f7f7
Root Error Command : 00000007 FEN NFEN CEN
Root Error Status : 00000054 MSG# 00 FER nfer FUF mur UR mcr cer
Correctable Error Source ID : 2d,01,00
Correctable Error Source ID : 2d,01,00
===============================================================================
Section 2 : PCI Express
-------------------------------------------------------------------------------
Descriptor @ ffff9d0fec420138
Section @ ffff9d0fec420368
Offset : 832
Length : 208
Flags : 0x00000000
Severity : Fatal
Port Type : Endpoint
Version : 1.1
Command/Status: 0x0400/0x0010
Device Id :
VenId:DevId : 10de:228b
Class code : 020300
Function No : 0x01
Device No : 0x00
Segment : 0x0000
Primary Bus : 0x2e
Second. Bus : 0x00
Slot : 0x0000
Dev. Serial # : 0000000000000000
Express Capability Information @ ffff9d0fec42039c
Device Caps : 00008de1 Role-Based Error Reporting: 1
Device Ctl : 2117 ur FE NF CE
Dev Status : 0009 UR fe nf CE
Root Ctl : 0000 fs nfs cs
AER Information @ ffff9d0fec4203d8
Uncorrectable Error Status : 00100000 UR ecrc mtlp rof uc ca cto fcp ptlp sd dlp und
Uncorrectable Error Mask : 00000000 ur ecrc mtlp rof uc ca cto fcp ptlp sd dlp und
Uncorrectable Error Severity : 00462030 ur ecrc MTLP ROF uc ca cto FCP ptlp SD DLP und
Correctable Error Status : 0000a000 ADV rtto rnro dllp tlp re
Correctable Error Mask : 00008000 adv rtto rnro dllp tlp re
Caps & Control : 00000014 ecrcchken ecrcchkcap ecrcgenen ecrcgencap FEP
Header Log : 04000001 00000003 2e020000 f7f7f7f7
Root Error Command : 00000007 FEN NFEN CEN
Root Error Status : 00000054 MSG# 00 FER nfer FUF mur UR mcr cer
Correctable Error Source ID : 2d,01,00
Correctable Error Source ID : 2d,01,00
===============================================================================
Section 3 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffff9d0fec420180
Section @ ffff9d0fec420438
Offset : 1040
Length : 192
Flags : 0x00000000
Severity : Informational
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
No valid data fields are present.
Similar issue. I had a FW13 7840U with 4060Ti in an TH3P4G3 eGPU enclosure and this worked mostly stable. Now with X7 358H and it constantly crashes. Tried Win11 and Bazzite. It runs in idle for a while, but under the lightest load it crashes.
Already tried different cables without luck. I ordered a Minisforum DEG2 to do more testing, but I don’t have very high hopes that this will fix it.
Let us know how you go with the deg2 was considering upgrading to a tb5 enclosure myself for future proofing (hopefully nova lake gets integrated tb5).
I noticed another strange thing: in my setup I have the monitor connected via USB-C (DP+Power) and additionally, when the eGPU is connected, it has a direct DP connection from eGPU to monitor.
Now when I enter the BIOS during startup (F2), and the direct DP connection is active, the laptop even crashes in BIOS, simply by browsing the menu. UI/graphics glitch and laptop becomes unresponsive.