RTX 5070 12GB - USB-C port stopped working

System: Framework 16 with AMD Ryzen AI 9 HX 370 & NVIDIA GeForce RTX 5070 12 GB

OS: Windows 11 Pro 25H2 Build 26200.8737

So, I upgraded to the 12GB version of the RTX 5070 earlier this week, and it had been working pretty good (aside from driver issues noted here).

However, after a reboot, I found that the USB-C port on the back of the 5070 stopped working.

I tried different monitors and cables, but none of them worked. So, I think that rules out it being an issue with the external display/cable.

I then plugged my monitor into a USB-C expansion card on the side, and that worked fine.

Device Manager doesn’t show any issues with the 5070. Or any driver, for that matter.

Not sure what’s causing this to stop working. Could I have accidentally pressed a key macro that disables the display? Is there a setting I need to check for that I’m overlooking?

Any help would be appreciated.

[EDIT] Okay, it started working again. I don’t think I did anything, so I’m not sure what caused it to stop working, and what caused it to start working again.

Congrats on the video card upgrade. Contact support so they have a datapoint on what is going on. This might be a new bug that needs to be flushed out or could be something with the new card. Let us know how it turns out!

I’m also currently having similar issues.

Type-C DP was working fine earlier today, went to reboot into Windows 11, and it stopped working, showing the exact same signs of “life” that you also had. It’s also still not working after booting back to Fedora 44. I hope that it also magically fixes itself?
This is super annoying for me since I recently moved to my FW16 as my main computer (from an Intel Extreme Edition Nuc), so it’s really annoying that the Type-C DP port just stopped working out of nowhere.

For ctx; I’ve got the 8GB version of the 5070 module, and I’m on a Ryzen 7040 series mainboard instead of the AI 300 series.

So… looks like they’re going to be sending me a replacement for this.

Just to give a recap of everything I did to get to this point:

1 - Confirmed with them that I’ve installed the latest BIOS and Framework drivers
2 - Confirmed there were no pending Windows Updates
3 - Reinstalled the drivers (multiple times)
4 - Scanned for hardware changes in Device Manager
5 - Provided photos of the GPU box (to show it wasn’t damaged in transit), my laptop, the GPU connectors and interposer
6 - Ran DDU to completely clear all Nvidia drivers and reinstall the Framework drivers
7 - Recorded a video to show that the external monitor wasn’t working when connected to the USB-C on the back, but did work through a side port
8 - Confirmed that this issue was only occurring with the 12GB 5070, not the 8GB 5070
9 - Removed the Graphics Module and took various photos of it by itself
10 - Performed a mainboard reset

So… I guess maybe something’s defective with the 12GB 5070 I received? No idea. I guess we’ll see if there are any issues with the replacement when I get it.

Received the replacement 12GB 5070 today, nothing is different. Rear USB-C port sometimes works, sometimes doesn’t. Still can’t update to the latest Nvidia drivers through the Nvidia App.

After going through several power cycles to test, I think I can narrow down what seems to cause the USB-C port to work or not…

Seems that it stops working after I fully shut down the laptop and then power it back on. Sleep or reboot is fine, though. But after the port stops working, it still wouldn’t work again after multiple shut downs, reboots, and sleeps.

However, after shutting down and then powering back on AFTER unplugging the laptop from the power supply, THEN the rear USB-C port started working again.

I have a feeling that the first 12GB 5070 wasn’t defective, unless somehow the replacement is ALSO defective… going to add this to my open ticket with Framework.

Next update…

After further testing with with Framework support (creating a new Windows user to use DDU to clean the drivers then reinstall the latest BIOS and drivers package, testing the dGPU USB-C port to see if it would recognize a flash drive, setting the MUX to Nvidia Only, more photos of the inside of my laptop)… they now decided to replace my mainboard.

So, next update when the new mainboard arrives.

Received the replacement Ryzen AI 8 HX 370 board on August 3. Replaced it, both issues still persist.

They then wanted me to reinstall Windows, which I refused as I had no reason to believe that’d fix my problems. Plus, then I’d have to waste several hours to reinstall and reconfigure everything. I suggested they think of another solution.

Made sure there were no pending Windows updates, ran sfc and chkdsk to fix any errors they could, and both issues still persisted.

Tried to run the standalone Nvidia driver installer (instead of trying to update through the Nvidia App), it fails at the first step (could not find compatible graphics hardware).

Provided them with the log files from Event Viewer, doesn’t seem like they really found anything related to the GPU issues.

They once again requested I reinstall Windows. Again, not happening. However, I then got the idea to use another SSD to install a fresh copy of Windows onto another drive. And… the issues were not fixed. Even on this completely clean install of Windows 11, the Nvidia installer doesn’t recognize the GPU. So, I’m glad I trusted my instincts and didn’t mess up my main install of Windows.,

I’ve replaced the GPU. I’ve replaced the mainboard. I’ve even replaced Windows. The issues with the USB-C port and the drivers remain.

Now they want me to ship my laptop to their repair center to diagnose it directly and repair anything that might be broken. I’ve informed them this is absolutely out of the question. Nearly all major components have been replaced at this point, and there’s been no change. And then they want me to be without my laptop for weeks for them to maybe fix something that they couldn’t just tell me to do? The whole reason I went with Framework in the first place was because it was user-repairable/upgradable, since having to ship laptops for repairs in the past has been a massive hassle. I never want to do that again.

Surely, I can’t be the only one experiencing these issues with the 12GB 5070???

Just guessing at what to try next:

Reset the BIOS
Try going into the BIOS and put the machine in standalone mode (battery disconnect) then physically disconnect the battery and leave it unplugged for a good 15 minutes. Press the power button to make sure zero residual power is left.

