Video of where the crash takes place :

http://www.youtube.com/watch?v=7DMkVaMuXns

The obvious question is whether you can reproduce this every time you enter that fight. If you can, you probably should post your DXDiag output as suggested in the forum and cross your fingers...

I was lucky enough not to experience this one myself. :/

The Sauna crash is most likely not hardware or codec related. People with otherwise very stable experiences have reported repeated and nearly random crashing in the Sauna - particularly with Chauncey present.

The DXDiag is useless, and we must stop with the codecs, game in summer made hastily , that's the real reason.

Whenever I approach Chauncey, the game hangs and back desk

My config :

OS : Windows 7 édition Familiale Premium 64-bit
Processor : Intel® Core™ i5 CPU 750 @ 2.67GHz (4 CPUs), ~2.7GHz
Memory : 6144MB RAM
Available OS Memory : 6136MB RAM
DirectX Version: DirectX 11

Card name : NVIDIA GeForce GT 220
Manufacturer : NVIDIA
Chip type : GeForce GT 220
Display Memory: 3798 MB
Dedicated Memory : 986 MB
Shared Memory : 2811 MB
Current Mode: 1680 x 1050

I tried to set options, but nothing helped.

We must wait for the patch, unfortunately ...

Some specific codecs can cause problems - not just for this game either. Most of these 3rd party codecs are completely unnecessary as well. While it is almost certainly unrelated to your issues it is generally a good reason to ask for a DXDIAG output. Again, in your case with the sauna crashes, this seems to be a reproduceable glitch across a range of hardware configurations, drivers, operating systems, and patch versions regardless of installed codecs. Not everyone exerpiences however as the specific call that triggers it appears to be slightly random. Some people are lucky not to be in the steam room long enough to crash and it is possible that some hardware/software combinations simply do not crash in this area.

That last possibility is one of the best reasons to still post the DXDIAG output - if it is a something that does not present on particular hardware configurations but only on some (even if some=most) then it will help the devs formulate a fix. In the mean time though, yes it is broken and an actual bug and it is one of the more annoying ones too.

Try saving and reloading (seperate save file) just before talking to him. I was able to get through the encounter by doing this a couple times (like 8 crashes) but since they didn't always happen at exactly the same time I was eventually able to get through it. It also seems to help, for some reason, to wait for him to sit down first and to close the steam room doors before talking to him. I think that may be because the actual trigger for the crash could be one of the nameless npc bathers.

Post your dxdiag. Saying that codecs aren't an issue is like saying "dust clogging my CPU and Video card won't cause it to over heat". I'll just face palm and walk away at that.

I have no mod, the game is original, my problems came after the first patch

I agree. This is starting to feel like stubborness about refusing to post your DXDIAG output; it does not contain any personal information besides potentially whatever you chose to name your computer. You can just censor that part.

Granted, with this issue there's about a high probability you will not have anything in there that indicates a culprit; there is still a chance that someone will see something that could be responsible. It should be important to note though that this problem is not caused by any of the patches and had been happening with all versions including the launch version. As I said earlier though, there is a strange sort of randomness to it. Being completely unable to get through the sauna even using the "save, proceed, crash, reload, proceed, save, crash, reload..." method is unusual however so it is worth at least letting people look at your DXDIAG output and the codec lists in particular.

If you can't post it for whatever reason then there probably won't be any more help forthcoming. If it is the same sort of crash others have experienced, hopefully it will be rolled up in the upcoming (long time coming) patch. If it isn't fixed by that patch then expect to be asked for a DXDIAG output to be included in your post.

We are just trying to help here - and none of us work for Bethesda or Obsidian so we have no agenda beyond distracting ourselves at work/school/wherever.