Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Pc Specs: HP-Pavilion 23-B034 AIO pc, 6GB DDR3 RAM, Original O.S Windows 8, Current O.S Windows 10 x64 ver 20H2

I'm trying to fix a computer for grandparents and noticed that the current AMD APU is fried and causing screen tears.  I checked the specifications for this system and made sure that the APU was able to be upgraded at least.  Heres the link for the pre-built all in one system https://support.hp.com/us-en/document/c03518188

the original APU is a FM2 socket AMD Trinity dual core A6-5400K that was having display issues.  I went and bought a AMD Trinity quad-core A8-5600k and installed it on the board.  Mind you its a FM2 socket as well.  Now it says that it isn't compatible at all with this motherboard https://support.hp.com/us-en/document/c03428780

and will force a shutdown before I can do anything.  I did try to do a BIOS update because I did get it to boot up to Windows with the APU installed.  While it was booted up, I checked the temperatures, installed the drivers, checked to see if everything was running like normal before I did the BIOS update. I did notice that the screen stopped tearing after the driver was installed and working.

   What I want to know is why this A8-5600k works but the board refuses to think that it isn't compatible?  If i got it to boot up normally and everything was working showing like it is supposed to, why does it still say that the APU is not compatible and force shut down after restarting system?

Link to post
Share on other sites
8 minutes ago, xy535 said:

What I want to know is why this A8-5600k works but the board refuses to think that it isn't compatible?  If i got it to boot up normally and everything was working showing like it is supposed to, why does it still say that the APU is not compatible and force shut down after restarting system?

HP BIOS's are like this. The 5600K did not come with the system from HP. Usually the locked variants work fine, but as always, ymmv. HP would prefer you to buy a new system rather than upgrade an old one.

Main: AMD Ryzen 7 1700X, Nvidia GTX 780, 16 GB 2667 MT/s DDR4 Fedora 33 x86_64

Secondary: Intel Xeon X5670, Nvidia GTX 660, 24 GB 1333 MT/s DDR3 Windows 10 Home x86_64

Server: Intel Xeon X5670, 60 GB 1333 MT/s DDR3-R Ubuntu Server 20.04.1 LTS x86_64

Laptop: Intel Core i5-3320M, 16 GB 1600 MT/s DDR3 Fedora 33 x86_64

Link to post
Share on other sites
11 minutes ago, svmlegacy said:

HP BIOS's are like this. The 5600K did not come with the system from HP. Usually the locked variants work fine, but as always, ymmv. HP would prefer you to buy a new system rather than upgrade an old one.

Ah that makes sense I've heard about HP doing that but didn't want to believe it haha do you happen to know if there's a way to bypass the lock?

Edited by xy535
trying to tag a quate
Link to post
Share on other sites
11 minutes ago, xy535 said:

Ah that makes sense I've heard about HP doing that but didn't want to believe it haha do you happen to know if there's a way to bypass the lock?

Honestly, just buy a different FM2 motherboard and put it in the case. It'll be much less of a headache, and they aren't that expensive.

Option 2 is to try a locked APU like the A8-5500. No guarantee's.

(Previous CPU was a K... HP really did fuzz this BIOS.)

 

(And I just realized this is an All-In-One)...

Regardless, I doubt the APU itself is actually at fault. It's very rare to see a dying or dead CPU/APU that was never overclocked. You're probably looking at a different system entirely.

Main: AMD Ryzen 7 1700X, Nvidia GTX 780, 16 GB 2667 MT/s DDR4 Fedora 33 x86_64

Secondary: Intel Xeon X5670, Nvidia GTX 660, 24 GB 1333 MT/s DDR3 Windows 10 Home x86_64

Server: Intel Xeon X5670, 60 GB 1333 MT/s DDR3-R Ubuntu Server 20.04.1 LTS x86_64

Laptop: Intel Core i5-3320M, 16 GB 1600 MT/s DDR3 Fedora 33 x86_64

Link to post
Share on other sites
6 minutes ago, svmlegacy said:

Honestly, just buy a different FM2 motherboard and put it in the case. It'll be much less of a headache, and they aren't that expensive.

Option 2 is to try a locked APU like the A8-5500. No guarantee's.

(Previous CPU was a K... HP really did fuzz this BIOS.)

 

(And I just realized this is an All-In-One)...

Regardless, I doubt the APU itself is actually at fault. It's very rare to see a dying or dead CPU/APU that was never overclocked. You're probably looking at a different system entirely.

what do you mean different system entirely?

Link to post
Share on other sites
2 minutes ago, xy535 said:

