Bsod windows 7 professional x64

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

6 memory dumps
6 different BSOD error codes, 4 different causes blamed
Most likely a hardware issue.

Keep an eye on Catalyst Control Center and the NEC USB 3.0 stuff - they have some issues with older drivers on Win7 systems.

I would suggest running Driver Verifier even though this is likely to be a hardware problem. The reason for this is the address' in the dump files suggest that there's an address issue happening (and this could be isolated by Driver Verifier if it's a 3rd party driver). Please use these directions for running Driver Verifier:

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.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov 12 07:46:28.789 2010 (UTC - 5:00)
System Uptime: 0 days 0:08:52.147
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c7b )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
Bugcheck code 00000019
Arguments 00000000`00000003 fffffa80`03303510 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov 12 07:04:33.517 2010 (UTC - 5:00)
System Uptime: 0 days 0:07:32.515
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+298 )
BUGCHECK_STR:  0x1a_8886
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  VSSVC.exe
Bugcheck code 0000001A
Arguments 00000000`00008886 fffffa80`034356f0 fffffa80`01e94710 00000000`00000600
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov 12 06:56:15.359 2010 (UTC - 5:00)
System Uptime: 0 days 0:06:23.717
Probably caused by : ntkrnlmp.exe ( nt!RtlInsertElementGenericTableFullAvl+97 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
Bugcheck code 00000050
Arguments fffff8a0`08f046b8 00000000`00000000 fffff800`02cf47ab 00000000`00000002
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrn.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrn.exe
Debug session time: Thu Nov 11 08:30:54.345 2010 (UTC - 5:00)
System Uptime: 0 days 0:06:08.343
*** WARNING: Unable to verify timestamp for ntoskrn.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrn.exe
Probably caused by : memory_corruption
*** WARNING: symbols timestamp is wrong 0x4a5bc11e 0x4a5bc14f for Ntfs.sys
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`05fa96e8 fffff880`05fa8f50 fffff880`012c195b
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 11 07:51:47.186 2010 (UTC - 5:00)
System Uptime: 0 days 0:07:49.544
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+18d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  Azureus.exe
Bugcheck code 0000000A
Arguments 00000000`0007fffd 00000000`00000002 00000000`00000000 fffff800`02c8219d
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 11 07:21:12.529 2010 (UTC - 5:00)
System Uptime: 0 days 0:02:30.887
*** WARNING: Unable to verify timestamp for spsys.sys
*** ERROR: Module load completed but symbols could not be loaded for spsys.sys
Probably caused by : spsys.sys ( spsys+1fc7e )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  sppsvc.exe
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 fffff880`07509c7e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  

That error can be caused by bad memory also. I'd suggest just using the one stick until your new one comes in.

Have you tried the good stick in the other slot? This is to rule out a problem with the slot.