after patch 1.3 a couple of ctd's are constantly occuring. Most notably mid camp mccarran. While not totally game breaking it is pretty bad, especially since many things go on there. Notably there were no solid, immutable ctd's like this encountered before.

Can anyone tell when a fix for the new patch specific issues will be rolling out?

"Soon." <_<

...in short, nope. And even when they do hand out a new patch, it's never guaranteed that it'll fix anyone's specific issue.

Crap, I'm running into this too. Due to various reasons I had to put FNV aside for a while (I had +/- 70 hours into the game) and barely had any crashes after the first 1-2 patches came out. Now after the recent updates I find my game to crash to the desktop reasonably often. My current problem being that it triggers when I approach the Terminal Building of the Camp McCarran location. If I approach from the road, I need to be pretty close to the door, if I first walk into the camp and then rotate my view to look at the building it will also crash.

Must be some graphical rendering bug that manifests itself. (That or my save game is causing issues, since it's from 1.1 or so, but would be weird though, since it only manifests itself consistently with, say, Camp McCarran's Terminal Building.)

Edit: even when walking backwards towards the building I trigger the crash in the same place. After managing to generate a crashdump I did some initial digging and got to:

FAULTING_THREAD:  000012dcBUGCHECK_STR:  APPLICATION_FAULT_MEMORY_CORRUPTION_INVALID_POINTER_READ_LARGEPRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGEDEFAULT_BUCKET_ID:  MEMORY_CORRUPTION_LARGELAST_CONTROL_TRANSFER:  from 0043fd55 to 004a51aaSTACK_TEXT:  WARNING: Stack unwind information not available. Following frames may be wrong.0018f988 0043fd55 00541fba 0102b9fc 39221960 FalloutNV+0xa51aa0018f99c 0054cca0 1a435934 011f20b8 0f28a6ac FalloutNV+0x3fd550018f9c0 0054c1f0 00000000 00000000 00000016 FalloutNV+0x14cca00018fa14 00453ac3 00000001 d58c2d7f 00000000 FalloutNV+0x14c1f00018fb2c 6c260863 0c989a00 00000000 0c989a04 FalloutNV+0x53ac30018fbe4 7741bb15 00000008 00000000 00000000 d3d9!CheckForDeviceLost+0x1180018fbfc 7741ba97 00000000 00000000 00000000 ntdll!RtlpQueryInformationActivationContextBasicInformation+0x700018fc7c 00000000 00000c94 00001864 00cd033a ntdll!RtlQueryInformationActivationContext+0x3d4

Managed to get debugger attached and dump some information the moment I hit the crash point in Camp McCarran:

