|
Gandalf Tomsen
Registered User
Join date: 6 Feb 2007
Posts: 2
|
06-21-2007 08:29
When I exit the SL program, whether loged on or not, i get a crash and an error message that contains a memory read error. (the instruction at "0x7910f29" referenced memory at "0x00000000". The memory could not be read.) this began with the install of the new verision (june 2007). i updated my graphics drivers and reinstalled SL clean twice. The first look viewer does the same thing. The only real annoyance is that when I log back in all the tutorial pops ups run again.
|
|
Alan Wijaya
Registered User
Join date: 13 Dec 2006
Posts: 6
|
same here
07-04-2007 20:52
I have exactly the same problem. Been a while now and with both First Look and regular client. After a couple of "clean installs" getting tired of sending crash reports lol. Anyone help on this one?
CPU: AMD Athlon 64 3200+ Memory: 1024 MB OS Version: Microsoft Windows XP Service Pack 2 (Build 2600) Graphics Card: Radeon X1300 (with latest drivers hehe)
|
|
Tybalt Brando
Catalyst
Join date: 25 Dec 2006
Posts: 347
|
07-04-2007 22:07
Thank you. I am going to copy this for when I decide to play "Cuss out a Linden". They told me it was my RAM
|
|
Gandalf Tomsen
Registered User
Join date: 6 Feb 2007
Posts: 2
|
Fix for crash
07-05-2007 07:09
I finally found a fix for this. The new Catalyst driver (7.5) from ATI was causing it. i rolled back to the driver before (7.4) and the problem disappeared. From: Gandalf Tomsen When I exit the SL program, whether loged on or not, i get a crash and an error message that contains a memory read error. (the instruction at "0x7910f29" referenced memory at "0x00000000". The memory could not be read.) this began with the install of the new verision (june 2007). i updated my graphics drivers and reinstalled SL clean twice. The first look viewer does the same thing. The only real annoyance is that when I log back in all the tutorial pops ups run again.
|
|
Tybalt Brando
Catalyst
Join date: 25 Dec 2006
Posts: 347
|
07-05-2007 11:09
From: Gandalf Tomsen I finally found a fix for this. The new Catalyst driver (7.5) from ATI was causing it. i rolled back to the driver before (7.4) and the problem disappeared. Hmm. Wonder if there is a fix for Nvidia.
|