Nisgeis,
I am running the 169.25 drivers. I still get the BSOD crash. I was using this when I first installed the U-Boat update. I then have tried various beta drivers and I got the Black screen hard lock up with those, so I went back to the 169.25 drivers.

Thanks

Does it happen consistently when you start taking damage in the external view, or is it random and only occurs after some period of time? Also, is it stock only, with PE3 or both.

I'm Running two installs one is with TMO only, Fleet Boats. The other is Uboat with Operation Monsun and PE3. On the TMO it crashes while taking damage no external view but I have the event camera on. I have tried it with the event camera off and external views on, same thing. The Uboat with PE3 it crashes randomly. I will pay more attention to when it crashes when I get some time to do a patrol. I am willing to try any testing to help resolve this issue.

Thanks

I previously had 169.25 and problems, inlcuding the very specific and infamous nklvddmkm driver related error....if you've never heard of the nklvddmkm error, count yourself extremely lucky. (Google nklvddmkm) The nklvddmkm error caused the immediate CTD or BSOD (I can't now recall which) whenever an explosion took place (torpedoe hit)...and possibly also when a DD would fire at me, but i don't recall encountering DD's at that time.

I then moved on to using 174.93. Immediately upon installing those drivers, the nklvddmkm error disappeared, forever it seems as I've not had any specific nklvddmkm error messages appear when I experience BSOD's. However, I do sometimes get a Windows message when I reboot announcing that the improper shutdown was attributable to a generic NVidia problem....of course, Micros$ft and Nvidia have been arguing back and forth since the release of VISTA over whose fault the nklvddmkm error was.

So I use:
174.93 drivers + VISTA32 + 8800GTX + SH4 1.4 or SH4 1.5 with no problems.

174.93 drivers + VISTA32 + 8800GTX + SH4 1.4 + PE3.x with no problems

174.93 drivers + VISTA32 + 8800GTX + SH4 1.5 + PE3.x = BSOD when DD fires or Torp hits (maybe the DD firing indicates a hit on my sub). The BSOD's are not random...they occur with the explosion,etc.

174.93 drivers + VISTA32 + 8800GTX + SH4 1.5 + W_Clear's Environ MOD(s) =no problems encountered yet(if I turn OFF in-game "Post Processing" and "Texture High" Options.


Note: As with Karbo, in all cases the BSODs will occur whether I am in Periscope view or external view...and the DD firing can be at extreme distance from my sub/periscope view, just a small slight flash of a deck gun, and BAM! BSOD! It's not as if the graphics "demand" comprising some huge dramatic torp explosion is overloading my 8800GTX. When I next get the energy to do some more methodical testing, I'll try to see if I get a BSOD if I am internal, looking down at my feet let's say, when a torp hits...or on the NAV Map.

I too have been running that driver and have tried every other driver.


HOWEVER... i have noticed a possible related scenario.

My SH4 1.5 stock worked fine on same driver when i ONCE got a torpedo hit. I had no BSOD BUT it was just ONE hit and im not sure if it was a fluke. I then installed BSE2... then the troubles were ntoiced when i was hitting a target. I then cleaned the game off and the registry (efficiantly i believe including the mods).

But when i reinstalled the program i noticed the BSOD would happen on the stock and/or mod when installed.

is it possible that the mod was incompatable with my PC? And that there reminants of mod in the registery or a file somewhere?

This is just a possibilty and i cant be sure. It may of actualy happened from the start and have nothing to do with the mod.


Anyways a update from Ubi tech support is that they have tried alot of BASIC troubleshooting, all stuff that i have already tried and to no success... They have now put my help ticket on hold... not sure what that means.

It happens everytime a vessal/craft/plane takes damage in all views.

OK, this is sounding stranger by the minute.

Karbo has trouble with the 1.5 and PE3, but with random crashes,
Icecold has stock 1.5 trouble, when taking damage and Doolittle has a bit of troubole with stock and more with PE3 when taking damage. This is not looking like one problem with PE3... hmmm.

For explosion related crashes, there are two possibilities. There are the particle effects to consider and also the sound effects. I think PE3 has altered sound effects as well, though not sure about that.

For Doolittle, to see if it's the particle explosion effects, there are two files we can remove to bypass the new effects. If you take /data/library/particles.dat and /data/library/materials.dat out of the PE3 mods and then install them, you should get the stock particle effects, but everything else intact. If that doesn't crash, we'll know it was a contributing factor, if it doesn't then it's possibly the sound of the explosion being played that makes it go bang. To test that it should be enough to just uncheck all the sound options. Though as you are only getting the trouble in external views, it's likely they are particle related.