Access violation - code c0000005 (first chance)FalloutNV+0xa51aa:004a51aa 8b00            mov     eax,dword ptr [eax]  ds:002b:c49cbc10=????????0:000:x86> !anolyze -vFAULTING_IP: FalloutNV+a51aa004a51aa 8b00            mov     eax,dword ptr [eax]EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff).exr 0xffffffffffffffffExceptionAddress: 00000000004a51aa (FalloutNV+0x00000000000a51aa)   ExceptionCode: c0000005 (Access violation)  ExceptionFlags: 00000000NumberParameters: 2   Parameter[0]: 0000000000000000   Parameter[1]: 00000000c49cbc10Attempt to read from address 00000000c49cbc10FAULTING_THREAD:  0000000000001a28PROCESS_NAME:  FalloutNV.exeERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.EXCEPTION_PARAMETER1:  0000000000000000EXCEPTION_PARAMETER2:  00000000c49cbc10READ_ADDRESS:  00000000c49cbc10 FOLLOWUP_IP: FalloutNV+a51aa004a51aa 8b00            mov     eax,dword ptr [eax]MOD_LIST: NTGLOBALFLAG:  0APPLICATION_VERIFIER_FLAGS:  0CHKIMG_EXTENSION: !chkimg -lo 50 -d !KERNEL32!chkimg -lo 50 -d !KERNEL32    769a103d-769a1041  5 bytes - KERNEL32!CreateProcessW	[ 8b ff 55 8b ec:e9 08 f1 f3 ff ]    769a1072-769a1076  5 bytes - KERNEL32!CreateProcessA (+0x35)	[ 8b ff 55 8b ec:e9 13 f1 f3 ff ]    769a34c8-769a34cc  5 bytes - KERNEL32!FreeLibraryStub (+0x2456)	[ 8b ff 55 8b ec:e9 3d cc f3 ff ]    769a4913-769a4917  5 bytes - KERNEL32!LoadLibraryExAStub (+0x144b)	[ 8b ff 55 8b ec:e9 32 b7 f3 ff ]    769a492b-769a492f  5 bytes - KERNEL32!LoadLibraryW (+0x18)	[ 8b ff 55 8b ec:e9 5a b7 f3 ff ]    769a495d-769a4961  5 bytes - KERNEL32!LoadLibraryExWStub (+0x32)	[ 8b ff 55 8b ec:e9 a8 b6 f3 ff ]    769a49d7-769a49db  5 bytes - KERNEL32!LoadLibraryA (+0x7a)	[ 8b ff 55 8b ec:e9 ee b6 f3 ff ]35 errors : !KERNEL32 (769a103d-769a49db)BUGCHECK_STR:  APPLICATION_FAULT_MEMORY_CORRUPTION_INVALID_POINTER_READ_ZEROED_STACK_LARGEPRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGEDEFAULT_BUCKET_ID:  MEMORY_CORRUPTION_LARGELAST_CONTROL_TRANSFER:  from 000000000043fd55 to 00000000004a51aaSTACK_TEXT:  WARNING: Stack unwind information not available. Following frames may be wrong.0018f988 0043fd55 00541fba 0102b9fc 37221960 FalloutNV+0xa51aa0018f99c 0054cca0 066d6f1c 011f20b8 1b28a6c8 FalloutNV+0x3fd550018f9c0 0054c1f0 00000000 00000000 00000016 FalloutNV+0x14cca00018fa14 00453ac3 00000001 cba59e08 00000000 FalloutNV+0x14c1f00018fa90 00453412 45000000 c6b00000 00000bc5 FalloutNV+0x53ac30018fb04 0086deb2 03be1650 00000001 00000000 FalloutNV+0x534120018fb1c 0086cdb4 00000000 00000000 00000000 FalloutNV+0x46deb20018fb74 00869658 00000000 778a0d38 0100db28 FalloutNV+0x46cdb40018fef8 00ec9770 00400000 00000000 01544f44 FalloutNV+0x4696580018ff88 769a33ca 7efde000 0018ffd4 77419ed2 FalloutNV+0xac97700018ff94 77419ed2 7efde000 778a0ee8 00000000 KERNEL32!BaseThreadInitThunk+0xe0018ffd4 77419ea5 00ec97db 7efde000 00000000 ntdll_773e0000!__RtlUserThreadStart+0x700018ffec 00000000 00ec97db 7efde000 00000000 ntdll_773e0000!_RtlUserThreadStart+0x1bSYMBOL_NAME:  memory_corruption!KERNEL32FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: memory_corruptionIMAGE_NAME:  memory_corruptionDEBUG_FLR_IMAGE_TIMESTAMP:  0STACK_COMMAND:  ~0s ; kbFAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE_c0000005_memory_corruption!KERNEL32BUCKET_ID:  X64_APPLICATION_FAULT_MEMORY_CORRUPTION_INVALID_POINTER_READ_ZEROED_STACK_LARGE_memory_corruption!KERNEL320:000:x86> .exr -1ExceptionAddress: 00000000004a51aa (FalloutNV+0x00000000000a51aa)   ExceptionCode: c0000005 (Access violation)  ExceptionFlags: 00000000NumberParameters: 2   Parameter[0]: 0000000000000000   Parameter[1]: 00000000c49cbc10Attempt to read from address 00000000c49cbc100:000:x86> reax=c49cbc10 ebx=00000001 ecx=c49cbc10 edx=37221960 esi=00000000 edi=fffffffeeip=004a51aa esp=0018f984 ebp=0018f988 iopl=0         nv up ei ng nz ac po nccs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00210292FalloutNV+0xa51aa:004a51aa 8b00            mov     eax,dword ptr [eax]  ds:002b:c49cbc10=????????

Can't do much beyond this without debugging symbols of course.
The question is why it would cause a typical invalid pointer error at the same spot all the time.

Edit: Funny, exiting the camp and immediately entering again clears whatever was causing the issue. Guess something is messing with pointers when it comes to the save file handling because I can still duplicate it whenever I load the specific save file.