what do you mean different system entirely?

The original problem described, how did you determine the APU is at fault? APU failures are very rare

Main: AMD Ryzen 7 1700X, Nvidia GTX 780, 16 GB 2667 MT/s DDR4 Fedora 33 x86_64

Secondary: Intel Xeon X5670, Nvidia GTX 660, 24 GB 1333 MT/s DDR3 Windows 10 Home x86_64

Server: Intel Xeon X5670, 60 GB 1333 MT/s DDR3-R Ubuntu Server 20.04.1 LTS x86_64

Laptop: Intel Core i5-3320M, 16 GB 1600 MT/s DDR3 Fedora 33 x86_64

Link to post
Share on other sites

Well it all started when I was upgrading the system from win 8 to win 10.  Grandparents told me that the display driver wasn't working all that well.  As soon as I upgraded operating systems and did some testing.  I did install the amd driver and saw that it was screen tearring so bad i couldnt hardly see the screen.  i even uninstalled the display driver completly off the system and it was working like normal with some discoloration.  At first i thought it mightve been the screen.  so i did some more testing used hardware moniter to check the stress test tempratures, and i noticed the temprature was 62c and higher on the cpu/apu I took the back panel off and went to check out the cpu/apu.  The thermal compound was so dry that I spent almost an hour hour trying to use cleaner and 92% alcohol just to get the dry compound off.  The system wasnt so thick in dust the fan itself and heatsink i cleaned it anyway.  i reinstalled the driver and tested the temps on benchmarking and it still screen teared the temps stayed at 45 to 50c.  i did some research and sometimes it can be the apu causing the tears.  i bet on it and got an upgrade.  when i did manage to boot it up the first thing i did was install the display driver from the site.  it didnt screen tear at all and it ran buttery smooth.  (i did some screen testing as well through the bios. and there wasnt an issue with the color or any lights missing.)

Link to post
Share on other sites

my apologies i'm so scrambled at the moment.  hope what i typed makes sense.

Link to post
Share on other sites

@xy535 Obviously the 5600K can't be tested by the BIOS alone.

 

Were the memory slots dusty? I've seen that cause issues before, and from the sounds of it there's enough dust in the case to cause that.

Main: AMD Ryzen 7 1700X, Nvidia GTX 780, 16 GB 2667 MT/s DDR4 Fedora 33 x86_64

Secondary: Intel Xeon X5670, Nvidia GTX 660, 24 GB 1333 MT/s DDR3 Windows 10 Home x86_64

Server: Intel Xeon X5670, 60 GB 1333 MT/s DDR3-R Ubuntu Server 20.04.1 LTS x86_64

Laptop: Intel Core i5-3320M, 16 GB 1600 MT/s DDR3 Fedora 33 x86_64

Link to post
Share on other sites
3 hours ago, svmlegacy said:

@xy535 Obviously the 5600K can't be tested by the BIOS alone.

 

Were the memory slots dusty? I've seen that cause issues before, and from the sounds of it there's enough dust in the case to cause that.

I did clean the ram slots to be safe but i didnt see anything the ram i cleaned off just incase .  If i had an fm2 board id be able to know better. And let me rephrase i tested the moniter by using the diagnostics aaand the display driver.  The diagnostics showed no missing lights and discoloration. Also i put the old cpu/ apu back on before i went to sleep and it was still screen tearing

Link to post
Share on other sites
1 minute ago, xy535 said:

I did clean the ram slots to be safe but i didnt see anything the ram i cleaned off just incase .  If i had an fm2 board id be able to know better. And let me rephrase i tested the moniter by using the diagnostics aaand the display driver.  The diagnostics showed no missing lights and discoloration. Also i put the old cpu/ apu back on before i went to sleep and it was still screen tearing

Have you tried DDU and installing fresh drivers from AMD?

Main: AMD Ryzen 7 1700X, Nvidia GTX 780, 16 GB 2667 MT/s DDR4 Fedora 33 x86_64

Secondary: Intel Xeon X5670, Nvidia GTX 660, 24 GB 1333 MT/s DDR3 Windows 10 Home x86_64

Server: Intel Xeon X5670, 60 GB 1333 MT/s DDR3-R Ubuntu Server 20.04.1 LTS x86_64

Laptop: Intel Core i5-3320M, 16 GB 1600 MT/s DDR3 Fedora 33 x86_64

Link to post
Share on other sites

thats what i always did driver wise i always installed from the amd site but ddu? suprisingly im not familiar with the term. can you tell me what ddu means?  i did also try installing older versions instead of the latest version of the driver but no go sadly

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×