BSODs in Windows 7 x64. Graphic card or memory issue?

The debugger can't access symbols for your copy of Windows 7.
Please let us know where you got your copy of Win7 from.
If it was on a disk, what did the disk say?

There's really nothing that's identified by the BSOD's.

First, please uninstall your copy of Acronis True Image - it's an older version that may have some issues with Win7 (even if it's listed as "compatible"). You can reinstall it after we've finished troubleshooting.

Please run Driver Verifier according to these instructions to see if it can get us any extra information:

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"
- 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.

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

Summary of the BSOD's:

Code:

*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.20576.amd64fre.win7_ldr.091115-1505
Debug session time: Sat Jan 23 06:53:51.775 2010 (GMT-5)
System Uptime: 0 days 3:40:40.821
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 7F, {8, 80050031, 6f8, fffff80002cc64df}
Probably caused by : ntoskrnl.exe ( nt+689c0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.20576.amd64fre.win7_ldr.091115-1505
Debug session time: Mon Jan 25 11:14:51.944 2010 (GMT-5)
System Uptime: 2 days 4:19:44.451
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 7F, {8, 80050031, 6f8, fffff80002cc24df}
Probably caused by : ntoskrnl.exe ( nt+689c0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

Thanks for quick replay usasma.

I have unistalled Acronis. It was a trial version anyway.

I have run driver verfier tool and computer crashed before it was able to load windows. I used restore point to recover.

Windows 7 Ultimate 6.1.7600 build 7600

I attached mini dump file created by crash caused by driver verfier.

And it blames vsdatant.sys - a component of ZoneAlarm.

Please uninstall ZoneAlarm to verify that this is the problem.
IMMEDIATELY install one of these free antivirus programs for protection if you don't have one: Free AntiVirus

You can use this free firewall control app to take the place of ZoneAlarm: Windows 7 Firewall Control : Sphinx Software

Summary of the BSOD:

Code:

*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.20576.amd64fre.win7_ldr.091115-1505
Debug session time: Tue Jan 26 03:41:39.789 2010 (GMT-5)
System Uptime: 0 days 0:00:15.210
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck C4, {121, 2, fffff88002c674b0, 0}
*** WARNING: Unable to verify timestamp for vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
Probably caused by : vsdatant.sys ( vsdatant+674b0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

Please turn Driver Verifier off. It can cause errors in drivers even if you aren't getting BSOD's without it running.

If you get further BSOD's, then we'll have a look to see if running Driver Verifier is appropriate.

The first BSOD was due to the Peer Block application - but I suspect that it's primarily due to the stress of Driver Verifier. The second BSOD was due to ntoskrnl.exe - which isn't even in the realm of testing for this run of Driver Verifier.