Windows 10: BSOD Video scheduler int. error - random - always video 'triggered'

I've been having random BSOD's playing video content, or even just loading a page with video content that I would guess auto-plays or does a pre-roll etc.

It happens regardless of browsers FF, IE, Chrome, Vivaldi (chrome fork) I do not use Edge and will not use it "for testing".

It could be 5 seconds after starting and loading a page with the content, or I could play russian roulette and at some point using one of the browsers above, watching a youtube video, or lauching DishTV's player (chrome based) Today for example.. I had a BSOD when I started IE and logged into a site that has video roll content on its main page.

After the BSOD finished writing and rebooted my pc I launched IE, went to the same page (it dynamically updates on every load) and it BSOD'd again, did it a third time after bsod & restart .. page loaded without issue and allowed me to play content. Some time, from now until it happens again, I'll be loading any of the other video content, Youtube, CBS, CNBC any place with video content that isn't a by default "load but not play" type site, and I'm sure to get a BSOD. The only way I've not had BSOD issues, is to stay away from pages that have video or animation content.

In firefox I have a flash stopper so that content won't (unless it bypasses) load/start automatically but that only prolongs when I might have a BSOD while at such sites, because the moment I do select something to start playing .. I'm back in the russian roulette game. Will it be this video? that video? the Next video?

Most of the debugs I've run so far all point back to something like this:
FAILURE_ID_HASH_STRING: km:0x119_5_driver_faulted_system_command_dxgmms2!vidschiprocessisrfaultedpacket

I've tried several "fixes" on the net so far .. my last was to fully uninstall all radeon software and drivers .. windows came back with the generic video card, and then updated that to the RX580 driver from April 2017, that GPF'd (BSOD'd) too, so I then did update driver, pointed it to the directory on my hard drive for the latest AMD driver and it appeared to take, the date updated for around the time of the driver, though the revision number isn't directly visible on the download site, as it uses something like 17.x where that a package release number for their Catalyst or now Crimson stuff not the driver itself.

I'm hoping you can see something different, or at cause that may help resolve this.

ran the tool to collect logs, let me know if there's something missing.

Thank you!!Attachment 153187

:)

 

Fall Creators Update crashes on SLI Surround Configuration

Are you experiencing BSOD with video scheduler internal error?

 

Windows 10 Operating System error

Continually receive a blue screen at random with message : Video scheduler error. How to fix ?

 

FYI, just finished updating specs, previous specs were for my older machine, an AMD a10 also with Windows 10Pro (via free upgrade path) where I've not had this level of problems .. but it was a budget build ... this time I went for a fairly high end video card (for its time) and if the basic driver worked for this card I'd be done with this BSOD bs and just run with it, but the basic driver won't work with enabling multi monitor.

Other than this BSOD issue, the only other problem I've had that is kicking my a** is a failure to activate screen saver/lock screen properly. Oddly I had a VNC session open and while it was, screen saver operated flawlessly .. but it also disabled backgrounds and other such stuff like it would normally do..and it got "stuck" that way even after shutting down the service. The fix was a reboot, and that brought back my windows in-built rotating desktop displays, but also the same "wont go to screen saver // lock screen"

 

These crashes appear to be happening because your video card driver (atikmdag.sys) is sending faulty interrupts to the graphics stack.

Code: 0: kd> k # Child-SP RetAddr Call Site 00 fffff803`1b0699e8 fffff80e`d3c2355e nt!KeBugCheckEx 01 fffff803`1b0699f0 fffff80e`d5b26962 watchdog!WdLogEvent5_WdCriticalError+0xce 02 fffff803`1b069a30 fffff80e`d5b1b17a dxgmms2!VidSchiProcessIsrFaultedPacket+0x23e 03 fffff803`1b069ab0 fffff80e`d5b0ad0d dxgmms2!memset+0x517a 04 fffff803`1b069b00 fffff80e`d3c4be84 dxgmms2!VidSchDdiNotifyInterrupt+0x8d 05 fffff803`1b069b30 ffff8c8b`9e996030 dxgkrnl+0xbe84 06 fffff803`1b069b38 0000000a`001ac74c 0xffff8c8b`9e996030 07 fffff803`1b069b40 ffff8c8b`00000000 0x0000000a`001ac74c 08 fffff803`1b069b48 fffff803`00000000 0xffff8c8b`00000000 09 fffff803`1b069b50 ffff8c8b`9e973000 0xfffff803`00000000 0a fffff803`1b069b58 fffff803`1764787b 0xffff8c8b`9e973000 0b fffff803`1b069b60 ffff8c8b`9e976518 atikmpag+0x4787b 0c fffff803`1b069b68 fffff803`1dad53e4 0xffff8c8b`9e976518 0d fffff803`1b069b70 00005b1d`5a9346ca atikmdag+0xf53e4 0e fffff803`1b069b78 00000000`00000000 0x00005b1d`5a9346ca[/quote]
This shows that the bugcheck is happening at a Device IRQL.
Code: Debugger saved IRQL for processor 0x0 -- 11[/quote]
From the logs collected your installed video driver is from 5/16/2017, and the
latest radeon graphics driver is from 9/7/2017. More specifically you are running version 22.19.162.4 of atikmdag.sys and the latest version is 22.19.676.0.

