this happens mainly when the system has been put to sleep for a longer period of time (ie overnight).....no matter what i press it won't resume from sleep. the power button is blinking like its in sleep mode, but the keyboard does nothing. the one thing i find odd is when i hit the spacebar i can see the LED lights on my razer mamba charging station flicker as if its sending a signal. (both mouse and keyboard are connected to usb 2 ports; no usb 3 ports are in use at this time) moving the mouse also does not resume the system at this point. the only thing i can do is switch the power off at the psu and turn it back on, then start it normally, which does not result in a windows error. this just seems very odd to me. any help would be appreciated. thanks. im using the latest 1003 bios.
![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Crosshair V sleep issue....
- Thread starter Rogue71
- Start date
Go Advanced>APM and enable wake by USB etc and see if that allows the system to resume from your mouse or keyboard. Also try the on-board power switch and see if the board resumes if you press that instead of the power button on the case.
-Raja
-Raja
Go Advanced>APM and enable wake by USB etc and see if that allows the system to resume from your mouse or keyboard. Also try the on-board power switch and see if the board resumes if you press that instead of the power button on the case.
-Raja
thanks for the response raja, however, there are no choices anywhere in the bios that i can find that relate to wake by usb at all. in fact all the usual apm settings im used to seeing (ie power management s1/s3) are not there. if i put my system to sleep i can wake it up after only a min or two with the mouse or kb , but any prolonged time and i cannot wake it up no matter what i press. i did enable a few of the apm options just in case. fyi the bios descriptions for this board kinda suck. some of the terms are not explained properly. the only other change i did to my install was to disable my page file due to my amount of ram and the fact that im using an ssd. i did this on my last system and it worked just fine. i changed it to a small page file this morning and will put my system to sleep for the day while im gone to test that theory, but i do not think that has any bearing on whats going on here. id appreciate any other input.
* after comparing the bios to the manual, it seems that bios 1003 is missing things (ie "usb wakeup device from s3/s4" under the sb usb config)
why would asus release a bios that would take features out without making a note on the download site that states this clearly???
so now im wondering if i should downgrade this bios, and if so, to which number. after seeing all the issues online regarding earlier bios problems i initally upgraded to 1003 hoping i wouldnt have any issues.
Last edited:
so i went ahead and re-enabled the default-sized page file on my C drive. now the system wakes up when i put it to sleep for a long period (at least it did for me today). to my knowledge sleep is supposed to affect the ram not the hard drive...so whats going on?? ive had the page disabled on my last system before this upgrade without issues. i have hybernate disabled....i have a quesion regarding the memory power down feature in the bios. ive never seen this on any other boards. how does this feature affect a system that is put to sleep. if the memory powers down i would think the sleep cycle would be screwed up....
*Update...well i initially set the page file to 1-4 gb. it seemed to be working yesterday, but this morning it did not wake. so now im adjusting the page to 2-8 gb to see if that will work....NOPE 2 days later its random. sometimes it will wake sometiems not. i still feel that this isnt the problem but its the only area in which im getting any kind of result. failing this ill set it back to default size which is a complete waste.
should i just downgrade the bios or keep the 1003?
*Update...well i initially set the page file to 1-4 gb. it seemed to be working yesterday, but this morning it did not wake. so now im adjusting the page to 2-8 gb to see if that will work....NOPE 2 days later its random. sometimes it will wake sometiems not. i still feel that this isnt the problem but its the only area in which im getting any kind of result. failing this ill set it back to default size which is a complete waste.
should i just downgrade the bios or keep the 1003?
Last edited:
*Update...well i initially set the page file to 1-4 gb. it seemed to be working yesterday, but this morning it did not wake. so now im adjusting the page to 2-8 gb to see if that will work....NOPE 2 days later its random. sometimes it will wake sometiems not. i still feel that this isnt the problem but its the only area in which im getting any kind of result. failing this ill set it back to default size which is a complete waste.
should i just downgrade the bios or keep the 1003?
Sounds like some kind of DRAM instability to me. I would slacken all DRAM timings and increas CPU/NB voltage to around 1.25V and see if that helps.
-Raja
Sounds like some kind of DRAM instability to me. I would slacken all DRAM timings and increas CPU/NB voltage to around 1.25V and see if that helps.
-Raja
the page file isnt it. i finally just set it back to default and let the system handle it. seems every second or so time i put it to sleep for a long time it doesnt want to wake up. when i do restart the machine it sometimes goes to black screen and hangs.then i have to reset again and it loads fine.
i had a mild overclock on the sytem as well and ive set it back to stock just to see what happens.
i memtested the memory all the way thorugh a full cycle when i got the system. ive had issues with bad ram sticks in the past that cause headaches. i also did prime95 and occt testing (at stock and o/c) to ensure my speeds were stable...the ram is at stock speeds. i haven't had any other system performance issues or glitches at all. ill see how it runs for a few days and report back.
ram in my system is:
G.Skill F3-12800CL9Q-16GBXL. i set the spec timings, 9-9-9-24 and voltage is auto at 1.5v
the bios default timings were different when set to auto. if it were a dram instability issue i would think i would be having other issues, but who knows. if the current settings do not rectify the problem i will change the dram timings back to auto and see what happens.
what does the "memory power down" feature in the bios do exactly?
what does the "memory power down" feature in the bios do exactly?
Pretty much what is says, don't have the board in front of me right now but it's liekly either to be related to low power states (C1 etc) or used for hibernation modes. Leave it at default.
Back to the S3 situation:
If the memory is even slightly unstable, S3 will show it (Prime and Memtest won't always catch every type of error - really depends on the pattern). When the system resumes all of the data written to DRAM will be read back for the restore and if there is any corruption due to a mis-read the resume will fail. To rule some of that out I would at least set Command Rate 2T, Read to Read and Write to Write at 7 clocks and finally overvolt CPU/NB to around 1.25V.
-Raja
Pretty much what is says, don't have the board in front of me right now but it's liekly either to be related to low power states (C1 etc) or used for hibernation modes. Leave it at default.
Back to the S3 situation:
If the memory is even slightly unstable, S3 will show it (Prime and Memtest won't always catch every type of error - really depends on the pattern). When the system resumes all of the data written to DRAM will be read back for the restore and if there is any corruption due to a mis-read the resume will fail. To rule some of that out I would at least set Command Rate 2T, Read to Read and Write to Write at 7 clocks and finally overvolt CPU/NB to around 1.25V.
-Raja
alright. since my settings last night didnt work, i will try your ideas with the ram. i set ram timings back to auto with are 11-11-11-28, instead of the spec 9-9-9-24. ill also adjust the settings u suggested and see what happens. thanks.
seems when i attempted to just restart my system to implement your changes it hung at boot with a black screen. took me 2 restarts to get it going....so maybe this isnt directly related to a sleep issue...i dunno. ok settings i have changed are:
command rate 2T (was same when set to auto)
read to read delay 7
write to write delay 7
cpu/nb 1.25 (auto was 1.15)
also enabled s3 video repost
will update.
UPDATE: unfortunately these settings did not change the problem. i got home this afternoon and it did wake up, but i put it to sleep for a few hours this evening and again it did not want to wake up via keyboard. it seems to be about every second time i put it to sleep for any long amount of time it doesnt wanna wake up. this is weird....
Last edited:
Pull tow of the memory modules and re-try.
Also, do you have the latest FW on your SSD?
-Raja
i just checked this. yes i have the lastest firmware on the ssd. when going to the corsair forums i was delighted to see people having similar issues relating tothe ssd....but the firmware that apparently fixes those issues i already have. also, the workaround they gave specified disabling the "quick boot" function. this function has been on every single board ive ever owned.....but of course not on this one with bios 1003. i also tried the settings posted on the gskill website regarding settings for amd boards and my memory kit, but these settings seem to also have no effect. so now im back to square one......
although im really not believing its a ram issue....i picked up another pack of ram today (Corsair Vengeance CMZ16GX3M4A1600C9) thats on the QVL list. ill try that out and see what happens.
Last edited:
well im not sure why, but this new ram seems to have solved the problem. ive put the systemto sleep 3 times and ive been able to wake it each time. the only setting that i can see that is different in the bios is that "memory power down" is now disabled. this ram uses exactly the same settings as the ripjaws, and ive seen many people online using the gskill, so im not sure what the problem is with this set. either there is a setting i cant see that was changed by the corsair memory, this set is just picky, or the memory powerdown setting was the culprit all along.
got a store credit for the gskill so im happy. system still working great.
got a store credit for the gskill so im happy. system still working great.
Last edited: