[identity profile] hoffman-log.livejournal.com posting in [community profile] techrecovery
So here's my problem. I've never had to post one to this place before, because between several Microsoft and CompTIA certifications, one would assume i know my (stuff). But this is driving me nuts.

Problem: The computer will suddenly freeze up, nothing will work. This means mouse and keyboard fail, and the sound suddenly quits. It simply LOCKS. Only solution is to shut off the power and restart.

For a while i thought it was thermal related, but this couldn't be it, because when i reboot (a whole three seconds later) it works fine. Oh, as far as suggestions go, "Take it back to the manufacturer" isn't really an option, i techincally AM the manufacturer (built everything myself from scratch. go me!)

Specs: This should be helpful, maybe... ABIT KR7A-RAID 266MHz FSB, AMD Athlon 1800+, 256MB PC2300 (i think) DDR ECC RAM, Windows XP Pro, and if there's anything else you would like to know, let me know.

All right. Problem submitted to the think-tank. Let's see what it generates...

_MaH

Date: 2003-01-14 01:49 pm (UTC)
From: [identity profile] nix.livejournal.com
update the BIOS yet? I had to do that when I got my ABIT KR7A board...

Date: 2003-01-14 01:58 pm (UTC)
From: [identity profile] diji.livejournal.com
You seem to indicate that for a period of time, the system was working normally. If so, what has changed between the time it was all working, and the time it wasn't? Have you possibly added new hardware or software? Were there any intermittant problems before than might have led up to this?

If it hasn't worked... possibly bad hardware combination?

Date: 2003-01-14 02:08 pm (UTC)
From: [identity profile] diji.livejournal.com
You might try booting into Safe Mode and then just operating the system as close to normally as you can in those conditions... if it works fine after it would have normally failed, then its an extended driver or piece of software.

Alternately, you could zap everything out of your start up folder, as well as all the stuff in the run part of the registry (HKEY_CURRENT_USER\Software\Windows\Current Version\Run) and see if the problem occurs. :)

Happy hunting.

Date: 2003-01-14 04:21 pm (UTC)
From: [identity profile] alacrity.livejournal.com
Generally water cooling systems are only necessary if one is overclocking. Are you presently, or have you in the past, overclocked? That can cause a very small amount of damage to hardware that could result in a slightly higher incidence of fuzzy bits (bits in memory, or in computations that come out in the grey area and are interpreted incorrectly, yes, I just made up the term "fuzzy bits" as I'm not actually sure what the real word for this is.)

Also, if you are presently overclocking, it is quite likely you've simply pushed it too far and it is not at a stable speed. In which case, slow down! ;-)

A few basic troubleshooting questions:

Date: 2003-01-14 01:59 pm (UTC)
From: [identity profile] synthe.livejournal.com
When did this start happening?
Did you or anyone else change anything around that time?
What other troubleshooting have you tried?
Have you tried WinXP Safe mode? Clean boot?
Tried removing non-essential hardware?

Re: A few basic troubleshooting questions:

Date: 2003-01-14 11:20 pm (UTC)
From: [identity profile] tjernobyl.livejournal.com
I had a random lockup problem for quite a while as well, often triggered when I moved the mouse. One of the standoffs on the case had been installed incorrectly and would occasionally contact one of the pins on the back of the motherboard. As the mouse was right next to the case, sometimes the movement would do it. Other times I could smack it and be just fine. Mechanical fluke..

Date: 2003-01-14 02:09 pm (UTC)
inahandbasket: animated gif of spider jerusalem being an angry avatar of justice (Default)
From: [personal profile] inahandbasket
so this started happening after you rebuilt the machine?
I had similar issues going on with my mcahine at one point.
It turned out to be one of the RAM chips which was very slighly flaky. Took it out, everything was fine.
If you have a spare HD, try swapping that in and see if it works fine for a few days. if so, it's software. if not, check your ram.

just some thoughts.

Date: 2003-01-14 02:14 pm (UTC)
From: [identity profile] diji.livejournal.com
Its possible it could be cache as well... although not likely.

Date: 2003-01-14 02:17 pm (UTC)
inahandbasket: animated gif of spider jerusalem being an angry avatar of justice (Default)
From: [personal profile] inahandbasket
yeah, i'd be pretty shocked. But anything's possible however unlikely.
;o)

hardware troubleshooting

Date: 2003-01-14 02:37 pm (UTC)
From: [identity profile] chupchup.livejournal.com
While it's too early to rule out software problems, you need to completely rule out hardware problems before you can even begin to look at software causes. So swap out each of the hardware components, one at a time, and give it a good stress-test until it crashes again. Some of these (disk, RAM, video) can be tested with good diagnostic software--you may or may not get the right answer from diagnostics, but you may at least be able to reproduce the problem consistently!

Offhand, it sounds like you might have a faulty CPU. I had similar problems with an Athlon/KT-133 system which would hang only while I was playing a certain game--and would be fine after a reset/power off--but when I was testing some other components on an ASUS motherboard (also KT-133-based) at a friend's place and brought these home, the ASUS motherboard wouldn't even boot with my Athlon in place! When I swapped it out for a Duron 750, it ran fine, and the game ran without hanging! I'm still investigating an RMA for the faulty Athlon 1100...

Date: 2003-01-14 03:48 pm (UTC)
From: [identity profile] greeklady.livejournal.com
To me this is screaming an overheating problem, AMD is known for heat issues. But try the safe mode thing mentioned above... I am currious. Please post results.

Re:

Date: 2003-01-14 05:13 pm (UTC)
From: [identity profile] greeklady.livejournal.com
I didn't look at the specs too much. Do you only have one chip? I would test with whatcha got.

I have seen stranger things with ram so it wouldn't surprise me if it was.

Date: 2003-01-14 07:53 pm (UTC)
From: [identity profile] wildkard.livejournal.com
All I can recommend at this point is that if you think it's termal; even casually.... install motherboard monitor or something that equally reads your heat sensors (your motherboard *does* have sensors right? yeah, a KR7A should.) and be generating a log. I've known a few systems that cooled off fast enough once they weren't generating additional heat.

*sigh* Other than that... it's a stumper. Good for hours of sitting around in safe and limited device profile modes and seeing if you can pinpoint what in XP is crashing it. :/

Date: 2003-01-16 11:08 pm (UTC)
From: [identity profile] geam.livejournal.com
How many watt power supply?
How many hard drives?
How many CD-ROMs.
Are your speakers powered through your sound card?
Is your monitor powered through your power supply? (Note: I do not mean _by_ the power supply.)

Normally a computer will restart randomly if too much power is being drawn, but it could also lock up. You said you were changing tracks when it froze up one time -- does it normally lock up when you do that?
If so, are you playing media from a CD-ROM?
Also, what type of mouse?
If USB, how many other USB devices do you have?

Just some questions to make you think.

Profile

techrecovery: (Default)
Elitist Computer Nerd Posse

April 2017

S M T W T F S
      1
2345678
91011121314 15
16171819202122
23242526272829
30      

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Mar. 19th, 2026 11:06 pm
Powered by Dreamwidth Studios