General Warning Samsung Magician software, locks CPU at max speed!

Hi
Maybe its my configuration but finally got this beast working perfectly.
Added my first Samsung EVO 850 and loaded Magician as done before when installing these drives into my laptop, selected default Overprovisioning, then Maximum performance, and then checked Intel XTU.

OMG instead of 0.737V core voltage, 0% Current throttling, 1-2% CPU usage, 1.24 to the odd spike up to 1.6GHz Core speed
Is was 1.4 to 1.6V core voltage, 97 to 99% Current throttling, 8- 17% CPU usage, 3.5 GHz ramping up to 3.78 GHz ( max in turbo on this CPU is 3.8GHz slowing down to 3.56 then cycling up again constantly.
In the Bios the package temp went up from average ( warm room 27C ) 41C to 52C.m( Max is 67C.

CPU-Z confirmed core voltage had gone up from 0.737 to 1.48V ... So assume XTU readings were coorect.

Thanks to the the overkill 8x 140mm Noctua Fans and the amazing Noctua NH-D15 cooler, individual core temps only rose from average of 29C to 37C . And the package temp stayed under 53C. Guess overkill paid off.

Thankfully after every change I had been checking Intel XTU temps volts and core frequency etc.

I uninstalled Magician and then went back to the previous restore point - all back to Normal.

As during this time the fan speed only went up from 320 to 428 rpm, hardly possible to percieve the extra noise, and I certainly dont want o be checking crap like this daily. So I went totally oveboard "belt and braces" and cleared the CMOS and reloaded Win 10. but no Magician ... Maybe they should rensme it "Scocerer"!
Again - All back to Normal.

Why it did it I dont know ...
FYI my build
Win 10 Home
Xeon CPU E51650 V3
SM X10SRA-O 2011 MB with C612 PCH.
Intel 750 PCIe NVMe ( needs UEFI miniport loaded )
Samsung DDR 4 ECC Memory

Just a warning. Weird as I had used thrm 3 times before.

I Don't suppose anyone knows how to create that "Overprovisioning" partition?, as apparently it really improves SSD life. Is it just an unallocated partition or another simple drive partition.?

Submariner wrote in post #18010850
I Don't suppose anyone knows how to create that "Overprovisioning" partition?, as apparently it really improves SSD life. Is it just an unallocated partition or another simple drive partition.?

Go to http://www.samsung.com …_04_Over-provisioning.pdf and specifically look at item #3. There are some alternative methods of setting up OP. Having said that I would read the entire document so you thoroughly understand the ramifications of space allocation.

Magician doesn't touch voltages or overclocking. Overprovisioning sets aside some of the SSD storage, to increase overall drive life. RAPID mode uses RAM to cache the most-used files. I'm using RAPID mode to speed up the LR catalog.

I've been running both speed tweaks on my i7 desktop, on both the 840 Pro C: drive, and now on the 850 Pro swap drive, (you can only do one drive per PC) with zero problems.
It runs on the second desktop's 850 Evo, and the ultrabook's 850 Evo. All three PC's have great access times, and no issues.

I install magician but I don't let it run resident. It's only for firmware upgrades. The acceleration using RAM it claims only helps benchmarks.

John from PA wrote in post #18010911
Go to http://www.samsung.com …_04_Over-provisioning.pdf and specifically look at item #3. There are some alternative methods of setting up OP. Having said that I would read the entire document so you thoroughly understand the ramifications of space allocation.

Thanks, for the link.
I will have to get it into that space allocation stuff. Already had an intriguing insight inti the use of cores by software.

skid00skid00 wrote in post #18011145
Magician doesn't touch voltages or overclocking. Overprovisioning sets aside some of the SSD storage, to increase overall drive life. RAPID mode uses RAM to cache the most-used files. I'm using RAPID mode to speed up the LR catalog.

I've been running both speed tweaks on my i7 desktop, on both the 840 Pro C: drive, and now on the 850 Pro swap drive, (you can only do one drive per PC) with zero problems.
It runs on the second desktop's 850 Evo, and the ultrabook's 850 Evo. All three PC's have great access times, and no issues.

Very pleased for you.
But it polaxed this box. Tried it twice!
Way beyond my knowledge - but seeing is believing
After removing Magician see below
0.737V core voltage, 0% Current throttling, 1-2% CPU usage, 1.24 to the odd spike up to 1.6GHz

tim wrote in post #18011329
I install magician but I don't let it run resident. It's only for firmware upgrades. The acceleration using RAM it claims only helps benchmarks.

Well I too have used it before and it was a great tool for setting up, especially when you dont understand it. But even off it screwed this box totally.
Removed all is perfect again.

tim wrote in post #18011329
I install magician but I don't let it run resident. It's only for firmware upgrades. The acceleration using RAM it claims only helps benchmarks.

RAPID mode decreased access times to my LR catalog by a factor of 10, per windows' Resource Monitor. I haven't timed a large batch of LR 1:1 preview creation, but the difference exists.

Submariner wrote in post #18011486
Very pleased for you.
But it polaxed this box. Tried it twice!
Way beyond my knowledge - but seeing is believing
After removing Magician see below
0.737V core voltage, 0% Current throttling, 1-2% CPU usage, 1.24 to the odd spike up to 1.6GHz

I want to repeat to the readers out there, that Magician will NOT change CPU voltage. There's something else going on with Sub's PC. I've overclocked my last two PC builds, so I have enough knowledge to be confident in what I'm talking about.

Note that Sub used the Maximum setting in Magician, which sets Window's power plan higher. This won't change vCore (CPU voltage), but if the PC's BIOS isn't set up correctly, it could let the mobo run higher power limits. This isn't Magician's fault, it would be incorrect BIOS settings.

skid00skid00 wrote in post #18011715
I want to repeat to the readers out there, that Magician will NOT change CPU voltage. There's something else going on with Sub's PC. I've overclocked my last two PC builds, so I have enough knowledge to be confident in what I'm talking about.

Note that Sub used the Maximum setting in Magician, which sets Window's power plan higher. This won't change vCore (CPU voltage), but if the PC's BIOS isn't set up correctly, it could let the mobo run higher power limits. This isn't Magician's fault, it would be incorrect BIOS settings.

You are partially correct, Magician can not change the CPU Voltage directly, but most processors now utilize power saving strategies. At idle the voltage and clock speed are lower to prolong life, save energy and lower heat output, as the CPU is loaded the clock speed and voltage are increased. This can be turned off, causing the CPU to remain at max clock speed and voltage all the time, but it is not an incorrect setting.

In Sub's case Magician was causing the CPU to run at high load, which correctly raised the clock speed and cpu voltage.

skid00skid00 wrote in post #18011715
I want to repeat to the readers out there, that Magician will NOT change CPU voltage. There's something else going on with Sub's PC. I've overclocked my last two PC builds, so I have enough knowledge to be confident in what I'm talking about.

Note that Sub used the Maximum setting in Magician, which sets Window's power plan higher. This won't change vCore (CPU voltage), but if the PC's BIOS isn't set up correctly, it could let the mobo run higher power limits. This isn't Magician's fault, it would be incorrect BIOS settings.

Hi Skid
Certainly not challenging your knowledge.
All I Was reporting was my specific configuration / Bios etc had a nasty problem with this ( and note I have used it 3 times before on 2 different 850 Evos, with perfect results on HP and Sony stuff ). I would also state, I have had a nightmare with Supermicros Bios's. NB great support from the Technical team at Supermicro in Holland and appalling commercial and RMA support from Supermicro UK.

My Reason for alerting the community, is simply had I not checked with XTU; there were virtually no outward signs this had happened. My old ears could hardly tell the difference between fans at 320 rpm and 485 rpm. But I suspect had that CPU spent its life running between its max. Speed of 3.5G.Hz and its max. turbo speed of 3.8Ghz (permenantly cycling up and down) I doubt if it would have lasted too long?

One of the benefits of building your own and having problems with the MB meant I was checking things. Lets say I had bought on out of the box HP - I would never have checked or even know what to check with.

I am sure with your Overclocking knowledge you are "aware" of these issues. But thought many photographer type users ( like myself) might have been interested to know this could go on.

-dave-m- wrote in post #18011734
You are partially correct, Magician can not change the CPU Voltage directly, but most processors now utilize power saving strategies. At idle the voltage and clock speed are lower to prolong life, save energy and lower heat output, as the CPU is loaded the clock speed and voltage are increased. This can be turned off, causing the CPU to remain at max clock speed and voltage all the time, but it is not an incorrect setting.

In Sub's case Magician was causing the CPU to run at high load, which correctly raised the clock speed and cpu voltage.

Thanks Dave,
Great explanation .... As usual. The learning curve seems never ending - but very nice to understand why and what was happening. The effect on my PC certainly mirrored your explanation. Just at the time for me was super scary.

Just realised I forgot to post an image of what XTU saw ( and mirrored by CPU-Zs voltage reading) when it was cyling between its max CPU spped and its Max CPU Turbo Speed ( i.e. constantly between 3.5 and 3.7 Ghz

John from PA wrote in post #18010911
Go to http://www.samsung.com …_04_Over-provisioning.pdf and specifically look at item #3. There are some alternative methods of setting up OP. Having said that I would read the entire document so you thoroughly understand the ramifications of space allocation.

Thanks John
I read that but was a little confused as it seems to state its only needed for an OS disc? Uet the concept would appear to apply to any ssd disk?

Also are they saying its just an unallocated partition or domthey do some clever software to claim that as the PO area?

Quick Update
Maybe my problem was I hit the performance button in Magician.

I do from time to time check Intel XTU just to make sure, the processor is not locked on full speed as before.
Well after a month of trouble free running ... dismayed to find
The CPU at 3.5 GHz and the Voltage at 1.080V . Not the usual 1.2 GHz and 0.737V

Thinking what had I changed and there were 2 things

1. In PSE 13.1 I had changed the scratch disk from the OS Intel 750 PCIe SSD drive to the spare Samsung Evo 850 500GB SSD, and
2. In Windows 10 under Power Plan - I had moved from the "Balanced - Recommended" to "Performance" power plan option.

So I set the Scratch disk back to the the Intel ........ no joy! the CPU was still constantly at 3.5GHz [Its std. top speed]

The I set the Power plan back to "Balanced - Recommended" to "Performance" power plan option. And bingo!
As usual after under 1 minute CPU dropped to 1.2 GHz and the Core Voltage dropped to 0.737 V [also confirmed in ZCPU].

So it looks like if you set the Power Plan to Performance ..... then this crazy system option sets the CPU to PERMENENTLY sit at the CPU's max speed [not its Turbo speed.
Note there is no mention of this in the WIndows 10 pop-up Info Window!

So beware of this! As I cant believe its good for CPU to run at full throttle all the time!

It made me think about my earlier Magician Problem; and I do remember setting the Magician option to 'High Performance' .... maybe this in turn, flicked this Power Management Plan switch - and is unable to switch it back!
Sorry not willing to experiment, as its now running fine.
But there is a chance Magician can be used, as long as one does not select the High Performance option.

I only twigged on this issue thanks to DAVE - M's kind and informative earlier post.

Hell I was just about to reload the OS from scratch to get it back working.

So many thanks to Dave-m for putting me on the right track!