Timeline for Windows 7 gets stuck with ~1% CPU. Especially with multithreading
Current License: CC BY-SA 3.0
16 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Oct 10, 2012 at 12:55 | answer | added | Nelson Asinowski | timeline score: 1 | |
Oct 4, 2012 at 5:54 | history | tweeted | twitter.com/#!/StackSuper_User/status/253734851402924032 | ||
Oct 2, 2012 at 13:57 | comment | added | Amadeusz Wieczorek | Do you have an SSD? Since I've installed one, everything runs much smoother but occasionally I had a hiccup: the system would literally freeze for around 10 seconds. That could be either disk problem when OS needs to perform a kernel level disk operation or a motherboard issue. Mine is quite old, too | |
Oct 2, 2012 at 13:44 | history | edited | bwDraco | CC BY-SA 3.0 |
added 27 characters in body
|
Jul 2, 2012 at 20:34 | comment | added | Julian Knight | Re the % CPU, I don't think this is relevant. On my PC, running Process Explorer with other background tasks keeps the CPU at around 9%. | |
Jul 2, 2012 at 15:09 | comment | added | Martheen | Try plug an external HDD and process the files from there | |
Jul 2, 2012 at 12:23 | comment | added | James P | @meow: I would suggest that as a possible workaround you could try reducing the number of threads to 4. You might want to try turning off Hyperthreading in the BIOS - it doesn't have much benefit anyway. If you want to determine if the problem is with the machine or that particular software then you will need to be more specific about what other scenarios show the same problem. You could also try running the program in safe mode (if it will run) to see if some driver or background software is interfering. | |
Jul 2, 2012 at 12:06 | history | edited | meow | CC BY-SA 3.0 |
added info: process explorer pic
|
Jul 2, 2012 at 12:02 | comment | added | meow | By the way, I ran another check with Process Explorer; nothing is at the limits. CPU is flat, RAM is constant at e.g. 60%, I/O is flat, GPU is flat, network is flat, disk is flat. See this pic: minus.com/lbtjBN8RCsl7UV You see exactly where the process grinds to a halt. At first, 2 of the 8 threads continue working, then they die down too. | |
Jul 2, 2012 at 11:40 | history | edited | Sathyajith Bhat♦ | CC BY-SA 3.0 |
edited title
|
Jul 2, 2012 at 10:41 | comment | added | M'vy | Hum, readings on the internet say CPUTIN is rarely accurate. If the cores would have hit 90C+ this would have been a problem. Anyway, I would run some air in the PC first, just to rule out that possible cause. | |
Jul 2, 2012 at 10:13 | comment | added | meow | Also interestingly, the high max numbers show up only for CPUTIN and AUXTIN. The temperatures of the 4 cores themselves have the max around 60°C. | |
Jul 2, 2012 at 10:12 | comment | added | meow | Hm... I don't know. With HWMonitor I see the CPU temp constantly around 45°C, but the max shows very high numbers ~90-120°C even when I clear the max... However I never see high numbers in for the current temperature. Could it be that the CPU creates very short temperature spikes and immediately "shuts itself down" again? | |
Jul 2, 2012 at 9:09 | comment | added | M'vy | Any Temperature problem? | |
Jul 2, 2012 at 9:07 | comment | added | meow | Update: I ran the Windows memory check and the memory seems to be fine. To me, it "feels" like there is some conflict where everything starts waiting for something the system should do and it doesn't... | |
Jul 2, 2012 at 8:09 | history | asked | meow | CC BY-SA 3.0 |