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
---------
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
---------