Derlep

It's a MSI GE60, which has terrible cooling design, specially for the CPU, with a single long heatpipe. It's the same model as this. The very next model was redesigned and uses 2 fans and shorter pipes.

I know the MB monitors power and reacts to it (if the GPU is pulling a lot of power, the CPU gets throttled, independent of temperatures or load), so it could be that if it detects too much draw it panic reboots. There are no high wattage BGA CPUs, so yeah. The VCCIN is also set (and locked) at a generous 2.05V.

1 hour ago, tmash said:

@Derlep Yeah liquid metal fixed my temp jumping, though not max temp as significant.

That's what I was afraid of. If using the CPU only on a mildly cool room, it can handle ~47W fine without throttling, so I don't know if it'd help much (it would help with 10 second benchmarks for sure though!). I will probably still give it a go.

1 hour ago, tmash said:

v0 and v1 only gives wrong voltage reading

v1 voltage reporting seemed OK to me. The problem was not reading, the problem was less stability at any given voltage. It ran hotter before changing any values too.

7 hours ago, tmash said:

@Derlep Try MC v1, it works fine on a y510p which had the same issue

Can confirm 1 works for me. I also tried 4, with that one after selecting 37 the max gets raised to 39, but any oc settings over 37 don't stick, so you're stuck on 37.

The problem with 1 is that is seems a bit buggy with the voltage regulation. Fixed voltage works, but is kinda useless. Dynamic seems iffy, I have to target 50~100 mV over the static setting in order for it to be stable. The settings I used for x37 with MC v7 are definitely not stable with MC v1. Frequency regulation seemed wonky too, specially at idle.

Long story short, I can get 4.1GHz on a single core. Anything more thermal throttles like crazy. Any less voltage -> reboot. My CPU does not seem very good; it can do 3.7 @ 1.08, 4.1 @ ~1.20, and then I tried 1.35 V and it ran for a few seconds at 4.5 but ended up rebooting (I suspect something strange is going on, because with newer frimwares the lack of voltage usually results on a bluescreen or lockup, not reboot.)

So yeah, maybe with better cooling. Does that liquid thermal paste really help? I go from 50 to 90º in less than a second and back again too, I don't know if that's a sign of bad thermal conductivity or not (I'd say it is). Last time I repasted I didn't notice any improvements.

On 23/6/2016 at 7:56 AM, MiSJAH said:

E1781IMS.110

Is my bios, I'm unsure how to check if it is AMI Atio 4 or 5?

It seems to be AMI Aptio 4. The "problem" / potential problem I see is that it has 5(x2) patches for different processors. Ubutool will happily patch it and leave only the Haswell (06C3) ones. I think it is probably fine, but who knows.

15 hours ago, tmash said:

First, remove the microcode, or do 00h, then open R/w everything select CPU MSR register, do and post a screenshot of it before throttlestop and after throttlestop bin increase (in your case 37x all cores).

What throttlestop version are you using?

I had similar issue locking at 38x unless I shutdown completely. Also, make sure you aren't using Windows uefi mode, standard uefi is ok as it works here, bios works aswell. Disable fast boot when shutting down.

The microcode downgrade will have to wait as going to 0 is a more significant change and I'm not brave enough to flash that yet

I'm using TS 8.10b2; exe md5 95ABE57810F9C0DCFC549E41D83F2F9A

I did the MSR thing but I don't know if this is correct as there are no changes before/after, not sure what I should be looking for other than the PATCH ID which stays at 6.

I'm using legacy boot and booting from cold. Also attempted sleep-resume and hibernation-resume.

Hello,

I am attempting this method on an 4710HQ. I downgraded the microcode to 06, but the repeatedly increasing max multiplier thing does not seem to be working. I can get x37 on all cores, but the max stays at 37.

Tested microcodes:

17: max 37-36-35-35

07: max 37-37-37-37

06: max 37-37-37-37

(stock cfg is 35-34-33-33 with +2 bins)

Is there any trick apart from re-opening the FIVR window after increasing the values? Is it possible that other components/BIOS are locking it somehow? Any ideas about ways to check what the issue might be?

Thank you