After Win10, HP desktop will not wake up from sleep

Hi All
the problem has been solved i downloaded the following driver from AMD,
looks like the original os must have been vista not windows 7 don't know if this would have impact or not?
I followed the post from Kolibri42 starting with Action,install legacy etc right to the inf file and it has worked.
So thanks again for all your help you all have been great.

Windows Vista - 64-Bit Edition
AMD Chipset Drivers
Revision Number
13.4
File Size
26.4 MB
Release Date
4/24/2013
DOWNLOAD*
Driver Details
Supports Windows Vista (32-bit & 64-bit)

This package is for motherboards with 700 series or newer AMD chipsets, and includes:
AMD Chipset Drivers
AMD AHCI Driver
AMD USB 3.0 Driver

Hi Richard
Thanks for all the info you have given,I have managed to sort the problem with all the info from you and others on this site.I think the difference with mine was the original OS on my pc was vista so I had to use the driver associated with that instead of the windows 7 version.
Thanks again for replying .
Eggheed.

Hi Eggheed,

No problem, pleased it helped someone.

R

Thanks for providing so much information, I just solved this problem! :)

But it did take quite a bit of reading and some links weren't working in older posts, so I'll just try to create an easy guide. I've only tested this for Windows 10 64 bit.

1. Get the driver
Use this link: https://www.amd.com/en/support/chips...-chipsets/785g

At the point of writing this post, the driver packages for Windows 7 and Windows 10 all link to the same file. The path in step 3 will most likely differ, if you download a different driver package.

If the link doesn't work anymore, search for the driver on AMD's support pages. The chipset is called 785G.

2. Extract the driver
Double-click on the file you downloaded. Click on install. Nothing will be installed, it only extracts the files. After extraction you can either let the program install an updated USB-driver or quit the program. It doesn't offer to to change your SATA-driver.

3. Installing the driver
Right-click on the start-button and select device manager. Look for "IDE ATA/ATAPI Controller" (could be different in your language). Click on the ">"-sign and you should see "AMD SATA-Controller". Double-click on the controller. Choose "Driver" at the top of the window and select "Update driver". Select "Search for drivers on my computer". Point the dialogue to C:\AMD\AMD-Chipset-Drivers\Packages\Drivers\SBDrv or wherever you extracted the files to. Click on next. Windows will now search through the directories and select the correct driver. Accept to let Windows install the driver.

4. Reboot
Reboot your computer.

That's it!

The only downside to this driver update is that there actually is a performance hit you take. I've lost ~ 40 - 50 % in random 4K reads and writes. But I have to admit that it isn't really noticeable on a Samsung EVO 850 120 GB. I will post the benchmark nonetheless. I used CrystalDiskMark 8.

Before:

[Read]
SEQ 1MiB (Q= 8, T= 1): 277.384 MB/s [ 264.5 IOPS] < 30109.23 us>
SEQ 1MiB (Q= 1, T= 1): 237.456 MB/s [ 226.5 IOPS] < 4403.90 us>
RND 4KiB (Q= 32, T= 1): 155.638 MB/s [ 37997.6 IOPS] < 815.00 us>
RND 4KiB (Q= 1, T= 1): 13.138 MB/s [ 3207.5 IOPS] < 309.36 us>

[Write]
SEQ 1MiB (Q= 8, T= 1): 251.391 MB/s [ 239.7 IOPS] < 33074.60 us>
SEQ 1MiB (Q= 1, T= 1): 219.991 MB/s [ 209.8 IOPS] < 4747.62 us>
RND 4KiB (Q= 32, T= 1): 139.205 MB/s [ 33985.6 IOPS] < 936.46 us>
RND 4KiB (Q= 1, T= 1): 66.590 MB/s [ 16257.3 IOPS] < 61.02 us>

Profile: Default
Test: 1 GiB (x5) [C: 31% (34/111GiB)]
Mode: [Admin]
Time: Measure 5 sec / Interval 5 sec
Date: 2021/04/07 16:48:34
OS: Windows 10 Professional [10.0 Build 19042] (x64)

After:

[Read]
SEQ 1MiB (Q= 8, T= 1): 276.232 MB/s [ 263.4 IOPS] < 30266.77 us>
SEQ 1MiB (Q= 1, T= 1): 251.299 MB/s [ 239.7 IOPS] < 4162.00 us>
RND 4KiB (Q= 32, T= 1): 109.452 MB/s [ 26721.7 IOPS] < 1195.81 us>
RND 4KiB (Q= 1, T= 1): 13.580 MB/s [ 3315.4 IOPS] < 299.33 us>

[Write]
SEQ 1MiB (Q= 8, T= 1): 252.777 MB/s [ 241.1 IOPS] < 32839.10 us>
SEQ 1MiB (Q= 1, T= 1): 234.082 MB/s [ 223.2 IOPS] < 4466.85 us>
RND 4KiB (Q= 32, T= 1): 109.365 MB/s [ 26700.4 IOPS] < 1197.21 us>
RND 4KiB (Q= 1, T= 1): 72.861 MB/s [ 17788.3 IOPS] < 55.76 us>

Profile: Default
Test: 1 GiB (x5) [C: 37% (42/111GiB)]
Mode: [Admin]
Time: Measure 5 sec / Interval 5 sec
Date: 2021/04/12 18:12:30
OS: Windows 10 Professional [10.0 Build 19042] (x64)

- - - Updated - - -

I've had this computer (HP Compaq 6005 with an AMD Phenom II X4 B95 Processor and 16GB of RAM) for 6 years now, and it is still the little engine that could. Currently, it is a triple boot system with Windows 7, Windows 10, and Ubuntu 18.04. Recently, I discovered this same issue of black screen on wake from sleep, which was occurring in all 3 operating systems.

Frankly, this seems like an issue with the on-board graphics adapter - ATI/AMD Radeon HD 4200. The issue started happening to me recently when I removed the PCI Express graphics card (AMD/ATI [Turks] Radeon HD 7570) and switched to the built-in DisplayPort output. When I put the computer into Suspend state (not Hibernate) and then tried to wake it using the keyboard, mouse, or power button, it would seem to wake up and come back online, but the Stand-By light would also continue to blink and the screen would remain black. I could not figure out how to resolve this issue using the BIOS setup or graphics drivers. Indeed, it was not even clear if this was a graphics driver issue since it happens on Linux too, and the display otherwise operates fine at its maximum supported resolution of 2560 x 1440. Whatever the reason, it all went away when I re-installed the original PCI Express graphics card.

There are a lot of proposed solutions in this forum, but I don't get the sense that any of them have actually hit the nail on the head as to what is actually causing this issue. The issue was also very disturbing to me because using the on-board graphics also caused me some serious problems in Windows 7 that made it basically unusable for mysterious reasons, but that's another story and it also went away as soon as the graphics card returned.

If anyone has any further updates on what causes this issue and how to correct it (or what to look for in order to fix it), please post.