Question pc does not recognize monitor

konstantinos vasilis

Junior Member
Dec 20, 2019
7
2
36
I open the pc, starts fine. PC does not recognize monitor. I tried with GPU and without. I tried 4 monitors that all working with other PCs. I tried DVI, VGA, HDMI. I used a different PSU, different RAMs, tried the GPU on other computer, GPU working fine. I removed the battery and restated BIOS. PC still does not recognize monitor, any ideas to fix it? Or the motherboard has a problem?

motherboardGA-A320M-S2H (1.x)
GPU :MSI radeon r7 240 2GB
CPU :amd a6 9500
RAM :crusial ballistix sport LT 4GB
Memory Part No.:BLS4G4D240FSB.8FBD2
 
Last edited:

Steltek

Diamond Member
Mar 29, 2001
3,345
1,086
136
Your A6 APU has built-in graphics, and the motherboard should have a built-in video port. If you have not done so, try to plug the monitor into the motherboard video port instead of the graphics card. It may be that you need to access the motherboard BIOS to change the video output default to the graphics card.

EDIT: Nevermind, I see that you must have tried this. If you've done this and it doesn't work, it sounds like you might have a motherboard problem. The only other thing I can think of is to try a different type of video cable connection from the motherboard to the monitor (i.e. motherboard has HDMI, DVI, and VGA connectors, try changing cables and using another type of port connection to the monitor in case one of the motherboard ports is bad).
 
Last edited:

Steltek

