I keep getting BSODs on my RX 460

[kotipuka01]

Hi everyone,

about two weeks ago I purchased an RX 460 and since then, I have had 4 or 5 BSODs. Can anyone help me figure out why? My GPU stayed unscrewed into the case for about 10 days, but I don't think that is the cause. I have been playing mostly GTA V. I tried a clean reinstall using DDU but that didn't work.

Here is what I could find with BlueScreenView:
http://imgur.com/a/ExSOE

My config:
OS: Windows 10 Enterprise 64bit
CPU: Intel i3-6100 3.7 GHz
MB: GIGABYTE GA-H110M-S2H
GPU: SAPPHIRE RX460 2GB OC
RAM: Kingston HyperX Fury 1x8 GB 2133 MHz
HDD: Toshiba 1TB
PSU: Cooler Master B500v2

Thanks in advance

 

[elbert]

Check your bios as you may need the latest verison. http://www.gigabyte.com/products/product-page.aspx?pid=5606#bios

Try reseating your video card by taking it out and putting it back in. You need to secure it with a screw.

Check your drivers to ensure you have the latest drivers for your OS. Those that effect the motherboard for sure. You could use iobytes to driverbooster to figure out what needs updated.
http://www.iobit.com/en/driver-booster.php

 

[kotipuka01]

Check your bios as you may need the latest verison. http://www.gigabyte.com/products/product-page.aspx?pid=5606#bios

Try reseating your video card by taking it out and putting it back in. You need to secure it with a screw.

Check your drivers to ensure you have the latest drivers for your OS. Those that effect the motherboard for sure. You could use iobytes to driverbooster to figure out what needs updated.
http://www.iobit.com/en/driver-booster.php

Thanks for the advice. But first I will try not to play GTA V for a couple of days, as it tends to behave weirdly
And my video card is screwed in at the moment

 

[johnbl]

note: if you replaced the GPU with out going into BIOS and resetting it to defaults. You should boot into bios, change any setting and change it back and save the results. It will force the bios to rescan your hardware and rebuild the database of hardware settings that are handed to windows when it boots. Failure to do this can result in the computer thinking it has two GPU cards (one that it just detected and one that is no longer responding because it was removed) the removed card still is assigned the hardware resources until the new BIOS scan is triggered by a update or a bios setting change.
-----------
your bugchecks shows two problems:
one was a bad parameter passed to the directx subsystem
and 3 bugchecks where the directx did not get a response to a call within the timeout period. It assume the GPU failed and called a bugcheck.

I would do the following:
update the BIOS or reset it to defaults. do not enable any BIOS overclock
boot into windows, update the motherboard drivers to the current version for your motherboard.
focus on any motherboard sound drivers.

if you have extra sound drivers that are not in use, go into windows control panel and disable any that you do not have a speaker connected to. your video card has sound support built in, if you don't have speakers in your monitor that gets the sound signal from the GPU cable you can disable the GPU sound support. the extra sound cards/drivers can cause the delay that causes the bugcheck 0x116 error.
two sound driver conflicts can cause the other bugcheck by corrupting the memory data structures.
(updated sound drivers and the bios RESET tend to fix these conflicts when the BIOS database is rebuilt)

the errors can also be due to overclocking drivers, you want to remove the overclock and make sure you do not have extra copies of the overclocking driver running from different directories. (happens a lot with MSI software)

 

[kotipuka01]

your bugchecks shows two problems:
one was a bad parameter passed to the directx subsystem
and 3 bugchecks where the directx did not get a response to a call within the timeout period. It assume the GPU failed and called a bugcheck.

I would do the following:
update the BIOS or reset it to defaults. do not enable any BIOS overclock
boot into windows, update the motherboard drivers to the current version for your motherboard.
focus on any motherboard sound drivers.

if you have extra sound drivers that are not in use, go into windows control panel and disable any that you do not have a speaker connected to. your video card has sound support built in, if you don't have speakers in your monitor that gets the sound signal from the GPU cable you can disable the GPU sound support. the extra sound cards/drivers can cause the delay that causes the bugcheck 0x116 error.
two sound driver conflicts can cause the other bugcheck by corrupting the memory data structures.
(updated sound drivers and the bios RESET tend to fix these conflicts when the BIOS database is rebuilt)

the errors can also be due to overclocking drivers, you want to remove the overclock and make sure you do not have extra copies of the overclocking driver running from different directories. (happens a lot with MSI software)

Well, I ran Iobit Driver Booster as elbert suggested and it updated some chipset drivers + the audio driver. I disabled the audio devices created by the AMD driver in the "Playback devices" tab. I haven't overclocked anything, although I do have MSI Afterburner installed but I barely use it. I will try to update my BIOS if the problem persists.

Thank you for the detailed answer

 

[kotipuka01]

Sad thing is, that I don't even get BSOD anymore. It just crashes and restarts. Should I try installing Windows 7?

 

[johnbl]

afterburner still tweaks voltages even if you don't make any changes.
I would remove it until you get the problem isolated. Also, different versions of afterburner install from different directories.
I have seen people run as many as 6 copies at one time by mistake.

it is generally not a good idea to run a 3rd party driver installer.
drivers should come from your hardware vendor because they know how they implemented the electronics and they compile the driver for the options used on your motherboard. the third party vendors just collect drivers and offer them to be installed without knowing the exact chip revisions you have installed on your motherboard or knowing what bugs are in the electronics of your motherboard.
That being said, it sure is a easy way to find drivers that just might work correctly.
you just don't know.

when you get system lockups that don't crash: you should google how to force a memory dump from a keyboard. make the registry settings.
then change the memory dump type from a mini dump to a kernel memory dump and reboot.
the next time the system locks up, use the keyboard to force the memory dump. if you get one then someone can look at it and see why the system stopped responding.

Sad thing is, that I don't even get BSOD anymore. It just crashes and restarts. Should I try installing Windows 7?