Solved BSOD:s and instability on new motherboard (Gigabyte G1 Sniper 3)

[Zurtax]

Hi, a few weeks ago I purchased a Gigabyte G1 Sniper 3 along with an Intel i5 3570k. I wanted to try Windows 8.1 when I installed the new motherboard but when I installed drivers bsod:s and freezes occurred. I thought that perhaps everything wasn't optimized for the latest Windows and went back to Win 7. First I went to the official site and downloaded drivers but exactly the same thing started happening. Not having much to lose on my C: I reinstalled again and went to the supplied disc for drivers, for a while everything seemed to work but perhaps 2 days later the main issue resurfaced: bsod:s, freezing and just plain instability. Along the process I have memtested my memory, updated my BIOS to the latest (F8j), updated drivers from the Gigabyte site and Qualcom Atheros site (for the network card) and as I'm writing this I'm in a sort of safe boot (a bit more stable) from msconfig.exe. I have checked all temperatures and nothing is too high. My previous setup had all the same components except the motherboard + cpu and that system was rock solid (perhaps the cpu got a little warm but no crashes) with an older gigabyte am2+ matx board along with a Phenom II 3 ghz quad core.

Kind regards Zurtax

 

[Arc]

Update Intel XHCI driver from https://downloadcenter.intel.com/SearchResult.aspx?lang=eng
Update Killer e2200 driver from Killer Gaming :: Support :: Driver Download Support

You are using a beta of display driver. Uninstall it using AMD Catalyst Un-install Utility and then install the latest WHQL only.

Then report us back. Let us know the situation.

 

[Zurtax]

After I did all of the above the system felt more stable but recently I've had 2 more bsod:s I will supply with some fresh information. Thank you so much for your(Ace) patience!

I will also try the "driver verifier" to see which driver might be at fault.

 

[Arc]

After I did all of the above the system felt more stable but recently I've had 2 more bsod:s I will supply with some fresh information. Thank you so much for your(Ace) patience!

I will also try the "driver verifier" to see which driver might be at fault.

You have not done.

The display driver is still a BETA.

fffff880`0429e000 fffff880`0433c000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
[COLOR=Red]    Image name: atikmpag.sys
    Timestamp:        Tue Oct 08 17:57:46 2013[/COLOR] (5253FA42)
    CheckSum:         0009C10E
    ImageSize:        0009E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

And it is about the latest WHQL ...

   Information

WHQL
Release Date: September 18th 2013
Version: 13.9
In Device Manager: 13.152

A driver of September cannot have the timestamp of October.

Please dont supply any information that is misleading.

When "All of the above" are really done, let us know. We will suggest you about the storage controllers .... intel and marvell.

 

[Zurtax]

I did absolutely not try to give you any misleading information Arc, I uninstalled the beta driver, ran the amd cleanup utility and installed the 13.9 whql driver. I had no idea that there was a bit of the old one left. I have now tried to uninstall the old and install the whql again. When I ran the Intel Driver Update Utility (Intel® Driver Update Utility) I found an old driver for the Intel Network Controller which I have (tried to) update.

Thank you so much Arc, just knowing someone is looking at the problem helps!

 

[Arc]

This is another BSOD caused by the display driver.

fffff800`00b9bcb8  fffff880`0f50682eUnable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** [COLOR=Red]ERROR: Module load completed but symbols could not be loaded for atikmdag.sys[/COLOR]
 atikmdag+0xff82e
-----------------------------------------------------------------------------------
fffff800`00b9bf68  fffff880`09487c19Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** [COLOR=Red]ERROR: Module load completed but symbols could not be loaded for atikmpag.sys[/COLOR]
 atikmpag+0x2dc19

And it is still the BETA driver.

fffff880`0945a000 fffff880`094f8000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
[COLOR=Red]    Image name: atikmpag.sys
    Timestamp:        Tue Oct 08 17:57:46 2013 [/COLOR](5253FA42)
    CheckSum:         0009C10E
    ImageSize:        0009E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Zurtax mate, you can easily understand that I have dealt with a great number of the exact same issue, and nobody reported that the BETA is still present after running Catalist Uninstall utility.

Is not it fair enough to decide that either you are not doing it or doing it wrong?

As far as the BETA drivers will be there, the display will continue to crash.

Well, my job is done here. I will request other members to continue with you.

 

[ICIT2LOL]

Z just a thought mate have you tried testing the hard drives?? it could possibly be your C: drive is going or gone bad.
I suppose you have well I am assuming you have done a sfc and chkdsk (unless the C: is a SSD of course).

Done any malware scans??
if not try these if only for elimination purposes

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

http://www.sevenforums.com/tutorials/433-disk-check.html

http://www.superantispyware.com/

http://www.malwarebytes.org/products/malwarebytes_free/

http://www.bleepingcomputer.com/download/adwcleaner/

(download from bleeping computer) - delete any rubbish you find and I would disconnect the other drives while you do this.

 

[Zurtax]

Thank you all for all the help and tips, today when I was going to start my computer it didn't feel like booting at all and once some of my ram modules was removed it booted and thanks to that I earlier had another go at installing the whql driver things have been running without errors for a few hours. If no more problems occur I will mark this thread as solved. The fact that an earlier run of memtest showed no errors is slightly weird...