Leonardo T. de Carvalho wrote:
> Dan Swartzendruber wrote:
>
>
>>none of this explains why he is freezing though.
>>
>
> Yup, when the memory is not properly recognized , the system
> hangs at random times...
> I've seen this, mainly on SiS mboards..
> =o(
>
>
Thank you!
And correct. If the memory is there, and not properly configured, things
can get "goofy". I had a machine do this to me. Spent most of a week
trying to figure out what was wrong.
I had another box just hang KDE after adding memory to it. I never
understood why, but the only thing that fixed it was blowing away the
.kde directory, and .kderc. Then it would come up.
Also, the original poster mentioned that Windows had booted. If so, then
check the memory in Windows to see if:
1) It's recognizing ALL of it (or only some of it).
2) If it's flaging some of it as bad.
if it's not recognizing it all, then there is another problem. I was
looking for information, not giving a solution until we know the extent
of the problem, and do a little diagnosing.
Ric
