Ubuntu 17.10/Gigabyte/Ryzen issues still?
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
Built a Gigabyte AB350M-D3H system using Ryzen 1200, 16.04 did not work. Waited until mid-October 2017 to get 17.10 official support for Gigabyte/Ryzen, and seemed stable enough ... no random crashes.
But now I am seeing random crashes and lockups... and seemingly excessive CPU activity after up for a while and cursor is used.
Additional note, I did remove the CPU with possible return of the motherboard, but ultimately did not feel Microcenter needs to suffer for the incompatibility. Reinstalled the CPU applying what I THOUGHT was the correct amount of thermal compound, I but may have been wrong.
What is the most probable cause of shutdowns... Ubuntu 17.10/Ryzen/Gigabyte or CPU overheating due to bad installation?
I am not trying to cause waves or point fingers, but having this "server" crash is more than inconvenient. The next steps, as I see it:
Keep uninstall/reinstall the CPU until it may improve (risky)
Buy a new ASRock motherboard, reinstall the CPU once and waste an otherwise decent Gigabyte motherboard (really? damm!)
17.10 overheating lockup
asked Feb 22 at 3:07
Ozymandias
12
add a comment |Â
up vote
0
down vote
favorite
Built a Gigabyte AB350M-D3H system using Ryzen 1200, 16.04 did not work. Waited until mid-October 2017 to get 17.10 official support for Gigabyte/Ryzen, and seemed stable enough ... no random crashes.
But now I am seeing random crashes and lockups... and seemingly excessive CPU activity after up for a while and cursor is used.
Additional note, I did remove the CPU with possible return of the motherboard, but ultimately did not feel Microcenter needs to suffer for the incompatibility. Reinstalled the CPU applying what I THOUGHT was the correct amount of thermal compound, I but may have been wrong.
What is the most probable cause of shutdowns... Ubuntu 17.10/Ryzen/Gigabyte or CPU overheating due to bad installation?
I am not trying to cause waves or point fingers, but having this "server" crash is more than inconvenient. The next steps, as I see it:
Keep uninstall/reinstall the CPU until it may improve (risky)
Buy a new ASRock motherboard, reinstall the CPU once and waste an otherwise decent Gigabyte motherboard (really? damm!)
17.10 overheating lockup
asked Feb 22 at 3:07
Ozymandias
12
As stated above ... not trying to bash Gigabyte or Ubuntu ... but there were issues with Gigabyte/Ryzen/Ubuntu last year. Just want to know if the motherboard is probably salvageable or if I just chalk it up to "should goggle first for unexpected issues" and buy a new ASRock motherboard.
– Ozymandias
Feb 23 at 5:03
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Built a Gigabyte AB350M-D3H system using Ryzen 1200, 16.04 did not work. Waited until mid-October 2017 to get 17.10 official support for Gigabyte/Ryzen, and seemed stable enough ... no random crashes.
But now I am seeing random crashes and lockups... and seemingly excessive CPU activity after up for a while and cursor is used.
Additional note, I did remove the CPU with possible return of the motherboard, but ultimately did not feel Microcenter needs to suffer for the incompatibility. Reinstalled the CPU applying what I THOUGHT was the correct amount of thermal compound, I but may have been wrong.
What is the most probable cause of shutdowns... Ubuntu 17.10/Ryzen/Gigabyte or CPU overheating due to bad installation?
I am not trying to cause waves or point fingers, but having this "server" crash is more than inconvenient. The next steps, as I see it:
Keep uninstall/reinstall the CPU until it may improve (risky)
Buy a new ASRock motherboard, reinstall the CPU once and waste an otherwise decent Gigabyte motherboard (really? damm!)
17.10 overheating lockup
asked Feb 22 at 3:07
Ozymandias
12
Built a Gigabyte AB350M-D3H system using Ryzen 1200, 16.04 did not work. Waited until mid-October 2017 to get 17.10 official support for Gigabyte/Ryzen, and seemed stable enough ... no random crashes.
But now I am seeing random crashes and lockups... and seemingly excessive CPU activity after up for a while and cursor is used.
Additional note, I did remove the CPU with possible return of the motherboard, but ultimately did not feel Microcenter needs to suffer for the incompatibility. Reinstalled the CPU applying what I THOUGHT was the correct amount of thermal compound, I but may have been wrong.
What is the most probable cause of shutdowns... Ubuntu 17.10/Ryzen/Gigabyte or CPU overheating due to bad installation?
I am not trying to cause waves or point fingers, but having this "server" crash is more than inconvenient. The next steps, as I see it:
Keep uninstall/reinstall the CPU until it may improve (risky)
Buy a new ASRock motherboard, reinstall the CPU once and waste an otherwise decent Gigabyte motherboard (really? damm!)
17.10 overheating lockup
17.10 overheating lockup
asked Feb 22 at 3:07
Ozymandias
12
asked Feb 22 at 3:07
Ozymandias
12
edited Feb 22 at 6:30
asked Feb 22 at 3:07
Ozymandias
12
asked Feb 22 at 3:07
Ozymandias
12
asked Feb 22 at 3:07
Ozymandias
12
12
As stated above ... not trying to bash Gigabyte or Ubuntu ... but there were issues with Gigabyte/Ryzen/Ubuntu last year. Just want to know if the motherboard is probably salvageable or if I just chalk it up to "should goggle first for unexpected issues" and buy a new ASRock motherboard.
– Ozymandias
Feb 23 at 5:03
add a comment |Â
As stated above ... not trying to bash Gigabyte or Ubuntu ... but there were issues with Gigabyte/Ryzen/Ubuntu last year. Just want to know if the motherboard is probably salvageable or if I just chalk it up to "should goggle first for unexpected issues" and buy a new ASRock motherboard.
– Ozymandias
Feb 23 at 5:03
As stated above ... not trying to bash Gigabyte or Ubuntu ... but there were issues with Gigabyte/Ryzen/Ubuntu last year. Just want to know if the motherboard is probably salvageable or if I just chalk it up to "should goggle first for unexpected issues" and buy a new ASRock motherboard.
– Ozymandias
Feb 23 at 5:03
As stated above ... not trying to bash Gigabyte or Ubuntu ... but there were issues with Gigabyte/Ryzen/Ubuntu last year. Just want to know if the motherboard is probably salvageable or if I just chalk it up to "should goggle first for unexpected issues" and buy a new ASRock motherboard.
– Ozymandias
Feb 23 at 5:03
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1008567%2fubuntu-17-10-gigabyte-ryzen-issues-still%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
As stated above ... not trying to bash Gigabyte or Ubuntu ... but there were issues with Gigabyte/Ryzen/Ubuntu last year. Just want to know if the motherboard is probably salvageable or if I just chalk it up to "should goggle first for unexpected issues" and buy a new ASRock motherboard.
– Ozymandias
Feb 23 at 5:03