Yes that's fine, every system will be different but by the sounds of things you were taking you're VCore way too low.Hi All,
*SNIP*
Regards
Scott
Use the settings in the first post of the thread as a template. The LLC should be fine at the level recommended. Mine is still set as such.
As for the VCore boot the system with the template VCore and run 10 run of Intel burn test on the highest setting. If no problems occur take the VCore down a notch and repeat until the system crashes either on start-up or when running the burn test. Once you find the point it crashes at bump the VCore back up to the point where it was stable and leave it there for now.
Then later today or tomorrow leave the computer on over night running prime95. Prime95 slowly adjusts to get more and more demanding on the CPU so it should test most possible situations you're CPU will encounter stress wise. If you wake up to a bluescreen persist to bump the VCore up one more.
If other problems persist post back here and I'm sure we can try and help with other settings such as VTT and DRAM voltage. But like said Neil's settings are pretty solid in the first place so it shouldn't come to this
Make sure you monitor the Temperature and VCore while running the tests. I recommend HWmonitor. You don't really want the temp over 70/75c and a VCore no higher than 1.42/1.45v. VCore wise I'm running at 4.40Ghz and get a VCore of 1.31 idle and around 1.36/7 under load so aim around this. Obviously the higher the overclock the higher VCore you will expect so if you are going for a 4.50 or above expect higher
As for running it over night this kind of requires abit of trust but after doing the testing with the burn test before hand it should be ok. The system should shut-down before anything bad happens. If you are paranoid like my self (And a poor student how wouldn't be able to afford another computer). Set your self aside an afternoon and having it running. Boil the kettle and catch up on a TV show or watch a movie. Keep checking back intermittently to make sure you're computer isn't on fire XD
Aha yeah mine used to do this a lot. Bugged the hell out of me and spent a stupidly long time trying to work out what it was. Just bump the VCore up one more and that should do that trick. I had the same error, tried new drivers, format etc etc seeing as it passed benchmarks. Think it's just down to bad power management in low power idle states. Used to happen a lot being idle on YouTube etcMe Again!
I managed to run all night in prime95 and it lasted the full 24hours.
But my machine was just sitting on the desktop and i got a blue screen
Any Ideas
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa8009571028, 0x00000000be200000, 0x000000000005110a). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 102512-8252-01.
Cheers
Scott
This is due to the LLC level you set when following Neil's guide and is perfectly normal, it steps up the VCore when needed to tackle VDroop, this is the alternative to dynamic VCore which will tend to run at a higher VCore that it would if it was set dynamicly but due to the instability of the dynamic VCore on this board it's the one to go withOh your going to fall out with me
I have the CPU VCore set to 1.305 is this right on the pic? why so high?
And again
Cheers Again
Scott
It crashed again I will the voltage again!!
How far show i go?
Cheers
Scott
Hi people, now I know this may be an old thread but I just wanted to join in as I just got this motherboard to replace my Z68AP-D3.
However I have some questions.
After updating the BIOS to U1G, I noticed that I no longer have the LLC option available?
Is there anyway to get this back as I cant seem to find a stable OC without it.
I can't even do 4.5GHz on this with 1.35v without LLC, whereas I can do 4.5GHz with my old Z68AP-D3 with 1.34v with LLC level 6.