PC trouble: Problem fixed! New question, page 5.
#41
Senior Member
Posts like a Northstar
Join Date: Jun 2006
Location: Waukesha, Wisconsin
Posts: 747
Likes: 0
Received 0 Likes
on
0 Posts
it looks to me like you have something running silently in the background churning up all your CPU....go to run command and type MSCONFIG and go to the STARTUP tab.
Anything look suspicious there? Is it possible to post it? Spam or spyware can reside there in the startup. If you are not sure about something, Google it and find out what it is. That always works for me. If it is bad stuff, you should also be able to find out how to remove it. Task Manager has the same files, but if you End Task there, they will just return at the next startup. You can uncheck the file in the System Configuration Tool (MSCONFIG) and it will not come back unless you check it again.
In short, your issue could be a software problem or hardware problem. You never know unless you work at it. Sorry
Anything look suspicious there? Is it possible to post it? Spam or spyware can reside there in the startup. If you are not sure about something, Google it and find out what it is. That always works for me. If it is bad stuff, you should also be able to find out how to remove it. Task Manager has the same files, but if you End Task there, they will just return at the next startup. You can uncheck the file in the System Configuration Tool (MSCONFIG) and it will not come back unless you check it again.
In short, your issue could be a software problem or hardware problem. You never know unless you work at it. Sorry
#42
Well that SMART data looks ok...I'm definitely thinking memory now. Go along with john'* idea of remove one, test, repeat. might just be a dying memory module or just one of the chips is bad and the computer is trying to sort around it. do you ever get "memory cannot be read" error messages?
#44
Senior Member
Posts like a Turbo
Join Date: Oct 2006
Location: Kansas City, MO
Posts: 319
Likes: 0
Received 0 Likes
on
0 Posts
Just for a laugh, you might check this as well:
http://www.bonnevilleclub.com/forum/...hlight=desktop
http://www.bonnevilleclub.com/forum/...hlight=desktop
#45
Senior Member
True Car Nut
Thread Starter
Originally Posted by BLACK94SSEi
Yeah, Uh I suggested removing a memory chip and rebooting too but I guess it wasnt on the top of the to do list.
#46
Senior Member
True Car Nut
Thread Starter
Here is a view of my startup tab... it couldn't be resized to fit the whole thing on the screen, so first pic is top of the list and second is bottom of the list.
See anything weird? All looks normal to me, except for that blank line. That'* been there for a while, but I don't know how to get rid of it.
See anything weird? All looks normal to me, except for that blank line. That'* been there for a while, but I don't know how to get rid of it.
#47
Senior Member
Certified Car Nut
Join Date: Jul 2003
Location: Robbinsdale, MN
Posts: 15,408
Likes: 0
Received 0 Likes
on
0 Posts
There'* a couple on there that I might get rid of just because I don't like them (auto update checkers), but nothing suspicious or that should cause the symptoms you describe. I hate those blank lines, too, but they require you manually dig through the registry to track them down.
You stated you have a new(er) power supply, so I would move that way down the list as it should be OK...
Motherboard is difficult to test without a spare laying around, and then it has to be identical (to prevent windows from having to look for new drivers and such), so I would save that for last...
HD read fine by the tests suggested...
So, we're back to the physical memory like BLACK94SSEi and I suggested.
Since you mentioned it was during the initial windows boot (the little wavy bar), if I remember correctly, we have to lean towards a potential hardware issue
You stated you have a new(er) power supply, so I would move that way down the list as it should be OK...
Motherboard is difficult to test without a spare laying around, and then it has to be identical (to prevent windows from having to look for new drivers and such), so I would save that for last...
HD read fine by the tests suggested...
So, we're back to the physical memory like BLACK94SSEi and I suggested.
Since you mentioned it was during the initial windows boot (the little wavy bar), if I remember correctly, we have to lean towards a potential hardware issue
#50
Senior Member
Posts like a Turbo
Join Date: Oct 2006
Location: Kansas City, MO
Posts: 319
Likes: 0
Received 0 Likes
on
0 Posts
"Motherboard is difficult to test without a spare laying around, and then it has to be identical (to prevent windows from having to look for new drivers and such), so I would save that for last... "
Actually, if it'* an OEM PC (Windows Preinstalled), you have to buy either:
1) The replacement motherboard from the OEM
2) or a new copy of windows
Even putting in a new CPU will disable windows, and the OEM will not give you the codes you need to reactivate windows if you swap motherboards/put in a new CPU.
The only exception to this is is you have a volume license installed, which I've yet to see outside of a corporate environment.
Actually, if it'* an OEM PC (Windows Preinstalled), you have to buy either:
1) The replacement motherboard from the OEM
2) or a new copy of windows
Even putting in a new CPU will disable windows, and the OEM will not give you the codes you need to reactivate windows if you swap motherboards/put in a new CPU.
The only exception to this is is you have a volume license installed, which I've yet to see outside of a corporate environment.