If you are overclocking your GPU and/or have modified power settings for your GPU please reset everything to default. It also won't hurt if you monitor your GPU's temperature with something like HWMonitor to ensure it isn't overheating.

 

Thanks, but that must have been before I updated the driver.

It is the current driver now as via dxdiag

Attachment 153201

I'll upload a fresh debug on next GPF.

-T

 

We'll likely have to wait and see if it crashes now that your display driver is current.

 

yeah, it was current before the BSOD's, it BSOD'd the last time, and I uninstalled all drivers with AMD's "CleanupUtility" (though I've also used DDU before) and let windows update get the driver *it* wanted. I probably captured the data inbetween .. hence will get a fresh update on my next GPF/BSOD.

I have faith it will happen easily .. I just have to get yard work done before storms come rolling through or I'd be forcefully looking for the next one. :-D

 

Please post a memory.dmp using one drive or drop box.
File explorer > this PC > local C: drive > right upper corner search > type: C:\Windows\MEMORY.DMP > save to desktop > one drive or drop box share link > paste into thread

 

Diagnostic test

GPU TEST


Run Furmark tutorial



Note Run Furmark for around 30 minutes



Warning Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high
When finished, make a photo/screenshot of Furmark and post it.

In Furmark you can find a tool called 'GPU-Z' (if you want to install GPU-Z is up to you), when GPU-Z is open click on the 'Sensors' tab, on this tab you can monitor

• the frequency of the GPU,
• the GPU memory clock,
• the temperature,
• the power,
• the load on the GPU,
• Etc.

I would like you to make a screenshot of GPU-Z after you have either cancelled Furmark for any reason or Furmark is finished, post this screenshot in your next reply with the result of Furmark.

 

And your wish is granted *Smile

Dropbox - MEMORY-2017-09-18.1654.DMP

Attachment 154013

yes, I've been avoiding most video stuff, and it just so happened I click on something in youtube .. and bsod. Sometimes mere minutes, sometimes a few days .. longer when I abstain or try not to just have something "play" in the background while I'm working.

I was actually looking for a video to quote humorously in a work chat. ... poof! GPF & reboot.

Thanks again for looking at this stuff.. I'm sure I'd see the same as before.. GPF, 0x119 Video Scheduler, couldn't load modules for some AMD app/driver/thing, and so forth.

 

There was 1 bsod mini dump from today 9/18/2017.
The last bsod mini dump prior to this was from 9/13/2017.
Today's mini dump debugging indicated that there were 2 misbehaving hardware graphics drivers:
atikmpag.sys
atikmdag.sys

The logs indicate that the graphics drivers have been misbehaving since 6/20/2017
Earlier in this thread the video graphics drivers were troubleshooted.
Please describe in detail the steps that you had made in fixing the drivers.




Perform the following steps:

1) Uninstall everything AMD using Display driver uninstaller and install new drivers from the Asus or the AMD website.
2) The Asus web site is preferred.
3) Enter the computer's serial or product number and the operating system to view available drivers.
4) If you use the AMD web site be sure the "clean install" box is checked and only install the graphics driver.
Official Display Driver Uninstaller DDU Download
Display Driver Uninstaller Download version 17.0.7.2
Display Driver Uninstaller: How to use - Windows 7 Help Forums
AMD Support and Radeon Software Driver Download




