Things I had tried was, uninstalling and reinstalling SL with the new setup.
I really don't want to have to do a complete system reinstall of Windows AGAIN, when its not necessary.
Why why why why must SL be so dang difficult!!!!
Welcome to the Second Life Forums Archive
These forums are CLOSED. Please visit the new forums HERE
Constant Crashing After Adding New Ram |
|
|
Einsman Schlegel
Disenchanted Fool
Join date: 11 Jun 2003
Posts: 1,461
|
01-15-2005 13:33
Ok, so, now I have a fresh new set of 2gb of memory. I never experienced SL crashing on its own, usually if I had a problem, it was a system issue, not SL. But now, apparently its obvious SL has a HUGE memory problem when dealing with extensive amounts of memory.
Things I had tried was, uninstalling and reinstalling SL with the new setup. I really don't want to have to do a complete system reinstall of Windows AGAIN, when its not necessary. Why why why why must SL be so dang difficult!!!! _____________________
|
|
Totally Barmy
Proud Apoligist
Join date: 24 Aug 2004
Posts: 46
|
01-15-2005 14:12
It's more likely a problem with one of your new memory modules.
SL is using the memory, the memory is bad, bang! Perhaps and it is likely, you are not using the top memory in normal use, it would only become apparent when a very memory hungry app went to use it. |
|
Einsman Schlegel
Disenchanted Fool
Join date: 11 Jun 2003
Posts: 1,461
|
01-15-2005 14:24
It shouldn't be a problem with the memory modules, they're brand new chips, and all memory slots are filled (PC3200). Everything else seems just fine and dandy but SL.
_____________________
|
|
Moleculor Satyr
Fireflies!
Join date: 5 Jan 2004
Posts: 2,650
|
01-15-2005 14:34
Your RAM is most likely bad. Since SL uses much more memory than most other programs, SL is probably the only program that actually uses the bad chip.
_____________________
</sarcasm>
|
|
Einsman Schlegel
Disenchanted Fool
Join date: 11 Jun 2003
Posts: 1,461
|
01-15-2005 15:41
If it *is* bad Ram, how can you test it to check which ram is bad?
_____________________
|
|
Moleculor Satyr
Fireflies!
Join date: 5 Jan 2004
Posts: 2,650
|
01-15-2005 16:08
If it *is* bad Ram, how can you test it to check which ram is bad? Remove part of your RAM, test to see if you still crash. If you do, the bad RAM is still installed. If you don't, you have it in your hand. Repeat until you know which chip(s) are bad. _____________________
</sarcasm>
|
|
Candide LeMay
Registered User
Join date: 30 Dec 2004
Posts: 538
|
01-15-2005 17:36
this is the best memory tester I know
http://www.goldmemory.cz/ it can be also some of your bios settings, most "performance" options related to memory make my computer crash for example |
|
Carnildo Greenacre
Flight Engineer
Join date: 15 Nov 2003
Posts: 1,044
|
01-15-2005 22:50
I prefer MemTest86 (www.memtest86.com). It does a very thorough test of all but about 96kb of RAM -- the remaining little chunk is the part where the tester sits.
_____________________
perl -le '$_ = 1; (1 x $_) !~ /^(11+)\1+$/ && print while $_++;'
|
|
Eggy Lippmann
Wiktator
Join date: 1 May 2003
Posts: 7,939
|
01-16-2005 02:15
Disable the fast POST in your bios. It will test the memory for ages before booting.
_____________________
|
|
Catherine Omega
Geometry Ninja
Join date: 10 Jan 2003
Posts: 2,053
|
01-16-2005 03:30
I'd go with MemTest86, personally.
Also, what combination of modules do you have? You say all your slots are full, so I assume you most likely have 4x 512MB? Are they all the same brand? Are you attempting to run in dual mode? _____________________
|
|
Einsman Schlegel
Disenchanted Fool
Join date: 11 Jun 2003
Posts: 1,461
|
01-17-2005 23:30
Ah.. memtest.. thanks everyone!, this helped isolate the problem, apparently there's some sort of compatibility issue, which was corrected.
 _____________________
|
