VIDEO_SCHEDULER_INTERNAL_ERROR means your video card is unstable. 
 
Suggestions:
 
#1 Try the older driver that worked for you.
#2 Try doing #3 listed here to see if it helps stop the issue.

Update:
 
Haven't had much time for doing #2 today. Just gamed a bit tho and the crash happened again only this time luckily it crashed only the game and not windows, which in turn allowed me to look closer at Windows Event Viewer. There were two listed events when this happened:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffc70d45cc9460
P3: fffff80d1afdbd90
P4: 0
P5: acc
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20180201-1943.dmp
\\?\C:\Windows\TEMP\WER-21349500-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF3A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF3A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF5A.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_1c93832016872eed5ec9dca4f95124689365f70_00000000_cab_24a9cf59

Analysis symbol:
Rechecking for solution: 0
Report Id: 676b32f6-6515-4105-b9c5-296b5a576e5c
Report Status: 4
Hashed bucket:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 55a80ab8-b6b9-44e1-840a-811e003b0693

Problem signature:
P1: 141
P2: ffffc70d45cc9460
P3: fffff80d1afdbd90
P4: 0
P5: acc
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20180201-1943.dmp
\\?\C:\Windows\TEMP\WER-21349500-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF3A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF3A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF5A.tmp.txt
\\?\C:\Windows\Temp\WERF745.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_1c93832016872eed5ec9dca4f95124689365f70_00000000_cab_3b3dfa80

Analysis symbol:
Rechecking for solution: 0
Report Id: 676b32f6-6515-4105-b9c5-296b5a576e5c
Report Status: 268435456
Hashed bucket:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Debug mode is enabled now. Only problem  is that the card is no longer being stressed after I edited the ini files therefore the chance of it occurring are allot lower. I suppose I could just run Furmark, pretty certain it will just happen again tho. For some reason the GPU is overheating now.
 

Same thing I was thinking. Although it's only a month old. It was running on high load for those games in that month due to lack of settings and I guess me forgetting to edit the ini files manually.
Hopefully it resolves the issue. Would hate to RMA now since my card isn't even in stock anymore.

Cheers good to know.

Yeh I wanted to get the FTW3 hybrid kit, but sadly there was a post that there is an issue with this kit. I got the 12GHZ version too so the memory overheats even quicker. Sadly the kit is now sold out and still no news in the thread if the kit actually has issues or not. Only way to get it is from Newegg US shipping + EU tax, and with no news of risking a RMA with the card not worth the risk and increased cost.

Good to know I ordered thermal paste and will be doing the same. My only worry is since it now winter and I am already experiencing overheating issues, what will happen when summer comes.
 
What is last shunt mod RS3?

Yeah but I just spent enough on an entire new rig. Full blown water block is just too overpriced for no real advantage over AIO other than looks and even lower temps + you need to consider the maintenance involved with it too, other problem is the space it will take and that I''m already on a Corsair hybrid H150i for the CPU, so its simply too late to go full custom loop. Sure Arctic Cooling does have a block, but the EVGA FTW3 version is the only one that incorporates the liquid cooling block for  Vram cooling as well. Don't Know enough about the Kraken G12, looks like it just has a fan for the VRAm aswell tho + the cost of an additional hybrid pump.
 
I appreciate the suggestions tho. For now I will just try new thermal paste and hope it will solve the issue. By the time the thread about that particular hybrid kit gets resolved EVGA should finally have stock again in EU hopefully. It is possible they pulled it from stock as well because they are now aware of the issue.

bcavnaugh
shaolinn I have one of them cards on the way to test with and I will PM you with my findings.

 
Sweet. Although the card was handling full load for quite some time until this problem started appearing. For now the issue is somewhat under control since so far it's only crashed the software/game once. Will have to put in more hours to see how often it still happens. The thermal paste is already on it's way but will probably not make it until next week.

shaolinn
Update:  Got my first official windows 10 blue screen.
 
VIDEO_SCHEDULER_INTERNAL_ERROR again

What psu and how old?

K since I finally have some more time on my hands will.
 
1. Test different PCIE power lanes on the psu to check if PCIE 1 has gone bad. Also will test running the card off 2 PCIE power lanes connecting one 8pin VGA cable from each psu lane separately.
2. Move the card through the different PCIE lanes on the mobo.
 
If none of these solve the issue.
 
I'm down to
 
1. Waiting for thermal paste and taking off the stock cooler to redo the thermal paste of the cooling block.
2. Clean installing Windows 10 just in case something went wrong as usual with Microsoft forced updates.
 
 

Sajin
Every time you restart your computer you'll need to enable debug mode again. It doesn't stay on permanently.

I know debug mode didn't help in the first place tho.

You'll most likely end up needing to rma the card.

Most likely but its weekend anyway. How does the RMA process work anyway if they don't even have stock for your card. Any idea?
 

AHowes

shaolinn
Most likely but its weekend anyway. How does the RMA process work anyway if they don't even have stock for your card. Any idea?
 

It's quick and they say they hold stock for rma's.. no idea about elite cards though but possibly.

that's good to know. But they do state if found faulty they will exchange it for one deemed at equal standing or however they worded it. So mite just end up with a regular elite or ftw3.