|
CPU reaches 100% with nothing running in clean win7 install
|
|
|
jam320
Newbie
|
9. December 2012 @ 13:48 |
Link to this message
|
For several months I have tried to determine the sluggishness of my cpu after a clean win7 64 install. Here is some background:
SPECS:
Core 2 Quad Q6700 @ 2.66GHZ
Intel DG35EC
Corsair 4X2GB DDR2
Hitachi 1TB | WD Ext 1TB
Geforce 9600 GSO 768MB
NZXT HALE82 650W
Win7 Home Prem 64 | Vista Business 32
This win7 home prem sp1 64 OEM was previously working fine for over 6 months then things went weird. By weird I mean that a normal boot would take several minutes to reach the desktop. Booting in safe mode did not change the length of time either. Another thing that occurred was my desktop background went black. I read somewhere that suggested I create a new desktop profile and this would fix things. I did not. I cannot be certain of the cause of this but I recall two events that may be related.
(1) I had a laptop die around this time so I was going to transfer its hdd contents to the desktop. I connected it via SATA to my MOBO. However upon bootup win7 did not recognize it. Could this have corrupted something? I ran SuperMalwareBytes but it turned up nothing.
(2) I windows update occurred around this time. With my MOBO and CPU being outdated is it possible that they are not compatible up to a certain update? I currently am running Vista 32 on the other partition with no problems.
I decided to reinstall win7 on the partition however this did not solve the problem either. The new install was still sluggish and at time almost unresponsive e.g. the cpu would be at 65% and higher just running Firefox while my 8GB of ram read <40%.
I then decided to reformat the partition first and then install it. Again this did very little. I currently have that one installed and have installed of the win updates since. I ran memtest86 and passed. I installed process explorer but could not identify a specific area that had an abnormal consumption rate.
Any advice would be great. Thanks!
|
|
Advertisement
|
|
|
|
|
ddp
Moderator
|
9. December 2012 @ 15:20 |
Link to this message
|
task manager showing 8gigs of ram in win7? do you have or can borrow a spare hd to fresh install win7 to see if still a problem. do a scandisk on the hd to check for errors as maybe bad sectors on win7 side but not on vista which is why i asked about another hard drive.
|
|
jam320
Newbie
|
9. December 2012 @ 17:38 |
Link to this message
|
Originally posted by ddp:
task manager showing 8gigs of ram in win7? do you have or can borrow a spare hd to fresh install win7 to see if still a problem. do a scandisk on the hd to check for errors as maybe bad sectors on win7 side but not on vista which is why i asked about another hard drive.
I have an external hdd I can try this on. I will first run scandisk. I will report back with the outcome. Thanks.
|
|
jam320
Newbie
|
9. December 2012 @ 18:14 |
Link to this message
|
Originally posted by jam320:
Originally posted by ddp:
task manager showing 8gigs of ram in win7? do you have or can borrow a spare hd to fresh install win7 to see if still a problem. do a scandisk on the hd to check for errors as maybe bad sectors on win7 side but not on vista which is why i asked about another hard drive.
I have an external hdd I can try this on. I will first run scandisk. I will report back with the outcome. Thanks.
I used scandisk on that partition from the vista side and no errors were reported. Should I still consider using another hdd?
|
|
ddp
Moderator
|
9. December 2012 @ 18:18 |
Link to this message
|
yes with the hitachi drive disconnected.
|
|
snotboy1
Newbie
|
12. December 2012 @ 10:49 |
Link to this message
|
Originally posted by jam320:
For several months I have tried to determine the sluggishness of my cpu after a clean win7 64 install. Here is some background:
SPECS:
Core 2 Quad Q6700 @ 2.66GHZ
Intel DG35EC
Corsair 4X2GB DDR2
Hitachi 1TB | WD Ext 1TB
Geforce 9600 GSO 768MB
NZXT HALE82 650W
Win7 Home Prem 64 | Vista Business 32
This win7 home prem sp1 64 OEM was previously working fine for over 6 months then things went weird. By weird I mean that a normal boot would take several minutes to reach the desktop. Booting in safe mode did not change the length of time either. Another thing that occurred was my desktop background went black. I read somewhere that suggested I create a new desktop profile and this would fix things. I did not. I cannot be certain of the cause of this but I recall two events that may be related.
(1) I had a laptop die around this time so I was going to transfer its hdd contents to the desktop. I connected it via SATA to my MOBO. However upon bootup win7 did not recognize it. Could this have corrupted something? I ran SuperMalwareBytes but it turned up nothing.
(2) I windows update occurred around this time. With my MOBO and CPU being outdated is it possible that they are not compatible up to a certain update? I currently am running Vista 32 on the other partition with no problems.
I decided to reinstall win7 on the partition however this did not solve the problem either. The new install was still sluggish and at time almost unresponsive e.g. the cpu would be at 65% and higher just running Firefox while my 8GB of ram read <40%.
I then decided to reformat the partition first and then install it. Again this did very little. I currently have that one installed and have installed of the win updates since. I ran memtest86 and passed. I installed process explorer but could not identify a specific area that had an abnormal consumption rate.
Any advice would be great. Thanks!
--------------------------------------------------------------------
#1 YOU NEED A HIGHER WATTAGE POWER SUPPLY at least least 800 watts
#2 DONT DUAL BOOT (MEANING THAT YOU HAVE 2 OPERATING SYSTEMS ON THE SAME HARD DISK,
get rid of vista, reformat the hdd with a single win 7 partition
#3 buy a new graphics card
#4 after you re-install win7 make sure you get the system drivers from intel
#5 if you are going to transfer the files from the external hdd ( laptop),dump them in
a directory in the root or the my documents folder
#6 the desktop is a special folder in windows and sometimes behaves weird for storeing
large amounts of data.
#7 did you enable all SATA ports in the bios?
#8 did you run some kind of hdd test on both drives?
#9 are you sure that the boot drive is on port zero of the system board both by physical cable connection and that the bios is set to boot to it?
#10 BUY ANOTHER POWER SUPPLY OF HIGHER WATTAGE
|
|
jam320
Newbie
|
12. December 2012 @ 14:19 |
Link to this message
|
Thanks for the advice. I'm not sure 800 watts is needed. My 650w is brand new (1 week old), I previously had a 400w for 4 years so that's not an issue.
Also why do you suggest a new gpu? I know its old but its worked fine so far. Currently the issues are resulting without it plugged in anyways (no drivers installed either).
I ran chdsk on both partitions as well as hdtuner; both passed.
I will check on the your other suggestions though.
|
AfterDawn Addict
|
12. December 2012 @ 14:47 |
Link to this message
|
You don't need a PSU with a higher wattage at all, not for that spec. If it is new, then we can hopefully rule out that it is faulty. GPU is unrelated to this issue IMO so you don't need a new one.
Why do you dual boot with Vista? A clean format of your drive and a fresh install of Windows 7 would be advisable despite no chdsk errors. Do you realise that your 32bit Vista OS will not be recognising all of your 8GB RAM, don't you?
What temperature does it sit at under supposedly 100% load? Does the machine overheat and shut off?
|
Senior Member
|
12. December 2012 @ 15:01 |
Link to this message
|
Originally posted by snotboy1:
Originally posted by jam320:
For several months I have tried to determine the sluggishness of my cpu after a clean win7 64 install. Here is some background:
SPECS:
Core 2 Quad Q6700 @ 2.66GHZ
Intel DG35EC
Corsair 4X2GB DDR2
Hitachi 1TB | WD Ext 1TB
Geforce 9600 GSO 768MB
NZXT HALE82 650W
Win7 Home Prem 64 | Vista Business 32
This win7 home prem sp1 64 OEM was previously working fine for over 6 months then things went weird. By weird I mean that a normal boot would take several minutes to reach the desktop. Booting in safe mode did not change the length of time either. Another thing that occurred was my desktop background went black. I read somewhere that suggested I create a new desktop profile and this would fix things. I did not. I cannot be certain of the cause of this but I recall two events that may be related.
(1) I had a laptop die around this time so I was going to transfer its hdd contents to the desktop. I connected it via SATA to my MOBO. However upon bootup win7 did not recognize it. Could this have corrupted something? I ran SuperMalwareBytes but it turned up nothing.
(2) I windows update occurred around this time. With my MOBO and CPU being outdated is it possible that they are not compatible up to a certain update? I currently am running Vista 32 on the other partition with no problems.
I decided to reinstall win7 on the partition however this did not solve the problem either. The new install was still sluggish and at time almost unresponsive e.g. the cpu would be at 65% and higher just running Firefox while my 8GB of ram read <40%.
I then decided to reformat the partition first and then install it. Again this did very little. I currently have that one installed and have installed of the win updates since. I ran memtest86 and passed. I installed process explorer but could not identify a specific area that had an abnormal consumption rate.
Any advice would be great. Thanks!
--------------------------------------------------------------------
#1 YOU NEED A HIGHER WATTAGE POWER SUPPLY at least least 800 watts
#2 DONT DUAL BOOT (MEANING THAT YOU HAVE 2 OPERATING SYSTEMS ON THE SAME HARD DISK,
get rid of vista, reformat the hdd with a single win 7 partition
#3 buy a new graphics card
#4 after you re-install win7 make sure you get the system drivers from intel
#5 if you are going to transfer the files from the external hdd ( laptop),dump them in
a directory in the root or the my documents folder
#6 the desktop is a special folder in windows and sometimes behaves weird for storeing
large amounts of data.
#7 did you enable all SATA ports in the bios?
#8 did you run some kind of hdd test on both drives?
#9 are you sure that the boot drive is on port zero of the system board both by physical cable connection and that the bios is set to boot to it?
#10 BUY ANOTHER POWER SUPPLY OF HIGHER WATTAGE
where did you get some of that drivel?try not to talk with a paper arsehole,this guy needs advice not bull..t.
|
|
jam320
Newbie
|
12. December 2012 @ 15:32 |
Link to this message
|
Originally posted by ddp:
yes with the hitachi drive disconnected.
UPDATE: I used an unused Hitachi internal 500gb to SATA. Win7 installed and updates are currently ongoing. Currently trying to install Symantec Endpoint Protection RU1 but it keeps failing. I decided to install 11.05 instead but that failed as well. Additionally, BSOD restarted my pc once (couldn't get the error code in time). Currently checking Intel drivers.
|
|
ddp
Moderator
|
12. December 2012 @ 15:35 |
Link to this message
|
|
at what point did you get that bsod, before or after symantec?
|
|
jam320
Newbie
|
12. December 2012 @ 15:47 |
Link to this message
|
Originally posted by Ripper:
You don't need a PSU with a higher wattage at all, not for that spec. If it is new, then we can hopefully rule out that it is faulty. GPU is unrelated to this issue IMO so you don't need a new one.
Why do you dual boot with Vista? A clean format of your drive and a fresh install of Windows 7 would be advisable despite no chdsk errors. Do you realise that your 32bit Vista OS will not be recognising all of your 8GB RAM, don't you?
What temperature does it sit at under supposedly 100% load? Does the machine overheat and shut off?
Thanks for the reply. I know 32bit Vista is not ideal but it was my backup for Win7.
As far as I know the temperature was only an issue when running a game at full specs and letting it idle for several hours (it did shutdown at least 2 times). I never checked the temperature though.
|
|
jam320
Newbie
|
12. December 2012 @ 15:50 |
Link to this message
|
Originally posted by ddp:
at what point did you get that bsod, before or after symantec?
After the failed install of Symantec.
|
|
ddp
Moderator
|
12. December 2012 @ 16:10 |
Link to this message
|
|
|
|
snotboy1
Newbie
|
12. December 2012 @ 18:17 |
Link to this message
|
i still think that a higher wattage power supply will eliminate a lot of weird problems.
u said you were running the game at full blast for several hours that makes the gpu suck up current. i DO take offense about that comment about my post as drivel, i have been a tech all my life and so i will not waste my time on this subject again.
|
|
ddp
Moderator
|
12. December 2012 @ 18:44 |
Link to this message
|
|
|
|
jam320
Newbie
|
13. December 2012 @ 09:44 |
Link to this message
|
|
UPDATE: Ran Prime95 overnight for the CPU with no errors. Currently it is sluggish still and update kb982670 failed (only one to fail so far). Will try it again.
|
Staff Member
|
13. December 2012 @ 10:25 |
Link to this message
|
Just to add a little bit of advice here, don't rely on Task Manager when you are looking for CPU usage or trying to find a memory leak or whatever. At least try Process Explorer as that can give you a much better picture of your system running.
http://www.afterdawn.com/software/syste...ss_explorer.cfm
I had a similar problem with a laptop a bit over a year ago, I noticed sluggish performance and the CPU usage seemed to go off the chart from time to time. In Process Explorer, to my amazement, it was Hardware Interrupts and DPCs that was showing often very high CPU usage, which I had never seen before, and it did have a noticeable effect on my system.
Shotgun approach of driver updates and a BIOS update from manufacturer seemed to fix it for me. I couldn't tell you exactly what the problem had been, just that it's gone.
|
Staff Member
|
13. December 2012 @ 10:30 |
Link to this message
|
Also, since you are running a 64-bit version of Windows, your odds of having some kind of rootkit/bootkit problem are dramatically lower than usual, but there's a few ways it can happen so running a quick check with tdsskiller might be a good idea anywauy..
http://support.kaspersky.com/5350
Other than that, if your problem coincided with the installation (or failed installation as the case may be...) of a security product, then you should go to the vendor's website and find a removal tool for that specific product, which will check your system for every trace of it and remove it for you. Just another thought :-)
|
|
jam320
Newbie
|
13. December 2012 @ 11:33 |
Link to this message
|
Originally posted by Dela:
Also, since you are running a 64-bit version of Windows, your odds of having some kind of rootkit/bootkit problem are dramatically lower than usual, but there's a few ways it can happen so running a quick check with tdsskiller might be a good idea anywauy..
http://support.kaspersky.com/5350
Other than that, if your problem coincided with the installation (or failed installation as the case may be...) of a security product, then you should go to the vendor's website and find a removal tool for that specific product, which will check your system for every trace of it and remove it for you. Just another thought :-)
Thanks. I ran a rootkit scan several weeks ago but it wasn't Kaspersky so it wouldn't hurt to try this one. I'm not confident that it will not crash during the scan though. Since this is currently occurring with each attempt to add win updates.
|
|
ddp
Moderator
|
13. December 2012 @ 12:25 |
Link to this message
|
|
do a system restore to before symantec was attemped to be installed.
|
AfterDawn Addict
|
13. December 2012 @ 13:04 |
Link to this message
|
|
If your CPU was actually sitting idle at 100% load, then surely it would be overheating and causing the machine to shut off - this is obviously not the case if you can run Prime95 overnight with no issues.
Try another monitoring program like Dela suggested, perhaps your CPU and/or Windows is reporting the load incorrectly.
|
Staff Member
|
13. December 2012 @ 13:05 |
Link to this message
|
Originally posted by jam320:
Originally posted by Dela:
Also, since you are running a 64-bit version of Windows, your odds of having some kind of rootkit/bootkit problem are dramatically lower than usual, but there's a few ways it can happen so running a quick check with tdsskiller might be a good idea anywauy..
http://support.kaspersky.com/5350
Other than that, if your problem coincided with the installation (or failed installation as the case may be...) of a security product, then you should go to the vendor's website and find a removal tool for that specific product, which will check your system for every trace of it and remove it for you. Just another thought :-)
Thanks. I ran a rootkit scan several weeks ago but it wasn't Kaspersky so it wouldn't hurt to try this one. I'm not confident that it will not crash during the scan though. Since this is currently occurring with each attempt to add win updates.
When you say crash you mean the comp restarts? If the system is blue screening then you might be able to get your answer from a crash dump analysis. Windows 7 will create a Kernel Memory Dump by default as %SystemRoot%\MEMORY.DMP
When the system BSOD's, that means something has called KeBugCheckEx in Windows after encountering a problem in Kernel mode memory. The system is immediately halted, and a crash dump is written to the page file (pagefile.sys). By default, once the dump is written the system reboots (unless you manually set it to keep the BSOD displayed), and on boot a small tool will launch in the background that searches the pagefile for a memory dump and then extracts it as a crash dump. This will be MEMORY.DMP in your system root drive. I could be wrong, but in Windows 7 I think it might still be default that a minidump is also written to the directory "%systemroot%\windows\minidump\" which, if it is, you can upload the latest dump somewhere and I can analyse it for you if you want.
But ye, given that you already attempted a re-install (full re-install, or repair?) your problem might not be caused by a bad A/V installation. Instead, to me it seems like it could be your memory. I think that because your problem is getting progressively worse, and that is typically what you will see with a failing memory module.
To test memory, you just need Memtest86 (or Windows has a diagnostic utility you can boot into too, but Memtest86 is very good).
Memtest86 Auto Installer for USB Key: http://www.afterdawn.com/software/syste...t86plus_exe.cfm
Memtest86 bootable ISO: http://www.afterdawn.com/software/syste...t86plus_iso.cfm
I assume you already know how to boot from USB or CD so I don't need to go into that? It will run a test immediately on your memory. ANY errors is a bad sign. If you find yourself picking up errors, then end the program, turn off the PC and open it. Remove a memory module and then turn it on again, boot into Memtest86 and check for errors. If you still get errors, then remove another one (if there's only one more left, then re-insert the previously removed memory) and repeat the process. By process of elimination you should be able to find the memory stick giving you trouble.
If you find there's nothing wrong with your system's memory, it doesnt change the fact that something is going wrong in kernel mode memory, if you are getting system halts. A possibility for a system halt is a problem with a hard disk drive, particularly if there is problems during a swapping operation. Go to Control Panel (view as large icon) -> Administrative Tools -> Event Viewer. In Event Viewer, go to Windows logs, and then System (it might take a short while to pull up the logs). Any Disk errors?
If no memory or disk problems, then it must be either some kind of bad driver or bad hardware attached to the system that is causing the problem. If its a driver, then we might be able to get the system to spit up a more accurate BSOD and crash dump using a tool called Driver Verifier, but we can cross that bridge if we come to it :-)
I'll leave it at that for now.
|
AfterDawn Addict
|
13. December 2012 @ 14:17 |
Link to this message
|
Dela,
Quote:
I ran memtest86 and passed. I installed process explorer but could not identify a specific area that had an abnormal consumption rate.
It would be worth checking your modules individually though, if you did not before.
|
|
Advertisement
|
|
|
Staff Member
|
13. December 2012 @ 14:26 |
Link to this message
|
Originally posted by Ripper:
Dela,
Quote:
I ran memtest86 and passed. I installed process explorer but could not identify a specific area that had an abnormal consumption rate.
It would be worth checking your modules individually though, if you did not before.
Somehow I completely missed that part of his original post :-) Oh well, though if the system is actually BSOD'ing then its still down to kernel memory, which points the finger at device drivers or perhaps something more malicious, or a malfunctioning piece of hardware is also possible but hard to tell from here. If a driver than the answer could lie in a crash dump on the disk.
|
