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

"Display driver stopped responding..." - Dota 2


  • Please log in to reply
2 replies to this topic

#1 larfrage

larfrage

  • Members
  • 1 posts
  • OFFLINE
  •  

Posted 31 October 2015 - 04:26 PM

Hello everyone.

After installing Windows 10 (not upgrading from 8.1) I've started receiving this error while playing Dota 2: "Display dirver stopped responding and has recovered". This happens only when I'm searching for a match, and not when in the actual game.

Laptop: Asus G551JM - GTX860M 4GB, 16 GB RAM, i7-4710HQ

What I've tried: set TdrDelay to 8, installed latest display drivers, installed older display drivers.
Setting the TdrDelay to 8 caused my pc to crash when trying to play Dota (BSOD: Video Scheduler Internal Error). I've uploaded the dump file.

I'm pretty sure this is not a hardware issue, because before installing Windows 10, I could play Dota all day on Windows 8.1 without any errors.

Attached Files



BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:06:06 PM

Posted 01 November 2015 - 07:20 AM

The error you get is most likely a STOP error (it's a BSOD, but the system recovers before the BSOD can occur).

I would first suggest that you revert your TDR settings to the default value.

Then I'd try the suggestions in this topic:   http://www.sysnative.com/forums/bsod-kernel-dump-analysis-debugging-information/35-video-tdr-timeout-0x116-0x117.html#post29532
Also, please monitor your temps with this free utility (probably not relevant for you - but try it anyway):  http://www.cpuid.com/softwares/hwmonitor.html

 

The biggest issue here is getting the latest, W10 compatible drivers for your system.

What's the make and model of your system?

 

If it's an Asus G551JM - then there are no W10 video drivers from Asus.

You can try the latest drivers from nVidia, but there are no guarantees that they'll work (depends if Asus is using modified drivers for their system).
You can also try installing the Asus video drivers for W8.1 in compatibility mode to see if that'll help.

 

Analysis:
The following is for informational purposes only.
**************************Sat Oct 31 12:14:22.510 2015 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\103115-20171-01.dmp]
Windows 10 Kernel Version 10240 MP (8 procs) Free x64
Built by: 10240.16545.amd64fre.th1.150930-1750
System Uptime:0 days 0:04:08.979
Probably caused by :dxgmms2.sys ( dxgmms2!VidSchiSendToExecutionQueue+8422 )
BugCheck 119, {2, ffffffffc000009a, ffffd0005bbb09f0, ffffe000a9b58be0}
BugCheck Info: VIDEO_SCHEDULER_INTERNAL_ERROR (119)
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000009a
Arg3: ffffd0005bbb09f0
Arg4: ffffe000a9b58be0
BUGCHECK_STR:  0x119
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
CPUID:        "Intel® Core™ i7-4710HQ CPU @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: 2494
  BIOS Version                  G551JM.204
  BIOS Release Date             10/13/2014
  Manufacturer                  ASUSTeK COMPUTER INC.
  Product Name                  G551JM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
**************************Sat Oct 31 12:14:22.510 2015 (UTC - 5:00)**************************
ASMMAP64.sys                Thu Jul  2 05:13:26 2009 (4A4C7A36)
atkwmiacpi64.sys            Tue Jul  2 04:35:32 2013 (51D290D4)
iwdbus.sys                  Thu Mar 13 17:59:14 2014 (53222A32)
igdkmd64.sys                Wed Apr 23 16:26:24 2014 (535821F0)
Netwbw02.sys                Sun Feb 22 06:00:57 2015 (54E9B6E9)
SCDEmu.SYS                  Fri Feb 27 22:20:51 2015 (54F13413)
rt640x64.sys                Tue May  5 12:21:03 2015 (5548EDEF)
RtsPer.sys                  Wed May  6 03:22:09 2015 (5549C121)
AsusTP.sys                  Wed Jun 17 04:27:57 2015 (55812F8D)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
[ntelppm.sys                Thu Jul  9 23:12:59 2015 (559F383B)
ibtusb.sys                  Mon Jul 13 19:32:22 2015 (55A44A86)
NvStreamKms.sys             Sat Jul 25 05:22:15 2015 (55B35547)
RTKVHD64.sys                Tue Jul 28 08:38:18 2015 (55B777BA)
nvvad64v.sys                Mon Aug 10 03:51:42 2015 (55C8580E)
AsHIDSwitch64.sys           Tue Aug 18 04:45:30 2015 (55D2F0AA)
aswMonFlt.sys               Wed Sep 16 11:38:29 2015 (55F98CF5)
aswRvrt.sys                 Wed Sep 16 11:38:40 2015 (55F98D00)
aswHwid.sys                 Wed Sep 16 11:39:11 2015 (55F98D1F)
aswRdr2.sys                 Wed Sep 16 11:39:13 2015 (55F98D21)
aswSnx.sys                  Wed Sep 16 11:39:29 2015 (55F98D31)
aswVmm.sys                  Wed Sep 16 11:57:56 2015 (55F99184)
aswSP.sys                   Wed Sep 16 11:58:19 2015 (55F9919B)
aswStm.sys                  Wed Sep 16 12:01:52 2015 (55F99270)
nvlddmkm.sys                Fri Oct  2 22:08:52 2015 (560F38B4)
VBoxNetLwf.sys              Thu Oct 15 09:49:18 2015 (561FAEDE)
VBoxUSBMon.sys              Thu Oct 15 09:49:18 2015 (561FAEDE)
VBoxNetAdp6.sys             Thu Oct 15 09:49:18 2015 (561FAEDE)
VBoxDrv.sys                 Thu Oct 15 09:49:46 2015 (561FAEFA)

 

http://www.carrona.org/drivers/driver.php?id=ASMMAP64.sys
http://www.carrona.org/drivers/driver.php?id=atkwmiacpi64.sys
http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=Netwbw02.sys
http://www.carrona.org/drivers/driver.php?id=SCDEmu.SYS
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=RtsPer.sys
http://www.carrona.org/drivers/driver.php?id=AsusTP.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=ibtusb.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=AsHIDSwitch64.sys
http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys
http://www.carrona.org/drivers/driver.php?id=aswHwid.sys
http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
http://www.carrona.org/drivers/driver.php?id=aswVmm.sys
http://www.carrona.org/drivers/driver.php?id=aswSP.sys
http://www.carrona.org/drivers/driver.php?id=aswStm.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
VBoxNetLwf.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=VBoxUSBMon.sys
VBoxNetAdp6.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=VBoxDrv.sys
 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 HarmD

HarmD

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:12:06 AM

Posted 08 November 2015 - 02:44 PM

I have the issue too. Also, crash only happens in menu, especially after click on "Find game" or when dota window is not active (alt+tab). Also, tryed TdrDelay fix, but it only changed crash message from "Display dirver stopped responding and has recovered" to other: "Dota.exe has been blocked from using graphics hardware". It seems to be something wrong with last Dota 2 update, because I have Windows 10 installed from Technical Preview and it used to be fine.

 

Laptop: Lenovo Y570, GT 555M, i7-2670Q, 8GB.


Edited by HarmD, 08 November 2015 - 02:48 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users