CoreTemp | Measure and chart the evolution the temperature | Data Visualization library

Did more research today. The problem here is that %% counts as an argument to "run" something, but above it is where it's supposed to be defined. It's not.

I just used %diskspace% for a new script that outputs my Sink volume. It would work the same with the C script.

There's 2 questions here:

a) How to execute INVD (unsafely)

For this, you need to be running at CPL=0, and you have to make sure the CPU isn't using any "processor reserved memory protections" which are part of Intel's Software Guard Extensions (an extension to allow programs to have a shielded/private/encrypted space that the OS can't tamper with, often used for digital rights management schemes but possibly usable for enhancing security/confidentiality of other things).

Note that SGX is supported in recent versions of Linux, but I'm not sure when support was introduced or how old your kernel is, or if it's enabled/disabled.

If either of these isn't true (e.g. you're at CPL=3 or there are "processor reserved memory protections) you will get a general protection fault exception.

b) How to execute INVD Safely

For this, you have to make sure that the caches (which includes "external caches" - e.g. possibly including things like eDRAM and caches built into non-volatile RAM) don't contain any modified data that will cause problems if lost. This includes data from:

• IRQs. These can be disabled.

• NMI and machine check exceptions. For a running OS it's mostly impossible to stop/disable these and if you can disable them then it's like crossing your fingers while ignoring critical hardware failures (an extremely bad idea).

• the firmware's System Management Mode. This is a special CPU mode the firmware uses for various things (e.g. ECC scrubbing, some power management, emulation of legacy devices) that't beyond the control of the OS/kernel. It can't be disabled.

• writes done by the CPU itself. This includes updating the accessed/dirty flags in page tables (which can not be disabled), plus any performance monitoring or debugging features that store data in memory (which can be "not enabled").

With these restrictions (and not forgetting the performance problems) there are only 2 cases where INVD might be sane - early firmware code that needs to determine RAM chip sizes and configure memory controllers (where it's very likely to be useful/sane), and the instant before the computer is turned off (where it's likely to be pointless).

Guesswork

I'm guessing (based on my inability to think of any other plausible reason) that you want to construct temporary shielded/private area of memory (to enhance security - e.g. so that the data you put in that area won't/can't leak into RAM). In this case (ironically) it's possible that the tool designed specifically for this job (SGX) is preventing you from doing it badly.

I am just not the smartest right now, should've looked at the rest of the Code and should sleep xD. I could just remove the check,that checks if "sensors" is accessible (at least i think that is what it was used for). so from

As you can see from the sensors output, your CPU is running too hot. In response to that it is probably throttling like crazy to keep itself from melting. Strangely is only seems to be one of the cores that is too hot, which is unusual, because CPUs internally shuffle the workload between the cores to evenly distribute the load.

Here is what I'd recommend for debugging and fixing this:

1. verify that the CPU fan is running fine,
2. verify that the fan is properly mounted on the CPU (no gaps),
3. verify that your thermal paste between CPU and fan is sufficient -- in my experience this is actually the most likely culprit

If all of these are fine, then I'm afraid your CPU is broken and needs to be replaced.

But one thing is certain: this is not a software issue.

PS: I think you can ignore the high number of local time interrupts, because they are not unusual. The thermal interrupts on the other hand are. Here are my current values on a system that shows no issues:

I'm not sure this question really belongs on StackOverflow, might be more of a SuperUser question, but I'll provide an answer anyway.

For the plugins listed in the manual for Rainmeter, there is no installation needed, they come with Rainmeter (check the /Rainmeter/Plugins folder), and for 3rd party plugins you may find some instructions in the main plugins page of the Rainmeter manual.

Normally these would be distributed with a skin and installed using the Rainmeter Skin Installer, but may be manually installed by placing the .dll file in the Plugins folder under the settings path for the Rainmeter installation.

For the CoreTemp plugin specifically you'll need the CoreTemp application, which actually gathers the data from the temperature sensors, the plugin just exposes that data to Rainmeter skins. Instructions on how to integrate those data into your own skins is detailed on the page you've linked to.

In Handbrake you can pass advanced parameters so you only use a certain amount of CPU threads.

You can use threads, view the Handbrake CLI Documentation

When using threads you can specify any number of CPU processors to use. The default is auto.

The -x parameter stands for Advanced settings in the GUI of Handbrake, that is where threads will go.

The below tells Handbrake to only use one CPU thread for the Advanced setting: