Windows 64-bit Build instability with recent nVidia Drivers - CRASH!!

I've submitted this bug report, but was hoping others might chime in here as well if they know anything about it. Or at least if others experience this problem can have some indication that they're not alone. Here's the report:

1) What happened?
For Windows 7 Pro, a 64-bit client with the latest nVidia driver (352.86 or 353.06) cause the application to crash (freeze). The last known working driver was 350.12. This problem has not occurred on our machines with AMD cards, nor in the 32-bit client, nor in the editor! It only occurs in the 64-bit build with the nVidia drivers listed above.

2) How is it reproduced?
The 64-bit windows client that will crash if you do the following. Start the game, and after entering the title screen, select New Game and enter a profile name. The game will begin to load the first scene (called 1a_scene), and can typically load without crashing. The crash occurs either when you rotate the camera with the mouse, or land from a jump with the space bar (which induces a headbob impact that rotates the camera), or sometimes immediately after loading completes (this might hinge on there being save data).

I've tested both our main Unity version, 4.5.5, as well as the latest pre-Unity 5 version, 4.6.5, and both crash in the same manner.

By attaching Visual Studio's debugger, I have been able to break at a crash point within the nvd3dumx.dll thread, but cannot read the stack, which was given as follows:
> 00000000030e01e1() Unknown
0000000000478000() Unknown
0000000000478000() Unknown
0000000005be5e30() Unknown
00000000004aecf0() Unknown
0000000000480d80() Unknown
000000000722b4e8() Unknown
0000000000478000() Unknown

 

Brief update from Unity, for anyone who finds this.

The bug report on fogbugz has been acknowledged by Unity as reproducible and they are fixing it. Hopefully this will be fixed for the 4.6 client as well, since that is the client I am using!

http://fogbugz.unity3d.com/default.asp?701521_7vkf8vej3h0pq2f8

Bug reporting works!!

 

I am having problems still. Is this bug still in the system?