system interrupts deferred procedure calls and interrupt service routines

System Interrupts Deferred Procedure Calls And Interrupt Service Routines .Exe To Not

Office has seen some problems itself where some component has caused problems under certain conditions.

For a better experience, please enable JavaScript in your browser before proceeding.

Running - 63 52.80 System 4 NT Kernel System Running 106 26 28.33 the various other images are.

Use the Select Columns option to add the column for PID and Image Path.

From your post, possibly the 106 and 63 are PIDs and show what process is hosting the high usage, but you will probably need to know what inside that process is actually causing the problem.

For now, if you look for a PID in Task Manager, which ones are 106 and 26 and the 63 number If you have not done so, in Performance Monitor, under the System folder there are System Diagnostics and System Performance options.

If you right click on one of those and select Start, it will make a report for the Reports Section you can open and read.

Some versions of Win 7 seem to be limited in this capability.

System Interrupts Deferred Procedure Calls And Interrupt Service Routines .Exe To Not

Now you have two ways to go, one is trial and error method where you use msconfig.exe to not allow certain programs to start up and see if you can find the one responsible, or you can use an advanced version of Task Manager to see if you can pin it down.

If you feel it is necessary, there is an advanced version of msconfig.exe called AutoRuns at the site below.

If you decide to try the software, check SysInternals and look for Process Explorer.

There are instructional videos on the system and the latest Case of the Unexplained video for 2011 uses such an example as its first case.

Otherwise, maybe you will find the problem in the Startup area of Msconfig.exe after gaining information from Task Manager or Performance Monitor.

I drafted a reply yesterday, but it seems to have gone into the ether.

Here it is in brief: The original post data was a copypaste from Resource Manager - the column alignments didnt hold so it was hard to interpret.

Here is a snapshot from this morning transposed: Image System Interrupts PID - Description Deferred Procedure Calls and Interrupt Service Routines Status Running Threads - CPU 58 Average CPU 54.36 Image System PID 4 Description NT Kernel System Status Running Threads 102 CPU 32 Average CPU 28.37 Between the two, the kernel and system interrupts are using an average of about 83 of the cpu.

I also saw an HD Audio process and BCSSYNC listed as hogs - the latter because of housing an infection.

I had them both; killed both, rebooted, and CPU usage was around 2-3 That lasted a while and then it jumped up again.

I also saw the McAfee realtime scanner as a hog; killed it, and was back to 2-3.

This morning with all those changes still in place Im back to 100.

Any suggestions for next steps Im going to boot in safe mode and run malwarebytes.

I have a feeling the BCSSYNC wasis the culprit, and even though the process does not show active and there is no image for it, the virus is loading from the boot track or someplace.

That being the case, what do you mean by housing an infection If you do have some type of infection, it may have a watcher component that will replace the problem after you find and delete it.