It is currently Tue Nov 24, 2020 8:38 pm

All times are UTC




Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 13 posts ] 
Author Message
PostPosted: Sun Jan 17, 2010 12:51 pm 
Offline
Former MystOnline Moderator

Joined: Fri Nov 10, 2006 3:05 pm
Posts: 4208
Location: 56°2'26", -3°20'28"
JanB wrote:
Will there be a new sessien organized for those who missed the door(s)?

I hope so. Since the ratio of players is probably heavily biased towards US, I'd suggest same time on Saturday 23rd - there are a few in the beta group that "haven't shown their faces yet", so they may appreciate a second running. And it gives me time to get to the bottom of my issues :)

It's possibly worth making this a semi-regular event (once more people are invited into beta) so people needing a "Door Group" can always find one.

Edit:
@dadguy: I've got a completely wired connection here and the only thing that has really changed on this PC since the end of MOUL is the video driver, which I updated during the MQO beta. I'm suspicious of that, since what happened was very like the "Sticks and Stones" crash that some folks got in Relto, i.e. a video card related problem: That was fixed by turning off the sticks/stones Relto page. But I never used to have problems in Tsogal during MOUL :? .

Since no-one else had a problem it seems unlikely that it's a "client software fault", more likely a PC issue.

So, my possible problem sources are, I think:
1. Faulty/mis-seated system RAM
2. Faulty/mis-seated video card
3. Video Driver compatabilty issue

I've cleaned the dust out the PC and reseated the RAM and graphics card now. I'll privately test going into Tsogal with different graphics settings (I seemed to get further when I turned off shadows) and see what happens, then maybe roll back my video driver.

_________________
Image Mac - MOULagain KI#00004826 00004289
In the interests of the environment, this post has been constructed entirely from recycled electrons.


Last edited by Mac_Fife on Sun Jan 17, 2010 9:42 pm, edited 1 time in total.

Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Sun Jan 17, 2010 2:39 pm 
Offline
Obduction Backer

Joined: Fri May 12, 2006 5:33 pm
Posts: 438
Location: Netherlands, Hoofddorp
Quote:
Since no-one else had a problem it seems unlikely that it's a "client software fault", more likely a PC issue.

If you get a blue screen its 85% change it's a driver issue
Do you run XP Vista or Windows 7 ( maybe with Uruexpoloresr set to XP SP2 compatibility mode)?
Any clues to find in the event logs?

_________________
JanB MO:ULagain (Old) KI 00003068 JanB2 KI 00593052


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Sun Jan 17, 2010 6:32 pm 
Offline
Former MystOnline Moderator

Joined: Fri Nov 10, 2006 3:05 pm
Posts: 4208
Location: 56°2'26", -3°20'28"
JanB wrote:
If you get a blue screen its 85% change it's a driver issue
Do you run XP Vista or Windows 7 ( maybe with Uruexpoloresr set to XP SP2 compatibility mode)?
Any clues to find in the event logs?

An I'm 99% sure you're right about it being a driver issue :)
As I said, this is the same PC as I used for MOUL, and is running XP, now at SP3. The only BSOD problem I ever got back then was the Relto Stick and Stones one, which was related to drivers on certain video cards (nVidia ones at least).
I can get in to Tsogal, I can start to move around, but as soon as I turn to bring the central area into view, I crash :? .
Looking at the Minidump logs from each instance, they're all showing much the same thing, main codes being
Code:
Error code 1000007f, parameter1 0000000d, parameter2 00000000, parameter3 00000000, parameter4 00000000.

The RAM is passing all tests, so my next step is to go back to the driver I had at the end of MOUL.

_________________
Image Mac - MOULagain KI#00004826 00004289
In the interests of the environment, this post has been constructed entirely from recycled electrons.


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Sun Jan 17, 2010 6:59 pm 
Offline
Obduction Backer