Code: BugCheck 119, {5, ffffc70545889000, ffffc705466e1ad0, 106d7f}*** WARNING: Unable to verify timestamp for atikmpag.sys*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys*** WARNING: Unable to verify timestamp for atikmdag.sys*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sysProbably caused by : dxgmms2.sys ( dxgmms2!VidSchiProcessIsrFaultedPacket+23e )[/quote] Code: Name Radeon RX 580 SeriesPNP Device ID PCI\VEN_1002&DEV_67DF&SUBSYS_22FA1458&REV_E7\4&1DA95F35&0&0019 Adapter Type AMD Radeon Graphics Processor (0x67DF), Advanced Micro Devices, Inc. compatible Adapter Description Radeon RX 580 Series Adapter RAM (1,048,576) bytes Installed Drivers aticfx64.dll,aticfx64.dll,aticfx64.dll,amdxc64.dll,aticfx32,aticfx32,aticfx32,amdxc32,atiumd64,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64 Driver Version 22.19.676.0 INF File oem6.inf (ati2mtag_Polaris10DS section) Color Planes Not Available Color Table Entries 4294967296 Resolution 1920 x 1080 x 60 hertz Bits/Pixel 32 Memory Address 0xE0000000-0xF01FFFFF Memory Address 0xF0000000-0xF01FFFFF I/O Port 0x0000D000-0x0000DFFF Memory Address 0xFE900000-0xFE9FFFFF IRQ Channel IRQ 4294967288 I/O Port 0x000003B0-0x000003BB I/O Port 0x000003C0-0x000003DF Memory Address 0xA0000-0xBFFFF Driver c:\windows\system32\driverstore\filerepository\c0317685.inf_amd64_f4ed8f05a31c5d2d\atikmpag.sys (22.19.676.0, 529.02 KB (541,720 bytes), 9/13/2017 2:29 PM)[/quote] Code: 9/15/2017 10:00 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 440c6051-1740-4b98-a742-17db7e97b188 Problem signature: P1: 141 P2: ffffe6807f546010 P3: fffff804349ef818 P4: 0 P5: 4cc P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170915-0600.dmp \\?\C:\Windows\Temp\WER-73355140-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER658D.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER659C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER660B.tmp.txt \\?\C:\Windows\Temp\WER8318.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_333cd5bae59df8cd27c08ffd8d631088cbbfc7f5_00000000_cab_165b8598 Analysis symbol: Rechecking for solution: 0 Report Id: b517b64f-b906-4679-847d-ab5ca680edbe Report Status: 268435456 Hashed bucket:[/quote] Code: 8/23/2017 3:03 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 565604f2-bde8-4ffa-83d9-2d4049b1dc33 Problem signature: P1: 141 P2: ffffa28a76026010 P3: fffff80fda8ef7f8 P4: 0 P5: 4dc P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170822-2303.dmp \\?\C:\Windows\Temp\WER-3036484-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D04.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D14.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D44.tmp.txt \\?\C:\Windows\Temp\WER7139.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_b17cba2156741ff69847e548d6b9c6d41b7706e_00000000_cab_23ca732c Analysis symbol: Rechecking for solution: 0 Report Id: 22a20e70-106c-4498-9c60-5ef1dfb327ff Report Status: 268435456 Hashed bucket:[/quote] Code: 7/30/2017 8:22 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: efb07b59-7ad4-45be-8688-7765b7dd5adc Problem signature: P1: 141 P2: ffffbf83128e7010 P3: fffff80805c4f640 P4: 0 P5: 12f4 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170730-0421.dmp \\?\C:\Windows\Temp\WER-6021046-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE9B9.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE9B9.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE9F8.tmp.txt \\?\C:\Windows\Temp\WERFF17.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_87ce62af2fb439542e22dd2518bed83658e71d_00000000_cab_10fc0119 Analysis symbol: Rechecking for solution: 0 Report Id: 7cdbfa4e-13c4-4e12-88b1-b266dc6d3926 Report Status: 268435456 Hashed bucket:[/quote] Code: 7/24/2017 10:03 PM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 1d778b3a-ae88-4f64-9b23-4bdf3d156970 Problem signature: P1: 141 P2: ffff91033b06f010 P3: fffff804349af640 P4: 0 P5: 4e8 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170724-1803.dmp \\?\C:\Windows\Temp\WER-1082453-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER903C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER904B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER909A.tmp.txt \\?\C:\Windows\Temp\WERB067.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_d5132d1d24a43fa0572a9c5c1d6159f264b7d71_00000000_cab_3894b1cd Analysis symbol: Rechecking for solution: 0 Report Id: abd91ffd-e401-4103-86a3-2d12b72c1ff7 Report Status: 268435456 Hashed bucket:[/quote] Code: 7/16/2017 8:39 AM Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: a023c99e-ce33-4f30-8c28-a8a967e0ee2f Problem signature: P1: 100000ea P2: ffff8c03fe85f080 P3: 0 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\071617-12843-01.dmp \\?\C:\Windows\Temp\WER-13718-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER42C5.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER42D5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER42E6.tmp.txt \\?\C:\Windows\Temp\WER7FFE.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_100000ea_73a4f1b259244976455dfae11145c1e5b1a12e8_00000000_cab_1b508339 Analysis symbol: Rechecking for solution: 0 Report Id: 220c5333-bb65-4856-b021-b26656227ae0 Report Status: 268435456 Hashed bucket:[/quote] Code: 7/14/2017 6:50 AM Windows Error Reporting Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: e30ee3ed-0466-4d44-b164-8c6911180a15 Problem signature: P1: 100000ea P2: ffffdd8141fcf7c0 P3: 0 P4: 0 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\071417-10390-01.dmp \\?\C:\Windows\Temp\WER-12593-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CDB.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CDC.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CEC.tmp.txt \\?\C:\Windows\Temp\WERA26F.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_100000ea_c73ddc6e8b8c581cb794152cc3fd9298f1084aa_00000000_cab_1b58a558 Analysis symbol: Rechecking for solution: 0 Report Id: ae177017-dd16-4618-8f9f-60bf837228d8 Report Status: 268435456 Hashed bucket:[/quote] Code: 7/14/2017 6:49 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: ca971641-4959-4390-87c2-6d6107c71050 Problem signature: P1: 141 P2: ffffdd81439b5360 P3: fffff805b242f640 P4: 0 P5: 2e90 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170714-0242.dmp \\?\C:\Windows\Temp\WER-12593-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C9B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CBA.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CCB.tmp.txt \\?\C:\Windows\Temp\WER7C75.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_cb7ffe952b4af3c97bb045b2c911350a8b16f3a_00000000_cab_1b587f9f Analysis symbol: Rechecking for solution: 0 Report Id: 0b931c42-66dc-4541-904d-8139bbb438d9 Report Status: 268435456 Hashed bucket:[/quote] Code: 6/20/2017 2:32 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 6ce40d40-aef4-4c20-9004-ce8423c836b1 Problem signature: P1: 141 P2: ffffe58e2b54e010 P3: fffff806ead0f654 P4: 0 P5: 47c P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170615-1927.dmp \\?\C:\Windows\Temp\WER-8562-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BB3.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BC3.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BD3.tmp.txt \\?\C:\Windows\Temp\WER4C5B.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_ba6147d968bbd99c1462afb73d8aca40f6f541_00000000_cab_18704f77 Analysis symbol: Rechecking for solution: 0 Report Id: 5e5188c3-7d41-4ad6-8503-eb5537defa4e Report Status: 268435456 Hashed bucket:[/quote]

 

