The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Samsung Series 7 Chronos One core is stuck at ~100% (NP700Z5C-S02UB)

    Discussion in 'Samsung' started by MK_Dev, May 13, 2013.

  1. MK_Dev

    MK_Dev Newbie

    Reputations:
    0
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    5
    I've got a weird problem that I asked about on superuser.com. Got a suggestion, but nothing that worked (original question: One CPU core stuck at 100% doing kernel stuff - Super User).

    I'm copy-pasting the same question here:

    A few days ago I started experiencing a weird issue - one core was stuck at 100% doing some kernel stuff. This problem is NOT OS specific: it occurs in Windows 7 (including Safe Mode), Ubuntu 12.04 installed on the hard drive and Ubuntu 12.04 on live USB.

    What I've tried so far:
    • Different OSes
    • Disabling hyperthreading (with hyperthreading enabled, only one thread gets locked, not the whole core)
    • Resetting BIOS
    • Updated BIOS from P03ABJ to P05ABJ
    • Re-installed Windows 7

    My system:
    • Samsung Series 7 Chronos (NP700Z5C-S02UB)
    • Core i7-3635QM CPU
    • Windows 7 Professional SP1 or Ubuntu 12.04

    EDIT: So this is a bit bizarre. I "reset" the laptop and re-installed Win7. After a short while the problem disappeared both in Windows AND Linux. Now, after installing Intel chipset drivers the problem is back again.

    I'm at a loss as to what could be causing this. Any ideas?

    Thanks!
     
  2. John Ratsey

    John Ratsey Moderately inquisitive Super Moderator

    Reputations:
    7,197
    Messages:
    28,841
    Likes Received:
    2,166
    Trophy Points:
    581
  3. MK_Dev

    MK_Dev Newbie

    Reputations:
    0
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    5
    Hey John, thanks for the reply.

    I will definitely give this a try. However, I must note (and I'll update my posts in a sec) that this this problem started when I had P03ABJ BIOS. I updated to P05ABJ (latest available according to Samsung's BIOS Update tool) and the problem persisted.

    MK
     
  4. John Ratsey

    John Ratsey Moderately inquisitive Super Moderator

    Reputations:
    7,197
    Messages:
    28,841
    Likes Received:
    2,166
    Trophy Points:
    581
    OK. Google for "site: Samsung Notebook Forum high CPU utilization NP700Z5C" (and other similar wordings) to find more discussion about this issue.

    John
     
  5. John Ratsey

    John Ratsey Moderately inquisitive Super Moderator

    Reputations:
    7,197
    Messages:
    28,841
    Likes Received:
    2,166
    Trophy Points:
    581
    I see that the forum software is messing up my instructions:

    It should read "site:forum.notebookreview.com /samsung/ high CPU utilization NP700Z5C"

    John
     
  6. MK_Dev

    MK_Dev Newbie

    Reputations:
    0
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    5
    No worries. I've been doing research for the last two days and probably got tunnel vision so I never actually searched for those phrases. Anyhow, I was able to somewhat mitigate the problem by installing Intel Rapid Storage drivers. However, like others, I'm still getting weird CPU usage for the first couple of minutes or so. I really like the laptop but this issue is really disappointing.
     
  7. John Ratsey

    John Ratsey Moderately inquisitive Super Moderator

    Reputations:
    7,197
    Messages:
    28,841
    Likes Received:
    2,166
    Trophy Points:
    581
    I should have remembered the Rapid Storage issue. :(

    Activity during the first couple of minutes is probably housekeeping and/or virus scanning. The easiest way to avoid that is to use sleep / hibernation to minimise the restarts.

    John