In your original post,
Full Path : C:\Windows\Minidump\102610-16364-01.dmp
Full Path : C:\Windows\Minidump\081710-15475-01.dmp
are what we're interested in here. If there doesn't seem to be any consistency in regards to these BSOD's then we can try to find the culprit(s) by analyzing files your computer saves, or "dumps," when crashes like yours occur. These files, just like the file path suggests, are called "minidumps."
First, navigate to this page:http://go.microsoft.com/fwlink/?LinkID=191420
and download the Windows 7 SDK. Install it on your computer (or another computer if your computer isn't stable enough).
Navigate through the installer until you reach Installation Options - you're interested in the Debugging Tools redistributable package.
Once it's installed, you want to run a program called "windbg.exe", which, under a default installation, should be located in:
x86: %programfiles%\Debugging Tools for Windows\
x64: %programfiles%\Debugging Tools for Windows (x64)\
When you open WinDbg, the first thing you'll need to do before you can analyze one of these minidump files is to point WinDbg to a location where it can read "symbol files", which for our purposes here are just files that contain important information WinDbg needs to be able to analyze the minidump.
Click on the File menu
Click on "Symbol File Path ..."
paste this into the Symbol File Path box and click OK:
If you don't have internet access, navigate to this page on another computer:
and download the symbol file package that corresponds to the affected operating system. Transfer the installer over to the computer you installed the Debugging Tools on and run the package. The default install path for the symbol files should be:
If you downloaded and installed the Symbol File package instead, you'll need to point WinDbg to the above path.
Once WinDbg knows where to read symbol files, open up your minidump file and analyze it. These minidump files are saved in:
It's helpful to first open up an explorer window where the minidump files are saved so you can:
a.) see what you're dealing with (how many minidump files are in this folder)
b.) what they're dated (it helps to sort them by most recent)
Go back to WinDbg, click File > Open Crash Dump, and navigate to the directory where the minidump files are saved. Choose the most recent minidump available.
Wait for WinDbg to download/collect symbol files, and when it's ready enter:
and press enter.
WinDbg will output an analysis of the minidump file in question.
You can copy and paste the output in WinDbg as a reply in this topic so we can analyze it for you. It This output may help us determine if your problem is malware related or not. It may be more helpful to analyze at least a few of these minidump files and upload their contents (but please don't go overboard with the amount of logs you post - I'm new at this forum and am currently not aware of any posting limits enforced on this site). If it looks to be malware related, get with a Malware Response Team member and they should be able to assist you.
Edited by dodes, 30 October 2010 - 10:04 AM.