Solved BSOD when gaming

[demongorgan]

hi all im having an issue with my new build.. wen i try and game i get a black screen of death, then the system restarts.. it wont happen instantly during gaming but at random times.. sometimes it happens after 5 min others after 30min-hour.

the below happens:
pc restarts
speakers make a buzzing noise and then pc restarts
game freezes and i have to alt+tab out and close
pc black screens then restarts

sometimes i here a usb connect/disconnect sound, sometimes it says display driver has stopped working.

things i have done:
uninstalled all amd drivers (once using add/remove programs and once using amd remove all drivers tool)
re-installed amd 14.4 drivers and also tried older drivers
got all the latest drivers off of gigabyte website for my mobo
added aditional fans for cooling
cleaned out the pci-e slot and de-dusted my components
removed and reseated componetns

ran chk/f and seatools for windows tool (my drive came back in full working condition)
ran memtest86+ for 10 passes (no errors found)
ran prime95 for 2 hours (again no errors or lock ups temp never went over 36c)
ran furmark for 2 hours full burn test 1366x768, AAx8 extream burn test ( again no bsod and no artifacts temp stayed constant at 67c on full load throughout test)

gpu temp never goes over 65c in CCC and i have core temp running and non of the cores seem to go over 30c when gaming
have antimalware bytes and Microsoft security essentials: ran both, no viruses or malware present

win7 64bit sp1
mobo: ga-78lmt-usb3
cpu: fx4350
ram: corsair value 4gb @1333
gpu: vtx3d r9 290-x-treme edition
psu: corsair Cx750m
hdd: seagate 500gb 7200rpm
monitor: 47" hdtv running through the HDMI 1920x1080p (running in 1366x768 though)