This should effectively stop and hopefully reset the EC.

Plug the battery back in and this time boot to that “fresh” copy of Windows 11. Maybe ask support which version of Ubuntu or Fedora they tested the 5070 12gb the most and make a USB of it to try and see if it is OS related.

My suspicion is it is something with the BIOS and possibly related to the EC.

This is presuming there is not a hardware connection issue like with the interposer.

Thanks for the suggestion, but unfortunately no dice. Both issues still persist.

I wouldn’t think that the interposer would be a problem, since I’ve replaced it each time I’ve replaced the GPU. So, it should be as new as replacement 5070.

Have you tried testing with a different monitor and USB-C cable? Ignore the rest of this message if so - I’m just typing up my rough justifications for asking.

Obviously you’ve proven that the side ports can pass video to an external monitor using at least one cable (maybe you’ve already tried ruling this out), but not all USB-C cables are built to the same specs and the video output from the dGPU may be of a different quality than the USB-C display port video provided by the side port modules. That possibility could extend to the type of external monitor, too - it could be that one specific external monitor struggles with one video source and not another.

Yep, tried different cables and monitors, same problem. When the rear USB-C port stops working, nothing plugged into it will work. Multiple monitors, flash drives, etc.

My entire RX7700S module is dead and is currently in the process of being replaced, but while going through testing I noticed it did try to do a DP Alt handshake with my display but couldn’t finish it (obviously because the GPU is dead).

So, if:

  1. The GPU still works
  2. The interposer still works
    – Get framework_tool from GitHub - FrameworkComputer/framework-system: Rust libraries and tools to interact with the Framework Computer systems · GitHub
    – Query the connection with the expansion bay with
    framework_tool --expansion-bay
    – If you don’t see errors the Expansion Bay is fine, interposer-wise.
  3. The USB-C port is suddenly no longer visible on the system bus
    – On Linux this should be fairly easy to diagnose with
    lspci -tv
  4. It tries to do a handshake but could not complete it, or nothing happens at all

Then your USB-C port is very likely dead or at least malfunctioning.

Best is to send Support at least the following, using Linux:

  1. A short video of you hooking up your display to the USB-C port, and clearly show that the display doesn’t initialize. Best to do it with a good brand new cable fresh out of the package so they can’t blame a malfunctioning cable. (make sure that’s also clear in the video too, by the way)
  2. The output of framework_tool --expansion-bay which shows them the EEPROM readout from the expansion bay from one of their own diagnostics tools. (no error = no connection issue with the mainboard)
  3. The output of lspci -tv when it clearly shows there is no longer a active USB-C port on the back of the expansion bay according to the system bus. (this should be the case if its really malfunctioning, by the way)
  4. Check any kernel responses in Linux when connecting/disconnecting the display with dmesg -w. Take a note of what you see or don’t see, then attach /var/log/dmesg to that mail and write down your remarks aswell. – They want to see how your kernel responds interacting with the suspected malfunctioning hardware, if any.
  5. Alternatively also check if the EC reports any USB related errors in general and/or while disconnecting/connecting with
    framework_tool --console follow
    and if it does send them that info aswell

If you don’t have a multiboot system, create a persistent bootable Linux USB stick with Nvidia drivers on a secondary USB stick from a Live USB installer (Fedora or Ubuntu as these are also officially supported by Framework) and perform these steps from there, as modern Windows is a terrible environment to do deep hardware diagnostics IMHO.

Good luck!

I’ll keep this in mind for later, as I’ll need to first setup a Linux Live USB (I guess I’ll go with Ubuntu for this purpose).

Just to note that Framework has replaced both my mainboard and 12GB 5070. So unless both the old and new ones were faulty in the same way (which is entirely possible), these issues are likely part of something not unique to a faulty unit.

With that said, I just got another update from Framework, and it seems that the issues (at least, in regards to the rear USB-C sometimes working or not) may be related to PD issues that have been troubling all AMD boards. And they linked me to this GitHub issue: PD Related Issue on AMD platform · Issue #225 · FrameworkComputer/SoftwareFirmwareIssueTracker · GitHub

Still not sure what’s up with the driver issues, though.

Alright, heard back from Framework support, and they’re able to duplicate the issue with not being able to update to the latest Nvidia drivers.

They’ve requested I create a GitHub issue to track this: FW16 - Cannot update drivers for 12GB GeForce RTX 5070 · Issue #253 · FrameworkComputer/SoftwareFirmwareIssueTracker · GitHub

So… I guess nothing else to do about this for now.

Nvidia just released driver version 616.56 today, and this DOES properly recognize the 12GB 5070.

While the Nvidia App didn’t show any updates were available, the standalone installer still worked fine.

Strange, because the release notes for the previous version showed that the 12 GB 5070 was supported. Oh well, at least that’s resolved now.

Now, just looks like we need a BIOS update to fix the PD issue for the USB-C port.

Popping in to say I’m experiencing the exact same issue with my 5070 12gb module. Appreciate your keeping this updated, @BPM. Installed, connected to my LG OLED via USBC to HDMI adapter no problem, shut down when I was done. No connectivity today after turning the laptop back on. Confirmed not a cable chain issue as everything still works via side USBC. Just reinstalled the Framework driver package, no change. Guess I’ll wait for a new BIOS as well.

Edit: Went into the BIOS, changed virtually nothing, booted into Windows, now it works. :man_shrugging:t3:

Please please PLEASE tell me what settings you changed! I am having the exact same issue on my RTX 5070 8GB module and I am going through the same troubleshooting steps

For anyone who stumbles onto this thread in the future, I was able to fix it by downgrading my BIOS to 3.06