and here I am 3 years later solving the same issue thanks to you guys. I followed ThisKory99 summarized tutorial and it worked like a charm. I just used another bootable usb tool as the original link was dead but no biggie, those tools are common. Now my RAM works great again, I can overclock...
Just upping this wonderful thread to thank CodeRush.
This weekend out of nowhere after 5 years of flawless service, my P8Z68-V Pro / i5 2500k started to behave oddly. I suddenly lost my H24 5years overclock and the BIOS detected only 8GB of the 12 I have installed. The UEFI still was showink...
I can't wait to have my mouse and keyboard working under the UEFI... maybe better changing them ... would be quicker I guess hehe. no offense. this is the thing that bothers me most with the wrong CPU temp reading.
IMHO, it causes more troubles than anything. why the hell bothering for those max 3% final overclock?
I tried Autotuning and he was NEVER able to get anything more that a series of blue screens. Even when I got the "successfull" message, it just BSOD 2 seconds after.
What did I do after...
Raja, do you know if there is an hidden option somewhere that prohibits the autotuning and TPU to touch BCLK when trying the highest overclockt possible? thx
DO yo have a speaker connected to spkr header? does it beeps ? how?
you can try the following.
- put everything out of the case
- connect CPU+ his heatsink (ensure fam is connected to cpu fan header)
- connect just 2 dimm of ram on A1 and B1(apparently 1 dimm prohibits the board to boot)...
Did you do a Memtest? Did you verify that your heatsink is mounted correctly? What temp do you have? You should also try to mount everything out of your case with the bare minimum components and see if it's stable
That's because ASUS changed the temperature reading source to the package one (that's their justification on ASUS forums)... Anyway this is still wrong ... Any air cooling CPU temp can go bellow case temp.
Nothing really. Just the assurance that my deduction skills are not that off. I've build Rigs for 15 years now and most of the issues I got always have been due to silly stuff I made, bad connections, dust in connections etc... Never with bad components. That's a lesson learnt, always test your...
He certainly connected the screen to the incorrect plug iGPU when dGPU was chosen into the bios ... So at post the system initialize the wrong adapter and it's just until windows that things correct themselves... I'm taking a bet on this one!