BSODs after Graphics Card Failure

Toggle sidebar Toggle sidebar
C

Colaht

Reputable
Apr 1, 2014
6
0
4,510
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
 
Sort by date Sort by votes
C

Colaht

Reputable
Apr 1, 2014
6
0
4,510
On Sun 3/30/2014 7:13:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033014-213471-01.dmp
This was probably caused by the following module: npfs.sys (Npfs+0x97DE)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF880018647DE, 0xFFFFF88003396EF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS 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 Sun 3/30/2014 7:13:03 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: npfs.sys (Npfs+0x97DE)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF880018647DE, 0xFFFFF88003396EF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS 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 Sun 3/30/2014 3:52:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033014-25474-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000393B09C, 0xFFFFF88006FABC70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 3/30/2014 3:39:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033014-20482-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x23EB0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800F023EB0, 0xFFFFF88004FB0688, 0xFFFFF88004FAFEE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 Sun 3/30/2014 2:47:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033014-54678-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF880014E9E2E)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFC4, 0xB, 0x0, 0xFFFFF880014E9E2E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Sun 3/30/2014 1:53:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033014-21184-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x2601E)
Bugcheck code: 0xA0000001 (0x5, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. CUSTOM_ERROR



On Wed 3/26/2014 2:32:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032614-20358-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800696AF38, 0xFFFFF8800696A790, 0xFFFFF880012F6DC5)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 3/26/2014 7:04:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032614-30919-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF88008A97000, 0x0, 0xFFFFF80003653725, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 2/8/2013 4:40:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020813-19905-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x81E7A)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8006D40B50, 0xFFFFF80000B9C510)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Upvote 0 Downvote
C

Colaht

Reputable
Apr 1, 2014
6
0
4,510
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.
 
Upvote 0 Downvote
C

Colaht

Reputable
Apr 1, 2014
6
0
4,510
Anybody?

I just swapped my PSU for a new 700watt, way above par for my system. Swapped the HD Sata Cable and ran a Disk Check that came up clean. Deleted some irrelevant software and drivers and still getting BSODs
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom