New Member ASRock GPU Thread
Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD and Intel Graphics Cards
Forum Description: Question about ASRock AMD and Intel Graphics Cards
URL: https://forum.asrock.com/forum_posts.asp?TID=113254
Printed Date: 26 Aug 2025 at 10:01pm Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: New Member ASRock GPU Thread
Posted By: Xaltar
Subject: New Member ASRock GPU Thread
Date Posted: 08 Jul 2025 at 5:25pm
This thread is for new members to post queries and issues pertaining to ASRock's GPUs.
-------------
|
Replies:
Posted By: Alakazzam
Date Posted: 12 Jul 2025 at 4:49am
Hello ASRock team and community,
I'm currently experiencing an issue with my ASRock RX 9070 XT Taichi related to the ARGB Link mode.
When connected to my ARGB controller (Nollie 16-channel), the GPU's lighting works perfectly as long as an effect is active. However, as soon as I set the lighting to ?œoff??(no ARGB signal), the GPU starts flickering its LEDs rapidly, as if it?™s in some kind of fault mode.
?”ï? What I?™ve tested: Proper ARGB 5V 3-pin cable (correct pinout: 5V-D-G)
Multiple ARGB channels on the controller
Switching the LED mode using the physical button on the GPU
Other ARGB components connected to the same controller work flawlessly
Tried static black color instead of ?œoff??to prevent the flickering (temporary workaround)
?? Request: I kindly ask the ASRock team to provide a firmware fix or update for the RX 9070 XT Taichi. I believe this is a bug in how the GPU handles ARGB Link when the signal is idle or turned off.
|
Posted By: Des-101
Date Posted: 13 Jul 2025 at 8:01pm
Hey all,
I've just recently purchased the Arc B580 Steel Legend 12gb OC and struggling to get the ASRRBGLED app to work to control the LED lighting!
I've installed the .NET runtime libraries and On initial startup it starts normal with the card listed.
The moment I try to adjust any settings the app hangs! The LEDs on the card "Freeze" and I'm unable to do anything else! Restarting the App does nothing along with forcing it closed via Task Manager & re-trying again!
Even soft boots fail to fix it - App loads but nothing works & the GPU LEDs are still frozen.
Only a complete system shutdown & then having to cold start fixes the issue!
Going into Computer Management on the PC and checking the logs, it shows up as a missing .NET library - which I've got installed! (Yes, It's the correct version & Library file
I also have Razer Keyboard which should also be able to link the the ASRRGBLED App yet that's also missing from devices - there's also no options to be able link the GPU LED to the Razer apps (which reading on their website, there should be).
Anyone got any ideas of what's going on?
NOTE: This is all on a brand new system, New Windows 11 install, All latest drivers installed. AM5 socket on B650 chipset.
Cheers for any help.
|
Posted By: Xaltar
Date Posted: 13 Jul 2025 at 8:19pm
Hello, welcome to the forums both of you 
I would recommend you both open a support ticket with ASRock https://tw.asrock.com/events/tsd.asp" rel="nofollow - here
I will also get in touch with my contacts at ASRock and inquire if there is a known issue regarding the ASRRGBLED app.
Please post back here when you get a response and/or if you find a solution 
-------------
|
Posted By: Des-101
Date Posted: 16 Jul 2025 at 3:02pm
Xaltar wrote:
Hello, welcome to the forums both of you 
I would recommend you both open a support ticket with ASRock https://tw.asrock.com/events/tsd.asp" rel="nofollow - here
I will also get in touch with my contacts at ASRock and inquire if there is a known issue regarding the ASRRGBLED app.
Please post back here when you get a response and/or if you find a solution  |
Thanks for the reply. I have tried raising a Support ticket yet their system is currently broken & although I've tried multiple times, the ticket hasn't gone through & I've not received a confirmation email!
I tried on a few different browsers (Edge, Opera & Chrome) & different devices yet they all did the same thing - Form filled out, hit "Submit", page reloads back to a blank form! And no email received (All email folders checked).
|
Posted By: cliff
Date Posted: 27 Jul 2025 at 3:36am
I fell in love Asrock rack a few years ago! So yeah.. I am here loving your AMD GPU's.. Just remember us linux users.. I would also recommend OPENRGB for everthing, especally for those who like the light shows. Last,we live in a world of color and art. Your boards don't have to be black or white.. Throw some color options out there.
|
Posted By: Xaltar
Date Posted: 11 Aug 2025 at 3:55pm
Welcome to the forums SHADEZ86
https://forum.asrock.com/forum_posts.asp?TID=113291" rel="nofollow - Here is your new thread.
-------------
|
Posted By: Pilgrim
Date Posted: 23 Aug 2025 at 1:01am
Hello! I've been ASRock G41M-S3 motherboard user since 2011, recently had to upgrade and became the happy possessor of H510M-HDV/M.2 SE with i3-10100 and 8 GB RAM. Now I'm trying to understand the logic of onboard graphics shared memory. The interface of Win 10 indicates that there is 128 MB shared to Intel UHD 630, but the rest of RAM is 7.64 GB. CPU-Z also responses, that there is 7824 MB left, what means the shared memory is 8192 - 7824 = 368 = 128 + 240, can't get what 240 MB is shared for. UEFI setting is Auto, and the available values are 128/256/512/1024, and setting any of them manually still leaves 128 MB indicated as shared memory by the software. Could you kindly explain how to understand this mathematics and set shared memory properly?
|
Posted By: Xaltar
Date Posted: 23 Aug 2025 at 1:42am
Shared memory is automatically allocated depending on your amount of RAM and the demand from the application in use (or game). In general (windows) use a minimum of 128mb is allocated.
That is my understanding at least. At one point some years ago some games mistakenly report only 128mb of vRAM and refuse to load but I suspect that has been addressed now.
I hope this explanation helps.
-------------
|
Posted By: Pilgrim
Date Posted: 23 Aug 2025 at 2:19pm
Well, on the previous motherboard it was certainly defined in BIOS and indicated by Windows as 64/128/256 MB.
Now I've set 512 MB in UEFI, CPU-Z indicates 7568 MB, that means allocated 624 MB, what is 112 MB allocated for?
By the way, there was another problem. I've installed the graphics driver from ASRock site, it was OK, then I installed the rest of audio, inf and ME drivers, and somehow Intel Graphics Center was gone, and I couldn't reinstall any driver for the video, it was working with only Win10 basic driver. The only option recommended in web was to re-install Windows 10, so I did it and installed oldest driver from Intel site and inf driver only, so it looks working with Intel driver now (graphics is ok), but shared memory issue remains unclear.
I've even read somewhere, this brain copulation is the way manufacturers persuade users to buy an additional graphics card.
|
Posted By: Xaltar
Date Posted: 23 Aug 2025 at 4:00pm
You have now set the minimum allocation to 512mb, this is the lowest amount that the OS will report to applications. As I said, the memory sharing scales to what the programs need. it dynamically allocates and reallocates RAM to vRAM and back.
There is absolutely no incentive for manufacturers to trick or persuade users to buy a dedicated GPU, there is absolutely no guarantee that the user will purchase a GPU from them over a competitor. iGPU functionality is a balancing act beteen system resources and GPU performance. That is the only reason shared memory is dynamic. It allows the system to allocate more memory to the system when there are no graphically intensive loads and more to the iGPU when there are. It's that simple. When you factor in that the majority of people using an iGPU are using more budget focused systems, it also stands to reason that they would not have huge amounts of RAM to work with. iGPU RAM allocation becomes a non issue with 32gb and beyond.
On my systems that don't need/use a dedicated GPU I leave the share memory allocation set to auto.
-------------
|
Posted By: Pilgrim
Date Posted: 23 Aug 2025 at 9:49pm
I see you mean it can change while OS is running. Huh, right now it's indicating '0.1-0.2 of 3.7 GB' in Task Manager, 625 MB in Resource Monitor, and 624 MB in CPU-Z, every program reports in its own way. Weird stuff, gentlemen, weird stuff.
|
|