any idea what be the bother chaps? the only other thing is that i downloaded a windows 7 iso (as i couldn't get the official Microsoft one to work) and am currently running trial until i get paid on Friday to buy the official software so i can get my key from aria-pc



have currently set pc to do not reboot and have changed dump to small memory dump 256kb and have access to the location so waiting on next bsod,

 

[demongorgan]

just adding my msinfo.rar and info from who crashedme

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 13/05/2014 10:04:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051314-18564-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80052C74F8, 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 Sun 11/05/2014 01:06:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051114-20326-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800528E8F8, 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 Sat 10/05/2014 10:01:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051014-25006-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004E2A8F8, 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 Thu 08/05/2014 22:38:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050814-30591-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80051604F8, 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 Wed 07/05/2014 00:26:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050714-25740-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80051FA038, 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
--------------------------------------------------------------------------------

5 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

 

[derekimo]

All your dumps are hardware related, I see you have ran some tests.

Let me get some hardware guys over here for you.

 

[Britton30]

I assume you have installed all the latest chipset and Etron USB drivers from Gigabyte? If not do that and test it out. It may even help to reinstall the USB drivers.

Check for a BIOS update too.

 

[essenbe]

Gary, you know more about AMD than I do, but is it possible to run Prime95 and not go over 36C?

demongorgan, Are you overclocking? If so, please set everything back to default levels, at least until we get this stable. Also, please download and install CPUz and post screenshots ( http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html ) of the CPU, Mainboard, Memory and SPD tabs. On the SPD tabs you can select each Dimm Slot from a dropdown list in the upper left. We only need the Dimm Slots that are populated with ram.

Also, is it happening in all games or just a particular one?

 

[demongorgan]

thanks for the reply guys,
am not overclocking this build on cpu or gpu so everything is stock.
ive got the latest bios update the beta f5da build (tried previuse builds also)
i have all the latest drivers from the gigabyte website inc the etron 3.0 drivers (was an issue with them when i first built the machine but managed to get them reinstalled)

ive got cpu-z installed so will get those screen shots over for you, and it seems to be doing it with dx11 games, as skyrim works fine on ultra, as do my older games. but bring in titanfall and Dayz standalone and it does it. its also done it whilst watching videos before. seeing as my ram has passes 10 passes without error i thought it could have been a cpu thermal issue what with the r9 290 kicking out quite a bit of heat so i purchased some additional fans to keep things cooler.

but even with my case now cooled a lot better it still does it, and after monitoring the cpu it never seems to go over 19c whilst surfing, 23c whilst gaming and 36c on prime 95 (temp sensor error prehaps?)

only other conclusion i could come to and my original thought was a GPU failure.. but then it passed 2 hours of fumark under extreme setting ad not a single bsod or artifact which is quite frustrating to say the least. i had the card ready to RMA but if i cant find a problem with it then they aria will prob say the same thing and charge me to get it back, and a service for looking at it (good way to deter RMA's without definitive proof)

 

[essenbe]

Is this a different system than in your system specs? Or is it another system and do you still have the system in your specs? Also, what CPU cooler are you using. Please go into BIOS and tell me the +12V, +5V and the +3.3V readings. Also tell me if your Sata controller is in IDE< AHCI or Raid mode and the timings, voltage and frequency of your ram. Also, the motherboard and CPU temps. I made the comment about temps because I have had AMD systems and never had one that would run Prime with high temps that low. But, that was a long time ago, too.

 

[demongorgan]

heres my shots from CPU-z

did you want me to download GPU-Z for sceenshots also?

 

[demongorgan]

Is this a different system than in your system specs? Or is it another system and do you still have the system in your specs?

ahh sorry thats my old system. i shall update it now

 

[essenbe]

If you would, please post the screenshot of GPUz. According to CPUz your card is running @ X1 instead of X16 as it should. Are you sure you have it in the right slot and fully seated?

 

[demongorgan]

downloading GPU-z now. yeah i have the right slot my mobo only has 1 pci-e slot, i can try reseating it again.

bios shots in .rar gpuz screenshots below

 

[essenbe]

On the main Page where it says PCI-E 3.0 X16 @ X1 1.1, click the question mark next to it. It will open a rendering window and see if the X1 1.1 changes. It often does.

 

[demongorgan]

On the main Page where it says PCI-E 3.0 X16 @ X1 1.1, click the question mark next to it. It will open a rendering window and see if the X1 1.1 changes. It often does.

yeah it did, screen shots above, prob a gpu power save feature

 

[essenbe]

It looks better, but it still should be X16 @ 3.0 instead of 2.0, but I really don't know if it makes a difference.

 

[essenbe]

Other than that, it's the only thing I see that looks out of line. Britton30 is more familiar with AMD systems, so he may see something in CPUz I didn't. But, when you get a chance Please get me the voltages and temps from BIOS. When you first started it up after building it, did you set bios to optimized defaults? And I noticed a couple of things in your bios that should be changed, but nothing that has anything to do with this. WHEA errors can be caused by several things. But, in overclocking it is usually you need more voltage.

I know it's early morning where you are, but it's 2 AM where I am. Well past my bed time. Let me think about this after some sleep, and I'll write back in a couple of hours and I have a couple of things we can try, but I'd like Britton30 to look at this first. Don't do it yet, but take a look at this and see if you think it could help http://www.sevenforums.com/tutorials/330579-graphics-card-problems-diagnose.html

Also, please be sure to let me know about the optimized defaults and the voltages and temps in BIOS. There usually is a Monitoring section in bios which will tell you those things. BIOS is the most accurate for voltages and temps. Most everything else is software readings and are notoriously inaccurate to some degree.

 

[ICIT2LOL]

Look I am not so well informed as the others but it seems from what I have Googled it is a temp related issue and I am thinking if this still happens when the standard frequency settings are put in that it may even be a bad CPU or GPU to start with?? (temp sensors not working as should be)

 

[demongorgan]

Other than that, it's the only thing I see that looks out of line. Britton30 is more familiar with AMD systems, so he may see something in CPUz I didn't. But, when you get a chance Please get me the voltages and temps from BIOS. When you first started it up after building it, did you set bios to optimized defaults? And I noticed a couple of things in your bios that should be changed, but nothing that has anything to do with this. WHEA errors can be caused by several things. But, in overclocking it is usually you need more voltage.

I know it's early morning where you are, but it's 2 AM where I am. Well past my bed time. Let me think about this after some sleep, and I'll write back in a couple of hours and I have a couple of things we can try, but I'd like Britton30 to look at this first. Don't do it yet, but take a look at this and see if you think it could help http://www.sevenforums.com/tutorials/330579-graphics-card-problems-diagnose.html

Also, please be sure to let me know about the optimized defaults and the voltages and temps in BIOS. There usually is a Monitoring section in bios which will tell you those things. BIOS is the most accurate for voltages and temps. Most everything else is software readings and are notoriously inaccurate to some degree.

Thanks for all your help so far, much appreciated. the voltage and temps from my bios "pc health section" are in the .zip in my above post hope thats the info you need. i've set to optimized in bios. would appreciate it if you could tell me those settings that need changing in the bios.

thanks

 

[demongorgan]

i have looked at the link you have gave me and it could be helpfull. i've ran furmark already with no issues but i could try running it longer, say 4 hours this time? to see if i can replicate the bsod. have the gpu-z log file all ready and waiting anyways. would the log work within games? or does it just work with the benchmark software

 

[essenbe]

It will work with anything. As soon as you start the log, I want you to play a game or anything else that makes you BSOD as fast as possible. As soon as it gets booted again, open GPUz and uncheck the log to file box. The log will be quite long, so turn it off as quick as possible. I also want you to BSOD as quick as possible. So, do whatever makes you BSOD fast.

 

[Britton30]

I see two thing which may not help the BSOD but should be changed.

The HT Link Frequency should be set as close to 2000MHz as possible, yours is 2200MHz. If it goes a bit below, that's OK. You may have to adjust the CPU Host Clock control a bit.

Your On Chip SATA type should be AHCI instead of Native IDE.