HighhBrid and anyone else new to this:
Something that I have found that speeds up my determining a vCore for a particular level is using Prime95, Asus AI Suite II, and Windows Event viewer (just click on the start button, and type "event" and you will see it). I have had this procedure identify a vCore as unstable in less than 5 minutes while the same vCore took a standard Prime95 run 5 hours to get a stopped worker.
This might be common knowledge, or me simply being mistaken about something, but it should be useful to people who are brand new at this. Especially those who don't take the time to read everything - and we know there are those out there.
This procedure is done with Prime95 doing a torture test, click custom, and change the Max FFT size number from the default 4096 to 8 (so both the min and max are 8 now). Then type in 90% of your available ram as usual in the memory box. This will do the 800000 tests that run up your temps to near the max you will see in all of prime testing, therefore you get an idea of your max temps at that vCore level in just a few minutes. It is also the test that tends to knock out a lot of my vCores, but if you go through the normal prime testing is takes about 15 minutes to get there.
Have Window Event Viewer open to Custom Views->Administrative Events. This window will not refresh itself, but you can click on Action->Refresh. While you are testing, if an error or warning happens, the window will not update automatically but you will see a "(!)New events Available" just to the right of where it tells you the number of events in your window. Click to refresh the window and if it is a Warning for a WHEA-Logger then stop the Prime95 test. Even if Prime95 is still running fine, just stop the test and move on.
Go to Asus AI Suite click on the Tool button, choose TurboV, and click Manual Mode. Here you can click on CPU Voltage and up your vCore one click, meaning you add .005 to it. Click the Apply button below it, then Yes to the warning box. These changes do not permanently change BIOS but they are active in your current session of windows. This way you save all the time and trouble of restarting, going into BIOS, making the change, hitting f10 to save it, and then waiting for windows to start again.
Go back and do the Prime95 testing with 8 min and max again just like the first time, and wait to see if you get any new WHEA warnings. If you do, then stop Prime95, add one click to vCore and repeat the process. If you make it about 15 minutes with no warnings, then you can restart your machine, go into bios and type in that vCore which had no warnings, then proceed to do a regular Prime95 test as the guide suggests and see if you make it 12 hours. Keep looking for WHEA warnings while doing the Pime95 testing as outlined in the guide also, many times they show up long before Prime95 gets a stopped worker.
Obviously this only works when your machine has minor instabilities at the level you are testing. If you have freezes, BSOD, or serious instability then you will have to restart to BIOS. This usually means you are not terribly close to the vCore you need for stability.
Also some people may not install all the motherboard programs and drivers, but you should get Asus Boot Setting, it lets you click a button and your computer automatically restarts and goes directly to BIOS - it is a convenient time saver.
Hope that help someone out there.