Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Random BSODs - Maybe failing GFX card?


  • Please log in to reply
13 replies to this topic

#1 Alphard

Alphard

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:14 PM

Posted 24 February 2014 - 10:32 AM

Hello people from Bleeping Computer. I've been having a lot of random BSODs these past months, first they were just random BSODs that happened here and there while I was playing something system intensive, but with time they became more and more constant and annoying to the point I had to ask for help. I suspect it may be the graphics card, due to it starting failing earlier than the BSODs (the HDMI port shows no output) but I need to be 100% sure before throwing money on a new card.

 

To start, I will post a summary of my system from Speccy

 

Operating System
    Windows 8.1 Pro 64-bit
CPU
    Intel Core i7 920 @ 2.67GHz    56 °C
    Bloomfield 45nm Technology
RAM
    8,00GB Single-Channel DDR3 @ 535MHz (7-7-7-20)
Motherboard
    ASUSTeK Computer INC. P6T (LGA1366)    49 °C
Graphics
    W2353 (1920x1080@60Hz)
    1024MB ATI AMD Radeon HD 5800 Series (XFX Pine Group)    65 °C (It's a 5850)
Storage
    465GB Western Digital WDC WD5000AVVS-63M8B0 ATA Device (SATA)
    223GB Corsair Force 3 SSD (SSD)    30 °C (Boot disk, Windows' here)
    931GB Seagate ST31000524AS (SATA)    38 °C
    931GB Western Digital WDC WD10EARS-00Z5B1 (SATA)    38 °C
    3726GB Seagate ST4000DM000-1F2168 (SATA)    37 °C
    931GB SAMSUNG HD103UJ (SATA)    34 °C
Optical Drives
    No optical disk drives detected
Audio
    Realtek High Definition Audio

 

 



BC AdBot (Login to Remove)

 


#2 dls62

dls62

  • Members
  • 623 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Berkshire, UK
  • Local time:11:14 PM

Posted 24 February 2014 - 10:43 AM

Please download BlueScreenView. If you download the appropiate zip file you will not need to install the software.

 

Extract the files and run BlueScreenView.exe

 

When the program window opens, select Edit > Select All

 

Then File > Save Selected Items

 

Save the report as BlueScreen.txt.  Open the file in Notepad and copy & paste all the contents in your next post.



#3 Alphard

Alphard
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:14 PM

Posted 24 February 2014 - 10:58 AM

Welp, I recently discovered that minidumps weren't being generated due to my pagefile being disabled (derp) so I only have 2 fairly recent minidumps, maybe should I try to crash the system some more?

 

==================================================
Dump File         : 022314-15562-01.dmp
Crash Time        : 23/02/2014 18:36:58
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : ffffe000`02efc4d0
Parameter 2       : fffff800`01c75d88
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`0000000d
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+fef94
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.3.9600.16455 (winblue_gdr.131103-1206)
Processor         : x64
Crash Address     : ntoskrnl.exe+14dca0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\022314-15562-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 9600
Dump File Size    : 308.152
Dump File Time    : 23/02/2014 18:39:41
==================================================

==================================================
Dump File         : 021914-15328-01.dmp
Crash Time        : 19/02/2014 18:13:58
Bug Check String  : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code    : 0x100000ea
Parameter 1       : ffffe000`00132880
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+18a99
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.3.9600.16455 (winblue_gdr.131103-1206)
Processor         : x64
Crash Address     : ntoskrnl.exe+14dca0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\021914-15328-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 9600
Dump File Size    : 280.624
Dump File Time    : 19/02/2014 18:16:05
==================================================

 

 

Also drivers atikmpag.sys and atikmdag.sys seem to be related to the BSODs somehow since they're marked in red on Bluescreenview along with dxgkrnl.sys.


 



#4 dls62

dls62

  • Members
  • 623 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Berkshire, UK
  • Local time:11:14 PM

Posted 24 February 2014 - 11:15 AM

Those two bugchecks certainly point towards it being the video card or its drivers as the cause.



#5 Alphard

Alphard
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:14 PM

Posted 24 February 2014 - 02:50 PM

So where I go from here? Is it possible that another piece of hardware such as the memory could be causing the issue?

 

Also I have to note that my Windows is not a clean install, I upgraded from 7, so the drivers could be the problem.



#6 dls62

dls62

  • Members
  • 623 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Berkshire, UK
  • Local time:11:14 PM

Posted 25 February 2014 - 07:33 AM

Make sure that your video drivers are up to date.  The latest drivers for your card are here.

 

You can use FurMark to stress test the graphics card.

 

MemTest86 would be a good tool to test your RAM to identify if there are any problems there.



#7 Alphard

Alphard
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:14 PM

Posted 26 February 2014 - 07:44 AM

Checked Catalyst and it's up to date.

 

Tested graphics card two times with furmark and it was ok.

 

bgtewo.pngywwzxy.png

 

Also tested the memory with Memtest86, 8 passes and no errors.



#8 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:03:44 AM

Posted 26 February 2014 - 08:17 AM

Hi Alphard

 

Please zip the actual crash dumps using "7-zip" and attach them with the next reply. You will find the dump files inside C:\Windows\Minidump folder.

 

http://www.7-zip.org/

 

Also publish a snapshot of your system using "Speccy".

 

http://www.bleepingcomputer.com/forums/t/323892/publish-a-snapshot-using-speccy/



#9 Alphard

Alphard
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:14 PM

Posted 26 February 2014 - 12:14 PM

Here are the minidumps:

Attached File  Minidump.zip   50.96KB   1 downloads

 

And here is the Speccy Snapshot:

http://speccy.piriform.com/results/eH7E8vqferUgsGsrST4CsCP



#10 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:03:44 AM

Posted 26 February 2014 - 01:32 PM

Hi

 

Your BSOD issue seems to be definitely related to the video card. But i can't say for sure whether the fault is with the card itself or the driver. I would suggest trying the below steps.

 

:step1: Uninstall Speedfan as it may affect the card's operation.

 

:step2: Remove the card from PCI-E slot and reinsert it. Sometime a simple contact issue can cause unexpected behaviors.

 

:step3: Clean install AMD Display driver.

 

Although you have the latest driver, a clean install without "Catalyst Control Center" may worth a try. First uninstall the current version properly.

 

http://support.amd.com/en-us/kb-articles/Pages/GPU57RemoveOldGraphicsDrivers.aspx

 

Then download and install the latest beta ( 2/25/14)  from http://support.amd.com/en-us/download/desktop?os=Windows+7+-+64

 

While installing choose "Custom" instead of "Express" and deselect everything except AMD Display Driver.

 

GoBitGo.COM-6-GPU-Article-Driver-Install

 

 

 

If the issue remains, swapping the card with a known good one is necessary. In my experience, stress tests are useless to find failing cards ( most times ).



#11 Alphard

Alphard
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:14 PM

Posted 26 February 2014 - 04:18 PM

Did everything you told. Earlier while I was playing a game I got another BSOD, but instead of generating a minidump, Windows generated a huge 600mb dump file, since BlueScreenView doesn't seem to analyse these (and I doen't know another tool that does) I had to get WhoCrashed to see whose BugCheck it was.

 

gjuqbs.png


Edited by Alphard, 26 February 2014 - 04:18 PM.


#12 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:03:44 AM

Posted 27 February 2014 - 12:01 AM

Hi

 

New BSOD shows Bugcheck 101 which is usually hardware related. This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

 

Source : http://msdn.microsoft.com/en-us/library/windows/hardware/ff557211(v=vs.85).aspx

 

Usually this bugcheck can be caused by Overclocking, Voltage tweaks, failing CPU , Failing MoBo or PSU which is failing under load. 

 

1. Enter BIOS setup and load "Default Values" to make sure CPU is working on recommended clock and voltage settings.

 

2. Set Memory timings manually. According to the specs, 9-9-9-24 timing and 1.65 volt is the recommended values. You should set that values manually in BIOS setup.

 

    http://www.newegg.com/Product/Product.aspx?Item=N82E16820145313

 

3. If the issue remains, try to get a PSU for testing purpose. A PSU which is failing under load can cause BSOD 101 as well as the BSOD 116 ( Video related BSOD you experienced ) error codes. 

 

This type of errors are painful to troubleshoot without components to swap and test.



#13 Alphard

Alphard
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:14 PM

Posted 27 February 2014 - 01:55 PM

I've reset BIOS to Default Values, but I didn't mess with the memory settings because my BIOS brings up a ton of memory options and I don't know which ones are to be set, so I left everything on Auto.

 

Also I'm starting to believe the mobo may be the issue (or one of them), since it displays some weird behavior on memory detection: sometimes it fails to detect a DIMM (it actually does detect the module, since it shows up on Speccy/AIDA64 but it doesn't show up in the system memory).

 

This system is seriously screwed up.


Edited by Alphard, 27 February 2014 - 01:57 PM.


#14 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:03:44 AM

Posted 27 February 2014 - 11:09 PM

Hi

 

The issues you are experiencing is definitely hardware related. It could be either the PSU or the MoBo but there is no way to test them other than swapping with a known good one. I would suggest using the service of a local PC repair shop who will have spare components to swap and test.

 

Btw, if your MoBo is still under warranty, you can try to get it replaced.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users