Persistent BSOD

[XiahoudDun]

- x86 (32-bit) or x64 ? Windows 7 32 bit
- the original installed OS on the system? Windows vista
- an OEM or full retail version? full retail
- What is the age of system (hardware)? about 4-5 years
- What is the age of OS installation about 6 months on windows 7

I have been haveing problems with this for about a month but are now more frequent. The blue screen says its hardware related but I would like to narrow it down more. I had to restore windows to a previous point to get windows to reboot again whenever the BSOD appears. Other things I've notice is sometimes plugin in my google chrome browser doesn't work and the database in Kapersky 2010 gets corrupted. I ran this under a different administrator to censor my name. I hope this doesn't change anything.

I hope you all can help. Thanks in advance.

 

[CarlTR6]

Welcome to the forum. Sorry you are having problems. I will take a look.

There are no mini dumps included in your upload. Read this tutorial and upload just the dump files.

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

To get you started, I find an almost guaranteed BSOD maker on your system:

Please uninstall any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dump, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads. Select delete; do not select reinstall.
Here is an alternative virtualization program that does not user the sptd.sys driver:

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

Also, please uninstall Kaspersky while you are trouble shooting. Kaspersky has been known to cause BSOD's on some Win 7 systems. You can reinstall it after you get your system stable; but I do not recommend doing so. Download and install Microsoft Security Essentials in its place and make sure Windows Firewall is turned on.

 

[cybercore]

I can't even open your "Documents.zip" <- re-upload it plz as described in BSOD posting instructions.

 

[CarlTR6]

I can't even open your "Documents.zip" <- re-upload it plz as described in BSOD posting instructions.

It worked fine for me. I got all of the files except no dump files.

 

[XiahoudDun]

I am at work so i can't do it now but I am unsure on what i did wrong. I read the forum post about how to post and i ran the BSOD Dump & System File Collection app as the perfmon /report and saved as html. I packed both the output directory and html in a winzip file using winrar (forgot version).

I'm not completely proficient in computers but did I not let the first app totally finish or completely miss something in the instructions?

 

[CarlTR6]

I doubt that you did anything wrong. All of the files are in your upload except for the dump files. The tutorial at the link I posted above will tell you how to find and upload just the dump files (we already have your system information from your first upload). The last screen shot in the first post will show you how to make sure your system is setup to save mini dumps. You may have omitted a step or your system may not be setup for mini dumps.

 

[XiahoudDun]

Okay so from what I understand now. I didn't have my system set to create minidumps (it was on kerneldump in the system failure settings). Now it is set to Small memory dump 128kb. My only .dmp file i see is the MEMORY.dmp in the /Windows directory and I have no Minidump directory.

So now i'm guessing I have to wait for my computer to crash again to get the relevent information into these small dumps? (I apologize for the beginner level questions but I'm new at this). I appreciate everyone patience and help in this.

 

[CarlTR6]

You figured it out and you are exactly right. Your next crash will produce a mini dump.