|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> It might have been a core stuck in a loop and it just needed a re-boot. You
> never can tell.
You can get task manager to show the CPU usage for each core
(Performance -> View -> CPU History -> One Graph Per CPU), it should
then be obvious if any of the cores are stuck in a loop.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
scott <sco### [at] scottcom> wrote:
> > It might have been a core stuck in a loop and it just needed a re-boot. You
> > never can tell.
>
> You can get task manager to show the CPU usage for each core
> (Performance -> View -> CPU History -> One Graph Per CPU), it should
> then be obvious if any of the cores are stuck in a loop.
I did not mean it literally. :-)
One of the irritations with my current, i7 laptop, is. Regularly the system'
process will use 13% ~ 25% of the recourses and the machine will be very
sluggish. But you never see a core maxed out.
You do with PovRay, though. :-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 17-2-2014 10:38, scott wrote:
>> It might have been a core stuck in a loop and it just needed a
>> re-boot. You
>> never can tell.
>
> You can get task manager to show the CPU usage for each core
> (Performance -> View -> CPU History -> One Graph Per CPU), it should
> then be obvious if any of the cores are stuck in a loop.
>
Of course. I forgot to check that yesterday. Stupid. ;-)
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 17-2-2014 12:40, Stephen wrote:
> scott <sco### [at] scottcom> wrote:
>>> It might have been a core stuck in a loop and it just needed a re-boot. You
>>> never can tell.
>>
>> You can get task manager to show the CPU usage for each core
>> (Performance -> View -> CPU History -> One Graph Per CPU), it should
>> then be obvious if any of the cores are stuck in a loop.
>
> I did not mean it literally. :-)
> One of the irritations with my current, i7 laptop, is. Regularly the system'
> process will use 13% ~ 25% of the recourses and the machine will be very
> sluggish. But you never see a core maxed out.
> You do with PovRay, though. :-)
My i7 PC does that too sometimes. It seems to have to do with some
arcane Windows process... I checked with the task manager and one or
another process was active.
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thomas de Groot <tho### [at] degrootorg> wrote:
> On 17-2-2014 9:56, Stephen wrote:
> > It might have been a core stuck in a loop and it just needed a re-boot. You
> > never can tell.
>
> Indeed. They should do what they are told though ;-)
>
Indeed but...
>
> Not sure about controlling fan speed. It seems to happen automatically
> in situations where external temp (for instance) is high. I shall have a
> look at speedfan too. Thanks!
>
instructions, it looks like it would be suitable for slowing down noisy fans.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thomas de Groot <tho### [at] degrootorg> wrote:
> In the mean time, this morning, it started up ok, without problems, and
> all temperatures are at normal levels. I really wonder what might have
> happened.
Btw, did you check that something wasn't consuming CPU time? Was the CPU
at 100% load?
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 17/02/2014 12:20 PM, Thomas de Groot wrote:
>
> My i7 PC does that too sometimes. It seems to have to do with some
> arcane Windows process... I checked with the task manager and one or
> another process was active.
Arcane indeed.
I downloaded Process Explorer to see if I could find out what was
causing it. Cyber-man's magic. Whooo! :-)
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 17/02/2014 17:26, Warp a écrit :
> Thomas de Groot <tho### [at] degrootorg> wrote:
>> In the mean time, this morning, it started up ok, without problems, and
>> all temperatures are at normal levels. I really wonder what might have
>> happened.
>
> Btw, did you check that something wasn't consuming CPU time? Was the CPU
> at 100% load?
>
IIRC, he said that the temperatures of cores were fine (and low) when
the incident happened. Of course, if it was at start-up of the computer,
they hadn't had the time to heat yet. (I guess they have that big
inertia of a block of alu-copper attached to them, something the other
chip might not have)
--
Just because nobody complains does not mean all parachutes are perfect.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 17-2-2014 17:26, Warp wrote:
> Thomas de Groot <tho### [at] degrootorg> wrote:
>> In the mean time, this morning, it started up ok, without problems, and
>> all temperatures are at normal levels. I really wonder what might have
>> happened.
>
> Btw, did you check that something wasn't consuming CPU time? Was the CPU
> at 100% load?
>
Well, that I forgot to check indeed. But I am pretty sure it was not the
case. The system was neither slowed down at all.
@ Le_Forgeron: the temperatures of the cores remained low the whole day.
Only the TMPIN1 of the motherboard showed an abnormal temperature of 99,
according to the CPUID Harware Monitor.
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 17-2-2014 23:09, Stephen wrote:
> On 17/02/2014 12:20 PM, Thomas de Groot wrote:
>>
>> My i7 PC does that too sometimes. It seems to have to do with some
>> arcane Windows process... I checked with the task manager and one or
>> another process was active.
>
> Arcane indeed.
> I downloaded Process Explorer to see if I could find out what was
> causing it. Cyber-man's magic. Whooo! :-)
>
>
svchost, SearchIndexer, taskmgr, are some of the arcanes (to me)
although normally they do not take up much cpu time.
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |