Need a Linden's help, crashing on log-in

Everytime I log in (it's been almost a week since I last logged on), the game crashes. I'm wondering if it has something to do with us WWIIOLers moving somewhere, and something had been built up where I left off. I've uninstalled, reinstalled, repatched, yet I stll crash, it worked fine before. Anyone got any ideas? I really want to get in and check out our new digs

We need more info, such as:

How far do you get before you crash? Startup screen or after?

What's your hardware setup:

video card
video driver
operating system
motherboard chipset
whether or not you have updated your motherboard AGP chipset drivers

------------------
System Information
------------------
Time of this report: 4/22/2003, 16:20:56
Machine name: JUSTIN
Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 1 (2600.xpsp1.020828-1920)
Language: English (Regional Setting: English)
System Manufacturer: 00101730 XL866
System Model: 15294800000510
BIOS: PhoenixBIOS 4.0 Release 6.0.F
Processor: AMD Athlon(tm) Processor, MMX, 3DNow, ~1.1GHz
Memory: 512MB RAM
Page File: 145MB used, 913MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0 (4.09.0000.0900)
DX Setup Parameters: None
DxDiag Version: 5.03.0000.0900 32bit Unicode

---------------
Display Devices
---------------
Card name: NVIDIA GeForce4 MX 440
Manufacturer: NVIDIA
Chip type: GeForce4 MX 440
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0171&SUBSYS_000210B0&REV_A3
Display Memory: 64.0 MB
Current Mode: 1024 x 768 (32 bit) (60Hz)
Monitor: Plug and Play Monitor
Monitor Max Res:
Driver Name: nv4_disp.dll
Driver Version: 6.14.0001.4345 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 3/20/2003 20:13:00, 3097098 bytes
WHQL Logo'd: No
WHQL Date Stamp: None
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 3/20/2003 20:13:00, 1261418 bytes
Device Identifier: {D7B71E3E-4231-11CF-F963-032002C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0171
SubSys ID: 0x000210B0
Revision ID: 0x00A3
Revision ID: 0x00A3
Video Accel: ModeMPEG2_A ModeMPEG2_B ModeMPEG2_C ModeMPEG2_D
Deinterlace Caps: {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run

Updated ALL drivers April 19th, this include motherboard drivers (the board's going on the fritz, it's soon to be replaced.

The thing it, the game worked before, the only changes have been adding a new stick of 256MB SDRAM PC133, and updating drivers. It doesn't work without the new RAM, either, and the original drivers don't solve it either. Sorry I didn't post my specs sooner, lost the presence of mind to do so last night.

I get as far as seeing the world while it loads, with the green loader bar on screen, and the tip of the day thing.

LOL... a full dxdiag from a WWIIO player. LOL... we know how to troubleshoot, that's for sure!

In the blood I tell ya, I cut it down, I figure the programmers here know how to make heads or tails, and extra info never hurt anyone

Same thing, Windows gives me a crash alert (asks if I would like to send error report, I decline), then the Linden Labs crash reporter comes up, I fill out the description of the event from my POV, and send. I'm trying different configuration here, and I'm about to try my original vid card drivers. I'll report back with results.

Linden, we're glad to be with you guys, ask CRS, we're hell on Earth when it comes to tracking down bugs

Hey, Eukayant -

If you updated your nVidia drivers to 43.45 and you're running on a GeForce4 MX, that could potentially be causing some problems - if nothing else, it'll be really slow. This is explained elsewhere, but for various reasons, you'll want to use the 41.09 drivers. I forget what thread I posted this on, though...

There are some upcoming support docs that explain the most common bugs/issues with graphics cards and stuff, it's not quite ready yet.

- Doug

Funny you should say that, I reverted to the original drivers I had, and poof! All of a sudden, I can get in, no lag, and everything is beautiful, "God is in his heaven, and all is right in the world." If that isn't already listed in the issues (I gather I made the mistake of being complacent about reading about the know software issues , well, here it is, the latest nVidia drivers for GF4MX cards are no good for SL

Yep, your report shows the bad drivers:



Glad to see you got back in.