Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Constant BSOD's on my desktop after getting a new gpu

18 Jul 2015   #1
Ghost Prodigy

NEW YORK
 
 
Constant BSOD's on my desktop after getting a new gpu

Hello, so a few months ago my R9 280x stopped functioning for whatever reason after a year of use, so I went out to buy a new one. I installed it, and everything seemed the same until I've begun experiencing multiple BSOD's every week. This has never occurred before I switched my gpu. Here's my specs and the crash dump details. Any help would be greatly appreciated!

System Information (local)
--------------------------------------------------------------------------------

computer name: NICKS-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., M5A97 R2.0
CPU: AuthenticAMD AMD FX(tm)-6300 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 8482414592 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 7/17/2015 9:37:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071715-80668-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x5039)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880010FB039, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a kernel-mode program 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 Fri 7/17/2015 9:37:22 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: bhdrvx64.sys (BHDrvx64+0xA8AA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880010FB039, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Program Files (x86)\Norton 360\NortonData\22.5.0.124\Definitions\BASHDefs\20150706.001\BHDrvx64.sys
product: BASH
company: Symantec Corporation
description: BASH Driver
Bug check description: This indicates that a kernel-mode program 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.
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: bhdrvx64.sys (BASH Driver, Symantec Corporation).
Google query: Symantec Corporation KMODE_EXCEPTION_NOT_HANDLED



On Sun 7/12/2015 7:53:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071215-89965-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xA (0x80, 0x2, 0x1, 0xFFFFF800032DC82F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sat 7/11/2015 1:53:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071015-63508-01.dmp
This was probably caused by the following module: ironx64.sys (Ironx64+0x32418)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880045DF418, 0xFFFFF8800317F588, 0xFFFFF8800317EDE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\N360x64\1605000.07C\Ironx64.SYS
product: Iron
company: Symantec Corporation
description: Iron Driver
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.
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: ironx64.sys (Iron Driver, Symantec Corporation).
Google query: Symantec Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Thu 7/9/2015 2:21:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070915-55333-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x196C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8801120196C, 0xFFFFF8800AAF4BD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 6/28/2015 3:32:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062815-19858-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032477BF, 0xFFFFF88008D66BB0, 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 Sat 6/20/2015 7:40:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062015-18985-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x50 (0xFFFFF6C4CB0D6B40, 0x0, 0xFFFFF80003272F0B, 0x5)
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 6/19/2015 4:26:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061915-14695-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x50 (0xFFFFF6A952000000, 0x0, 0xFFFFF80003275F0B, 0x5)
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 Mon 6/1/2015 9:58:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060115-13977-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x50 (0xFFFFF707ECE7F048, 0x0, 0xFFFFF80003288233, 0x5)
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 Mon 9/29/2014 9:57:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092914-16426-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0xC7DBB)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88011151DBB, 0xFFFFF880053FB228, 0xFFFFF880053FAA80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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.
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. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M


My System SpecsSystem Spec
.
19 Jul 2015   #2
Ghost Prodigy

NEW YORK
 
 

Bump
My System SpecsSystem Spec
19 Jul 2015   #3
Ghost Prodigy

NEW YORK
 
 

Everyone else seems to be using this so I guess I'll do the same

Gyazo - 04de97c28f9bec197cd6e8356c0ef096.png
My System SpecsSystem Spec
.

21 Jul 2015   #4
Ghost Prodigy

NEW YORK
 
 

bump
My System SpecsSystem Spec
22 Jul 2015   #5
Ghost Prodigy

NEW YORK
 
 

bump
My System SpecsSystem Spec
23 Jul 2015   #6
Ghost Prodigy

NEW YORK
 
 

bump
My System SpecsSystem Spec
24 Jul 2015   #7
Ghost Prodigy

NEW YORK
 
 

bump..
My System SpecsSystem Spec
26 Jul 2015   #8
Ghost Prodigy

NEW YORK
 
 

Bump
My System SpecsSystem Spec
Reply

 Constant BSOD's on my desktop after getting a new gpu




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
constant random BSOD after desktop loads
Hi, Having a hard time here, and now my PC has BSOD, so would greatly appreciate assistance :(. I'll post as much as possible about it to assist. Much thank you for already reading my thread! Since owned PC (pre-built, brand new) for several months since owning it, maybe once a month or more...
BSOD Help and Support
[BSOD] laptop constant random bsod's (IRQL_NOT_LESS_OR_EQUAL)
Laptop brand: Acer Model: Aspire 5560-sb653 OS: Windows 7 Home 64 bit Problem: Started 2 days ago. I was checking my email using Firefox and a "Display driver stopped working/ successfully recovered" message popped up, followed by first BSOD. After that, BSOD appeared at start-up. Tried...
BSOD Help and Support
bsod constant errors, restarting ,multiple bsod
pls solve and send me the solution to this .i have been experiencing this since i bought my pc since a long time.
BSOD Help and Support
Constant Crashing, constant BSOD's
Alright, so the situation has gotten worse, a few weeks back I made a thread and someone advised me to remove Daemon/Alcohol 120 and then remove the leftovers using a specific tool, and it seemed to be fine for a while, but now my computer is starting to crash full force. I was just playing...
BSOD Help and Support
COnstant BSOD's
Ok let me start by saying ty for any help provided I built this system 6 months ago, and I did not have any problems with it until recently. The problems started after I did a format and reinstalled windows 7 about 4 weeks ago. The computer BSOD's randomly even if it is just sitting there...
BSOD Help and Support
Constant BSOD
Hi, Ive built a system up by myself and have had intermittent BSODs since ive started it up. I replaced the wireless adaptor card and things seemed to calm down. I would get a BSOD rarely, but not enough to worry. Ive recently uninstalled Norton Antivirus which came with one of the...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 19:48.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App