Blue Screen Of Death just after I closed a game

Mido123

Reputable
Aug 2, 2015
13
0
4,510
People of tom's hardware :D

I have returned with a new BSOD error. This time this happened after I was closing Metal Gear Solid V and I think it is a Direct X issue. Please advise on the best course of action, should I lower the graphics setting on the game? I say that because I sort of went over board and put everything on "Ultra High", my card is a NVidia GTX 570.

I copied the dump file below so you guys can take a look at it.

Dump File : 090715-32963-01.dmp
Crash Time : 9/7/2015 9:13:38 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`0542fd30
Parameter 3 : fffff880`07fe9648
Parameter 4 : fffff880`07fe8ea0
Caused By Driver : dxgmms1.sys
Caused By Address : dxgmms1.sys+2395f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : dxgmms1.sys+2fd30
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090715-32963-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 416,464
Dump File Time : 9/7/2015 9:14:48 PM

Thanks
 
Solution
the directx graphics subsystem was passed a bad memory address and called a bugcheck.
you have several suspect drivers installed that can corrupt data in memory or change timing (overclock) and cause this to happen.

I would remove or update the below drivers and see if you can reproduce the problem after the updates.
You will also want to go to your motherboard vendors website and get the various driver updates for your motherboard.
(BIOS update also, if you update your USB 3.0 drivers which are really out of date)

remove: overclocking software: RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Win7)
RTCore64.sys


update wdcsam64.sys
http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys

update
network driver...
error code 0xc0000005 = bad memory address was passed to directx so it called a bugcheck.

typical causes: overclocking, overheating, bad power to GPU. old GPU drivers.

-sound driver conflict between motherboard sound device and the GPU sound support. Update motherboard sound driver from motherboard vendor, boot into BIOS and reset BIOS to defaults or update, boot windows go to device manager and turn off unused high definition sound devices like the GPU sound support if you don't get sound via your graphics cable to your monitor.

if you have nvidia shadowplay running, be sure to update your ethernet drivers. Old ethernet drivers may cause the shadowplay service to mess up (as well as virus scanners) (or turn off shadowplay if you don't actually use it)

you can also copy your memory dumps from c:\windows\minidump directory to a server like microsoft onedrive, mark the files as public and post a link.
I can dump your driver list and BIOS info and maybe see what caused the failure.






 

Mido123

Reputable
Aug 2, 2015
13
0
4,510


 
the directx graphics subsystem was passed a bad memory address and called a bugcheck.
you have several suspect drivers installed that can corrupt data in memory or change timing (overclock) and cause this to happen.

I would remove or update the below drivers and see if you can reproduce the problem after the updates.
You will also want to go to your motherboard vendors website and get the various driver updates for your motherboard.
(BIOS update also, if you update your USB 3.0 drivers which are really out of date)

remove: overclocking software: RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Win7)
RTCore64.sys


update wdcsam64.sys
http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys

update
network driver:
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
\SystemRoot\system32\DRIVERS\Rt64win7.sys Wed Jun 23 02:10:45 2010
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
(first driver on the list should work)

remove:
\SystemRoot\system32\DRIVERS\AsrAppCharger.sys Thu Jun 10 23:37:12 2010 used to override max current on USB to charge apple devices faster.
 
Solution

Mido123

Reputable
Aug 2, 2015
13
0
4,510
Alright so, it's finally the weekend and I managed to do what you said. However as I was navigating my way through the links to download the drivers and in the background I was queuing up for MOBA game I got another BSOD.....

That's a copy of the .txt file generated from Blue Screen Viewer
==================================================
Dump File : 091115-30451-01.dmp
Crash Time : 9/11/2015 1:20:00 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`054ba686
Parameter 3 : fffff880`10663d10
Parameter 4 : 00000000`00000000
Caused By Driver : afd.sys
Caused By Address : afd.sys+49686
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+735c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\091115-30451-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 337,432
Dump File Time : 9/11/2015 1:21:09 PM
==================================================

Anyway, Im writing this the latest wdcsam64.sys is being installed, I've already doene everything you suggested. I uploaded this new BSOD dump file onto onedrive again its called "091115-30451-01.dmp" Here is the link for it if you want to check it out https://onedrive.live.com/?id=16F15FC196BE945%21144&cid=016F15FC196BE945&group=0

I thought I fixed all these problems a while back when I re-imaged my pc 2 months ago and someone suggested that I should plug my hard disk into a different SATA port which seemed to work and my PC would run fine and not crash. I don't know if these are all problems that were already there and just didn't appear or these are new since I installed so many games at once.

Thanks again for being a great help!
 
system was calling afd!AfdPoll64+0x5f0 with a bad memory address right before the system bugchecked.