Joined: Tue May 09, 2006 6:23 pm
Posts: 4589
Location: Dutch mountains
What happens to Mac in Tsogal did happen for me in the Cleft.
Every time I go to the Cleft and walk towards the bones in the desert my machine crashes.
Also this happens sometimes when I return on my Relto and turn around I will crash.
Never had this before in MOUL. And I think my computer is ok.
To me something has changed, but I do not know what.
I am no technie, but sometimes I think it is server related.
I remember from earlyer Beta tests (not sure if it was D'Mala or MOUL) this did happen before and after adjusting something on the serverside it was ok.


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Sun Jan 17, 2010 7:35 pm 
Offline
Obduction Backer

Joined: Fri May 12, 2006 5:33 pm
Posts: 438
Location: Netherlands, Hoofddorp
Quote:
Error code 1000007f, parameter1 0000000d


Google shows indeed a lot of interesting threads about that specific error!.

(driver + failing RAM etc.)

It is possible that was sorted out what went wrong than and that on the server side precautions were taken to avoid those failing instructions on the client side ( version related).
D'lanor has made some post in the past regarding that I remember.(He might be a valuable extra hand in the test team - But thats not up to us to decide.) :wink:

_________________
JanB MO:ULagain (Old) KI 00003068 JanB2 KI 00593052


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Sun Jan 17, 2010 8:35 pm 
Offline
Former MystOnline Moderator

Joined: Fri Nov 10, 2006 3:05 pm
Posts: 4208
Location: 56°2'26", -3°20'28"
Yes, it's an ntkernel error, which is different to the one I had in MOUL, which I think was a "paged fault in non-paged area": That was the driver incorrectly addressing an area of video RAM. This makes me a little less certain that it can be fixed by changing the driver. I've had some "real" work to do today, so reverting drivers hasn't been top of my priority list :)

BTW: This is now all bit off-topic. Should maybe get the relevant posts picked out and moved to a new thread in the "Technical Discussion" area.

_________________
Image Mac - MOULagain KI#00004826 00004289
In the interests of the environment, this post has been constructed entirely from recycled electrons.


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Sun Jan 17, 2010 9:18 pm 
Offline
Obduction Backer

Joined: Tue May 09, 2006 6:23 pm
Posts: 4589
Location: Dutch mountains
Thinking the same.
Split these posts from http://mystonline.com/forums/viewtopic.php?t=19024


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Sun Jan 17, 2010 9:29 pm 
Offline
Former MystOnline Moderator

Joined: Fri Nov 10, 2006 3:05 pm
Posts: 4208
Location: 56°2'26", -3°20'28"
SOLVED! (I hope)

I'm in Tsogal and splashing around in the puddles! :D :D :D

OK, I uninstalled the latest nVidia drivers (v195.62), re-booted then let the Windows "Found New Hardware" wizard search Windows Update for a driver. It picked up a 2008 version and installed that. Everything seems to be working great now.

nVidia driver versions are a real pain to follow: The file names and version labels never seem to match the version numbers displayed when you check the control panel :?

In case anyone else ever encounters anything similar:
Graphics card is nVidia GeForce 6200, 256MB
From DxDiag:
- "Faulty" driver:
- - Driver Version: 6.14.0011.9562 (English)
- - Driver Date/Size: 11/21/2009 02:34:54, 6282752 bytes
- Working driver:
- - Driver Version: 6.14.0011.7813 (English)
- - Driver Date/Size: 9/17/2008 23:55:00, 6057472 bytes

I'll pop in and out of Tsogal a couple of times over the next few days to make sure this wasn't a fluke!

_________________
Image Mac - MOULagain KI#00004826 00004289
In the interests of the environment, this post has been constructed entirely from recycled electrons.


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Sun Jan 17, 2010 11:29 pm 
Offline
Obduction Backer

Joined: Tue May 09, 2006 7:45 pm
Posts: 1410
Location: Wilmington, DE KI: 291428
Yay!! Hopefully we can have a Tsogal party next Saturday (again).

Welldone!

Dadguy

_________________
Member of the Guild of Greeters


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Mon Jan 18, 2010 1:20 am 
Offline
Obduction Backer

Joined: Wed Nov 08, 2006 9:56 pm
Posts: 249
Location: NYC
Mac I tried a graphics update to v195.62 and I could not get it to work at all. I had a little trouble trying to roll back the driver but did finally get it to roll back. I would say stay away from that v195.62. I almost remember that I tried that once before and had same results.


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Mon Jan 18, 2010 5:55 am 
Offline
Obduction Backer

Joined: Tue May 09, 2006 7:45 pm
Posts: 1410
Location: Wilmington, DE KI: 291428
By the way, that is probably a ticket of interest. Not that they have the resources to resolve it, but it might make a nice note in the FAQs that they present when we go broader with MOULagain.

Dadguy

_________________
Member of the Guild of Greeters


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Mon Jan 18, 2010 6:09 am 
Offline

Joined: Thu May 18, 2006 11:08 pm
Posts: 3847
Location: In the Cleft
wow, wonderful.
ys the Nvida Drivers are quite tricky at times. I had to adjust my 6000 series FX for a number of things, i have a 7600 GT now, so i dont have that challenge but my old 6000 series was a tough card to deal with, and i had to use a range of drivers.

glad you got that figured out. MOUL is quite demanding on video cards especiallly when there is lot of stuff moving around like the pollen in the air, the water and other dynamic elements in Tsogal, even tho small, it has a lot going on mechanically.....

very glad you got a fix and ys i would ticket it with details for the bug base. RAWA is entering everything for the future.

_________________
URU MOUL Lives
Admin
3D World and Game Developers Group Linkedin
"We Build Worlds"


Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: Mon Jan 18, 2010 7:08 pm 
Offline
Former MystOnline Moderator

Joined: Fri Nov 10, 2006 3:05 pm
Posts: 4208
Location: 56°2'26", -3°20'28"
Ticketed as 9041-OPXB-0128 if anyone else ever needs to reference it :wink:

For reference, here's the data I extracted from the minidump file that was created on the first crash I had:
Code:
D:\Support Tools>dumpchk C:\WINXP\Minidump\Mini011610-01.dmp
Loading dump file C:\WINXP\Minidump\Mini011610-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion        0000000f
MinorVersion        00000a28
DirectoryTableBase  4f27d000
PfnDataBase         81b03000
PsLoadedModuleList  8055b1c0
PsActiveProcessHead 80561358
MachineImageType    0000014c
NumberProcessors    00000001
BugCheckCode        1000007f
BugCheckParameter1  0000000d
BugCheckParameter2  00000000
BugCheckParameter3  00000000
BugCheckParameter4  00000000
PaeEnabled          00000000
KdDebuggerDataBlock 8054cde0
MiniDumpFields      00000dff

TRIAGE_DUMP32:
ServicePackBuild      00000300
SizeOfDump            00010000
ValidOffset           0000fffc
ContextOffset         00000320
ExceptionOffset       000007d0
MmOffset              00001068
UnloadedDriversOffset 000010a0
PrcbOffset            00001878
ProcessOffset         000024c8
ThreadOffset          00002728
CallStackOffset       00002980
SizeOfCallStack       000006f4
DriverListOffset      00003308
DriverCount           00000083
StringPoolOffset      000059f0
StringPoolSize        00001210
BrokenDriverOffset    00000000
TriageOptions         00000041
TopOfStack            b31c990c
DebuggerDataOffset    00003078
DebuggerDataSize      00000290
DataBlocksOffset      00006c00
DataBlocksCount       00000003


Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sat Jan 16 22:44:49 2010
System Uptime: 0 days 4:48:39
start    end        module name
804d7000 806ed780   nt             Checksum: 0021C247  Timestamp: Tue Aug 04 16:
14:34 2009 (4A78505A)

Unloaded modules:
b2df3000 b2e1e000   kmixer.sys    Timestamp: unavailable (00000000)
f799b000 f799d000   splitter.sys    Timestamp: unavailable (00000000)
b32ea000 b3315000   kmixer.sys    Timestamp: unavailable (00000000)
f7a97000 f7a98000   drmkaud.sys    Timestamp: unavailable (00000000)
b36f5000 b3702000   DMusic.sys    Timestamp: unavailable (00000000)
b42a2000 b42b0000   swmidi.sys    Timestamp: unavailable (00000000)
b333d000 b3360000   aec.sys     Timestamp: unavailable (00000000)
f7995000 f7997000   splitter.sys    Timestamp: unavailable (00000000)
b7faa000 b7fab000   SiSPort.sys    Timestamp: unavailable (00000000)
b6e1f000 b6e24000   Cdaudio.SYS    Timestamp: unavailable (00000000)
b87d4000 b87d7000   Sfloppy.SYS    Timestamp: unavailable (00000000)

Finished dump check

D:\Support Tools>

_________________
Image Mac - MOULagain KI#00004826 00004289
In the interests of the environment, this post has been constructed entirely from recycled electrons.


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 13 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to: