Live Chat & Podcast at 1:00PM Eastern on Sunday!
There's no such thing as a stupid question, but they're the easiest to answer.
JoinTour
Login
Search
Windows 7
Tag Cloud
access acer asus bios bsod computer crash desktop driver drivers error ethernet excel freeze gaming hard drive hardware hdmi internet laptop malware memory monitor motherboard music netgear network printer problem ram registry router server slow software sound trojan ubuntu 11.10 uninstall usb video virus vista wifi windows windows 7 windows 7 32 bit windows 7 64 bit windows xp wireless
Search
Search for:
Tech Support Guy Forums > Operating Systems > Windows 7 >
Many BSODs

Reply  
Thread Tools
Mark941's Avatar
Junior Member with 7 posts.
 
Join Date: Apr 2008
20-Nov-2009, 11:58 PM #1
Many BSODs
So I'm running a fresh copy of Windows 7 Ultimate and I seem to be getting frequent BSODs. They only happen either right at login or while I'm playing a game, and all seem to be caused by something different. Below are the minidumps.
Attached Files
File Type: zip crash dumps.zip (140.5 KB, 5 views)
Mark941's Avatar
Junior Member with 7 posts.
 
Join Date: Apr 2008
21-Nov-2009, 10:30 AM #2
Another crash, here's the dump.
Attached Files
File Type: zip 112109-15678-01.zip (36.1 KB, 2 views)
Rollin' Rog's Avatar
Computer Specs
Distinguished Member with 46,024 posts.
 
Join Date: Dec 2000
Location: North of Hollywoodland
Experience: I know when to fold em'
21-Nov-2009, 12:44 PM #3
Can you supply some more information about the hardware configuration? What have you loaded Win7 onto? You may be overtaxing the hardware. What is the Windows Experience Index for this system? http://windows.microsoft.com/en-us/w...perience-index




The variety of these faults would point to a hardware issue.

Has the ram been tested? Are you overclocking anything? If stress related, heat could be a cause.

You can test ram by running mdsched.exe and once the scanner has rebooted press F1 for Advanced options and run the Extended tests.

I would not even be satisfied with a "pass" here but would also try Memtest86 to confirm the results, and really you might want to test on one module at a time.

Beginners Guides: Diagnosing Bad Memory

Memtest86 - A Stand-alone Memory Diagnostic

--------------------------------------------------------------------

You should also open the Control Panel > Action Center > Maintenance and look at the Reliabilty history graph and other tools there that might flag persistent problems.
Mark941's Avatar
Junior Member with 7 posts.
 
Join Date: Apr 2008
21-Nov-2009, 03:34 PM #4
Processor Intel(R) Core(TM)2 Extreme CPU X9650 @ 3.00GHz 7.3
Memory (RAM) 4.00 GB 5.5
Graphics NVIDIA GeForce 8800 Ultra 6.9
Gaming graphics 1919 MB Total available graphics memory 6.9
Primary hard disk 39GB Free (78GB Total) 5.9

I'm not overclocking anything, and I don't think it's overheating seeing as a just got a new fan. I also don't think it's memory because XP was working just fine before I installed Windows 7, but I'll run a RAM test and check back just to make sure.
Rollin' Rog's Avatar
Computer Specs
Distinguished Member with 46,024 posts.
 
Join Date: Dec 2000
Location: North of Hollywoodland
Experience: I know when to fold em'
22-Nov-2009, 02:21 PM #5
Ok, I've looked at all the minidumps trying to find some common denominator that might explain the variety of errors. At first I thought it might be the Nvidia Ethernet driver.

But here is the back trace of the BSOD with the fewest loaded drivers.

My suspicion here is the Sata drivers, as nvstor32.sys is common to all of them, and indeed has multiple identical modules in many. Other drivers get nailed as faulting because of pool corruption that involves them but is not necessarily caused by them.

BUCKET_ID: 0x7E_nt!KiFastCallEntry+f7

Followup: MachineOwner
---------

