Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?

To: peter michaelson who wrote (3362)	11/2/1998 5:46:00 PM
From: Spots	Read Replies (1) \| Respond to of 14778

>>The instruction at "0x5f412f6e" referenced memory at "0x00000000". You have two major problems, the first being your idiotic ideas about me, in every listed category; the second being your hardware. I can't help you with the former problem. For the latter, you're probably out of luck too (because of your error in judgement in the former), but I have some guesses: You have a memory hardware failure, caused maybe by ... You have your motherboard timings set too aggressively for your memory/mb/chipset capabilities. These can show up long after the settings because of gradual deterioration of various things (such as some of the following). You need to reseat your simms (dimms). You have ignored all the good advice about adequate cooling on this thread. You bought cheap memory and the connections are aging, so the resistance goes up and ... (many possibilities -- weak signals, longer time constants, blah, blah). You have MIXED memory types/speeds in a motherboard that can handle them but is iffy (if it couldn't handle them, you would have failed sooner), or that can't handle the gradual progression of something out of spec. Your motherboard has failed, or repeat the memory ailings above. Your chipset has been bombarded by too many cosmic rays emanating from your excessively brilliant stock trades. I would go on, but you get the idea. There are just any number of things that could cause this, but they are 99.99% hardware related. In MY case (yes, I have had this problem), I had set the bios memory timings too aggressively. I toned 'em down and the ol' server perked up. I should've just overclocked the momma <gg>. Spots PS. I hope someone else answers. I don't deserve the epithets.