F5F Stay Refreshed Hardware Desktop Default setting prioritizes integrated graphics instead of using the GPU.

Default setting prioritizes integrated graphics instead of using the GPU.

Default setting prioritizes integrated graphics instead of using the GPU.

Pages (2): 1 2 Next
K
kfhd
Member
60
07-25-2025, 09:31 PM
#1
This situation is really frustrating. It's occurring with two different systems, both mine. Despite my experience setting up and troubleshooting numerous PCs, this one keeps reverting to the integrated graphics unexpectedly. The only workaround I've tried so far is removing and reinstalling Adrenalin. I've adjusted the BIOS settings in a couple of places—like under Settings, IO Ports, and NBIO—and changed the initial display output to PCIe 1 slot. The integrated graphics should be disabled, but it still activates randomly. I just recently upgraded to another system (R5 9600X with B650M Gigabyte) and it's the same problem. I'm also questioning whether all Gigabyte boards are reliable.
K
kfhd
07-25-2025, 09:31 PM #1

This situation is really frustrating. It's occurring with two different systems, both mine. Despite my experience setting up and troubleshooting numerous PCs, this one keeps reverting to the integrated graphics unexpectedly. The only workaround I've tried so far is removing and reinstalling Adrenalin. I've adjusted the BIOS settings in a couple of places—like under Settings, IO Ports, and NBIO—and changed the initial display output to PCIe 1 slot. The integrated graphics should be disabled, but it still activates randomly. I just recently upgraded to another system (R5 9600X with B650M Gigabyte) and it's the same problem. I'm also questioning whether all Gigabyte boards are reliable.

S
StephanKruger
Member
226
07-28-2025, 02:42 PM
#2
I don't speak for current boards, but I noticed several problems with older Gigabyte boards. Based on your description, it might be a BIOS issue—try updating or reverting to an earlier BIOS version. If the iGPU isn't visible in Windows, that could help. You might also test booting from a Linux USB drive to confirm proper iGPU disabling. Your motherboards may still be covered under warranty. It would be wise to reach out to Gigabyte for RMA support or at least ask them to assist with this unusual behavior. Good luck!
S
StephanKruger
07-28-2025, 02:42 PM #2

I don't speak for current boards, but I noticed several problems with older Gigabyte boards. Based on your description, it might be a BIOS issue—try updating or reverting to an earlier BIOS version. If the iGPU isn't visible in Windows, that could help. You might also test booting from a Linux USB drive to confirm proper iGPU disabling. Your motherboards may still be covered under warranty. It would be wise to reach out to Gigabyte for RMA support or at least ask them to assist with this unusual behavior. Good luck!

G
goldenagate
Member
209
08-17-2025, 02:59 AM
#3
I'm avoiding any contact with Gigabyte because their RMA process turned down my claim for a clearly faulty board under warranty. I'm also unsure why reinstalling Adrenalin would resolve a BIOS or motherboard issue. It seems to work temporarily, though the BIOS settings aren't behaving as expected even though I'm certain about them. The iGPU usually isn't visible in Windows, but it appears unexpectedly sometimes—this doesn't make sense.
G
goldenagate
08-17-2025, 02:59 AM #3

I'm avoiding any contact with Gigabyte because their RMA process turned down my claim for a clearly faulty board under warranty. I'm also unsure why reinstalling Adrenalin would resolve a BIOS or motherboard issue. It seems to work temporarily, though the BIOS settings aren't behaving as expected even though I'm certain about them. The iGPU usually isn't visible in Windows, but it appears unexpectedly sometimes—this doesn't make sense.

A
Allsky93
Junior Member
42
08-17-2025, 11:23 AM
#4
If RMA isn't available, consider alternative solutions. Have you attempted to reset the CMOS memory? Remember to activate the XMP/DOCP settings afterward. Keeping the integrated graphics active in the BIOS may help—try turning off the integrated graphics in the Windows Device Manager instead.
A
Allsky93
08-17-2025, 11:23 AM #4