[/quote] per AMD, un-installed via control panel, programs & features, uninstall radeon/amd installer, whichever. Then I ran AMD Clean Uninstall Utility. Rebooted when prompted.

Windows came up, I logged, in, headed to Device Manager, and just as I got there, the display updated from Microsoft's Generic Adapter, to the Radeon driver Microsoft Provides. Once that was installed, I right clicked, chose update, browsed for the folder I extracted the drivers to, and told it to install.

I must have run the collection tool between the update, and before I actually updated, then didn't run it again, until after I'd installed the updated driver, and hence posted the collection tools' Zip file from when the driver was microsoft's provided AMD driver from several months ago.

I posted the dxdiag screen showing that I was at that time (but after uploading) current on drivers. I haven't purposefully changed drivers since my DxDiag post.

 

Turn off Windows updates of non-Microsoft drivers.
Enable or Disable Driver Updates in Windows Update in Windows 10 Windows 10 Windows Update Activation Tutorials
Use DDU in post #10.
Turn back on Windows updates of non-Microsoft drivers if desired.

The memory dump displayed 2 additional misbehaving drivers.
IDSvia64.sys
hcmon.sys

1) Uninstall Norton AV
Uninstall and Reinstall Norton product using the Norton Remove and Reinstall tool
2) Turn on Windows defender
3) Update hcmon.sys (if you no longer use it then uninstall)


Updating a driver: Microsoft Community


IDSvia64.sys Norton Internet Security NORTON™ - Antivirus Software and Spyware Removal
hcmon.sys VMware USB monitor VMware Support & Downloads for Desktop, Application & Data Center Virtualization | United States

Code: IDSVia64 IDSVia64 IDSVia64 Kernel System Running OK TRUE FALSE 8,192 823,296 0 7/26/2017 4:25:09 PM \??\C:\Program Files (x86)\Norton Security Suite 4,096[/quote] Code: hcmon VMware hcmon VMware hcmon Kernel Auto Running OK TRUE FALSE 4,096 40,960 0 8/18/2016 1:43:53 AM C:\WINDOWS\system32\DRIVERS\hcmon.sys 8,192[/quote]