Quote:
0: kd> kd (display back trace)
*** WARNING: Unable to verify timestamp for mcupdate_GenuineIntel.dll
*** ERROR: Module load completed but symbols could not be loaded for mcupdate_GenuineIntel.dll
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*** WARNING: Unable to verify timestamp for BOOTVID.dll
*** ERROR: Module load completed but symbols could not be loaded for BOOTVID.dll
*** WARNING: Unable to verify timestamp for CLFS.SYS
*** ERROR: Module load completed but symbols could not be loaded for CLFS.SYS
*** WARNING: Unable to verify timestamp for CI.dll
*** ERROR: Module load completed but symbols could not be loaded for CI.dll
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
*** WARNING: Unable to verify timestamp for rdyboost.sys
*** ERROR: Module load completed but symbols could not be loaded for rdyboost.sys
*** WARNING: Unable to verify timestamp for nvstor32.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor32.sys
*** WARNING: Unable to verify timestamp for amdxata.sys
*** ERROR: Module load completed but symbols could not be loaded for amdxata.sys
*** WARNING: Unable to verify timestamp for spldr.sys
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
Couldn't resolve error at 'display back trace)'
Unstable or corrupt Sata drivers could cause all the varied BSODs, much like bad ram.

----------------------------------

This is from a different BSOD (fileinfo.sys was the flagged culprit) >>

Quote:
BUCKET_ID: 0x19_3_fileinfo!FIStreamGetInfo+109

Followup: MachineOwner
---------

2: kd> kd (display back trace)
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
*** WARNING: Unable to verify timestamp for nvstor32.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor32.sys
*** WARNING: Unable to verify timestamp for amdxata.sys
*** ERROR: Module load completed but symbols could not be loaded for amdxata.sys
*** WARNING: Unable to verify timestamp for spldr.sys
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
*** WARNING: Unable to verify timestamp for drmk.sys
*** ERROR: Module load completed but symbols could not be loaded for drmk.sys
*** WARNING: Unable to verify timestamp for dump_nvstor32.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_nvstor32.sys
*** WARNING: Unable to verify timestamp for LHidFilt.Sys
*** ERROR: Module load completed but symbols could not be loaded for LHidFilt.Sys
*** WARNING: Unable to verify timestamp for LMouFilt.Sys
*** ERROR: Module load completed but symbols could not be loaded for LMouFilt.Sys
*** WARNING: Unable to verify timestamp for avgntflt.sys
*** ERROR: Module load completed but symbols could not be loaded for avgntflt.sys
*** WARNING: Unable to verify timestamp for ssmdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for ssmdrv.sys
*** WARNING: Unable to verify timestamp for avipbb.sys
*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys
*** WARNING: Unable to verify timestamp for avgio.sys
*** ERROR: Module load completed but symbols could not be loaded for avgio.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for nvBridge.kmd
*** ERROR: Module load completed but symbols could not be loaded for nvBridge.kmd
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for nvmf6232.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6232.sys
*** WARNING: Unable to verify timestamp for TSDDD.dll
*** ERROR: Module load completed but symbols could not be loaded for TSDDD.dll
*** WARNING: Unable to verify timestamp for peauth.sys
*** ERROR: Module load completed but symbols could not be loaded for peauth.sys
*** WARNING: Unable to verify timestamp for secdrv.SYS
*** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
Couldn't resolve error at 'display back trace)'
Mark941's Avatar
Junior Member with 7 posts.
 
Join Date: Apr 2008
22-Nov-2009, 09:26 PM #6
Ok I'm going to bed now, but I'll test it out tomorrow. Thanks for the help.
Reply

THIS THREAD HAS EXPIRED.
Are you having the same problem? We have volunteers ready to answer your question, but first you'll have to join for free. Need help getting started? Check out our Welcome Guide.

Search Tech Support Guy

Find the solution to your
computer problem!




Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
WELCOME TO TECH SUPPORT GUY! Are you looking for the solution to your computer problem? Join our site today to ask your question -- for free! Our site is run completely by volunteers who want to help you solve your computer problems. See our Welcome Guide to get started.
Thread Tools



Facebook Facebook Twitter Twitter TechGuy.tv TechGuy.tv Mobile TSG Mobile
You Are Using:
Server ID
Advertisements do not imply our endorsement of that product or service.
All times are GMT -4. The time now is 07:00 PM.
Copyright © 1996 - 2011 TechGuy, Inc. All rights reserved.

Powered by Cermak Technologies, Inc.