Do you have any of your boot drives on the Marvell controller?
-Raja
No. I have the Marvell controller disabled
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.
Do you have any of your boot drives on the Marvell controller?
-Raja
I am having the same issues here. Just yesterday, I completely wiped my system, upgraded the BIOS to 1801 (after trying 1606 and 1702) and reinstalled Windows 7 SP1 with the latest drivers for everything, leaving the BIOS options at their defaults in an attempt to get sleep working.
Won't wake from sleep after 15-20 minutes.
Manually disabled PLL Overvoltage (previously I had been doing this anyway) won't wake from sleep.
Manually enabled S3 etc. (as it was previously set to) still won't wake up.
In 1502, the machine would power on, but never boot, and required me to do a cold boot to start up. (power off & on, rather than reset)
Now, in 1801 when waking from sleep, the power comes on for a second and then cuts out.
My system is a Sabertooth P67 (my second B3 board, after the first wouldn't up the CPU multiplier from 16x regardless of load or BIOS config) with a 2500K and 2x4GB Corsair RAM and a GTX570. Currently, while trying to sort out these sleep issues, it is not overclocked, but I was running it at 4.5GHz with PLL Overvoltage disabled previously. (system was 100% stable after extensive testing)
There are seven SATA devices connected up to my system, so I can't disable the Marvell controller, but it isn't booting off a drive connected to that.
The DRAM Data REF or Ctrl REF options do not seem to be there on the Sabertooth board.
No. I have the Marvell controller disabled
I'm not familiar with AIDA 64, but have downloaded the trial. What kind of report do you need?I need a full drivers list - possibly an AIDA 64 report if you can provide one please.
It's on the ASUS FTP: ftp://ftp.asus.com.tw/pub/ASUS/mb/LGA1155/SABERTOOTH_P67/The 18** BIOSes have leaked out from somewhere and should not have. Generally speaking when BIOSes are ready for users to flash en masse they are passed to me with the fix list and instructions. I then put them up on the forum.
Can you tell me where you downloaded this BIOS from please?
I'm not familiar with AIDA 64, but have downloaded the trial. What kind of report do you need?
It's on the ASUS FTP: ftp://ftp.asus.com.tw/pub/ASUS/mb/LGA1155/SABERTOOTH_P67/
Sorry, didn't understand that much. With 1.5v for CPU PLL everything runs smooth, burning programms run without any errors. I just thought lower is better like for vcore...Any particular reason you have 1.50V set for PLL?
This will impact downstream sampling margins and possibly affect the signal eye size on this architecture (it isn't like LGA 1366 and 1156 inmplementations). Do you still need to offset the DQ and CMD/CTRL reference with PLL set to default?
-Raja
Sorry, didn't understand that much. With 1.5v for CPU PLL everything runs smooth, burning programms run without any errors. I just thought lower is better like for vcore...
Should I raise it to it's default ?
May I ask a little off topic question ? On P8Z68-V Pro what's the difference between the red and black USB 2.0 ports ? They are all connected to Intel controller right ? Is there any technical difference ?
Ok can you get me an AIDA 64 report please?
-Raja
Oh, ok. I did try many times at auto or 1.8v manualy set. Sometimes it works, sometimes not. The only way to get it working 100% of times is to set those offsets.You should use PLL at default on this architecture - the clocking limitations of this architecture are very bound to the right PLL voltage level (hence the internal PLL OV option working the way it does). I think the reason you are having to offset the DQ and CMD refs is to compensate for any timing mismatch caused in the clock distribution network within the CPU due to a low PLL voltage.
So yes, try default of 1.8V for PLL and see if you still need DQ and CMD ref offset for S3 resume.
-Raja
Sorry for the delay. Because I was trying various drivers and options, and had installed a few other things unrelated to this, I ended up wiping the machine again today and starting fresh.Ok cool, the full report please. This will show us all drivers etc and hardware you are using.
-Raja
Could be a weak memory controller then I suppose. It's certainly not normal to need to offset those voltages for S3 at stock.
-Raja
Ok can you get me an AIDA 64 report please?
-Raja
find which USB port its on and set it to reset on resume, that should fix it. Had the same problem with my BT mxrevolution mouse
http://technet.microsoft.com/en-us/library/cc947756(WS.10).aspx
thats the quick explanation and a link to the reg key
Here's another shall we say "interesting" MS hotfix for S3 resume where the result is no response/display:
http://support.microsoft.com/kb/2410477
Might be worth people checking this out if experiencing these symptoms.
-Raja
id be concerned id they werent. HID=Human Interface Device
http://technet.microsoft.com/en-us/library/cc947756(WS.10).aspx
thats the quick explanation and a link to the reg key
Raja, what's your take on this?
I have a P8P67Dlx B3 board. It does not resume from Sleep. Tried all the listed solutions including all the listed BIOS.
Bought a P8Z68v pro. Same hardware. Same OS, I just let Windows7 update the drivers and S3 is working fine.
Should I RMA the P8P67Dlx B3?
Tks,
Pierre
I realise that it is a sample size of one, but this seems to give credence to the idea that the P67 hardware is fundamentally flawed if a straight swap for a Z68 board fixed things.If you're using the latest BIOSes on both boards then you can try and RMA.
-Raja
Raja, what's your take on this?
I have a P8P67Dlx B3 board. It does not resume from Sleep. Tried all the listed solutions including all the listed BIOS.
Bought a P8Z68v pro. Same hardware. Same OS, I just let Windows7 update the drivers and S3 is working fine.
Should I RMA the P8P67Dlx B3?
Tks,
Pierre
I realise that it is a sample size of one, but this seems to give credence to the idea that the P67 hardware is fundamentally flawed if a straight swap for a Z68 board fixed things.
Can you give us any details on what is being done to resolve the sleep issues with the P67 boards?
You asked for an AIDA64 report of my system last week, but I am not convinced that this is a software/driver issue at all, especially as the 1702/1801 BIOSes have made this worse in my system. (now powers off immediately, rather than hanging upon waking)
These issues have been around for months now—if they cannot be resolved, the board is unfit for use as far as I am concerned, and I still have problems with SATA drive access hanging for 30+ seconds at a time. (Intel or Marvell ports, happened on both my Sabertooth boards)