Locking up when returning to computer after idle
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=8605
Printed Date: 03 Jan 2025 at 2:13am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Locking up when returning to computer after idle
Posted By: JayB33
Subject: Locking up when returning to computer after idle
Date Posted: 05 May 2018 at 11:03am
|
I've had a couple of issues where the computer's been left on the desktop for a while (long enough for the the screen to go into standby) but then when I've returned to it, it locks up. On one occasion the mouse cursor and performance in general went into an unrecoverable stutter; the computer was virtually unusable in that state but a quick reset brought it back to normal. Another time when I logged a user out after returning to the computer, the screen went black as it normally does before returning to the login screen, but then it never came back on again even after I turned the monitor off and on. I have no power saving features enabled on my CPU, except core parking. All cores are forced to 4.0 GHz @ 1.26v. 98.5% of the time (or so) I can return to the computer and continue using it fine. My specs are: ThermalTake View 71 TG RGB Case Seasonic Prime Titanium 850W Power Supply Unit ASRock X399 Fatal1ty Professional Gaming Motherboard AMD Ryzen Threadripper 1950X CPU nVidia GeForce GTX 1080 GPU TXD416G3600HC18ADC01 - 4x RAM Modules Samsung 960 Pro - 3x 512 GB NVMe Drives Samsung 950 Pro - 512 GB SSD Samsung 940 Pro - 256 GB SSD Crucial M4 - 256 GB SSD XSPC Raystorm Neo (AMD sTR4) Chrome CPU Waterblock AquaComputer Kryographics 1080 Nickel GPU Waterblock Hardware Labs Black Ice Nemesis GTS 420 Radiator Noctua NF-A14 IndustrialPPC 2000 RPM IP67 PWM 140mm - 3x Radiator Fans ThermalTake Riing 14 RGB - 3x Case Fans XSPC Photon D5 270 Reservoir AquaComputer D5 Pump Motor AquaComputer Aquaero 6 LT Fan Controller Mayhems XT-1 UV Green Coolant Mayhems Ultra Clear 16 / 10 Tubing Bitspower Black Sparkle 16 / 10 Fittings EK-AF Black Nickel 10MM Ball Valve Schiit Audio Modi DAC Schiit Audio Magni Headphone Amplifier Schiit Audio Loki Hardware Equalizer Beyerdynamic DT 880 Pro Headphones Dali Zensor 1 Speakers Amptastic Mini 1 Speaker Amplifier Atacama SL600 Speaker Stands Das Keyboard 4 Professional Mechanical Keyboard Steelseries Rival 300 Mouse Steelseries Dex Mouse Mat |
Replies:
Posted By: wardog
Date Posted: 05 May 2018 at 11:25am
|
" rel="nofollow - Nice Rig! THANK YOU for the hardware list on the first post. The Team memory p/n is a 2x8GB Kit, so two of those kits. Two things I'll ask 1. As a test, lower it to stock and post if it behaves the way described. 2. Go to http://www.softnology.biz/files.html and install the Freeware, then post screen captures from within Thaiphoon itself using the internal Screengrab function. Do this for all 44 sticks, the post links here please 2a. While I'm thinking of it, latest 2.00 BIOS flashed? If not, lower it to stock FIRST, then use the Instant Flash method. NEVER flash using a Windows based flasher. I'm guessing by the hardware you know all this, but if not post back and I'll guide you. |
Posted By: JayB33
Date Posted: 05 May 2018 at 12:01pm
|
Thanks for responding. I'm on BIOS 2.0. There's no easy way to recreate the issue because it happens so infrequently, and I really want to leave it in overclocked mode. I know you want to rule out any overclocking, but the default clocks are so conservative that I really can't stand leaving them like that even for general use, and I'm certain that my current settings are stable. Of course, if my issue occurs a massive amount in the future, then I will immediately oblige. Here are the Thaiphoon screenshots you requested:     More stuff:   |
Posted By: wardog
Date Posted: 05 May 2018 at 12:41pm
|
" rel="nofollow - Cool. All mem is alike and same Week. How infrequent are we talking here? 1.26v. Did you take it to 4.0 and then work/test it to lower it at 1.26v? 1.26 is on the tight side IMO, from what I've learned on TR. Not tight tight, but ....... And you ARE running the Extreme Presets in RDC? . |
Posted By: JayB33
Date Posted: 05 May 2018 at 1:13pm
|
I tried 1.26v after reading about someone who got 4GHz @ 1.225v or so on a forum thread and it seemed stable after prime 95 testing. I then played a lot of games and it didn't crash then either. The lockups after resuming are a very rare occurance, in fact I have only had one unrecoverable stutter after bringing the monitor out of standby and one black screen after logging a user out (the hard drive lights seemed to still be responding). I have owned the computer since Jan and must've entered standby mode hundreds of times. I realise those two lockups could be described as an anomaly, but in my experience they tend to repeat themselves eventually in computing, so I was wondering if it could be a motherboard firmware glitch. I'm using the fast preset. The Extreme preset was disabled as an upcoming feature in the version of Ryzen Calculator I used to generate the memory settings. |
Posted By: JayB33
Date Posted: 05 May 2018 at 6:00pm
Saw this in patch notes of:GeForce Hotfix Driver Version 397.55- Windows 10: Driver may get removed after PC has been left idle for an extended period of time. Looks like the black screen issue may be solved. Still don't have a clue what the stutter was. |
Posted By: datonyb
Date Posted: 05 May 2018 at 8:01pm
|
" rel="nofollow - i would agree with wardog the voltage does seem tobe on the low side maybe its causing the intermitent issue from resuming from the sleep state to a lowish voltage ? ------------- [url=https://valid.x86.fr/jpg250]  [/url]3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
Posted By: chubalz
Date Posted: 05 May 2018 at 9:00pm
|
Ryzen Threadripper 1.26v on a 4ghz is way impossible. Even my Ryzen 5 1.3375v only 3.8ghz. ------------- Ryzen 5 1600 3.80ghz @1.3375v Asrock X370 Gaming X 5.20 Bios CM MA610P Aorus Xtreme Gtx1080ti Gskill Trident Z RGB F4-300016D-16GTZR @2800mhz SamsungEvo 250 2Tb Firecuda 1Tb WDBlack Corsair RM650X |
Posted By: datonyb
Date Posted: 06 May 2018 at 12:05am
well it cant be impossible ,as hes doing it but it may be the reason its locking when transitioning out of sleep mode i would adjust it up myself and test it for a while maybe at least 1.3 volts i can do 3.9 ghz at 1.3 volts with my 1700 but upped the voltage a little to rule out instability with higher clocked ram ------------- [url=https://valid.x86.fr/jpg250] [/url]3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
chubalz wrote:Posted By: chubalz
Date Posted: 06 May 2018 at 12:40am
|
I think the problem is stability. Nvidia previous driver issue is only Gtx 1060, he is using Gtx 1080. Updating to latest driver will not fix his idle lockups. And you are right the cpu voltage must be increase for stability.
------------- Ryzen 5 1600 3.80ghz @1.3375v Asrock X370 Gaming X 5.20 Bios CM MA610P Aorus Xtreme Gtx1080ti Gskill Trident Z RGB F4-300016D-16GTZR @2800mhz SamsungEvo 250 2Tb Firecuda 1Tb WDBlack Corsair RM650X |
Posted By: JayB33
Date Posted: 06 May 2018 at 2:40am
The thing is Threadripper has been speed binned by AMD. Apparently only the top 5% of dies make it to retail (could be higher for the 1950x), so you have a much higher chance of a golden sample and the CPU being fine at lower voltage. I can't get the motherboard to post at 4.2 GHz even at 1.35v though if that makes you happy. :P |
Posted By: chubalz
Date Posted: 06 May 2018 at 3:12am
|
" rel="nofollow - Why not give a try increase voltage? so we can rule out the problem its not the voltage. Or make it stock default settings. ok? ------------- Ryzen 5 1600 3.80ghz @1.3375v Asrock X370 Gaming X 5.20 Bios CM MA610P Aorus Xtreme Gtx1080ti Gskill Trident Z RGB F4-300016D-16GTZR @2800mhz SamsungEvo 250 2Tb Firecuda 1Tb WDBlack Corsair RM650X |
Posted By: JayB33
Date Posted: 06 May 2018 at 7:24am
|
I will increase voltage if it happens again, but it doesn't happen very often. |