Locking up computer - CPU Vcore experiencing massive fluctuation(33%)

Go back to square one- don;t overclock and set the computer up as such making sure you are using a proper memory voltage for the memory - running 1.5v memory at 1.65v will surely not work. Then if you want to overclock, read up on it and as mentioned - don't use auto overclocking. Most voltages are OK left on their auto setting, but some are not - especially memory voltage and Vcore. I was using ta 1600MHz profile from my memory which specified 1.6v, had the memory voltage set to auto, and my MB set it to 1.7v! For Vcore use a voltage offset - that will increment it above or below the VID for the chip and is the best way to manage Vcore IMO. You also need to do overclock incrementally - up it a bit, then run tests for quite some time, up it again if the test succeeds otherwise you need to do some tweaking, etc. It is a slow process, especially if you are new to it.

Those settings are all fine, though it should not be necessary to turn them off if running at stock speeds and voltages. It is often wise to turn at least some of those those off if you are overclocking.

As you pointed out, what is important is he test the system at stock multiplier, stock BLCK (processor frequency), stock Vcore, a valid memory profile and memory voltage. The best and quickest way to test for this level of instability it is to run prime95 with it set to check for roundoff errors with it set to use 75% of the memory.

Cheers

Alright, thanks. I'm trying to run TRULY stock as to get rid of any ASUS overclocking as a culprit. I do think optimized defaults includes an auto-overclock (Turbo mode) as it states it's turbo target is 3800mhz. Who knows what voltages and such they use, could this not be causing the locking up?

Here is an updated list of what I have changed so far after resetting to "optimal defaults":
- Disabled TPU switch on mobo (for auto-overclocking; was off stock)
- Disabled EPU switch on mobo (for power saving; was off stock)
- Disabled Turbo mode (UEFI)
- Changed duty Control/Line-In Calibration up to Extreme/Ultra High respectively as well
- Changed RAM voltage/timings

There is also something called "Ai overclock tuner" which I left at "Auto". The other options were "manual" and "XMP", both of which controlled the BLCK/CPU ratio and the latter which also controlled the RAM profile selection. Now I will take a guess that with turbo mode turned off, this doesn't exactly function anymore anyways. Should I leave this as AUTO or manually set it to 100% ratio?

Had another lock up even with the overclocking completely disabled as described above.

This time something to note: After I rebooted I got a graphical glitch twice that I have gotten a few times before. After it boots past UEFI/BIOS a pixelated image occurs. The pixels were orange, white, green, and one other color, randomly dispersed almost like a messy game of tetris. Interestingly enough, This error occured when booting off the SSD, and also when booting off the thumb stick (was trying to run MemTest)

That is my fault for not mentioning it happened before (forgot until it happened again twice today).

I am using Intel HD graphics now (testing graphics card). I am not using Virtu as I don't need multiple GPU support, however I can hear my video card is still running (fan atleast). Is this normal?
- If this still locks up I will be cloning my OS onto an HDD (testing the SSD).
- If that locks up, I will be trying this HDD on a SATA II port (test SATA III).
- If that doesn't work, I will be taking the computer back to the retailer for them to deal with :). Is that a good plan?

You are right, I will get on that. Thanks!

I returned the video card and have a Radeon 6770 to test in the meantime. The pixelation I spoke of on boot is STILL HAPPENING, but only after I exit the UEFI; it never happens when I boot straight past into the OS. This may as well have been the case with the GTX 580 and this pixelation on boot may be a separate problem altogether. Are errors after exiting UEFI on ASUS boards common? (Happens when booting to different drives as well)