Printable View
You got that right. From my experience SB needs at least 1V at idle to not BSOD randomly and you'll have it with proper LLC level and a little higher load Vcore. And reading about the idle BSODs with high fixed Vcore makes me believe it doesn't like that as well.
I did not begin with overclocking waiting till I get my new revised B3 board, I'm just at 3.8Ghz HT on, LLC regular, speedstep, c-states...all enable with offset -0.15 with bios ver.1305. My voltages are
IDLE=0,82 / LOAD 1C=1,056/1,064 / LOAD 8C Lynx&SmallFFT=1,096 / LOAD 8C Blend=1,104/1,112
No problems at idle, low or heavy load, prime and linx stable... didn't try any lower yet.
Regards
you r right. i think stasio or sin remarked that SB should not go underQuote:
Originally Posted by nijel
1V@idle. i am using also offset with c1 etc.. and have no problems so far ( no BSODīs, no freeze, no reboots) and go up with the blck until 105. so i think the board and SB are :up:
I do suspect that there might be an issue with the USB ports because the freeze occurs more often when my mp3 Walkman is hooked up, or when the printer is on. However, I cannot confirm this at this time IMO.Quote:
Originally Posted by chawks2
So how did you solve this? Changed the MB?
I still got trouble with my P8P67 WS Revolution board.
Getting nvlddmkm.sys stopped responding error whenever I decide to run 3DMARK Vantage. Gone through a Zotac GTX 480 AMP!, ASUS GTX 580 DirectCU II, 9600GT. Everything is kept @ stock.
For fun I tried a Radeon x600, and it works without any problems.
This problem only appears in Windows 7. Iīve installed Vista to see if the same error appears, but it works 100%. Could it be a driver issue of some kind?
If I turn Aero on and run some harddrive benchmarks, I will see that nvlddmkm.sys stopped responding...
Anyone?
I would not call it solved, but more of a workaround. I just moved the USB devices I have connected all the time to the USB3 controller. Since then, I have not experienced a lockup/BSOD, if you review the MEMORY.DMP file there was mention of the USB controller with one hairy looking BSOD code.Quote:
Originally Posted by ghmz
I have yet to bring this to the attn of the ASUS tech staff, but it certainly looks like a driver/legacy USB controller issue.
Whats your motherboard temps? I get around 38c idle @ motherboard. Around 50c load... seems abit high? Its a P8P67 WS Revolution.
That's interesting, I found to have more crashes when using Winamp and my external DAC, connected via an USB/SPDIF interface.Quote:
Originally Posted by chawks2
Maybe a USB failure. But I had BSOD when idling and doing nothing else than running windows 7, with windows sounds off, so it's not necessarily a USB issue.
As far as Asrock boards are concerned, it's an ASUS brand so I won't be surprised if the design in any of its form has to deal with these ASUS P67 issues.
Normal that those using offset modes and C states may have stable systems as their idling specs won't be the same as others who keep full speed at idle like I do. I won't use EIST and the rest because the board is buggish and vdroop too much when idling on one or two cores causing BSOD, or something like that. If Gigabyte boards doesn't have this issue then there's a flaw in ASUS design like there has already been on their previous boards before and that's all.
Yeah I've never had a BSOD at idle or a random freeze, not once on this system. This is on a GB UD5.
Besides the normal BIOS issues (many of which were resolved), this system has been as stable as my P5WDH system was.
I dont think any GB users are having the random bsod/freeze, except some when using offsets. So this may be mostly some Asus issue.
Only BSOD I ever had that wasn't caused by way too low vcore while starting windows, or priming/gaming at high overclock at too low vcore, was halokx2k.sys or somethinig (X-fi), and those were to a faulty driver (known issue, which was fixed in an update), and aother ha10kx2k bsod I got was due to Ventrilo constantly triggering the Dolby Digital Live activation and my voice recording suddenly not working, then when I started Crossfire (FPS game), x-trap triggerd ha10kx2k bsod (oddly enough it was xtrap that triggered it with the faulty sound driver too)
Unfortunately, I had the BSOD when not using the devices also. It would occur in the 1-3 day time range, after moving to the USB3 controller, I am on 6 days of no BSOD. :up:Quote:
Originally Posted by Pacha
Again, my solution is a workaround, NO consumer should EVER have to deal with these types of problems NOR should they have to move devices to a different controller to obtain stability. I will do more research and submit my findings to ASUS, I'm hoping the USB issue is driver related, or else this baby is going back to ASUS.:shakes:
Totally agree with that.Quote:
Originally Posted by chawks2
BTW, if you are using vcore manual mode try LLC extreme and VCCIO 1.1875V, that made me reach 6 days without BSOD while 1-3 days before.
Now I'm trying 4.5GHz instead of 4.6 to limit BSOD, and it looks like it's working, with high vcore (1.38V), while I'm LynX and Prime stable at 4.7 1.375V without problem and possibly higher. ASUS Extreme overclocking board probably, extreme stability though... :rolleyes:
After many C2D boards burnt for a lot of guys (between 1-5 per person on french oc board OCM), my Commando which burnt also after a few days at stock specs, then next one which had the same problems as these P67 boards and needed vmods, then burnt at least 10 different kits of RAM even at stock specs with correct vmem at multimeter, and now random BSOD/reboot issue with the P8P67, these haven't been named ASUX for nothing a few years ago. Good definition of their old slogan "ASUS, Rock Solid" :D
I think I'm going Gigabyte next time.
Got my B3 deluxe today , got from 1.355v to 1.35v at 4.8ghz .
Excellent board .
Sorry but... lawl!Quote:
Originally Posted by dany74q
That's basically no significant difference at all... :s
Sounds good to me! My 2600K requires more volts than that at 4.8. I use about 1.344 for 4.6...
True , though I had`nt anticipated any major change whatsoever, other than the SATA issue being fixed the board is identical .Quote:
Originally Posted by tentp0le
No complains really , am just glad that I hav`nt received a worse board..
Is it possible to change PCI-Express link width from 16x to 8x manually? Tried a P8P67 Deluxe board with my GTX 580 in 16x slot, and get nvlddmkm error. But when I put it in the 8x slot I get no errors...
My board is a P8P67 WS Revolution.
Try to plug a molex in the motherboard for extra juice pci-e.Quote:
Originally Posted by Darkstormz
Already done that, without any success... :down:Quote:
Originally Posted by Bullu$
Too bad...
Is it possible to change the mem-timings in windows 7 with asus software? Try to find it but seems like there is no.
Unfortunately I don't believe there is any way to do that considering MemSet/CPUTweaker has not been/will not be updated for Sandy Bridge.Quote:
Originally Posted by Bullu$
By any chance does anyone know if it's better to have a set vcore or use the offset?
Do you need to pump high voltage 24/7 to the CPU?
If yes go fixed, otherwise go offset.
How high is high? Roughly 1.5v for 5.2ghz is what I'm at right now.Quote:
Originally Posted by nijel
Offset saves you the most power in the long run because it drops vCore when idling (it could probably be good for the chip, since it will run most of the time at ~1V instead of 1.3-1.4V). It is quite a bit harder to work with though: making sure the vCore while idling/loading a single core isn't too low to keep stability can be a bit challenging. In the end if you can get good results with offset stick with it, otherwise don't waste too much time and go for fixed.Quote:
Originally Posted by aznsniper911
Exactly.
It's not that hard to find the proper LLC level + offset which will give you stable 0-100% load Vcore. Testing 1 thread LinX first and 4 threads after that is the key. Wouldn't say it's waste of time especially if 1.5V is your goal for 24/7.
BTW as I see it SB BSODs quite often in idle/low load with high fixed Vcore as well.