Need someone to do an analysis of this minidump

mrsotok

Prominent
Nov 9, 2017
42
0
530
Hello, recently I've got some BSODs when I was browsing chrome.
The screen went "No signal" then a BSOD appeared with low resolution with the error code: VIDEO_SCHEDULER_INTERNAL_ERROR. I have changed my old card (I had this BSOD with my old one too. It also happened whenever I set my memory profile to XMP. I did ran a test on my memory sticks to see if they were stable or not and the results were normal (no errors). I think that it could be the motherboard (AB350-Gaming 3). My old card was a Palit 1060 3GB and my new one is the 1070 Jetstream. My RAM is 2x4GB Corsair 3000MHz C15 (Currently set to 2133MHz for stability. Thanks in advance

Here is the crash dump:

Windows 8 Kernel Version 17763 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff806`7cc16000 PsLoadedModuleList = 0xfffff806`7d035a50
Debug session time: Sat Oct 27 04:28:34.487 2018 (UTC - 4:00)
System Uptime: 0 days 0:05:19.205
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffff910990fd2960
Arg4: ffff800d3b5a1810

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x119

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80685f340db to fffff8067cdc6f30

STACK_TEXT:
ffff9109`90fd2878 fffff806`85f340db : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff9109`90fd2960 : nt!KeBugCheckEx
ffff9109`90fd2880 fffff806`87d6b3e8 : 00000000`00000000 ffff800d`3b59e000 ffff800d`3b59e000 ffff800d`3b5a1810 : watchdog!WdLogEvent5_WdCriticalError+0xdb
ffff9109`90fd28c0 fffff806`87dc594d : ffff800d`00000000 ffff800d`3b5a1810 ffff800d`3b490000 ffff800d`3dc02550 : dxgmms2!VidSchiSendToExecutionQueue+0x15578
ffff9109`90fd2a00 fffff806`87dd5285 : ffff800d`3dc02550 ffff800d`3b572600 00000000`00000000 ffff800d`3b572620 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffff9109`90fd2b80 fffff806`87dd50fa : ffff800d`3b490400 fffff806`87dd5030 ffff800d`3b490000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
ffff9109`90fd2bd0 fffff806`7cd376c5 : ffff800d`3b487680 fffff806`00000001 ffff800d`3b490000 00000065`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffff9109`90fd2c10 fffff806`7cdce38c : ffffd880`39b79180 ffff800d`3b487680 fffff806`7cd37670 64894c78`eb068949 : nt!PspSystemThreadStartup+0x55
ffff9109`90fd2c60 00000000`00000000 : ffff9109`90fd3000 ffff9109`90fcd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c


STACK_COMMAND: kb

FOLLOWUP_IP:
dxgmms2!VidSchiSendToExecutionQueue+15578
fffff806`87d6b3e8 0f1f440000 nop dword ptr [rax+rax]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+15578

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x119_dxgmms2!VidSchiSendToExecutionQueue+15578

BUCKET_ID: X64_0x119_dxgmms2!VidSchiSendToExecutionQueue+15578

Followup: MachineOwner
---------
 
what Nvidia drivers are you running? where did you get them from?

try running ddu in safe mode, delete the Nvidia drivers off system and either get new ones from Windows update or Nvidia, depending which is opposite to where you got them last time - http://www.tomshardware.com/faq/id-2767677/perform-clean-install-video-card-drivers.html

Can you follow option one on the following link - here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and I will get someone to convert file into a format I can read
 
No BSOD yet.. but some games act weirdly. For Honor and Hearts of Iron IV minimize themselves and I have to click on them again. Black Ops 2 Zombies crashes and a window popped up saying: Unhandled exception caught. What now?
 


Most people don't want BSOD. But I get the appeal, it means you might get an answer to all the crazy. I know the feeling, my PC was doing strange things for last few weeks and we threw everything we could think at the problem. I am not sure if its fixed as it wasn't giving BSOD to me, and if it had, we could have figured out cause. Like many times with BSOD, I will only know its fixed when it stops happening.

I sent link to a friend, he will reply with a post that I can use to see whats going on. He may not have answer but he is helping :)

 
Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/Qwqq.html

File: 110618-5734-01.dmp (Nov 6 2018 - 15:18:47)
BugCheck: [VIDEO_SCHEDULER_INTERNAL_ERROR (119)]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by: dxgmms2.sys (Process: RGBFusion.exe)
Uptime: 0 Day(s), 0 Hour(s), 07 Min(s), and 49 Sec(s)

The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

Possible Motherboard page: https://www.gigabyte.com/us/Motherboard/GA-AB350-Gaming-3-rev-1x#kf
BIOS version: F20 (Dated: 02/06/2018)

I can't help you with this. Wait for additional replies. Good luck.
 
Did you run DDU like I suggested up top? looks like you running the windows update versions (I recognise the date), so I assume you did. The 3 most recent from Nvidia might be an idea.

Their drivers used to be more consistent, now its hit and miss. You need to experiment to find ones that work. I had (have?) a problem where my GPU drivers would just stop responding to windows, and went through 3 versions of Win 10 + 5 Nvidia drivers just to stop trying to fight it, I am still using the Windows update drivers. Problem has just stopped, seemingly by itself. I still don't understand it.
 
I'll try installing the three latest ones, as you mentioned. But can you take a look at this?

"Probably caused by: dxgmms2.sys (Process: RGBFusion.exe)"

RGBFusion is an app that I am using for my motherboard's lighting. Could the app cause the issue or could it be caused by the motherboard?
 
The line above is more a clue to me

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by: dxgmms2.sys (Process: RGBFusion.exe)

nvlddmkm.sys is the Nvidia driver
dxgmms2.sys is direct X

normally seeing both together means it was Nvidia drivers caused Direct X to crash, as I doubt RGB fusion has much to do with direct X.

RGB fusion likely the victim, it is what crashed but it didn't do it of its own accord. That is like blaming the game you were playing when GPU crashed.

Having said that, have you got latest version? Only came out about 2 weeks ago - https://www.gigabyte.com/us/Motherboard/GA-AB350-Gaming-3-rev-1x#support-dl-utility
 
I downloaded the latest GPU and BIOS version... I'll keep you informed for any crashes.
The only thing I changed in the GPU control panel is the power consumption which is on maximum performance.
 
This seems bsod to have happened before alot looking at this thread (pretty old by now ~2015),one thing that seemed to work is make games to work in W7 compatibility mode if i read the thread correctly. Try this,rightclick the shortcut for pubg,choose properties and there compatibility mode,change to W7 if not set at that.Test and see if this helps.
 
Yes.. 😀

I don't know why it says that i have W8! I never liked them anyways.. lol
Okay so, I got the new 417.22 installed and I am looking forward to any good or bad signs