AMD Motherboards - x399 taichi broken sleep W10

Print Page | Close Window

x399 taichi broken sleep W10

Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=6178
Printed Date: 26 Dec 2024 at 11:07am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: x399 taichi broken sleep W10

Posted By: TANWare
Subject: x399 taichi broken sleep W10
Date Posted: 24 Sep 2017 at 11:02am

I just built my system. Have it running at boot 4.0 GHz @1.3750 on a 1950x. W10 Pro installed but there is an issue with sleep.

At boot R15 = 3462 with no issue. If I sleep on waking I get R15 =2993. Cpuz , hwmonitor show the overclocks all holding. CPU not overclocked I get on boot R15=3025 and after sleep R15=3025 so no change.

I should note XMP is 3466 in both cases.

Replies:

Posted By: TANWare
Date Posted: 25 Sep 2017 at 11:51pm

" rel="nofollow - Did support see this? I posted here so others if they have the issue can post too.

Posted By: MisterJ
Date Posted: 26 Sep 2017 at 1:27am

" rel="nofollow - TANWare, a user with ID ASRock_TSD posts here sometime, but doubt support has seen your post. If you want support, I suggest you open a ticket. Almost everyone here, including moderators, are users not ASRock people.
Do you have the latest AMD chip set drivers DLed from here?: http://support.amd.com/en-us/download
If not please DL and install them. They contain the latest Sleep mode support. Enjoy, John.

-------------
Fat1 X399 Pro Gaming, TR 1950X, RAID0 3xSamsung SSD 960 EVO, G.SKILL FlareX F4-3200C14Q-32GFX, Win 10 x64 Pro, Enermx Platimax 850, Enermx Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 2.00, 2xHDDs WD

Posted By: TANWare
Date Posted: 26 Sep 2017 at 1:59am

Thanks, I updated the drivers. While it did not fix the sleep issue it does make the system a sight bit more table in the results of R15. I was hoping others had seen the same behavior, so even if a ticket needs posting there is a history of it being an issue and not just repeatable here.