Assassinative Bluescreen 3rd

Windows is lying to you! :)
Seriously, updating through Windows Update or the Update driver function of Device Manager will not fix your problem.

Please follow zigzag3143's advice and uninstall the current drivers - then visit the video card chipset manufacturer's website ( Drivers - Download NVIDIA Drivers ) to download and install the latest version available there.
__________________________________________________________________________________________
FYI - Windows Update and the Update drivers function of Device Manager only check the Microsoft servers for drivers. And, if the manufacturer's don't submit the drivers to Microsoft, then you won't get an updated version - and Microsoft will tell you that it's the most updated version available.

For example, Asus hasn't submitted an updated version of the ASACPI.sys driver to Microsoft - so the 2005 version is the one that you get when you visit the Microsoft update sites. But that version will give you problems, so you'll have to visit the Asus website to get a more updated version.

The nVidia drivers were updated from the last BSOD.

This dump file blames the kernel (core) of the operating system. If this were the case you'd be having many more issues other than the occasional BSOD.

But, this is almost certainly a device driver BSOD (more info here; BSOD Index ) so let's see if Driver Verifier can force the system to reveal the name of the offending drivers.

To do this, please run Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 00:29:44.623 2010 (UTC - 4:00)
System Uptime: 0 days 4:04:59.386
BugCheck 4A, {74f32dd9, 2, 0, fffff88007941c60}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
PROCESS_NAME:  AssassinsCreed
BUGCHECK_STR:  RAISED_IRQL_FAULT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 

It said what about Driver Verifier? Please let us know the exact error message that you're receiving.

While it's possible that this could be an issue with x64, installing an x86 version is much more likely to work because of the reinstallation rather than the difference between the 2 versions.