BSOD Caused By Graphic Drivers -- Seems to occur at random times

[Nu2jirsa1]

Del

 

[essenbe]

Hi Ech0es, I'll try to help. You only have 1 Dump file. So, if you would, please make sure your system is configured for Small Memory Dumps. http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

The dump file is your Graphics driver, as you probably knew

 [COLOR=red]atikmdag[/COLOR]
start             end                 module name
fffff880`11038000 fffff880`11fe2000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Mon Aug 11 21:37:53 2014 (53E97E01)
    CheckSum:         00F38D59
    ImageSize:        00FAA000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You may try to make sure you have the latest DirectX installed http://support.microsoft.com/kb/179113

You may either try to disable hardware acceleration in Adobe Flash just to see if that helps.

If the problem continues, I would consider uninstalling Firefox, just as a test to see if that has something to do with the crashes.

 

[Nu2jirsa1]

Del

 

[essenbe]

Ech0es, If you would, please don't delete any more dump files. Sometimes several of them together can give us a better idea of what is happening. I am not overly enthused with AMD drivers, but Nvidia has it's issues too, so none of them is perfect, although I do think Nvidia is quicker to respond to an issue. But, there are many issues that can cause drivers to crash, some hardware some software. At this point, I am not sure how best to respond if the driver update didn't help. If you continue to have problems, please upload the same files you uploaded before. Hopefully they will have more dump files in them.

 

[Nu2jirsa1]

Del

 

[essenbe]

I can tell you this is a known BSOD causer

 dtsoftbus01
start             end                 module name
fffff880`01b6e000 fffff880`01bb6000   dtsoftbus01   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\dtsoftbus01.sys
    Image name: dtsoftbus01.sys
    Timestamp:        Fri Feb 21 03:49:36 2014 (53072130)
    CheckSum:         00047544
    ImageSize:        00048000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Daemon Tools driver

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause of BSOD's.

1. Uninstall Daemon Tools.
2. Download the SPTD standalone installer and follow these steps:
- Double click the executable to open it
- Click the button shown below



If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.

After you have completed that open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

 

[essenbe]

The dump file was the same thing. The only exception is the first dump you provided lists it ad a TDR error. (Time delay and Recovery) meaning the driver crashed and did not recover in the time required by Windows, so Windows assumed a Graphics failure and crashed.

The last one was simply a driver crash without listing the TDR. Truthfully, I'm not sure there is a major difference on a Desktop computer. A laptop can be a big difference.

 

[Nu2jirsa1]

Del

 

[essenbe]

None of the dump files pointed to it, but any SPDT Pass Through are well known causes of BSODs. Sometimes other programs can conflict with drivers or cause the BSOD themselves but the debugger will catch the 'victims' and not the cause.

 

[Nu2jirsa1]

Del

 

[essenbe]

I hope it helps. Yes, diagnosing a BSOD can be a real pain sometimes most of the time. It can involve a lot of testing and trying different things. Many times the debugger (on your computer) will catch the victim and not the cause.

 

[Nu2jirsa1]

Del

 

[essenbe]

Yea, the AMD forums are full of people posting about it. The 'Fishbowl' test, I think just tests HTML5. It dosent seem very stressful to me. I ran it with 2000 fish, just to see what would happen.

View attachment 335214

Download this and run it. Set it on the preset extreme. Heaven Benchmark | Unigine: real-time 3D engine (game, simulation, visualization and VR) the set up should look like this
View attachment 335215

Then press run then when it starts moving, press the Benchmark in the top left, but be sure to watch your temps. They will get pretty high

 

[Nu2jirsa1]

Del

 

[essenbe]

Th good part is you didn't crash and your temps stayed good.

 

[Nu2jirsa1]

Del

 

[essenbe]

If you want to see if it will BSOD. Enable all Non Microsoft drivers

   Warning

Be sure to create a Systm Restore point before proceeding further http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.

What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.

   Warning

Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Nu2jirsa1]

Del

 

[essenbe]

Or until you get a BSOD or two. The idea is to stress the drivers to get the weakest ones to crash and hopefully catch them. It will run a little sluggish because extra stress is being put on the drivers.

 

[Nu2jirsa1]

Del