HARD crash on Basovka

[Shadrach]

Hi,
I'm guessing this one would be really hard to find the cause for (I'm probably the only one who gets it), but I will still try as it got annoying today. It happened twice in a row today so I'm just throwing this out there to see if anyone has the same or any idea what could be causing it.

I keep getting serious crashes on Basovka, no CTD, just a black screen with the sound just beeping or clicking. It happens every time at the same place, when playing as russians, running out of the station of Basovka.

Just before I get outside the doors it crashes. Not every time, of course (as the map would be unplayable then) but *really* annoying like today when I was Komandir and had some really good arty going... I've thought about GPU overheating but then again it's only on Basovka it happens regularly.

Using a Gforce 7800 GS
Nvidia nForce 2 motherboard
AMD Athlon 2Ghz
Soundblaster Audigy 2 ZS
2 Gigs Ram

Fairly recent drivers all around, and I've had the problem a long time so should't be related to driver versions.

Are there any logs or crash dumps I could find and send to someone in the know? Can't find any in the RO folder...

-S

 

[Zetsumei]

maybe a bad sector on your harddisc or some bad memory.

Anyway try running checkdisk and memtest to test if everything is ok

You might have a redorchestra.log in your ro system folder.

Try going to the maps folder of ro and deleting RO-Basovka.rom and going and then verifying the cache inside steam ^^.

 

[Shadrach]

Thanks Zetsu, I will do that. Will see how it goes, if it happens again I will update.

Could someone please take a look at the attached zip file containing my ini-files, might be a clue in there? The log is included as well, but I really doubt the system manages to write a log with this type of crash...

 

[Zetsumei]

your log file got no info

is the log file from a session where the game crashed?

 

[Shadrach]

Yes, it probably didnt have time to write a log, it just went froze in an instant...

I'll try to play some basovka today to maybe recreate the crash, although I feel like my computer just broke every time it happens, its so brutal

UPDATE:
got a couple of crashes, I can basically recreate it every time I stand outside the station looking to the bunker, bang, crash in a couple of seconds.
Attached a couple of logs. Crashes occur after this:

Log: xD3D9Helper::Init (QuadEmulation)

You can even see that it crashes while it is actually writing to the log...

 

[Zetsumei]

if you got a multicore processor try setting afinity to one core.

But did you try deleting and redownloading basovka already?

 

[Aeneas2020]

may sound like an odd problem but what antivirus software are you running...because i was getting crash after crash after crash very similar to this with certain games in very specific places (especially RO on certain maps)...i was running panda antivirus which has been known to give u BSOD and restart for no reason...although its more likely to be hardware i guess.

 

[Shadrach]

I'm running F-secure AV, but usually I disable it before playing, so I have nothing but default system processes taking cpu

I have deleted Basovka and it got redownloaded. Didnt help any though. What I am trying now is running in just Direct3D not Direct3D v 9. So far so good, it seems to be working. The entry in the log gave me the idea it was related to the init of D3D9, since the crash happened just after.

Of course I would like to run in D3D9 but I can live without bloom or fsaa I guess

 

[Aeneas2020]

hmm im assuming coz u sound like u know what ur talking about that ur Direct X and drivers are all up to date...oh and btw i got that crash i was talking about even when my AV was disabled most odd. I'll read through some other posts relating to errors like urs and see what i can dig up mate.

 

[Zetsumei]

I'm running F-secure AV, but usually I disable it before playing, so I have nothing but default system processes taking cpu

I have deleted Basovka and it got redownloaded. Didnt help any though. What I am trying now is running in just Direct3D not Direct3D v 9. So far so good, it seems to be working. The entry in the log gave me the idea it was related to the init of D3D9, since the crash happened just after.

Of course I would like to run in D3D9 but I can live without bloom or fsaa I guess

if the problem happends in d3d9x then try updating your directx and vidcard drivers.