Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


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


25 Jan 2010   #1

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

Hello,

Few days before New Year i bought new "fancy" and "strong" computer.
Configuration:
Motherboard: GIGABYTE PP55-UD3P
Processor: Intel i5-750
Graphic card: GIGABYTE ATI RADEON 5870 1GB DDR5
Memory: Kingston 2x2GB DDR3 1600MHz (1333MHz is default i didnt overcloacked)
Hard disk: 1TB Samsung 7200rpm 32MB cash
Monitor: SONY LCD TV 32" Bravia

I installed windows 7 x64... and my nightmare begins.

First I got some BSODs during installation of drivers that came in card package. I am not sure if it was graphic card or motherbord drivers. I downloaded and installed newest 9.12 Catalist from ATI site, drivers for 5800 serie for windows 7 x64.

Then I proudly installed DIRT 2 that came with ATI RADEON 5870. I got couple of crashes during DIRT intro as many other ati card owners complaint about on forums. I think I eliminated that problem when i set GPU and memory frenquency to be 850MHz and 1200MHz for all windows energy saving states (there are 3 of those in ati profile file). Before I did that I had quite a few graphic card crashes with stripes on screen and had to hard reset the computer (problem that is also well known to ati card users according to forums).

And finally when i thought i had solved all issues (no crashes for a few days) i got two BSODs in last three days. I leave computer to download something and after few hours ... crash.
I have plugged this computer and my work laptop both to SONY TV (PC is connected via HDMI cable and laptop via VGA cable). I switch often between computers. Most crashes happens while TV is turned off (maybe there is some issue here?).

I havent overcloacked anything in bios. I didnt flashed motherboard or graphic card bios.

Please if anyone can help to get my system stable i am afraid hard disk will get corrupted due all this hard resets.

My System SpecsSystem Spec
.

25 Jan 2010   #2
Microsoft MVP

 
 

The debugger can't access symbols for your copy of Windows 7.
Please let us know where you got your copy of Windows 7 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 Windows 7 (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:
Quote:
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/Windows 7 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
My System SpecsSystem Spec
26 Jan 2010   #3

Windows 7 x64
 
 

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.
My System SpecsSystem Spec
.


26 Jan 2010   #4
Microsoft MVP

 
 

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
My System SpecsSystem Spec
27 Jan 2010   #5

Windows 7 x64
 
 

Thanks usasma. I added to your reputation

I uninstalled Zone alarm and installed Windows 7 firewall control.
Then i run driver verifier utility again.

This time I was able to log into windows. But i got two more BSODs. First BSOD happened when i started PeerBlock application and other when i was downloading two debbuging tools at a same time from Microsoft site.
My System SpecsSystem Spec
27 Jan 2010   #6
Microsoft MVP

 
 

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.
My System SpecsSystem Spec
28 Jan 2010   #7

Windows 7 x64
 
 

I turned on driver verifier for half an hour or so and during that time i started most programs i am usually using to see what is crashing the system. Everything works fine for now will keep to monitor and post if any problems.
I guess most problems were caused by graphic card anyway so will have to wait for new drivers.
Thanks
My System SpecsSystem Spec
Reply

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




Thread Tools



Similar help and support threads for2: BSODs in Windows 7 x64. Graphic card or memory issue?
Thread Forum
Weird graphic card memory Graphic Cards
graphic card memory. Graphic Cards
HELP! Graphic card issue Graphic Cards
More memory to graphic card Graphic Cards
Graphic Card Issue after clean install of Windows 7 Graphic Cards
graphic card radeon issue Graphic Cards
Graphic Card Memory Graphic Cards

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:04 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33