From absolute hell to running weeks straight with zero green frames, zero Code 43, zero black screens – December 2025
After months of investing essentially all my free time to working the bugs out and getting proper passthrough working to the point I am mostly satisfied for the application. Along the way I was giving a great deal of help from Uzumo. As he commented and built upon here: https://github.com/isc30/ryzen-gpu-passthrough-proxmox/blob/main/README.md, concepts that go on to be expanded into the hookscript method as outlined in Uzumo's dialog here https://github.com/isc30/ryzen-gpu-passthrough-proxmox/issues/131#issue-3266798285.
Now I have been scolded for seeking help regarding roms here on Proxmox but Uzumo was happy to provide the link https://github.com/isc30/ryzen-gpu-passthrough-proxmox. That gave me a great starting point. My novice eyes overlooked the https://github.com/isc30/ryzen-gpu-passthrough-proxmox/tree/main/Tools section. Here you can find what we need to get iGPU roms extracted. I did however end up reaching out to Minisforum and they passed along the shall we call it official vbios. The GopDriver and vbios is critical for this method. Getting the right one is tricky and not designed for the end user obviously. I would like to see companies which boast support for Proxmox get this process along to the consumer in a less convoluted fashion as clearly this is what we are trying to accomplish. Though I digress, I love my finished product.
Presently I am really only using a few vm's:
It's been a couple months since I started out https://forum.proxmox.com/threads/p...passthrough-a-desperate-plea-for-help.172139/. Since then I have made quite a few changes on the original each one coming with a story I wont bore you with unless you ask.
Instead I was hoping to collect a few other folks who have the same configuration as me that could help me inhance. Heck even just reconsider aspects of it I really don't care but initally I just wanted to help others who have been reaching out inquiring what I am working with.
Granted this is a significantly different setup on the MS-A2 lowered power delidded processor which minisforum wants locked to 45watts if you read the guides on the support section for our product. It becomes evidently clear people with this setup have issues with heat. I did find ways to modify and mitgate with bios settings, custimzed fan stages with aggressive speeds after 65. Also I cleared the original phasechange compound and upgraded to the best rated phase change pad I could find. If you are interested I will find the details. I have an after market fan directed to it at low speed in the "homelab server room". I am now able to have default or higher power settings in the bios and not ever see temperatures exceed 60. Which you need to install Cockpit for Proxmox to give you a Debian alternative frontend to help in various ways and for us its all about the temperature.
I don't want to get to far off topic here as I do want to provide a guide for this hardware but you have to check out https://github.com/filebrowser/filebrowser! This makes the editiing of our server files much easier than any other way I can image. I even allows you to make bookmarks as URL directly to a file. Which in turn brings up an editor! This is a priceless edition to debugging a wildly artifacting system that needs to be restarted hundreds and hunreds of times testing different settings. I also found a cgit project which literally runs automated backups every so many minutes on the tree structure for changes and you as the administrator can review and map out chronologically over time on a sort of giant map. Look I know how pathetic it is telling this to a community like this. But I intend my reader of this post to be almost as novice as me. Hence this is priceless knowledge as having quick access to the files is necessary.
Anyways enough about those seemingly abstract topics here is what I am using at the moment and Yes it is now zero artifacts for weeks. The real problem comes in when you 1) want to tweak to utilize power settings, as this setup essentially turns them off but if you essentially piss around enough you in theory could get them working too. Hence why I am making this thread to see if other wanted to dialouge about these igpu's and passthrough techniques. Not as though that hasn't been done before.. Its just that I have yet to see it done "right" per say, Myself included.
But heres the kicker I have got this setup to work flawlessly with stresstests of display @ 4k60p ; 4 x 4 ; downscaled in a grid 8k Japan video at 60p. For our system this is a great litmus test. If it is not setup correctly with the settings which essentially worked for others in the Ryzan lineup because in our case we need more tweaking for the buggs to be gone. I have a lot of bandwidth so this was fine for me. Essentially this would NOT work with the original setup with the hookscript and all. But now I can leave the system running for days on weeks. No flaws no jarred blackscreens, display driver crashes, green screens and on and on. All of which corrupt the working environment.
If you are admittedly a novice with OS's and you cant tell the nuance's here the signs are nerve racking and alarming to the point most would quit. However if you consider the way the frame buffer is a total mess when we have problems its wise to have a bootable wintousb. I found an incredible one so that we can boot our server test the hardware and get peace of mind back in order if your server is a mess with graphic artifacts or you need direct access for firmware updates like nvme drives for example. I cant STRESS ENOUGH the importance of never assuming that early artifacts will stay forever. (many times it was actually fixed with the configuration I had. But the drivers and system files had taken a serious beating from the previous attempt. Thus noticing the little signs such as if the screen blanks out even once. 2) The issues are all mendable with a safemode boot and driver wiping tools followed by a fresh installaion of the drivers.
Get our Gop Driver I posted here – save yourself the hassle of getting it if you are on 9955HX (others work but this is the type of thing were there is likely a better cleaner extract going around, also the bios version it was pulled from matters). So for us with artifacts and video issues it would be key to have the best foundation. Hence try mine sourced with https://github.com/LongSoft/UEFITool/releases/tag/A72 and posted here https://github.com/qemus/virtiso/releases.
You may notice my vbios has a different label in the following write up but that is because in the last month I heard back from Minisforum with what they said is a better one ?.. It is much larger in size like 128 kb. Whereas the majority of the vios post from the Ryzan like 80 percent had the same size like 43 kb or something .. Now I had 3 128 kb from the manufacturer, 1 I collected from tool which I shared and called it something that didnt fit into the rest nicely FOR THIS EXACT reason. I am not sure if it is correct. Now I am happy with the one I have but this is definitely worth consider.
If you have this exact MS-A2 (Ryzen 9 9955HX + Radeon 610M) and want to team up, share your hookscripts, fight over which 128 KB VBIOS is actually the golden one, get ASPM working reliably, fix the lingering Mediatek BT lingering crap, whatever – reply here.I’m done suffering alone. Let’s make this thing perfect together.
:
There is lingering disabled devices that need to be re-enabled each boot. A pain but not the end of the line. Just something to consider and maybe help me overcome. That and the number power settings I had the disfortune of having to ultimately disable. Although I had it working for days like this it was ultimately just not reliable.
CONTINUED ON THE NEXT POST L
After months of investing essentially all my free time to working the bugs out and getting proper passthrough working to the point I am mostly satisfied for the application. Along the way I was giving a great deal of help from Uzumo. As he commented and built upon here: https://github.com/isc30/ryzen-gpu-passthrough-proxmox/blob/main/README.md, concepts that go on to be expanded into the hookscript method as outlined in Uzumo's dialog here https://github.com/isc30/ryzen-gpu-passthrough-proxmox/issues/131#issue-3266798285.
Now I have been scolded for seeking help regarding roms here on Proxmox but Uzumo was happy to provide the link https://github.com/isc30/ryzen-gpu-passthrough-proxmox. That gave me a great starting point. My novice eyes overlooked the https://github.com/isc30/ryzen-gpu-passthrough-proxmox/tree/main/Tools section. Here you can find what we need to get iGPU roms extracted. I did however end up reaching out to Minisforum and they passed along the shall we call it official vbios. The GopDriver and vbios is critical for this method. Getting the right one is tricky and not designed for the end user obviously. I would like to see companies which boast support for Proxmox get this process along to the consumer in a less convoluted fashion as clearly this is what we are trying to accomplish. Though I digress, I love my finished product.
Presently I am really only using a few vm's:
- PFSense Community Edition which receives passthrough from the two X710 Intel slots and a back plain bridge to the vm's. This vm automatically boots and acts as a great home lab router/ server.
- I have installed a Mellanox ConnectX 4 I got for $50 USD on ebay and another for my PC.
It's been a couple months since I started out https://forum.proxmox.com/threads/p...passthrough-a-desperate-plea-for-help.172139/. Since then I have made quite a few changes on the original each one coming with a story I wont bore you with unless you ask.
Instead I was hoping to collect a few other folks who have the same configuration as me that could help me inhance. Heck even just reconsider aspects of it I really don't care but initally I just wanted to help others who have been reaching out inquiring what I am working with.
Granted this is a significantly different setup on the MS-A2 lowered power delidded processor which minisforum wants locked to 45watts if you read the guides on the support section for our product. It becomes evidently clear people with this setup have issues with heat. I did find ways to modify and mitgate with bios settings, custimzed fan stages with aggressive speeds after 65. Also I cleared the original phasechange compound and upgraded to the best rated phase change pad I could find. If you are interested I will find the details. I have an after market fan directed to it at low speed in the "homelab server room". I am now able to have default or higher power settings in the bios and not ever see temperatures exceed 60. Which you need to install Cockpit for Proxmox to give you a Debian alternative frontend to help in various ways and for us its all about the temperature.
I don't want to get to far off topic here as I do want to provide a guide for this hardware but you have to check out https://github.com/filebrowser/filebrowser! This makes the editiing of our server files much easier than any other way I can image. I even allows you to make bookmarks as URL directly to a file. Which in turn brings up an editor! This is a priceless edition to debugging a wildly artifacting system that needs to be restarted hundreds and hunreds of times testing different settings. I also found a cgit project which literally runs automated backups every so many minutes on the tree structure for changes and you as the administrator can review and map out chronologically over time on a sort of giant map. Look I know how pathetic it is telling this to a community like this. But I intend my reader of this post to be almost as novice as me. Hence this is priceless knowledge as having quick access to the files is necessary.
Anyways enough about those seemingly abstract topics here is what I am using at the moment and Yes it is now zero artifacts for weeks. The real problem comes in when you 1) want to tweak to utilize power settings, as this setup essentially turns them off but if you essentially piss around enough you in theory could get them working too. Hence why I am making this thread to see if other wanted to dialouge about these igpu's and passthrough techniques. Not as though that hasn't been done before.. Its just that I have yet to see it done "right" per say, Myself included.
But heres the kicker I have got this setup to work flawlessly with stresstests of display @ 4k60p ; 4 x 4 ; downscaled in a grid 8k Japan video at 60p. For our system this is a great litmus test. If it is not setup correctly with the settings which essentially worked for others in the Ryzan lineup because in our case we need more tweaking for the buggs to be gone. I have a lot of bandwidth so this was fine for me. Essentially this would NOT work with the original setup with the hookscript and all. But now I can leave the system running for days on weeks. No flaws no jarred blackscreens, display driver crashes, green screens and on and on. All of which corrupt the working environment.
If you are admittedly a novice with OS's and you cant tell the nuance's here the signs are nerve racking and alarming to the point most would quit. However if you consider the way the frame buffer is a total mess when we have problems its wise to have a bootable wintousb. I found an incredible one so that we can boot our server test the hardware and get peace of mind back in order if your server is a mess with graphic artifacts or you need direct access for firmware updates like nvme drives for example. I cant STRESS ENOUGH the importance of never assuming that early artifacts will stay forever. (many times it was actually fixed with the configuration I had. But the drivers and system files had taken a serious beating from the previous attempt. Thus noticing the little signs such as if the screen blanks out even once. 2) The issues are all mendable with a safemode boot and driver wiping tools followed by a fresh installaion of the drivers.
Remaining bugs I haven’t touched because I’m exhausted and it’s Christmas season
- power savings ASPM as I have them all disabled.
- After shutdown, switching to Ubuntu and then back to windows is not as clean as a fresh boot. I can't say there are artifacts anymore! So that is a major plus! I am passing though my aftermarket wifi 7 mediatek bluetooth and wifi. Then the same over in Ubuntu. but as you can see in the screenshot – lingering disabled devices that need to be re-enabled each boot. A pain but not the end of the line. Just something to consider and maybe help me overcome. That and the number power settings I had the disfortune of having to ultimately disable. Although I had it working for days like this it was ultimately just not reliable.
The exact files & VBIOS situation – EVERY detail because people keep asking
Get our Gop Driver I posted here – save yourself the hassle of getting it if you are on 9955HX (others work but this is the type of thing were there is likely a better cleaner extract going around, also the bios version it was pulled from matters). So for us with artifacts and video issues it would be key to have the best foundation. Hence try mine sourced with https://github.com/LongSoft/UEFITool/releases/tag/A72 and posted here https://github.com/qemus/virtiso/releases.
You may notice my vbios has a different label in the following write up but that is because in the last month I heard back from Minisforum with what they said is a better one ?.. It is much larger in size like 128 kb. Whereas the majority of the vios post from the Ryzan like 80 percent had the same size like 43 kb or something .. Now I had 3 128 kb from the manufacturer, 1 I collected from tool which I shared and called it something that didnt fit into the rest nicely FOR THIS EXACT reason. I am not sure if it is correct. Now I am happy with the one I have but this is definitely worth consider.
If you have this exact MS-A2 (Ryzen 9 9955HX + Radeon 610M) and want to team up, share your hookscripts, fight over which 128 KB VBIOS is actually the golden one, get ASPM working reliably, fix the lingering Mediatek BT lingering crap, whatever – reply here.I’m done suffering alone. Let’s make this thing perfect together.
:There is lingering disabled devices that need to be re-enabled each boot. A pain but not the end of the line. Just something to consider and maybe help me overcome. That and the number power settings I had the disfortune of having to ultimately disable. Although I had it working for days like this it was ultimately just not reliable.
CONTINUED ON THE NEXT POST L
Cheers