Windows/Linux random rebooting after installing Catalyst (works fine with generic graphics driver)

lem0nhead

Commendable
Mar 30, 2016
2
0
1,510
[no OC] After installing mobo Gigabyte GA-F2A68HM-H and APU AMD A10-7850k (Radeon R7), Windows and Linux started random rebooting (usually in less than 2 minutes after booting) after I installed the recommended Radeon drivers (I tried the last version from this month for Windows).
I couldn't find any other kind of correlation (for instance, I tried stressing the CPU/memory to see if it rebooted quicker).
With the default (generic) driver it works flawlessly (both in Windows and Linux) - but, of course, some features are not available (especially related to games)

Any ideas if this is a mobo or APU issue?
Thanks
 
Solution
Check for grounding issues one more time, then call AMD technical support. It could be a weird firmware issue, a bad card, BIOS/UEFI - or possibly something else. In generic graphics mode the graphics card should actually be doing very little, so when you activate the driver, you could be in effect turning on a bad card (or chip, piece of firmware, etc). If you have a spare computer somewhere, you can see if the card works with that. Also, BIOS implementations have always been notoriously finnicky, and I kind of doubt UEFI is much better (I run a BIOS system that has GPT compatibility, so I don't have firsthand knowledge of UEFI only systems). If there is something about your BIOS or UEFI that is not sane, it's always possible that...

JMW22

Reputable
Dec 21, 2015
74
0
4,710
This could be BIOS or UEFI, could be the card itself, or it could be a short - check all the grounds, make sure theres no little floating metal pieces or hanging wires, etc. One thing you can do in Linux, if you're able to get to a console screen: boot from a liveUSB so you'll have USB already mounted on boot (make sure the LiveUSB permits this), and then quckly log in and 'dmesg > dmesg.txt'. Unfortunately you won't have the dmesg colored output, but you'll be able to comb through it carefully looking for issues. I would check for bad grounds first.

And yes, you could have shook the machine around the time you installed the new driver, so there's no absolute correlation there, and I see no reason that windows drivers would be rebooting Linux.
 

lem0nhead

Commendable
Mar 30, 2016
2
0
1,510
Windows driver is not impacting Linux.

Running Windows with generic graphics driver: no issue
Running Windows with Radeon R7 driver: random reboots (Windows)

Running Linux with generic graphics driver (ati): no issue
Running Linux with Radeon R7 driver (catalyst): random reboots (Linux)

I tried going from generic to proprietary and reverting a couple times and the above scenario happens everytime.
 

JMW22

Reputable
Dec 21, 2015
74
0
4,710
Check for grounding issues one more time, then call AMD technical support. It could be a weird firmware issue, a bad card, BIOS/UEFI - or possibly something else. In generic graphics mode the graphics card should actually be doing very little, so when you activate the driver, you could be in effect turning on a bad card (or chip, piece of firmware, etc). If you have a spare computer somewhere, you can see if the card works with that. Also, BIOS implementations have always been notoriously finnicky, and I kind of doubt UEFI is much better (I run a BIOS system that has GPT compatibility, so I don't have firsthand knowledge of UEFI only systems). If there is something about your BIOS or UEFI that is not sane, it's always possible that activating a new piece of hardware could trigger it. Don't assume the BIOS/UEFI is sane out of the box either - go over it line by line and look for things that could be wrong.

Also, did you try the dmesg thing like I suggested? If you did, go ahead and post it up on a pastebin somewhere and post the link here. Linux is usually *quite* good at detecting hardware/firmware errors.
 
Solution