high CPU temperatures;upto 100 degrees celsius

Miles - All the monitors make use of some type of Platform Environment Control Interface (PECI channel for Intel). This channel is a single wire serial comm interface with limited bandwidth. It's also the channel used to report and control fan speeds. It's self timing and syncing based on individual requests to the controller by the CPU. It's not meant to handle any type of multitasking or shared communications. Poorly written and/or multiple software monitors will cause a crash because they are expecting data at a specific address and it may not be there or invalid. I've seen it happen in crash dumps. Just like multiple AVs. Argue with someone else because I've seen it happen. WADR.

I think you're good to go. :)

this is for everybody , who doesnt wanna use the third party tools to monitor the CPU temperature!
this service is natively present in windows(win 7) in my case.
just like any other shell programming, this one is called windows power shell. you can type in various scripts to get various thins done.
I found the small script on how to find your CPU temperature, using powershell scripting.
Im attaching the screenshots as well as the script!

Code:

Get-WmiObject -Query "SELECT * FROM MSAcpi_ThermalZoneTemperature"  -Namespace root\WMI | ForEach-Object { $temp = ($_.CurrentTemperature -2732)/10; Write-Host $_.InstanceName" = "$temp }

AS YOU CAN SEE INSIDE THE RED BOX WITHIN THE SCREENSHOT, its mentioning the CPU temperature recorded by the ACPI sensors!

carwiz said:

Miles - All the monitors make use of some type of Platform Environment Control Interface (PECI channel for Intel). This channel is a single wire serial comm interface with limited bandwidth. It's also the channel used to report and control fan speeds. It's self timing and syncing based on individual requests to the controller by the CPU. It's not meant to handle any type of multitasking or shared communications. Poorly written and/or multiple software monitors will cause a crash because they are expecting data at a specific address and it may not be there or invalid. I've seen it happen in crash dumps. Just like multiple AVs. Argue with someone else because I've seen it happen. WADR.

As a rule of thumb I assume any program that directly accesses the hardware has the potential to cause problems. Running more than one program that accesses the same hardware at a low level is asking for problems. Which wire it's on in every case may be useful information if you are working at that level. But I really don't think it matters to a user wanting to know the CPU temp. All he needs to know is don't use more than one of the same type low level monitor at the same time.. Again I don't understand the compulsion to lecture me on the subject. I think most of us know the hazards already.

aaryan said:

Thanks alot! Really helpful people!
Pray for me i dont get any severe issue regarding this :-P
Will rep u people! Gracias :-D

Ah but if stuff runs too smoothly you won't come back!!!