Windows 10: VIDEO SCHEDULER INTERNAL ERROR on wake from sleep

New thread created as requested by Axe0

I just updated my Windows 8.1 desktop to Windows 10 Home and all is now running fine apart from this BSOD which occurs when restarting the PC from Sleep. As I use the PC as a Media Centre the ability to Sleep is important.

Attachment 39302

Other forums http://druss.co/2015/08/windows-10-v...after-wake-up/ indicate that this problem is related to the drivers for the Intel HD graphics, however the HD Graphics is not enabled in BIOS on my machine and is not shown in Device Manager and graphics are provided by the Nvidia GTX 660 card.

Attachment 39303

The PC has been fully updated with the latest Windows Updates and I have installed the latest Nvidia Graphics driver 355.98 released 22nd September.

I have checked with the latest drivers available on the Asus site for my Z87-A motherboard (MEI_V11_0_0_1155-20150709_WHQL_1-5M) and in fact the Windows 10 drivers installed are later version than those on the Asus site
Attachment 39304

I have attached the debug files extracted just now. Attachment 39305

:)

 

BSOD after sleep.

Hello everyone.

I updated my laptop (ASUS N550JV) from Windows 8.1 to Windows 10.

Now, every time after sleep my laptop gets BSOD (video scheduler internal error).

Please, help me.

 

Sleep issue

I am running a Windows 10 Pro Desktop(up to date wrt updates).

I have an internal Tandberg RDX, that I use for Acronis Backup. There is always a cartridge inserted.

I have Acronis set to schedule backups overnight, and wake the PC to perform them.

This works fine in 'hibernate' state.

But, in 'sleep' state, the RDX device does not appear when waking from 'sleep'.

Suggestions welcomed.

 

Hi balein,

The cause is the Nvidia Video driver every time.
However, the driver is not up to date.
Please try this driver from Geforce
Code: 1: kd> lmvm nvlddmkm start end module name fffff800`3be00000 fffff800`3c8e8000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Fri Aug 07 01:16:04 2015 (55C3EAB4) CheckSum: 00AA7B6C ImageSize: 00AE8000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] Please do the following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

 

I have reinstalled the Nvidia driver from the link, however this is the same driver I installed two days ago. (355.98). I then ran sfc /scannow which reported "Windows Resource Protection did not find any integrity violation" (I had already run this yesterday when it did find and fix another error which I had in Outlook)
I then re-enabled Sleep, rebooted the PC and entered Sleep. When it awoke the BSOD occurred again. You will see an additional DMP file in the attached debug file Attachment 39314

 

What other possible solutions have you done so far?

 

The things have tried so far are
1. Run chkdsk /r and sfc /scannow
2. Update Nvidia drivers to latest version
3. Check with Chillblast Support who confirmed that the Intel Built in Graphics is disabled in the BIOS
4. Upgrade motherboard firmware to latest version available
5. Check Asus website for updated drivers, however all my drivers were actually later version than those on Asus site.
6. Post questions on forums like this

Earlier today I did try to see if it would record a TV program from Sleep as I was not sure of the TV server actually woke up the display card. When I returned the PC was sleeping and actually woke up without the BSOD, however the TV programme had not recorded. It then was able to Sleep and Wake up several times OK, but after a reboot the BSOD has returned. I will try this again while I am watching it to see what happens.

 

Alright, this might be the case of the bug with the sleep function.
Even though I'm convinced the problem is in windows 10 self, I'd like to make sure the GPU is fine.

Please check the temperatures of the GPU when idle and under load.
Please run Furmark





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

 

I've just uninstalled the Nvidia 355.98 driver and rebooted and it has reverted to the latest drivers released by Windows which is 353.82 and it is now able to wake up from sleep OK (just done it twice in a row). I will reboot and see if it still is OK then.

If this does not work I'll do the Furmark test

 

No it did not work - after the reboot I put it to Sleep and on Wake up the BSOD reappeared.

I ran Furmark - idle temperature is 32% on around 10% Power - it plateaued at around 86% at 114% power. After I stopped it it

I did not see any screen artefacts.

 

Alright, the GPU is fine.
This is definitily the bug then, there are lots of people having the same problem but not the same error.
You might want to submit this to Microsoft via their feedback app.

 

Latest update: I left the PC to Sleep by itself on the timer, rather than Sleeping via the Start screen, and when I came to restart it was fine. I then sent it to Sleep manually and woke it up again OK straight away.

I have posted on the Feedback App where there are quite a few other posts on the same problem which I upvoted, so hopefully MS will eventually resolve it.

 

Glad to hear that, hope it stays that way *Smile

 

So I have now been using the machine for a few days and a clear pattern has emerged.

If I boot up the PC and then let it Sleep using the timer it will wake up without any BSOD. I am able to use Media Portal to wake the PC when it needs to record a programme and then Windows handles the Sleep afterwards. This is repeatable and appears reliable.

If I manually Sleep the PC from the Power button on Start menu, then it will either (I) BSOD on wake up (ii) start the PC but not wake up the display, so I am left with a black screen and need to force a restart by truing off the PC using the physical Power Button on the PC case. (iii) sometimes wake up OK

This seems to indicate the problem is in the way Sleep is initiated by Windows. Do you know if there is any difference between the way Windows initiates Sleep from the timer as opposed to the Power Button on Start Menu?

 

I would say there is, but I cannot say for sure unfortunately.