• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

XP-m OC strange problems

E

evilpenguin81

n00b
Joined
Jul 7, 2004
Messages
6
I'm having a bit of a system problem and I wanted to find out if it could be OC related. I figured this would be the place to ask :)

My HTPC will randomly lock up for anywhere between 10 seconds and 1 minute. I can't move the mouse, all my MBM and Task Manager Logging files stop logging, and any show being recorded at the time will have a gap in it. Then after a little time, it just starts working again like nothing happened. When I check event viewer, there isn't anything logged for the time of the lock up.

I worry the problem might be hardware related. Here's my setup

Xp-m 2500+ OCed to 2 ghz 166 x 12 (idle 40C load 52C, vcore 1.50V-1.52V)
512 mb PC2700 Ram
Abit NF7-S mobo
PVR 250
Geforce 2 MX400

The system seems stable enough, I ran prime95 for 5 hours and I never got any errors and the temps were never out of hand. And even stranger, I'm pretty sure I caught it hanging during prime95, and when the it stopped hanging, prime95 kept going without complaining.

I honestly can't figure it out. Its almost like the clock on my CPU just stops running for a minute, then starts up again. Could this somehow be related to some aspect of Overclocking, or is my culprit elsewhere.
 
well, first, I personally would set the overclock back to default and see if the problem still happens -- only then could you really start troubleshooting.

also, 5 hours is no where near enough time to prime95 a system. I see people saying they do 9-12 hours, and still that isnt enough, i've had overclocks fail after 16 hours -- I personally like to run it for 24 hours
 
I do prime 95 + UT2004 for 24 hours to ensure full stability and burn in. prime 95 just by itself doesnt seem to be enough anymore. The poster above mentioned failing after 16 hours. Thats happened to me so 5 hours is nowhere near enough to guarantee stability.

Streekid got it right. Go back to stock speeds and see if its fixed. IF its not I dont know where to begin fixing it.
 
This occurence strikes familiarity with me. I can't tell you exactly what your problem is, but I have experienced things that have a similar pattern/similar symptoms.

One such occurence I just solved actually one or two weeks ago. My system would hang for 1-2 seconds, but it would reoccur about every 4-15 seconds, over and over again. Sometimes it would not do it at all for hours perhaps, but inevitably my comp would have a run of constant freezes. They were similar to yours in that every single operation would cease. My task manager never reported high CPU loads so I couldn't isolate any program. They were short hangs, but were most obvious because if you ran your mouse around in circles it would intermittently stop and then continue.

First step, which is obvious enough, is to do a virus/spyware scan. However I assume you've all ready ruled this out considering it is not logged in your task manager.

So next, you simply just have to try and isolate the problem. Find out under what circumstances you can guarantee it happening, if any. And find any that you can guarantee it won't. If you know you will experience the problem once a day, or once per hour, at least, then start closing programs/disabling hardware to see if you can operate beyond that period of time without the hinderance.

My issue turned out to be hardware related - my 802.11g card to be specific. I always had it running, set up for a preconfigured Ad-Hoc network and "Waiting for Peer...". The problem would continue even if I turned the card off (per the wireless manager's "Radio Off" button). I found out exactly what my problem was when I went as far as to disable the device entirely in my Network Connections view. I had to actually disable the hardware to get it to stop. It wasn't enough that I closed all programs associated with the device and turned its radio off, keeping it from making any connections.

My guess would be that your problem is similar, meaning that it is a hardware problem on that level. If you really cannot stop it, I would go so far as to remove your PCI cards. If you find which one does it, the problem might be alleviated by swapping PCI slots.

Sorry for the long response. Good luck.
 
i had a lockup problem like that too... ramped clock speed on my cpu before it got a chance to burn in enough... guess 2.5 was a lil too much for a outa box cpu 12x166 should run on any barton... bartons almost allways do 200x12 lol

hey check to see if the north or south bridge is getting too hot.. i have problems like that when i try to go to 2.7 ghtz... i need more cooling..
 
hey i just remembered somthing... could it be your hard drive? check the system log.. if it the hard drive theres gonna be a lot of warnings... had to rma my barricuda because it failed and did such a thing... the drive kept resetting itself
 
Run at stock speeds , if it still occurs unplug everything not 100% required to boot ur system. IE just one hard drive & Vid card only. No CD drive, no secondary drives, no floppy, no PCI cards at all. If it is then stable you can try adding each device one by one till the problem occurs again.
 
You must log in or register to reply here.
Back
Top