Discussion Locked

intermittant lockup

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Every few minutes my cursor locks up. I have removed software added shortly before this problem appeared. I deleted all temp files and all cookies. This reduced the problem somewhat but I am still having occasional problems. I have never experienced this problem before and am totally lost. One recent change is I upgraded my processor to a 500Mhz AMD K6-2 from a 350Mhz AMD K6-2. Can a defective processor cause this type of problem? Any comment would assist me.

J. Gerald Jung
gerryj@onebox.com

7 replies

by albert franco ii

Some things to check: (sorry if some seem obvious to you, but for others they're not...)

1) Check for a virus or trojan that is robbing cycles to do its dirty work.

2) Check in the system properties tab for any devices with problems. One of the drivers may be having trouble with the new configuration. (System icon in the control panel.)

3) Put the old processor back in and see if the problem disappears.

4) Did you change any BIOS parameters other than CPU speed with upgrade. (Memory speed or timing, etc.) This assumes that you are using the same motherboard. If the motherboard was changed too, then reinstall Windows because it probably got all the board related drivers screwed up.

5) Make sure all of the internal connections and boards are tight.

If these don't solve the problem then you need to use a system spying tool to see all of the running threads on the machine and determine which one is hogging the CPU when the cursor blocks up. This is actually related to the first and second suggestions--virii, trojans, and drivers...

Good Luck,
Al Franco, II

by admin

An AMD k6-2 500 runs much hotter than a 350.
I have seen this a lot and it's often due to heat. If you didn't put a bigger fan on -get one and do so. Also, you can get away without heatsink compound on a 350 -not so on a 500.
If you want a cheap easy test to see if this is it, set your motherboard back to 350Mhz (underclock it) and run it for a couple of days, if the problem goes away, this is it. I highly suspect this is it, especially if it happened with the hardware change.

This discussion is closed to new replies.