Problem with freezing in XP Professional

MrBleeble

New Member
First of all hi guys, I am a n00b here :)

Here is my problem. I have windows XP Pro and if I leave it for say 20 minutes some of the time when I get back it will be all weird and either nothing happens when you right-click or click on an icon, or the cursor/icons dissappear, or the screensaver freezes up, or the mouse cursor is really jerky and laggy and I can't click on anything. This happens whether the computer is on screensaver or on the desktop or locked.

The problem occurs less frequently when msn messenger is closed, and happens a lot when bittorrent is open as well.

Obviously this is a big problem when I am trying to download things as I cannot leave the computer :(

my power saving is set to monitor off after 20 minutes, hard disc off after 2 hours (but the problem happens long before this) and hibernate off

I wonder if anyone can shed any light on this?

Thanks guys!
 
In the power saving settings it's not a good idea to turn off the hdd because the lifetime of a harddisk depends mostly on power-on/power-off cycle numbers.
As for the freezing, I think is a RAM issue. You can check it with memtest.
 
when it freezes is probably your hardrive going back to power on mode from off mode cuz of the power saving feature.
 
I have tested it with memtest86, I left it for an hour and it gave 5 "passes" with no errors....

so I don't think it's the RAM.


Also I can use it for like 10 hours without a single freeze/crash but it's only as soon as I leave it when it screws up!
 
My friend had the same problem, We suggested to him to get more RAM he had 64mb, that's why it always froze, you need atleast 256mb for xp........but that's probably not the problem you have. :)
 
Another kind of computer freezing

I also have a problem with a feezing XP.

I think is hardware (I already formated the partition and re-install XP).

I changed IDE ribbons, checked electrical contacts at HDD, changed the video card, there isn't anything over-clocked, the teperature is OK...

When I put him to do something, like a completly scan with Northon AntyVirus, it completly feezes - just the reset button still works. This happens after a while, couple of minutes after the begining of the scan.

Anybody with an ideea? PLS
 
Zomby said:
I also have a problem with a feezing XP.

I think is hardware (I already formated the partition and re-install XP).

I changed IDE ribbons, checked electrical contacts at HDD, changed the video card, there isn't anything over-clocked, the teperature is OK...

When I put him to do something, like a completly scan with Northon AntyVirus, it completly feezes - just the reset button still works. This happens after a while, couple of minutes after the begining of the scan.

Anybody with an ideea? PLS

I agree with Lorand, Probably defective memory :o
 
Yes, but what could be the problem in MrBleeble's computer? He checked the RAM and it's ok. Disabled the power management and still the same...
 
I'l change computer's source.

If that doesn't work I will tray with another memory DIMM. But this is odd because it happened suddently, after I tried to over-clock my video card with coolbits. First I thaught that is because of over-clocking, then because of registry changes.

Thanks
 
right-click or click on an icon, or the cursor/icons dissappear, or the screensaver freezes up, or the mouse cursor is really jerky and laggy

Hi the solution is processor heating up.
Open your case and make sure the fan on the cpu is turning.
Get a can of compressed air and blow out the fan.



www.apluscr.com
 
Lorand said:
Sounds like bad memory, overheating CPU or defective power management.

If you were talking to me, I think I already ruled all those out.

The weird thing is, if I run winamp and leave it for like 6 hours with winamp playing a song, it won't freeze up....I did this yesterday while I was downloading something....

anyone got any ideas?
 
Last edited:
Go to Control Panel \ Performance & Maintenance \ Adminstrative Tools \ Event Viewer \ System and see what process started before the freeze.

Sounds like bad memory, overheating CPU or defective power management.
If you were talking to me, I think I already ruled all those out.

Actually that post was a reply for Zomby's problem.
 
Back
Top