Diamond Member
Mar 29, 2001
3,345
1,086
136
Another thing to check - what BIOS is installed on the motherboard? If it is F40 or above, support for the A series APUs was removed in order to support 3rd gen Ryzen CPUs (there wasn't enough room in the BIOS to support all of them, so they dropped Bristol Ridge APU/CPU support in BIOS F40 and later). This means your motherboard would not work with your CPU if the BIOS has been flashed to F40 or above.
 
  • Like
  • Wow
Reactions: Muadib and whm1974

konstantinos vasilis

Junior Member
Dec 20, 2019
7
2
36
Your A6 APU has built-in graphics, and the motherboard should have a built-in video port. If you have not done so, try to plug the monitor into the motherboard video port instead of the graphics card. It may be that you need to access the motherboard BIOS to change the video output default to the graphics card.

EDIT: Nevermind, I see that you must have tried this. If you've done this and it doesn't work, it sounds like you might have a motherboard problem. The only other thing I can think of is to try a different type of video cable connection from the motherboard to the monitor (i.e. motherboard has HDMI, DVI, and VGA connectors, try changing cables and using another type of port connection to the monitor in case one of the motherboard ports is bad).
I’ve tried all the connections of the monitor, on the motherboard and on the GPU, I wrote it above, ty for your answer anyway
 
Last edited:

konstantinos vasilis

Junior Member
Dec 20, 2019
7
2
36
Another thing to check - what BIOS is installed on the motherboard? If it is F40 or above, support for the A series APUs was removed in order to support 3rd gen Ryzen CPUs (there wasn't enough room in the BIOS to support all of them, so they dropped Bristol Ridge APU/CPU support in BIOS F40 and later). This means your motherboard would not work with your CPU if the BIOS has been flashed to F40 or above.
So what am I doing in that situation? I don’t know the bios version since I don’t have screen to check, is there another way to check it?
 
Last edited:

UsandThem

Elite Member
May 4, 2000
16,068
7,383
146
You mean removing the battery? I’ve already done that
That is not resetting your CMOS. Look in the manual for how to do it on your particular motherboard.

If after that you're still not getting a signal after trying all of those different components (and monitors), maybe your motherboard or CPU is defective. That or what the other user suggested about the current BIOS version dropping support for that CPU series.
 

konstantinos vasilis

Junior Member
Dec 20, 2019
7
2
36
That is not resetting your CMOS. Look in the manual for how to do it on your particular motherboard.

If after that you're still not getting a signal after trying all of those different components (and monitors), maybe your motherboard or CPU is defective. That or what the other user suggested about the current BIOS version dropping support for that CPU series.
Oh, you mean the 2pin clr_cmos. I ll give it a try too. Ty for the suggestion
 
  • Like
Reactions: UsandThem

Steltek

Diamond Member
Mar 29, 2001
3,345
1,086
136
So what am I doing in that situation? I don’t know the bios version since I don’t have screen to check, is there another way to check it?

First, try clearing the CMOS as UsandThem suggests - that is ALWAYS a good idea when you are having problems like this.

In this case, Gigabyte doesn't have a sticker on the MB/box label like some manufacturers do showing the BIOS initially installed and as you say there is no way to check since it won't boot. If the CMOS reset doesn't work, what to try next depends on whether you bought it new or used.

If you bought it new, and the box states it supports A-series APUs, then I'd presume that an A-series compatible BIOS (F32 or earlier) is installed and that the board is simply defective. I'd then return it if possible (preferred) or go through Gigabyte support for replacement (if no other choice). If you go through Gigabyte support, you might be able to request a board with the correct BIOS installed to support your CPU. Though, if you bought it through a retailer, they may be able to update the BIOS for you or even swap you with a board with a compatible BIOS for your APU. If you go this route, make sure not to install any BIOS above the F32 BIOS or you'll brick the board again (see the red BIOS notes on this page).

If you bought it used, it gets far more complicated because the prior owner may have flashed the BIOS to F40 or higher for their CPU and thus prevented it from working with your APU. In order to test, you'd need a supported CPU on this list that is not labeled as being a Bristol Ridge CPU core to try to boot with. You could check with the place/person you bought it to see if they can test it for you to see if it will boot with a supported CPU. If you bought it from a person, they may know what BIOS is installed.

That being said, I don't see anything on the Gigabyte website that says you can't flash the BIOS back from F40+ to F32 (the last BIOS that supported Bristol Ridge APU/CPU cores). There are sometimes BIOS updates that can't be reverted, but none of those on the Gigabyte support site are actually flagged as being such. However, in the end it could be non-revertable and refuse to flash back to BIOS F32 - you just won't know until you try it.
 
Last edited:

konstantinos vasilis

Junior Member
Dec 20, 2019
7
2
36
First, try clearing the CMOS as UsandThem suggests - that is ALWAYS a good idea when you are having problems like this.

In this case, Gigabyte doesn't have a sticker on the MB/box label like some manufacturers do showing the BIOS initially installed and as you say there is no way to check since it won't boot. If the CMOS reset doesn't work, what to try next depends on whether you bought it new or used.

If you bought it new, and the box states it supports A-series APUs, then I'd presume that an A-series compatible BIOS (F32 or earlier) is installed and that the board is simply defective. I'd then return it if possible (preferred) or go through Gigabyte support for replacement (if no other choice). If you go through Gigabyte support, you might be able to request a board with the correct BIOS installed to support your CPU. Though, if you bought it through a retailer, they may be able to update the BIOS for you or even swap you with a board with a compatible BIOS for your APU. If you go this route, make sure not to install any BIOS above the F32 BIOS or you'll brick the board again (see the red BIOS notes on this page).

If you bought it used, it gets far more complicated because the prior owner may have flashed the BIOS to F40 or higher for their CPU and thus prevented it from working with your APU. In order to test, you'd need a supported CPU on this list that is not labeled as being a Bristol Ridge CPU core to try to boot with. You could check with the place/person you bought it to see if they can test it for you to see if it will boot with a supported CPU. If you bought it from a person, they may know what BIOS is installed.

That being said, I don't see anything on the Gigabyte website that says you can't flash the BIOS back from F40+ to F32 (the last BIOS that supported Bristol Ridge APU/CPU cores). There are sometimes BIOS updates that can't be reverted, but none of those on the Gigabyte support site are actually flagged as being such. However, in the end it could be non-revertable and refuse to flash back to BIOS F32 - you just won't know until you try it.
well i cleared cmos, nothing again, i m talking with gigabyte now. Thanks a lot dude for taking all this time to do all this research and reply to me.
 
  • Like
Reactions: VirtualLarry

Steltek

Diamond Member
Mar 29, 2001
3,345
1,086
136
well i cleared cmos, nothing again, i m talking with gigabyte now. Thanks a lot dude for taking all this time to do all this research and reply to me.

No problem. We have all been there and done that when this kind of thing happens.

You tend to see BIOS issues a lot more often on AMD systems because they have stuck with the same sockets for so long. Good for us end users usually (in that we have so many choices of CPUs), but support becomes a pain when there isn't enough space in the BIOS chip to keep supporting prior CPUs while adding new ones.
 
  • Like
Reactions: VirtualLarry

konstantinos vasilis

Junior Member
Dec 20, 2019
7
2
36
No problem. We have all been there and done that when this kind of thing happens.

You tend to see BIOS issues a lot more often on AMD systems because they have stuck with the same sockets for so long. Good for us end users usually (in that we have so many choices of CPUs), but support becomes a pain when there isn't enough space in the BIOS chip to keep supporting prior CPUs while adding new ones.
ok ty about this information too, noted