Need help with fixing this issue.

Daemus · Jun 26, 2014

I'd been dealing with an issue wich was causing my pc to reach with the CPU at 100% all the time. How can i fix this? (I'm new here by the way. ^^')

jcgriff2 · Jun 27, 2014

Hi -

Use the Resource Monitor to help ID exactly what is consuming CPU -

START | type resmon | click on "CPU" tab | click on "Average CPU" column header to sort

Regards. . .

jcgriff2

Daemus · Jun 27, 2014

I did that and now i noticed a process consuming 60%-80% of the CPU called System Interrupt. What could this mean?

TomasD · Jun 30, 2014

Hi Daemus,

Huge CPU usage by System Interrupt usually means one of the following - a faulty hardware or a buggy driver.

To be more specific, we need to identify which driver is behind these interrupts and for that we require a XPERF trace. Please follow these steps to generate one:

Download Windows Software Development Kit (SDK) for Windows and run the setup.
Select Windows Performance Toolkit feature (all the others can be unchecked) and proceed with the download/installation.
Once the installation finishes, open an elevated Command Prompt by right-clicking on CMD.EXE shortcut in your start menu and selecting Run As Administrator from the context menu.
Type the following command, which will start tracing, in the Command Prompt window you just opened:
Code:
```
xperf -on PROC_THREAD+LOADER+PROFILE+INTERRUPT+DPC+DRIVERS+POWER+IDLE_STATES -stackwalk Profile -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 256 -FileMode Circular
```
If you see a yellow warning "xperf: warning: This system is not fully configured for x64 stack tracing" after running the above command, please complete these extra steps (otherwise, proceed to the step #5):
Read More:
1. Run the following command which will stop the tracing:
  
  Code:
  
  xperf -stop
2. Run the following command to enable stack tracing (by disabling Paging Executive):
  
  Code:
  
  REG ADD "HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management" -v DisablePagingExecutive -d 0x1 -t REG_DWORD -f
3. Reboot the computer
4. Once computer reboots, proceed from the step #3
If you see a red error "xperf: error: NT Kernel Logger: A device attached to the system is not functioning. (0x1f)" after running the above command, please complete these extra steps (otherwise, proceed to the step #5):
Read More:
1. Run the following command to disable Driver Verifier, which causes the above error:
  
  Code:
  
  verifier /reset
2. Reboot the computer
3. Once computer reboots, proceed from the step #3
If you see a red error "xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7)", please do the following (otherwise, proceed to the step #5):
Read More:
Make sure you do not have any programs that captures ETW data already running. Some examples of these are:
- Process Explorer
- Process Hacker
- Resource Monitor
- Process Monitor
- Latency Monitor
- Another instance of XPERF or WPR
Perform some activities with your computer for few minutes, making sure the issues you reported are reproduced.
Run the following command, which will stop the tracing, in the command prompt window you already have opened:
Code:
```
xperf -stop -d C:\CPU.etl
```
Compress file C:\CPU.etl
Upload the compressed file to a file sharing service (e.g. OneDrive or DropBox).
Share the download link here.

Thank you.

Search

Search

Need help with fixing this issue.

Daemus

New member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Daemus

New member

TomasD

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Need help with fixing this issue.

Daemus

New member

jcgriff2

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Daemus

New member

TomasD

Sysnative Staff, BSOD Kernel Dump Senior Analyst

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)