Topic: CTD/ BSOD on mapchange

First of all, I would like to say that this mod is awesome. And I really would love to play it for some hours. But it simply is not possible for me as for my wife. So I will post our system specs and afterwards our problem.

my rig:

Intel E6600
4 Gig of RAM
8800GTX
X-Fi Fatality
Vista x64

my wifes rig:

Intel E6600
2 Gig of RAM
8800 GTS
Vista x86

BF2142 runs great and for hours on our machines. Not a single problem. All settings are maxed out, except for the sound settings on my wifes machine.

Now our problem:

FS 1.1 (that full client version) installs properly, does that "shader thing" when connecting to a server and we are ingame. As long as there is no mapchange. Whenever the map changes from a space map to a ground map, I get a BSOD and my wife gets a CTD as soon as we hit the "join" button. Afterwards there is no chance of connecting to a server (no matter which type of map) without BSOD (me) or CTD (wife) unless we clear the cache-files. This occurs only and always on a change from space to ground map. After clearing the cache, we can play (after waiting for that shader thing again) until we have been playing a space map. Mapchange from space to ground, boom, BSOD and CTD.

Oh, my BSOD STOP-code is BCC 76. Always.

And yes, we are using the latest drivers for our hardware.

So please, please, is there any help?

Thanks in advance,

Shresel

2 (edited by Stardestroyersarecool 2007-10-30 11:17:12)

Re: CTD/ BSOD on mapchange

Weird. I have no clue. I have however read on some other forum that a guy was having a similar problem, he fixed it by lowering his geomitries in the graphics options. (300th post yay!)

First strike, playing from day one: SirKillsalot30

Resident Metal Gear Solid fan

Re: CTD/ BSOD on mapchange

Stardestroyersarecool wrote:

Weird. I have no clue. (300th post yay!)

sorry to say, but then dont post but let some dev do it instead...

____________
Former GC player known as "Saupadl"
GC-Veteran from 2 to 5.3

Ingame Name: FsTest Saupadl

4 (edited by Shadowfax 2007-10-30 12:42:23)

Re: CTD/ BSOD on mapchange

Well I think it'd be best for a dev or HelpDesk to offer some advice here, but here's my suggestions...

- Have you tried reinstalling FirstStrike? On the offchance some component's gone corrupted, an uninstall and reinstall can ensure the files are reliable...

NOTE: If you downloaded the FirstStrike setup using a Torrent (Peer-to-Peer) program such as BitTorrent, it must not be sharing the file as you install the mod, or it will corrupt FirstStrike. Either stop sharing of it temporarily, or copy the file to another location and run it from there.

- BSOD STOP-codes usually resemble "0x00000050" or "PAGE_FAULT_IN_NONPAGED_AREA" or a simliar message. Is "BCC 76" the exact message, or are there more BSOD details? If so, please include them here.

- Is there anything interesting in the Event Log? It's located at Start > Control Panel > System and Maintenance > Administrative Tools > Event Viewer. Sometimes Windows will record additional error information in there, might be worth checking out.

____________________________

ShadowfaxSTF is the name you'll see, as I strike first. The FS Manual, a must-read.
Proud user of the First Strike Mod Wiki, feel to browse our collections and add more fine winery!

Re: CTD/ BSOD on mapchange

HagenSaubauch wrote:
Stardestroyersarecool wrote:

Weird. I have no clue. (300th post yay!)

sorry to say, but then dont post but let some dev do it instead...

Ok yea I found a possible solution but ill say nothing sure, lesson learned thank you.

First strike, playing from day one: SirKillsalot30

Resident Metal Gear Solid fan

Re: CTD/ BSOD on mapchange

STOP-Code is 0x000000076 (not exactly sure about how many "0"). Or, to put it in a short version, BCCode 76.

But I downloaded FS again in 1.0 version will patch it then... Hopefully it will work. Maybe you are rigjht about the corrupted files.

7 (edited by ShreksEsel 2007-10-30 16:22:16)

Re: CTD/ BSOD on mapchange

Yeah... Success! Different version and now it works... Either the file was corrupted or the "1.1 full client" package doesn't work as it should.

EDIT1:
Full client seems to be the prob... A friend of mine just tried and got a bluescreen too.

EDIT2:
Have been happy too early... Just got another BSOD. Same BCCode as always. But it took much longer and I survived several mapchanges. And I can join servers after a restart without clearing the cache. So it's a bit better at least...