Continual BSOD All Day, Unable to Complete DM Log Collector

TMPinSYR · 30 Dec 2014

The problem began this morning on an otherwise very stable machine (Win7 Ultimate, x64). Almost anything I try ends in another BSOD. (Sorry: Title is inaccurate. It took 3 tries to get it to complete successfully.)

I'm somewhat tech-savvy but I'm at a loss on this one. Any help would be appreciated!

EDIT:
Ugh. The third attempt to grab the logs worked but as soon as I tried opening the browser to attach the zip file I got another BSOD. (I typed this on my Chromebook which, by the way, is rapidly becoming my favorite device!)

Finally copied the zip file to my Google Drive from the Win7 machine then attached it from the good old CB!

TMPinSYR · 30 Dec 2014

Figured I'd add some additional information as best as I can recall. Things I've tried...

Memory check (completed twice, no errors found)
Checkdisk (completed, no errors found)
Uninstalling AVG (still got a BSOD after that, then reinstalled AVG and got another BSOD)
Tried scanning for malware with AVG (at least twice, both times I got a BSOD midway through scan)
Successful Spybot - Search & Destroy scan yesterday (clean other than some tracking cookies)
Windows System Restore back to a restore point from yesterday (before the BSODs started)
Windows Update, system up to date

I may have tried other things as well, these are the ones that come to mind right now.

Golden · 31 Dec 2014

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c6360040, 0, fffff800030e1770, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ObFastReferenceObject+10 )

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

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Reference this tutorial to help you use MemTest86+:
RAM - Test with Memtest86+

Code:

Host Name:                 TODD-PC
OS Name:                   Microsoft Windows 7 Ultimate 
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Todd
Registered Organization:   
Product ID:                00426-OEM-8992662-00006
Original Install Date:     11/21/2009, 12:18:52 PM
System Boot Time:          12/30/2014, 2:42:55 PM
System Manufacturer:       Gigabyte Technology Co., Ltd.
System Model:              EP43-DS3LR

Counterfeit installations such as yours contains heavily modified code that causes the installation to behave it unexpected ways. Analysing BSOD's and determining their causes on these sorts of installations is very unreliable.

My recommendation is to start with a clean slate, and install a genuine version of Windows. This will minimise the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a genuine Windows installation, and are still experiencing BSOD's, we will be happy to help you solve them.