On Fri, 31 May 2002 01:12:19 -0400 "D. Olson" <[EMAIL PROTECTED]> wrote:
> CPU 1: Machine Check Exception > Bank 0: b200008000000800 > Bank 1: c200000000080a01 > Kernel Panic: CPU context corrupt > In interrupt handler - not syncing > > > Alan Cox had this to say on the matter: > > "If your cpu context corrupt is with a machine check exception report > then your processor took an internal fault reporting trap. So its not > a happy bit of silicon I suspect - be it overclocked, overheated, or > even faulty." > > > > Now, the trouble is, it is a dual PII 333MHz system, and I don't > overclock it and it has been working fine before this for a few > months. It's uptime was around 30 days when this happened. > > What is the cause of it? Just too much heat? It seems weird that it > would happen right now... I know people who have servers that run > forever without this kind of problem... And your other CPU probably will. The first 30 days are the time when hardware has the greatest chance of failure. After that the failure rate levels off and doesn't spike again until expected end of life. Think of it this way. Since yours blew in thirty days ...... hundreds of other CPU's will keep on running. Unfortunately you got the one. I realize this is no consolation but it's true. If you can take it back do so fast. Then on the next one. Use enough heat compound. A really good fan.... and feel safe that it probably won't happen again. If it does.... You've probably got a Mobo problem. However this kind of failure is very rare. James > >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