For Icecold can you try turning all the sound off by unchecing all the boxes? If it's a sound issue, that may explain why you are getting crashes on the internal view when you take damage. By the way, what's BSE2?

Karbo, sorry nothing new to try except the above, random crashes are going to be hard to troubleshoot.

Sorry dont know why i typed that... i ment PE2.

Nvidia have released another driver update... apparently it has fixed the problem...

But im guessing that the people saying this are linked to ubi... as it has not done anything with my issue.

Im thinking about a refund on the game, i am at the end of my teather. :damn:

If you mean the 175.16 drivers. I have installed them and I still have the same problems.

Ouch. That is really discouraging. This is the first time that I know of that a solution has not been found for a situation like this. And I'm discouraged that the devs haven't jumped in here to pick up on a legitimate problem. It's not as everyone else didn't jump in to try and it's not as if you haven't made an above and beyond the call of duty effort either.

hmm..
 

Hi!

I have read this thread and I also have this strange problem with deckgun and torpedoes. Whenever torpedo explode, my screen starts flicker in colors of a rainbow and soon after that game sometimes crashes. My specs are:

c2d e6600 (OC @ 3000)
GF 8800 GTS (with latest beta drivers)
Vista Home premium x64 (sp1)

I tried to run the game in windowed mode and I noticed that if game resolution is the same as my desktop resolution, SH4(ver. 1.5) does not go in windowed mode. So I lowered game resolution and started windowed mode and ran basic training mission and the problem was solved! I think ppl should try this!

So is there any command to force game to start in windowed mode, even if the gameresolution is same as my desktop resolution? (just to get bigger window)

BTW you have nice forum here! I just decided to join here just to reply to this post.

YEEHAA!
 

Thanks, Thermostator!:rock:

That did the trick. Windowed mode + one step lower resolution = YEEHAA!

Great!
 

Well, it seems that this might be temporary solution for this problem. Now we need to wait for hotfix/patch. Again, is there any way to force game to run in windowed mode (ie. command parameter, cfg -file edit ect.) even if the game resolution is the same as desktop resolution? I think Devs or modders should know this.

I'm not a modder, but one temporary solution is to set your resolution in main.cfg (located in \users\SH4\data\cfg) to as close to your native resolution as possible.
The native resolution of my display is 1280 x 1024. Therefore, I set my resolution to 1275 x 1020. The aspect ratio remains the same.

However, if you open the graphic settings in game, you have to reset those values next time you play the game.

And one more thing after all:
WELCOME!

I tried that...window at 1888 X1180 for my 1920X1200 monitor. Didn't work...I got instant BSOD when the first DD deck gun fired...
...Using VISTA32 + 8800GTX +SH4 1.5 + PE3

But you still got it working in "normal" windowed mode, as I explained?

Yes, the game loaded and the quick mission ran. Basically, one can insert any resolution paramters one chooses in the main.cfg file and the game will display accordingly. The 1888X1180 window was just slightly smaller than my monitor's native 1920X1200 res, so along the bottom I could still see the lower Windows Taskbar, which was irritating and distracting. Oddly, for some reason I couldn't 'grab' and move the 'window' down to cover that Taskbar. But, the main point is that ruining SH4 in windows-mode had no effect on the BSOD which occurs with PE + 1.5 + VISTA + 8800 card.

You can add me to the list of people that are having problems ruuning sh4+1.5+PE3.3 mod, I',m getting a black screen/lockups/sound looping everytime I get a torpedo hit etc etc & have to hard reset to get pc back up & running.

I spent hours trying different Nvidia forceware drivers with no success, have just un-installed the whole game & put it back on with patch 1.4, PE3.3 & everything is running sweet again :D

I just hope either Ubi or Nvidia get this bug sorted out!

You can all stop looking for a fix... because untill ubi release a patch it will never be compatable with 8800 GTX cards... So might aswell either be realy generous to ubi and be patiant or get a refund.

After lots of basic troubleshooting on there technical support ticket forum, they put my case on hold for over a month as DEVS look into it... and then today i got a reply...

"Response (UK Technical Support) 05/28/2008 11:25

Hello,

As a point of interest does it mention the GeForce 8800 series on the back of your game box? Our copy of the only mentions video cards upto the Nvidia GeForce 7800. It doesn't say that the game is actually compatible with the 8800GTX and it may be the case that your video-card is too powerful.

Regards,
Ubisoft Technical Support. "


Sorry all, but that reply was discusting, not only did they make me wait a month they got cocky at the end and basicaly said "it wont work and i dont care".