If RMA isn't available, consider alternative solutions. Have you attempted to reset the CMOS memory? Remember to activate the XMP/DOCP settings afterward. Keeping the integrated graphics active in the BIOS may help—try turning off the integrated graphics in the Windows Device Manager instead.

G
GDiamond1000
Member
54
09-04-2025, 09:34 PM
#5
This occurs when a display cable is connected to the GPU. It only happened on my setup when someone mistakenly attached it to the motherboard. The most surprising part was that the secondary GPU continued running games automatically.
G
GDiamond1000
09-04-2025, 09:34 PM #5

This occurs when a display cable is connected to the GPU. It only happened on my setup when someone mistakenly attached it to the motherboard. The most surprising part was that the secondary GPU continued running games automatically.

A
agasycookie
Member
103
09-05-2025, 10:47 PM
#6
Confirmed CMOS settings, reset to factory defaults, using the default BIOS. Didn't test other BIOS versions before. Once functioning properly and powered through the GPU, the iGPU disappears from Device Manager. This hasn't happened with any 7000-series Ryzens yet, though a few 9000-series models are affected. It seems to occur only on Gigabyte boards.
A
agasycookie
09-05-2025, 10:47 PM #6

Confirmed CMOS settings, reset to factory defaults, using the default BIOS. Didn't test other BIOS versions before. Once functioning properly and powered through the GPU, the iGPU disappears from Device Manager. This hasn't happened with any 7000-series Ryzens yet, though a few 9000-series models are affected. It seems to occur only on Gigabyte boards.

W
WZ_Galaktiik
Senior Member
251
09-06-2025, 12:14 AM
#7
Yes, there are cables for the GPU. It seems to work by going through the motherboard connectors.
W
WZ_Galaktiik
09-06-2025, 12:14 AM #7

Yes, there are cables for the GPU. It seems to work by going through the motherboard connectors.

G
GoobieBubba
Member
183
09-06-2025, 04:47 AM
#8
It varies by chipset, but it's possible to route video signals between GPU and iGPU in either direction. This capability existed when GPUs only supported a single display output.
G
GoobieBubba
09-06-2025, 04:47 AM #8

It varies by chipset, but it's possible to route video signals between GPU and iGPU in either direction. This capability existed when GPUs only supported a single display output.

H
HowBoutCoffee
Member
176
09-07-2025, 10:35 PM
#9
Considering this, it might happen that when the GPU fails, the iGPU gets turned on again so you can see what you're doing. However, the unusual part is your monitor remains connected to the GPU. This means a functional GPU is needed for the signal to travel from the iGPU to the GPU output.
H
HowBoutCoffee
09-07-2025, 10:35 PM #9

Considering this, it might happen that when the GPU fails, the iGPU gets turned on again so you can see what you're doing. However, the unusual part is your monitor remains connected to the GPU. This means a functional GPU is needed for the signal to travel from the iGPU to the GPU output.

R
rosie2435
Senior Member
475
09-18-2025, 06:09 PM
#10
The GPU works properly once the system starts. It only causes issues during boot, rarely. When using the iGPU, uninstalling Adrenalin restores normal GPU usage right away, confirming it functions correctly. It seems the BIOS isn't consistently turning off the iGPU on every boot, and when it does, it favors the iGPU over the GPU—exactly what I requested in the BIOS settings. I initially suspected an AMD driver problem, but even reverting the driver didn’t help.
R
rosie2435
09-18-2025, 06:09 PM #10

The GPU works properly once the system starts. It only causes issues during boot, rarely. When using the iGPU, uninstalling Adrenalin restores normal GPU usage right away, confirming it functions correctly. It seems the BIOS isn't consistently turning off the iGPU on every boot, and when it does, it favors the iGPU over the GPU—exactly what I requested in the BIOS settings. I initially suspected an AMD driver problem, but even reverting the driver didn’t help.

Pages (2): 1 2 Next