BSOD - Not sure of issue, DM log fire attached

ZhadowZ · 18 Jan 2015

I am not 100% what is causing my issues, I am pretty sure it is my very bad used GPU that is doing it.
It happens randomally during gaming (Not even intensive gaming). Watching Netflix. Playing Solitaire.

Never happens on a shut down, or restart, or just when doing nothing. Its usually when something visual happens.

Hopefully I get an answer soon, I plan on purchasing the 960 this week if it comes out and then very very soon as well upgrading to the i7 (If needed). So I want to fix this issue before doing all of that.

ZhadowZ · 18 Jan 2015

By the way, this has been happening for like 6 months. Just randomly started happening.

ZhadowZ · 19 Jan 2015

So I am running AVG Tune Up and AVG 1 Click Maintanance because I trust AVG.
And about to run MalwareBytes.

And it said one of my devices was not up to date.
What the heck is this.

Edit: I got this removed, AVG, and Malwarebytes were not finding or fixing it, I had to run computer in Safe Mode and use something called Junkware Removal Tool was suggested to me on TomHardware.
Originally I tried to run JRT and my PC crashed, I BSOD during the process. So I opened in Safe Mode and ran it and it was removed.

I am wondering and hoping that this was my BSOD issue and now I have resolved it!

ZhadowZ · 19 Jan 2015

Anyone? I notice other threads are being looked at but this one is near the bottom now.

Layback Bear · 19 Jan 2015

Are BSOD experts are very busy.

I did notice this from you post #2

By the way, this has been happening for like 6 months

Now your in a hurry.

I'm not a BSOD expert so I don't analyze logs.

I did notice this from post #3. I do not recommend using them or any other Tuneup program.
Windows 7 does not want or need tuneup programs.

So I am running AVG Tune Up and AVG 1 Click Maintanance because I trust AVG.

I wouldn't worry a bunch about what post get answered before yours. It's not like they cut ahead of you in the school lunch line.

When the proper member sees your post and has the time you will get taken care of.
Bear in mind that all helping members donate their time and expertise. Our help is free.

ZhadowZ · 21 Jan 2015

I have 2 dumpfiles that popped up for WinDbg
--------------------------------------------------------------------------

Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\011915-22838-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03065000 PsLoadedModuleList = 0xfffff800`032a86d0
Debug session time: Mon Jan 19 01:49:24.138 2015 (UTC - 6:00)
System Uptime: 0 days 0:08:51.652
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffff8b491773, 1, fffff880012ab832, 5}

Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCreate+210b )

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

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

Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\012015-29406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03007000 PsLoadedModuleList = 0xfffff800`0324a6d0
Debug session time: Tue Jan 20 12:33:00.586 2015 (UTC - 6:00)
System Uptime: 0 days 0:05:53.115
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffffff8948104a, 2, 0, fffff880040a5ede}

*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
Probably caused by : hardware ( usbfilter+1bf5 )

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

ZhadowZ · 22 Jan 2015

Edited. Added 2 WinDbg logs ^

Golden · 22 Jan 2015

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

ZhadowZ · 22 Jan 2015

Golden said:

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

My first post had one already uploaded.
But I just ran it again, and here is a fresh one.

Golden · 22 Jan 2015

Many of your chipset and OEM drivers haven't been updated and appear to be date around 2010 - you need to methodically update all your chipset and device drivers.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffffff8948104a, 2, 0, fffff880040a5ede}

*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
Probably caused by : hardware ( usbfilter+1bf5 )

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

2: kd> lmvm usbfilter
start             end                 module name
fffff880`06fe3000 fffff880`06ff2000   usbfilter T (no symbols)           
    Loaded symbol image file: usbfilter.sys
    Image path: \SystemRoot\system32\DRIVERS\usbfilter.sys
    Image name: usbfilter.sys
    Timestamp:        Wed Dec 15 21:04:49 2010 (4D0899C9)
    CheckSum:         00015056
    ImageSize:        0000F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update the AMD USB filter drivers - see link below:
Driver Reference Table

Code:

fffff880`0b707148  00000000`4944494f
fffff880`0b707150  fffffa80`0923e100
fffff880`0b707158  fffff880`00e155f7Unable to load image \SystemRoot\system32\DRIVERS\AiChargerPlus.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AiChargerPlus.sys
*** ERROR: Module load completed but symbols could not be loaded for AiChargerPlus.sys
 AiChargerPlus+0x5f7
fffff880`0b707160  fffffa80`08b73450
fffff880`0b707168  fffffa80`07103010
.
.
fffff880`00e15000 fffff880`00e16e00   AiChargerPlus T (no symbols)           
    Loaded symbol image file: AiChargerPlus.sys
    Image path: \SystemRoot\system32\DRIVERS\AiChargerPlus.sys
    Image name: AiChargerPlus.sys
    Timestamp:        Mon Nov 08 17:18:26 2010 (4CD79D3A)
    CheckSum:         00005A96
    ImageSize:        00001E00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Uninstall the ASUS Charger utility....early versions were a well-known cause of BSOD's.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffff8b491773, 1, fffff880012ab832, 5}


Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCreate+210b )

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

Check your hard disk for mechanical errors by running the LONG test using the DOS version of SeaTools:
SeaTools for DOS and Windows - How to Use

Recommendations:
1. Uninstall that AVG crap if you haven't already - all they produce now is bloated rubbish that stuff's systems up. They have't produced anything good in the last 5 years.
2. Replace MaCrappy with MSE - MSE never BSOD's, and having MaCrappy installed is worse than having a virus
3. Uninstall Daemon Tools Lite - its a well known cause of BSOD's