New
#21
All c-states have been enabled, never disabled them. 1.210 vcore and I booted up fine at 3.7ghz. Power is still over 95w at full load, no crash.. but still not right.
All c-states have been enabled, never disabled them. 1.210 vcore and I booted up fine at 3.7ghz. Power is still over 95w at full load, no crash.. but still not right.
If you look, you will find it, but I believe if you put a USB Flash drive in and on any screen press F12 (I think), it will put a picture of that page on the USB drive. Set the Vcore to offset, the sign to - and the value to .010. If it does not boot, or crashes during Intel Burn Test, Change the sign to + and the value to .010.
Just got home from work (I replied on lunch earlier) I killed my only flash drive while trying to put the memtest iso on it, so cellphone pics are the best i can do for now. If I set vcore to offset mode, it's going to offset from stock voltage, which I think is higher than the 1.210v I have it currently set to. I'll try the offset now and keep you updated shortly.
In between passes, the CPU drops to 58w and goes to 70, 80, 90 then 97... always over the TDP.
Lowest I could boot and run linpack at was 1.170v, and still ~97w. Any lower and it boots, but Intel burn crashes immediately. Seems like a hardware malfunction, motherboard or CPU. I feel like if it's the motherboard, it's already damaged the CPU, so I'd probably have to replace both. I hope there are viable options for me here, other than hardware replacement
Look at the core voltage in bios, it should tell you what it is currently set at. Tell me what that is. Then boot into Windows and open CPUz and look at the core voltage. After it has settled down after startup, what does it read? Next run a program that is just slightly stressful, like maybe a virus scan and tell me the core voltage during that. The stock voltage for your CPU is 1.20-1.25. It can be a little different depending on the CPU. At idle, your CPU should clock down to 1600 Mhz and core voltage should range around .850ish to 1.0xx. As the frequency increases the voltage increases as does the frequency. What you are seeing with Intel Burn Test, you will never see in actual usage. IBT puts more stress on the CPU than anything you will ever use. So, in real life you will never see the core voltage you see there. You will see the same CPU frequency you see there, but not the stress it is putting on the CPU. It is normal with IBT for it to run up and down, that is what the test does.
I think something is misreading somewhere. I don't believe there is any way you will run at 3.7GHz at 1.080V. That is very close to what idle voltage can run with it at 1.6Ghz. Just in case you don't know, I use the terms interchangeably, 1.6GHz is the same as 1600MHz.
No problem with the cell phone pics, they were fine. I just wanted to make sure you knew you could put them on a flash drive.
BTW, AXTU will tell you your voltages too. But it is never good to run 2 monitoring programs at the same time. That does not include CPUz.
Rebooted with 1.200 on the core and it's been over 10 minutes and it's still running at 3700mhz, flashed to 1600 for a second twice in cpu-z, but hasn't settled. During a virus scan it was 1.160v steady. 37w max. When idle, it's 1.168-1.176v, 10-11w. I'm going to run CoD Advanced Warfare with HWMonitor in the background for a bit, and see how my system handles it.
that isn't right. You should drop down the 1.6 and 0.800-1.02 at idle on the desktop. The 1.200 is right on what it should be.
The best tests are practical ones like running games and programs that you normally use. Artificial tests like IBT, Prime95 and such are good in their own right, but actual usage is the best tests. Just don't get too upset if you BSOD or freeze. Just bump the voltage higher by .005 at a time (if you are running a negative offset, reduce the negative to increase the voltage).
ROFLance, any updates? how is it going now? I hope things are going well. Please give us a status report.