TS2010 Still Doesn't Work

RRSignal

Cheesesteak Guru
So it arrived just before the New Year. But I can't get any of the driver sessions or quick drive to work. All eventually crash with the error: The instruction at 0x00d5d40c referenced memory at "0x00000000". The memory could not be written. No graphics appear, and I've tried lowering the settings as much as I can, even turning anti-aliasing off. This error happens whether using DirectX or OpenGL. No scenery will display - I just see the wireframe background before the program eventually crashes after abotu 5 minutes.

System specs:
E2200 2.2 Ghz dual-core
1 Mb RAM
nVidia 8400GS
Directx 9.0c
10 Gb free HD space
Windows XP SP2 (I am told TS2010 will work with SP2, even though it calls for SP3)

My system runs like a champ normally and I have very few background processes and services running.

Any ideas?
 
Hi RRsignal,

At a guess I would think your graphics card is the main problem. At one stage I had a 9600gs and tossed that out because it would not give me decent frame rates. Your 1 gig of ram could do with an addition of another gig too. Why don't you update to XP SP3? it's free.
However I could be wrong.

Cheers,
Bill69
 
.....referenced memory at "0x00000000". The memory could not be written........

This was a common problem when XP SP2 first came out (try Googling it). There does not seem to be a universal fix.

I would update to XP SP3 and see if that solves the problem (as Bill says its free!!!)

Cheers
 
Try upgrading your video drivers. If that doesn't help, you could try upgrading other drivers on your computer. Try closing any programs (and system tray junk) that you don't actually need running. And install SP1 if you didn't already.
 
Ok, thanks for all the suggestions. Unfortunately, none work. Updating to XP SP3 doesn't help. Using the latest nVidia driver doesn't help as well as using the older one. Applying TS2010 SP1 doesn't help. Also, I tested TS2010 on another machine (better Core2 processor, RAID, but also 1GB and the same video card, an 8400GS) with identical results.

FYI, one thing I left out is the exact errors I get. I get the same errors regardless of what route or session I run (not so sure about the kuids, but always these six errors) which occur almost immediately upon starting a session:

DriverSetupRule : Thread Exception: ER_Exception, line 466, file driversetuprule.gs (1)
DriverSetupRule : World.AddDriverCharacter> not 'drivercharacter' asset (file world.gs) (1)
DriverCommandRule : Thread Exception: ER_Exception, line 411, file drivercommandrule.gs (1)
DriverCommandRule : World.AddDriverCommand> not a DriverCommand asset: <kuid2:57344:80001:3> (file world.gs) (1)
DriverCommands : Thread Exception: ER_Exception, line 167, file DriverCommands.gs (1)
DriverCommands : World.FindDriverCommand> not a DriverCommand asset: <kuid2:57344:80001:3> (file world.gs) (1)

I still can't quick-drive either.
 
Just a silly question. Have you run a Extended database Repair in CM yet ? Looks like some of your assets aren't recognized properly.

If you have forget my suggestion. Though sometimes I have had to do two EDR's before everthing sorted out.
 
Quick Update:

After following Nickel's advice to rebuild the database (I did it three times) and then Ironwheel's advice in the other thread to validate the database, I can now run TS2010! I first did this on a machine that met at least all the minimum requirements.

But, I've also found that: 1. I don't even need Windows XP Service Pack *3*; it runs just fine in this machine, the Service Pack *2* (although the service pack for Trains itself, SP1, won't install without XP SP3 - that's not cool, Auran! I'm gonna submit a ticket on that, perhaps a workaround!) Also, TS2010 runs great even on my older nVidia driver. The new one broke some of my other programs (e.g. Bliss), so I rolled back to the 2-year-old video driver that came with my 8400GS and TS2010 still works just great!

Indeed, the machine I just upgraded to XP SP3, just a few hours ago, is a noticeably faster machine than this one (although they both have the identical video card and same amount of memory, 1GB). Yet, I just found out that this computer (older, running XP SP2) runs TS2010 just as fast (maybe 2 or 3 FPS less) than my hot machine!

Moral of the story: Windows service packs and video drivers probably aren't as big a deal as some (especially manufacturers) make them out to be. I've long known that to be the case, not just with Trainz. It seems that a lot of folks here are either considering expensive hardware upgrades or giving up on TS. DON'T! :)
 
Quick Update:

After following Nickel's advice to rebuild the database (I did it three times) and then Ironwheel's advice in the other thread to validate the database, I can now run TS2010! I first did this on a machine that met at least all the minimum requirements.

But, I've also found that: 1. I don't even need Windows XP Service Pack *3*; it runs just fine in this machine, the Service Pack *2* (although the service pack for Trains itself, SP1, won't install without XP SP3 - that's not cool, Auran! I'm gonna submit a ticket on that, perhaps a workaround!) Also, TS2010 runs great even on my older nVidia driver. The new one broke some of my other programs (e.g. Bliss), so I rolled back to the 2-year-old video driver that came with my 8400GS and TS2010 still works just great!

Indeed, the machine I just upgraded to XP SP3, just a few hours ago, is a noticeably faster machine than this one (although they both have the identical video card and same amount of memory, 1GB). Yet, I just found out that this computer (older, running XP SP2) runs TS2010 just as fast (maybe 2 or 3 FPS less) than my hot machine!

Moral of the story: Windows service packs and video drivers probably aren't as big a deal as some (especially manufacturers) make them out to be. I've long known that to be the case, not just with Trainz. It seems that a lot of folks here are either considering expensive hardware upgrades or giving up on TS. DON'T! :)

Hi,
I rebuild the database (I did it three times), but the same error.
What is the next way to go?
 
Regarding the service pack and not having XP SP3 just copy the patched install from the PC with SP3 and overwrite the one without and do an extended database repair which is what I did here.......... SP3 refused to install on one of my XP PC's, problem which for info was messed up permissions, now solved as upgraded to Win7.
 
Back
Top