I've crashed twice.. and here's the second error

cennie · **Posted:** Tue Apr 18, 2017 10:50 pm

UruLive.Live.1.918.OpenUru#131 - External.Release
Exception type: Access violation
Call stack (14 levels):
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x779998D5
0x77999902
0x753A336A
0x0089DACA
0x7C34C456
0x07608564
0x00461A19
0x0053D53D
0x0053F2EB
:oops:

cennie · **Posted:** Fri Apr 21, 2017 11:03 pm

UruLive.Live.1.918.OpenUru#131 - External.Release
Exception type: Access violation
Call stack (14 levels):
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x772298D5
0x77229902
0x74B6336A
0x0089DACA
0x7C34C456
0x07748564
0x00461A19
0x0053D53D
0x0053F2EB

Here's another I just had..

Mac_Fife · **Posted:** Sat Apr 22, 2017 11:45 am

I don't know if anyone is currently able to decipher stack dumps (I think it needs access to the debug database for the specific client in use) and all I could offer is to say that the offsets suggest that both crashes were caused by the same thing. Which does not help you much.

Anything else you can offer on what you were doing at the time of each crash?

cennie · **Posted:** Sat Apr 22, 2017 7:46 pm

UruLive.Live.1.918.OpenUru#131 - External.Release
Exception type: Access violation
Call stack (14 levels):
0x00000000
0x77B098D5
0x77B09902
0x75A8336A
0x0089DA78
0x00456597
0x0045277B
0x0051FC78
0x0051FA5D
0x0051F72F
0x0051F1BC
0x005830AD
0x0079A3B3
0xB0004226

I was relto'in out of Jalak

cennie · **Posted:** Sat Apr 22, 2017 8:10 pm

Also i noticed the first two.. the last 4 numbers were the same..

cennie · **Posted:** Mon May 01, 2017 12:12 am

This time i couldn't get to copy the stack dump.. but it was going to Negilahn 4/30/17 @ 4:38pm on
Barefoot3 KI # 04452432

I was helping Barefoot3 .. he also stackdumped but couldn't get to his either.

Acorn1 · **Joined:** Sat Jan 12, 2013 8:46 pm **Posts:** 979

Cennie, as Mac said previously, no-one can interpret the stack dumps any longer so there is no need to post them. But he invited you to say more about what you were doing when the crash happened. Eg was it picking up the Negilahn book for the first time, were you using the book in your relto or visiting someone else's, or were you in the nexus; did you arrive at Negilahn and then crash or did you not even get there - all that sort of detail might help

cennie · **Posted:** Sat May 06, 2017 5:39 pm

Acorn1 wrote:

Cennie, as Mac said previously, no-one can interpret the stack dumps any longer so there is no need to post them. But he invited you to say more about what you were doing when the crash happened. Eg was it picking up the Negilahn book for the first time, were you using the book in your relto or visiting someone else's, or were you in the nexus; did you arrive at Negilahn and then crash or did you not even get there - all that sort of detail might help

Thank you Acorn.. can do!

Mac_Fife · **Posted:** Sat May 06, 2017 7:12 pm

I'll give you an example from personal experience (and from a long time ago!):
I crashed shortly after arriving in Tsogal. The same thing happened when I tried going there again. Third time, I waited after arriving at the link-in point. Nothing happened, then as I turned round to face the garden I crashed. I realised this was just as the pond came into view. Same thing happened if I linked in and turned in the opposite direction. This gave the hint that it was something to do with displaying the water. I'd also recently updated my video drivers to the latest Nvidia driver so suspected that had something to do with it. Reverting to an older video driver cured my crashes. But I could only work this out from carefully observing what I was doing, but I appreciate that if a crash comes as a surprise then it's hard to register all the facts or know what's relevant.

rarified · **Posted:** Fri May 19, 2017 3:24 pm

Actually, for the technically inclined, the symbol table files for the last MOULa build will be available here (client), and the rest of the build artifacts starting here.

Unfortunately in this case, the "last MOULa build" is the one we just sent to Cyan to install, and these dumps are not from that build. And the older symbol tables are no longer available since some of the automated build system was updated and history discarded.

But in the future you can use those links and a debugger (capable of manipulating VS .NET (2003) artifacts) to at least locate the code that crashed.

_R

I've crashed twice.. and here's the second error

Who is online