Random BSODs after Graphics Card Failure

[Thaloc]

Hey everyone,

This is my first post like this, but my meager skills don't seem to cut it.

I guess this all started with my old graphics card failing. It was time for an upgrade so I stuck an old spare in my system while I shopped and waited on shipping. The spare worked fine for about a month and then the day before my new card shows up my system BSODs.

I just assumed my old card went tits up so I waited till the next day and put the new graphics card in when it arrived(Radeon R9 270). Only to find out my power supply is 50 watts under par for my system with the new card. I disconnected my disc drive to save power and everything seemed to work fine. I updated to the latest drivers with Catalyst Control center and the PC seemed to work better than ever.

I ran Skyrim and LoL from Wednesday to Sunday w/o a hitch. Then I installed the new Elder Scrolls Online and within 3 hours had 3B stop code. My system BSOD'd quite a lot the rest of the day with random stop codes;

D1
3B
7E Referencing dxgmms1.sys
3B Referencing npsf.sys

I cleaned my drivers with Driver Fusion and re installed fresh drivers for the new video card, still getting BSOD. I plan on running a memtest overnight tonight and see if that comes up with any errors. I know my PSU being 50 watts under is no good, and I plan to remedy that immediately, but do ya think that's the source of my problem?

My PC seems to run perfect as long as I'm not loading up a Elder Scrolls Online, I work from home and put eight - 10 solid hours of data analysis on it every day without a hitch, It only seems to want BSOD when I want to get my game on.

If any of you lovely ladies and gents could point me in the right direction to get my system sorted out I would be in your debt.

Happy to provide any further information if needed.

Sys Specs;

Operating System: Windows 7 Home Premium 64-bit - Service Pack 1
Processor: Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz
Motherboard: MSI H55M-E33
Memory: 8192MB RAM
DirectX Version: DirectX 11
AMD Radeon R9 200 Series


Below are my mini dumps.

 

[Thaloc]

And report from CPUZ

 

[Thaloc]

More BSODs after I installed a fresh 700 watt psu. Updated graphics driver to beta and swapped out the HD Sata Cable to a new one and still getting BSODs. Here are the dump files from today;

On Wed 4/2/2014 8:21:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040214-28314-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x18 (0x0, 0xFFFFFA800A144FE0, 0x2, 0xB600000000000001)
Error: REFERENCE_BY_POINTER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 4/2/2014 8:21:35 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x18 (0x0, 0xFFFFFA800A144FE0, 0x2, 0xB600000000000001)
Error: REFERENCE_BY_POINTER
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 4/2/2014 5:56:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040214-31356-01.dmp
This was probably caused by the following module: mpfilter.sys (MpFilter+0x122B9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880011A42B9, 0xFFFFF8800541AD10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\mpfilter.sys
product: Microsoft Malware Protection
company: Microsoft Corporation
description: Microsoft antimalware file system filter driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 4/2/2014 5:41:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040214-23493-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41284, 0xFFFFF900C37BC001, 0x1F96, 0xFFFFF90000812000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 4/2/2014 5:34:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040214-35131-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x9875877, 0x1877, 0x1876)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

[Thaloc]

A link to the Kernal-Dumps;

https://www.dropbox.com/s/j3hncsyg6cadojw/MEMORYDMP.zip

 

[Golden]

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 created on your desktop, and upload it here in your next reply.

 

[Thaloc]

As Requested, I really appreciate you taking the time.

 

[Golden]

fffff880`08928438  00000000`00000000
fffff880`08928440  fffff880`00000000
fffff880`08928448  fffff880`074638c9Unable to load image \SystemRoot\system32\DRIVERS\Sftfslh.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Sftfslh.sys
*** ERROR: Module load completed but symbols could not be loaded for Sftfslh.sys
 Sftfslh+0xf8c9
fffff880`08928450  fffffa80`09a07820
fffff880`08928458  fffffa80`09a20bb0

Driver Reference Table - Sftfslh.sys
Update the virtualisation driver by performing a Windows update.

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

Use !analyze -v to get detailed debugging information.

BugCheck 18, {0, fffffa800a144fe0, 2, b600000000000001}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48de1 )

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

Please do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html