Sign in with
Sign up | Sign in
Your question

Computer crashes randomly, but only with graphics drivers installed.

Tags:
  • Crash
  • Video Driver
  • Drivers
  • Computers
  • AMD
  • System Restart
  • Windows 8
  • Graphics
  • Windows 7
  • Blue Screen
  • Graphics Cards
Last response: in Graphics & Displays
Share
June 13, 2014 4:44:43 PM

I have been getting really tired of this issue. I just recently got a 290x, a new motherboard, and a new PSU (because I thought the issue was from this).

I have tried windows 7 and windows 8.1, with no difference except windows 7 actually knows there was a BSOD (windows 8.1 thinks life is all good).

Safe mode and normal mode with generic drivers never causes an issue. Only when I install the AMD drivers, does my computer start crashing randomly.

I have tried uninstalling Nvidia drivers (previous card was GTX 460), and AMD drivers with windows, and with DDU (most current version). At least in windows 7, after installing the drivers, the log says everything worked fine.

The number in the BSOD has ZERO hits on google, so I don't have anything to go off.

I have spent several days trying to tweak the install, install only certain things, uninstall old drivers, install different drivers, etc. with no success. I tested the card in a friends computer and there were no issues. I tested my ram with memtest86+ and no errors were found. I have been using the CPU for several years with no issues. I got a new HDD that worked in another computer just fine. The PSU is giving nominal readings, and is beyond suffienct for my build.

I don't know what else to do.... The only thing I can think of that could be the issue is my motherboard, which is new, and worked fine with the GTX 460.

Please, anyone, help me. :'( 

BSOD:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800E290468
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

I can provide more info on request.
Thanks in advance.

More about : computer crashes randomly graphics drivers installed

June 19, 2014 7:49:45 PM

scout_03 said:
use this to read the minidump files http://www.resplendence.com/whocrashed then this one on the sensor page for the other info and post the result http://www.hwinfo.com/download.php



--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.01
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


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

computer name: JAMES-DESKTOP
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., M5A78L-M/USB3
CPU: AuthenticAMD AMD Phenom(tm) II X4 970 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 17177890816 total
VM: 2147352576, free: 1916076032




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 6/20/2014 1:54:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061914-10484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x50 (0xFFFFD00189747188, 0x0, 0xFFFFF800456F4099, 0x2)
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/20/2014 1:54:25 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngAcquireSemaphore+0x9295)
Bugcheck code: 0x50 (0xFFFFD00189747188, 0x0, 0xFFFFF800456F4099, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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 Thu 6/19/2014 6:26:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061914-9671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5B0D35)
Bugcheck code: 0x124 (0x0, 0xFFFFE0003C36F038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 6/17/2014 3:12:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061614-8656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5B0D35)
Bugcheck code: 0x124 (0x0, 0xFFFFE000BA2FF038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 6/17/2014 2:47:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061614-10093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5B0D35)
Bugcheck code: 0x124 (0x0, 0xFFFFE001B21D2038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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/16/2014 2:46:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061614-11359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5B0D35)
Bugcheck code: 0x124 (0x0, 0xFFFFE001021318F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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/16/2014 2:30:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061614-10546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5B0D35)
Bugcheck code: 0x124 (0x0, 0xFFFFE0005968A038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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/16/2014 2:20:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061614-11859-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0xBD80)
Bugcheck code: 0x116 (0xFFFFE001E5462160, 0xFFFFF80070AC6D80, 0x0, 0xD)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR



On Mon 6/16/2014 4:16:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061514-14359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5B0D35)
Bugcheck code: 0x124 (0x0, 0xFFFFE001C06B4038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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/16/2014 3:44:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061514-14625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5B0D35)
Bugcheck code: 0x124 (0x0, 0xFFFFE0000EA97038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

14 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.






HWinfo:
http://i.imgur.com/GZODcpp.png
Most of the time the screen freezes, and the sound buzzes.
m
0
l
Related resources
a b \ Driver
a b À AMD
a b * Windows 8
a c 204 $ Windows 7
a c 96 U Graphics card
June 20, 2014 8:02:59 PM

do you have the latest driver for this gpu and did you overclock anything post a picture of the hwinfo sensor page i would try to test that gpu in another system .
m
0
l
June 22, 2014 9:05:46 AM

scout_03 said:
do you have the latest driver for this gpu and did you overclock anything post a picture of the hwinfo sensor page i would try to test that gpu in another system .


Yes, no overclocking, although i have tried, and noticed my computer stays stable for long when i severely underclock the GPU. The HWInfo link is in my last response.

The GPU is currently in another computer being tested, and I should have the results later today.

I would like to note that my computer just crashed again, but this time with my old graphics card, which I never had any problems with. The only other thing that has changed is that I got a new motherboard, and ram, which came back as ok when testing. I have RMA'd the motherboard.




The error was still FFFFFA800DBF7028. The most recent crash happened while playing Titanfall:

On Sun 6/22/2014 3:54:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062214-35880-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800DBF7028, 0xB4602000, 0x31000135)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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/22/2014 3:54:42 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0x1E3)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800DBF7028, 0xB4602000, 0x31000135)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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.
m
0
l
June 22, 2014 6:17:49 PM

Hopefully a different board with solve the issue. Any other thoughts are welcome though!
m
0
l
!