Core 0 100% usafe

ZeroG

ZeroG

ZeroG

Associate
Joined
8 Feb 2014
Posts
858
Location
Aberdeen
I'm hoping someone can help me with a very annoying issue I've been having recently. Just over a week ago Core 0 on my processor started hitting 100% usage and lagging out my computer, it would happen randomly and last for anything up to 10 minutes then stop. However things were fine after this until today when it started happening again. Sometimes it will subside and sometimes I would have to do a hard reboot to get the pc working again. It would work normally for anything between 5 minutes and 30 minutes before it would happen again.

https://www.dropbox.com/s/63mv9l2x6qsmid1/Screenshot 2014-02-22 13.13.32.png

https://www.dropbox.com/s/y4vl8fr4oj0nmly/Screenshot 2014-02-23 20.54.45.png

https://www.dropbox.com/s/t830etuhq71cz1m/Screenshot 2014-03-01 11.08.24.png

When this happens Hardware Interrupts and DPCs & DWM.exe seems to be what's taking up the core time. I've tried all the usual things like malware/virus scanning, updating drivers, disabling devices one at a time to see if it stops but it just randomly seems to stop on it's own most of the time.

I've done some searching about and come across xperf which I have installed and managed to get a trace run but I'm not sure if I can find the cause from the results which is a hefty 170mb file.

https://www.dropbox.com/s/b5q3tbgq0kik390/Screenshot 2014-03-01 21.55.34.png

Windows 7 Pro
i5 2500k @ Stock Speed
2x 8GB Corsair 1600MHz
Asus P8P67 Motherboard
XFX 7950 Graphics Card with 14.2 Beta drivers
 
DMW = Desktop windows manager.

Google throws up a few possibles.. Outlook, Logitech setpoint though this looks to be old/duff info.

Check your event logs, see if anything is logged around the time of the issue.

Use resource monitor, procexp and procmon to see if you can get a better idea of what it is doing. Is it opening network connections, accessing certain files etc.

Check scheduled tasks, see if anything is running at the time of the issue that might be doing it. It could be something like the experience index thing retesting your PC.
 
chaosophy said:
DMW = Desktop windows manager.

Google throws up a few possibles.. Outlook, Logitech setpoint though this looks to be old/duff info.

Check your event logs, see if anything is logged around the time of the issue.

Use resource monitor, procexp and procmon to see if you can get a better idea of what it is doing. Is it opening network connections, accessing certain files etc.

Check scheduled tasks, see if anything is running at the time of the issue that might be doing it. It could be something like the experience index thing retesting your PC.
Click to expand...

Thanks for the reply.

Although I do have a G9x mouse I don't have the Logitech software installed and I don't have Outlook/Office installed.

As per picture above procexp shows Hardware Interrupts & DPCs to be taking approx 25% of the core and dwm.exe is also quite high as well. I tried uninstalling the AMD drivers and just running with the standard VGA ones Windows installs but it still happened. I also disabled Aero incase that was causing any problems but it didn't make a difference. Resource monitor shows similar results to procexp. I couldn't see any unusual network connections being created during this, I had even disabled the network interface and pulled out the cable to make sure.


I've checked through scheduled tasks and there's nothing there that might explain my problem.

In the event view there are some errors.

1. The WinRing0_1_2_0 service failed to start due to the following error: The system cannot find the file specified. (I think this relates to the desktop gadgets I have installed for CPU Usage, GPU Meter & Network Meter). I did uninstall these to try out but same issue.

2. The device, \Device\Harddisk0\DR0, is not ready for access yet - Possibly down to me disabling some of my hdds to see if one of those was causing a problem (I have 4 mechanical and 2 ssd). There are hundreds of entries for this one it seems starting at 10:44 in the morning and going on until 15:08. - After some further checking it seems this could be indicative of a hard drive fault - I shall investigate this one further.

3. Name resolution for the name ipv6.msftncsi.com timed out after none of the configured DNS servers responded - Not sure why this is coming up as I don't use IPV6.

4. The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly - There was a few times I had to do a hard reboot when the machine wouldn't shut down - chkdsk ran after each time.

5. The device, \Device\Ide\iaStor0, did not respond within the timeout period.

Edit: As per point 2 above I've ran CrystalDiskInfo and all drives are showing ok as per pic below.


https://www.dropbox.com/s/dujtk123q2sh7l4/Screenshot 2014-03-02 07.56.46.png
 
Is an odd one.

With procexp make sure you run as Admin and then enable the lower pain (View, show lower pain), then when you click on the processes you can get the handle or dll info, might give more info as to what is going on.
You can also right click, properties the processes and check the tabs.

Also try procmon but make sure you filter by which ever processes you are interested in, other wise you just get a fast moving wall of info as it will show a lot of information about what is going on.

If you really want to get into the thread and stack level, download the Windows debug tools and set them all up to use Symbols, makes it a bit more readable instead of the normal memory addresses and offsets you get with out them.

It may also be worth using procexp to take a dump of the process, then open a thread over on the Technet forum and see if someone there can analyse it for you.

I've run the odd memory dump through Windbg to analyse BSODs but this is something I'd normally pass off to MS support as I tend to start getting myself lost poking around memory address and threads trying to track these things. :confused:
 
chaosophy said:
Is an odd one.

With procexp make sure you run as Admin and then enable the lower pain (View, show lower pain), then when you click on the processes you can get the handle or dll info, might give more info as to what is going on.
You can also right click, properties the processes and check the tabs.

Also try procmon but make sure you filter by which ever processes you are interested in, other wise you just get a fast moving wall of info as it will show a lot of information about what is going on.

If you really want to get into the thread and stack level, download the Windows debug tools and set them all up to use Symbols, makes it a bit more readable instead of the normal memory addresses and offsets you get with out them.

It may also be worth using procexp to take a dump of the process, then open a thread over on the Technet forum and see if someone there can analyse it for you.

I've run the odd memory dump through Windbg to analyse BSODs but this is something I'd normally pass off to MS support as I tend to start getting myself lost poking around memory address and threads trying to track these things. :confused:
Click to expand...

Thanks for the further info, I've downloaded and installed ProcMon and turned on the lower pane in Process Explorer so if it happens again hopefully I might get a bit more info to go on. I'm hoping I don't have any more issues but I'm also kinda hoping it does happen again so I can see if I can get to the bottom of the problem :) (Holding out for the first option however).
 
Just reporting back that so far the problem hasn't happened again. Seems strange that it should subside again, maybe it will return like it did nearer the end of the week, into the weekend.
 
Finally had enough last night and re-installed Windows 7. Don't have much installed at the moment, doing Windows updates, but I'm hoping the issue is a thing of the past.
 
You must log in or register to reply here.
Back
Top Bottom