Hi
I dnt know wat happened but my Workstation keeps on shutting down After every 20 min. I dnt know wat to do abt it??????
![]() |
|
| Forums Blogs Tips Articles Screens Polls | |
Shutting down Submitted by emylawson on Thu, 2008-04-03 08:39.
Thu, 2008-04-03 09:54 As far as I know there are
As far as I know there are two possibilities: 1) You have some virus or other malware. Not likely, because nowadays most of these don't try to be annoying anymore, they try to stay hidden instead to use your computer for the purposes of the creator of the virus. Also, you recently reinstalled, and installed a virus scanner... so really not likely. 2) Hardware failure. You already complained about the internet connection, now another component may have become faulty as well. How old is your computer? Things to check: Is the fan you can see in the back side of the computer spinning? If not, you need a new power supply. What is the processor temperature after the computer has been switched on for a while? You can check this using software, I don't know how to do that in windows though... look around in the control panel, I expect you will find it somewhere there. Is there a lot of dust inside the computer? (WARNING: don't just try to clean that out with a piece of cloth or a vacuum cleaner, you might damage both your computer and yourself). I guess it might be time to buy a new computer Thu, 2008-04-03 10:06 I keep having to move your
I keep having to move your topics. As for the question, not much for me to add in addition to what Taco said up there. Just a note though, I don't think Windows XP has a CPU temperature program anywhere. You'd have to install one. There are some notes here. It's also remotely possible that your installation is simply corrupt. It might be rare, but it can happen. I know, for instance, a GNU/Linux distribution which is so sensitive to that kind of stuff that you feel like walking on eggshells while burning (sidux, they use high compression). Windows might not use high compression, but that still doesn't entirely remove the possibility that something wasn't copied properly, even though it installed, and that it's now causing weird behavior like these shut downs. Cheers Fri, 2008-04-04 11:25 high compression???
It's also remotely possible that your installation is simply corrupt. It might be rare, but it can happen. I know, for instance, a GNU/Linux distribution which is so sensitive to that kind of stuff that you feel like walking on eggshells while burning (sidux, they use high compression). Windows might not use high compression, but that still doesn't entirely remove the possibility that something wasn't copied properly, even though it installed, and that it's now causing weird behavior like these shut downs. High compression makes the damage caused by a flipped bit worse, but on the other hand it makes the probability of such errors lower because there simply are less bits to flip. And a good installer has error detection (checksums and the like)... Anyway, that kind of problem is unlikely to cause a crash that happens after 20 minutes (although it might). It's much more likely to cause much weirder behavior, or nothing noticeable at all. As for sidux, I don't think your problems with it are caused by high compression. The software they distribute is simply not very well tested. Sat, 2008-04-05 00:37 sidux wrote:
As for sidux,
As for sidux, I don't think your problems with it are caused by high compression. The software they distribute is simply not very well tested. Actually.. I've been on their channel when I was burning it and they specifically say that it has to be burned Disk-At-Once (or Session-At-Once) and at slow 8x speed due to very high compression.. They have this in their topic and on their site as well. Sidux is actually supposed to stabilize sid. Sat, 2008-04-05 19:22 deb file format
As for sidux, I don't think your problems with it are caused by high compression. The software they distribute is simply not very well tested. Actually.. I've been on their channel when I was burning it and they specifically say that it has to be burned Disk-At-Once (or Session-At-Once) and at slow 8x speed due to very high compression.. They have this in their topic and on their site as well. Sidux is actually supposed to stabilize sid. OK I did some research on the deb package format... What surprises me (and yet doesn't because I already knew but forgot) is that the deb file format doesn't contain checksums like the rpm format does. How inconvenient, that way there is no way to notice at installation time your cdrom actually is a coaster. Unless the checksums are kept elsewhere (a md5sums file next to all the packages on the cd?), of course. Which they apparently aren't, otherwise that advice about careful burning would be unnecessary. Rpm has rpm hell, and apt/dpkg/deb has no verification... so both popular package management systems have design flaws? Huh, who would have thought that. EDIT to add: Actually both in "low" gzip compression and in "high" compression like lzma, a single flipped bit will lead to disastrous results. I get the impression the sidux folks are a bit confused... looking at their homepage... Oh. THIS IS VERY IMPORTANT: sidux, as a Linux LIVE-CD, is based on high compression technology, and because of that, special care is needed when burning the ISO image. Only use high quality CD-media [or DVD+RW] and burn in DAO-mode (disk-at-once) and not faster than x8. Note the words "LIVE-CD". It's not about installers and the compression of packages at all. Naturally a faulty live-cd cannot check itself and tell you it's corrupted, like an install cd (usually) could. Who's onlineThere are currently 0 users and 15 guests online.
|
User loginNew on forums
Recent blog posts |
Joined: 2008-03-26