Originally Posted by ABAD1DEA
lol i cleaned my cpu today built all together again and then pc didnt boot. LED-Debug 15
i thought my cpu broke and i switched grafic hard over to ivy bridge ect. and now after i cleaned my cpu again it works fine omg.
i dont know maybe it was the cpu or the bios. i lost one day and have to reinstall windows new on haswell pc.
btw. haswell was only working with one RAM slot and one stick. if i put more in #15 on LED poster.
When you delid the CPU are you putting the IHD back on after replacing the TIM? If not you need to make sure the CPU is being seated evenly, if not you will get memory slots not working b/c the contact between the CPU and the pins isn't good. THis is a byproduct of removing the PCH, because the pressure is very high with the IHS on there.
Originally Posted by ohhgourami
I realized that even for an OC that should be semi-stable, Prime95 still BSODs immediately. It's like shooting at a kevlar vest with a 50cal. Prime95 is just outright too demanding for Haswell.
Plus if Intel helped make AIDA64 work for Haswell, then I can trust it. I was skeptical about AIDA64 since I see a lot of reports of BSOD even after "passing". I guess those people just weren't running it long enough.
BTW, I'm at 1.285V for 4.5ghz and 36 uncore, and BSODed 12hours into the test. Looks like I need a bit more vcore.
Here you can see it is optimized for haswell: http://www.aida64.com/news/finalwire-aida64-300-kabini-haswell-l4-cache-windows-8
ANd here you can see Intel is one of their official partners: http://www.aida64.com/technology-partners
Originally Posted by Cyro999
Hey; Been troubleshooting for a little while and i cant make any sense of this.
I can't make IBT fail at 1.295vcore (didnt try lower..) i have cinebench passes at 1.28vcore (multiple times, np) This is 4.7.
x264, in the form of offline encoder; x264 bench; live encoding - brings down my system (or crashes with a "has stopped working" message) I'm lucky to last 90 seconds. My most recent fail was at 1.35vcore, this is unacceptable. It's rock solid at 4.5 1.195vcore.
I manual'd my uncore to 34x, i tried RAM (that will prime and 32m at 2000cas11) at a slightly increased voltage at 1066cas11. I tried +0.15 system agent, +0.1 on digital/analog io voltages (maybe a bit more?)
Tried vring at 1.2v, nothing. A ton of VRIN's, seems to just make things worse if i change it from my "optimal" vrin at this vcore which seems to be a touch below 1.9 with llc extreme
I tried other stuff too, cant remember to list everything i did, any tips? This is really a requirement for me, i use x264 every day. My temps are below 85c, often below 80c or even in low 70's when it fails. 0x0101.
Feels like i'm missing something obvious here, thanks in advance for any assistance
Take down the memory and see what happens.
People on other forums are telling me my voltage recommendations are too low, and that I need to increase them for 1.3-1.35v for 4.5ghz, these are guys with all types of boards, so I will come out with more profiles for easy 4.5ghz.
Also you guys you can try the build in CPU Upgrade to get a baseline if you want to try it out, it might work.
I also have another profile I have been working on, this one you set the VIN lower and the ring higher, lower temps with VIN and increase a tiny bit with vRING.
VIN LLC: Extreme
VIN Overide: 1.8v
CPU Vcore: 1.25-1.35v depending on your CPU's VID
Those shoudl be good enough for most, but reduce the SA, IOA, and IOD unless you OC memory, then change them to the above values.
Also on GBT adaptive voltage mode is used(and it works awesome that is why there is no vdroop and why you don't need offset to drop your vcore, you can just enable C3), that is what Intel recommends, the only thing you need to watch for is that with AVX instructions it will auto raise your vcore like 0.1v or sometimes less.
BDOSes: 101 is CPU for sure, 124 i also see as CPU. For me AIDA blue screens i it doesn't like it, and it happens suddenly, if the OC is slightly unstable it will give a message. I guess it is if really unstable it will just crash the system. Some here also said they saw 124 for memory, but drop down your memory and then go for it.