Screen can't come back from sleep

[secretliar]

Hi!

I have an issue with my new build :

Screen can go to sleep without any issue.

But the screen can't come back from sleep. Its turning on then going back to sleep, then turning on, then sleep again etc.

I can hear connection/disconnection sound of Windows indefinitely.

The only way I can gain access to computer is by pushing reset button 🙁


- Playing with the cable doesn't change anything.
- Screen is fine on a Intel build :/

Clean install of Windows 10 Pro on new build :

AMD Ryzen 5 2400 G (GPU drivers : 23.20.827.0 / 17.40.3701-feb12)

Asrock AB350M Pro4 (Chipset drivers : 18.10_feb )

HP Display 27er (drivers 1.0.0.0)



I don't know what to do :/

I tried reinstalling drivers but it's not working.
I don't know where to download previous drivers of chipset and you (in case that's a bug with latest only)

 

[drbones8472]

Turn off the ability for Windows to even go to sleep. Go to Power Settings and then go into Advanced and turn off everything in there that has anything to do with putting the PC to sleep or putting the Monitor to sleep.

 

[ko888]

Is the motherboard's BIOS up to date (i.e. Version 4.7)?

AMD ALL in 1 with VGA driver ver:17.40.3301 is available on ASRock's website.

http://www.asrock.com/mb/AMD/AB350M%20Pro4/index.asp#Download

 

[secretliar]

@drbones8472 : terrible answer

@ko888
BIOS is up to date.
I'll try these drivers

As the screen can be turned on at startup and is working on other PCs, should I worry about the CPU or MB? or should it be just a driver issue?

Thanks!

 

[ko888]

It would be the Raven Ridge APU that should be waking up your display panel. The APU's device driver may still have bugs in it.

 

[secretliar]

Thanks, so for now, no worry about the APU itself, just the drivers?

 

[ko888]

Thanks, so for now, no worry about the APU itself, just the drivers?

The APU itself should be fine. It may take a little time for AMD to work out all the bugs in their drivers.

 

[secretliar]

Thanks!

I tried the old drivers.

It's definetely a driver issue.

I still can hear the connect/disconnect sound cycle but the screen eventually turn on (which is wayyy better than press reset)

I hope a new driver is on the way to adress this issue