Issues with using Graphics drivers with A10-5800k?

JWhit

Honorable
Dec 22, 2013
4
0
10,510
So I have a new computer just built, using:
Motherboard:
GIGABYTE GA-F2A88X-D3H(http://www.newegg.com/Product/Product.aspx?Item=N82E16813128656 )

Processor:
AMD A10-5800K Trinity 3.8GHz
(http://www.newegg.com/Product/Product.aspx?Item=N82E16819113280)

I built the system, put in 8GB of RAM (2x4GB), installed Win 7 64bit, and all that jazz. After some extensive troubleshooting, with multiple clean installs, BSOD's, I eventually determined that I can make the system work 100% as long as I don't install the Display adapter drivers for the APU (installs radeon graphics drivers). I know this is the issue, becuase once those are installed, I can't boot up for more than 2 minutes without getting crashes. However, I can boot into safe mode, and if I go into device manager and uninstall display adapter drivers, it is able to reboot and run with no issues. So all the above leads me to believe that my my APU is the source of my problems, when it tries to use the "GPU" portion correctly, it stops working nearly instantly. After calling Gigabyte's support desk they had me try a few different settings in BIOS, changing GFX to forced IGP, and forcing 2gb to be set aside for it etc...No change. He believed it was an APU issue, and suggested I RMA it. The conflicting piece of information I have that makes me think it could be a motherboard issue, is that the board has 1 PCIe express x16 slot, that is labeled as the dual graphics channel. (so maybe designed more for AMD than Nvidia?) I have one spare Nvidea 9800 GeForce card that I installed while troubleshooting, once that card is in I get the same errors, and inability to boot properly. Could this still be an issue with APU, or should I be looking more at my motherboard? I'd really like to know for sure which component is failing so I only RMA the correct one! Any suggestions? It seems the drivers issue is fairly common with some the AMD A serries processors, (doing some searching around various tech forums), so I'm still suspecting that, but don't understand why that would affect my discreet card as well!

Like I said any suggestions, thoughts, or general ridicule from those with more knowledge of these things that me would be appreciated. Am I missing something obvious?
 
Does Windows save any .dmp files from the BSOD?

Secondly, switching hardware vendors for a GPU can lead to conflicts that are often solved with a reformat. When you originally set up your rig, you were only using the iGPU and the respective drivers, right? (Just double-checking.)
 

JWhit

Honorable
Dec 22, 2013
4
0
10,510
1) towards Stickg1; Yes, it had 2 options North bridge and Southbridge, not being an expert I tried both, with the same effect both times. This is even before the drivers for that card are installed, simply plug and play and get BSOD. I tried installing drivers first, but it gives message to the effect of no Nvidia hardware detected...

2) Yes, in fact the system has had clean install ~4 times before I realized I could simply uninstall the drivers in safe mode to make everything work fine. ((so only remnants of previous install would be "OLD windows" folder or whatnot.

In terms of drivers for the iGPU, I tried the ones that came with my motherboard CD, as well as the newest for model from AMD's website. All had the exact same effect. Like I said looking around it seems like there could be some issues with the A10 line and this, but the other graphics card kind of contradicted my theory, at least in my head. Where would .dmp files be stored? I'm booting my other machine up now to check it.
 

JWhit

Honorable
Dec 22, 2013
4
0
10,510
Further looking around seems to show that this is a common issue with the AMD APU's, to the point that they may be selling the A series with faulty GPU's as a regular processor for much cheaper. I'm currently in the process of RMAing my A10, once a new one arrives and I install I will update if it fixes the issue. Still semi unsure if the board is good, but it's a place to start.
 


Unfortunately that's the way it goes when troubleshooting faulty parts. It's a pain especially when you don't have extra known working parts to test with. Start with the APU RMA then if that doesn't work RMA the motherboard.