This is part of networking, a most likely caused by a network driver.
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
most likely this driver:\SystemRoot\system32\DRIVERS\Rt64win7.sys Wed Jun 23 02:10:45 2010
first attempt at a fix would to be to install the update:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false


another cause would be another driver corrupting memory of the afd.sys drivers data.
old drivers like \SystemRoot\system32\DRIVERS\AsrAppCharger.sys Thu Jun 10 23:37:12 2010
tend to do things like that.



 

Mido123

Reputable
Aug 2, 2015
13
0
4,510
I remember you mentioning this on your previous post. I deleted that system file that over rides the current, and I already downloaded the file from that link. However though I used the 3rd link that says Windows 7 and not the first one that says Windows Vista like you said, will that make a problem?

Thanks again

 

Mido123

Reputable
Aug 2, 2015
13
0
4,510
Hi

yet another BSOD,

==================================================
Dump File : 091415-27034-01.dmp
Crash Time : 9/14/2015 10:52:27 PM
Bug Check String :
Bug Check Code : 0x0000010e
Parameter 1 : 00000000`0000001f
Parameter 2 : fffff8a0`0d322010
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00063c6b
Caused By Driver : watchdog.sys
Caused By Address : watchdog.sys+122f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+735c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\091415-27034-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 395,400
Dump File Time : 9/14/2015 10:53:26 PM
==================================================

I uploaded the file on one drive again
https://onedrive.live.com/?id=16F15FC196BE945%21144&cid=016F15FC196BE945&group=0

it's the latest upload

I give up...

These BSODs only happen when i play metal Gear Solid V and whenever I google anything about them they are all graphics related..

Please help again
 
try and find out why this driver was not updated:
Realtek NDIS User mode I/O Driver - Ethernet
\SystemRoot\system32\DRIVERS\RtNdPt60.sys Sun Jul 19 19:27:32 2009

the last bugcheck was with directx trying to set up a direct memory transfer using a DMA controller, the DMA controller is a limited resource and you might have another device like a sound card having a conflict.

try and reset the BIOS to defaults or toggle a hardware setting, turn something off then back on. This can trick the BIOS into rescanning its hardware settings and rebuilding the database of settings it hands off to windows.

You might also see if you can get updated USB 3.0 drivers for your machine.
You have drivers from 2011, USB 3.0 drivers tend to have problems if they were before about april of 2013.
Etron USB 3.0 Extensible Hub Driver (get them from the motherboard vendor if they have them)
\SystemRoot\System32\Drivers\EtronHub3.sys Fri Jan 28 13:46:45 2011
\SystemRoot\System32\Drivers\EtronXHCI.sys Fri Jan 28 13:46:43 2011
 
I would first try to run memcheck. If your RAM has problems, it can create problems from ANY driver. It is also the most common problem with BSODs.
Also note that when you close a game, the RAM has to be emptied in order to get it ready for new inromation (if there is a problem when trying to empty it, it will BSOD, this was my problem, since I changed my ram I have never had a BSOD).

 

Mido123

Reputable
Aug 2, 2015
13
0
4,510


 

Mido123

Reputable
Aug 2, 2015
13
0
4,510
I did everything you said in your previous post and I still got another BSOD. The latest driver's for the USB3.0 from the vendor were from 2013. I also toggled the BIOS as you mentioned

the latest BSOD is on OneDrive, it's numbered 092115 - 28033-01 -- link is: https://onedrive.live.com/?id=16F15FC196BE945%21144&cid=016F15FC196BE945&group=0

Thanks again for your continuous help by the way

One thing for sure, all these blue screen's happen when I'm playing metal gear solid V, guess i should stop playing it all together. Adding to that, the last 3 blue screens had the same Bug Check String "SYSTEM_SERVICE_EXCEPTION", and the same Bug Check Code of 0x0000003b, same driver dxgmms1.ss but different parameters and different cause of addresses. I guess since it's the same bug check code this could only mean that the problem is being narrowed down
 
well, your bugcheck was in directx, this tends to indicate a problem with your graphics subystem.
It can be the graphics driver, the graphics hardware, the power to the graphics card or a conflict with the sound on the motherboard with the sound provided by the graphics card.

You also have a old motherboard, with a old processor. Sorry if this not not helpful, but I would be looking at making sure the hardware is ok, fans are spinning up, power levels look ok in BIOS, no overheating. Make sure there is no BIOS overclock of the PCI/e bus. (it should be set to 100MHz) Make sure the GPU is not overclocked.

find out what this driver is for:
C:\Windows\SysWOW64\Drivers\AsrAutoChkUpdDrv.sys Mon Mar 10 03:33:09 2014