Sporadic internal_video_scheduler_error when cold booting

floskan · Dec 15, 2023

I get sporadic but at this point almost daily internal_video_scheduler_error bluescreens when booting into windows for the first time (W11 build 23H2, 22531.2861). It happens when i use any of the latest nvidia drivers, but hasn't happened in 5 days since i swapped to an older driver (537.58). Is this a software issue that somehow makes me unable to use the latest nvidia drivers? First i assumed this to be a GPU issue but it's still happening with a different one i bough after returning the first one a few weeks ago. I had more dumps earlier but they got lost when i reformatted unfortunately.
I'm also attaching my log file.

Thanks in advance!

zbook · Dec 15, 2023

Today is Fri Dec 15 2023.

The dumps were all reported on Wed Dec 13 2023.

There were no reported unexpected shutdowns and restarts after Dec 13.

The computer has both AMD and Nvidia GPU drivers.

There was only one collected BSOD dump file and it was caused by misbehaving Nvidia GPU drivers.

Please perform the following steps:

1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

2) Turn off Windows fast startup:

Turn On or Off Fast Startup in Windows 11 Tutorial

This tutorial will show you how to turn on or off fast startup in Windows 11. There are three startup modes in Windows: Cold (traditional) Wake-from-hibernation Fast Starting with Windows 8.x, the default shutdown and restart scenario has been updated and named fast startup. Fast startup...

www.elevenforum.com

3) Make a new restore point:

Create System Restore Point in Windows 11 Tutorial

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

4) Monitor using Reliability monitor:

View Reliability History in Windows 11 Tutorial

This tutorial will show you how to view reliability history for your Windows 11 device. The Reliability Monitor provides a system stability overview and details about events that impact reliability. It calculates the Stability Index shown in the System Stability Chart. Reliability Monitor...

www.elevenforum.com

Code:

Name    NVIDIA GeForce RTX 4090
PNP Device ID    PCI\VEN_10DE&DEV_2684&SUBSYS_51021462&REV_A1\4&D7CE646&0&0009
Adapter Type    NVIDIA GeForce RTX 4090, NVIDIA compatible
Adapter Description    NVIDIA GeForce RTX 4090
Adapter RAM    (1,048,576) bytes
Installed Drivers    C:\Windows\System32\DriverStore\FileRepository\nvmdig.inf_amd64_ad813833cb149cd8\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmdig.inf_amd64_ad813833cb149cd8\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmdig.inf_amd64_ad813833cb149cd8\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmdig.inf_amd64_ad813833cb149cd8\nvldumdx.dll
Driver Version    31.0.15.3758
INF File    oem16.inf (Section063 section)
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVMDIG.INF_AMD64_AD813833CB149CD8\NVLDDMKM.SYS (31.0.15.3758, 56.45 MB (59,190,392 bytes), 15/12/2023 16:40)

Code:

nvlddmkm.sys Wed Dec  6 10:23:29 2023 (6570BC21)

floskan · Dec 15, 2023

zbook said:
Today is Fri Dec 15 2023.

The dumps were all reported on Wed Dec 13 2023.

There were no reported unexpected shutdowns and restarts after Dec 13.

The computer has both AMD and Nvidia GPU drivers.

There was only one collected BSOD dump file and it was caused by misbehaving Nvidia GPU drivers.

Please perform the following steps:

1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

2) Turn off Windows fast startup:

Turn On or Off Fast Startup in Windows 11 Tutorial

This tutorial will show you how to turn on or off fast startup in Windows 11. There are three startup modes in Windows: Cold (traditional) Wake-from-hibernation Fast Starting with Windows 8.x, the default shutdown and restart scenario has been updated and named fast startup. Fast startup...

www.elevenforum.com

3) Make a new restore point:

Create System Restore Point in Windows 11 Tutorial

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

4) Monitor using Reliability monitor:

View Reliability History in Windows 11 Tutorial

This tutorial will show you how to view reliability history for your Windows 11 device. The Reliability Monitor provides a system stability overview and details about events that impact reliability. It calculates the Stability Index shown in the System Stability Chart. Reliability Monitor...

www.elevenforum.com

Code:

Name NVIDIA GeForce RTX 4090 PNP Device ID PCI\VEN_10DE&DEV_2684&SUBSYS_51021462&REV_A1\4&D7CE646&0&0009 Adapter Type NVIDIA GeForce RTX 4090, NVIDIA compatible Adapter Description NVIDIA GeForce RTX 4090 Adapter RAM (1,048,576) bytes Installed Drivers C:\Windows\System32\DriverStore\FileRepository\nvmdig.inf_amd64_ad813833cb149cd8\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmdig.inf_amd64_ad813833cb149cd8\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmdig.inf_amd64_ad813833cb149cd8\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmdig.inf_amd64_ad813833cb149cd8\nvldumdx.dll Driver Version 31.0.15.3758 INF File oem16.inf (Section063 section) Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVMDIG.INF_AMD64_AD813833CB149CD8\NVLDDMKM.SYS (31.0.15.3758, 56.45 MB (59,190,392 bytes), 15/12/2023 16:40)

Code:

nvlddmkm.sys Wed Dec 6 10:23:29 2023 (6570BC21)

Yes, i had several dumps before i reformatted with the same error, reinstalled W11 and tried the very latest nvidia driver and crashed the next time i booted. Before that and after that i used 537.58 without any kind of error.

Here's my tuneup log:

Code:

Microsoft Windows 11 Home  Version 23H2 (OS Build 22631.2861)
 
==================================================================

    Started on 2023-12-15 at 22:24:23,31
   
        [SFC /ScanNow]
   
Beginning system scan.  This process will take some time.

Results:
 
Windows Resource Protection did not find any integrity violations.
 
==================================================================

    Started on 2023-12-15 at 22:25:24,44

        [DISM /online /cleanup-image /ScanHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.2861
 
The component store is repairable.

The operation completed successfully.
 
==================================================================

    Started on 2023-12-15 at 22:26:29,65

        [DISM /online /cleanup-image /RestoreHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.2861
 
The restore operation completed successfully.

The operation completed successfully.
 
==================================================================

The second "SFC /ScanNow" was skipped, as the first output the following:

Windows Resource Protection did not find any integrity violations.
 
==================================================================

    Started on 2023-12-15 at 22:30:33,15

        [ChkDsk /Scan]
 
The type of the file system is NTFS.
 
Stage 1: Examining basic file system structure ...
460544 file records processed.                                                      
File verification completed.
Phase duration (File record verification): 2.36 seconds.
10659 large file records processed.                                  
Phase duration (Orphan file record recovery): 4.77 milliseconds.
0 bad file records processed.                                    
Phase duration (Bad file record checking): 0.03 milliseconds.
 
Stage 2: Examining file name linkage ...
215 reparse records processed.                                    
576664 index entries processed.                                                      
Index verification completed.
Phase duration (Index verification): 5.45 seconds.
0 unindexed files scanned.                                      
Phase duration (Orphan reconnection): 264.53 milliseconds.
0 unindexed files recovered to lost and found.                  
Phase duration (Orphan recovery to lost and found): 0.08 milliseconds.
215 reparse records processed.                                    
Phase duration (Reparse point and Object ID verification): 1.37 milliseconds.
 
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 30.37 milliseconds.
58061 data files processed.                                          
Phase duration (Data attribute verification): 0.04 milliseconds.
CHKDSK is verifying Usn Journal...
38230944 USN bytes processed.                                                          
Usn Journal verification completed.
Phase duration (USN journal verification): 68.94 milliseconds.

Windows has scanned the file system and found no problems.

No further action is required.
 
975859711 KB total disk space.
132660904 KB in 274261 files.
183228 KB in 58062 indexes.
0 KB in bad sectors.
599147 KB in use by the system.
65536 KB occupied by the log file.
842416432 KB available on disk.
 
4096 bytes in each allocation unit.
243964927 total allocation units on disk.
210604108 allocation units available on disk.
Total duration: 8.19 seconds (8190 ms).
 
==================================================================
 
    Started on 2023-12-15 at 22:30:45,90
 
AutoReboot  
 
TRUE      
 
==================================================================
 
        [Set AutoReboot = False]
 
Updating property(s) of '\\FLOSKAN\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Home|C:\\Windows|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.
==================================================================
 
AutoReboot  
 
FALSE      
 
==================================================================
 
DebugInfoType  
 
3            
 
==================================================================

        [Set DebugInfoType = 7]

Updating property(s) of '\\FLOSKAN\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Home|C:\\Windows|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.
==================================================================
 
DebugInfoType  
 
7            
 
==================================================================

        [WMIC PageFile list]

AllocatedBaseSize=9216
CurrentUsage=86
Description=C:\pagefile.sys
InstallDate=20231210143009.219767+060
Name=C:\pagefile.sys
PeakUsage=86
Status=
TempPageFile=FALSE
 
==================================================================
 
AutomaticManagedPagefile  
 
TRUE                    
 
==================================================================

        [Set AutomaticManagedPagefile = True]

Updating property(s) of '\\FLOSKAN\ROOT\CIMV2:Win32_ComputerSystem.Name="FLOSKAN"'
Property(s) update successful.
==================================================================
 
AutomaticManagedPagefile  
 
TRUE                    
 
==================================================================

        [BcdEdit /enum {badmemory}]

RAM Defects
-----------
identifier              {badmemory}
 
==================================================================

    Finished on 2023-12-15 at 22:30:46,67
    It took 6 minutes and 23 seconds to complete the operations.

Here's a log from reliability monitor when i crashed:

Code:

Källa
Windows

Sammanfattning
Maskinvarufel

Datum
‎2023-‎12-‎13 17:10

Status
Inte rapporterat

Beskrivning
Ett problem med din maskinvara gör att Windows inte längre fungerar korrekt.

Problemsignatur
Händelsenamn:    LiveKernelEvent
Kod:    117
Parameter 1:    ffff960c4e1c4010
Parameter 2:    fffff801c98863a0
Parameter 3:    0
Parameter 4:    0
OS-version:    10_0_22631
Service Pack:    0_0
Produkt:    768_1
OS-version:    10.0.22631.2.0.0.768.101
Språkvariant-ID:    1053

Code:

Källa
Windows

Sammanfattning
Oväntad avstängning

Datum
‎2023-‎12-‎13 17:10

Status
Inte rapporterat

Problemsignatur
Händelsenamn:    BlueScreen
Kod:    119
Parameter 1:    2
Parameter 2:    ffffffffc000000d
Parameter 3:    fffff58f557672a0
Parameter 4:    ffff960c4a189940
OS-version:    10_0_22631
Service Pack:    0_0
Produkt:    768_1
OS-version:    10.0.22631.2.0.0.768.101
Språkvariant-ID:    1053

floskan · Dec 15, 2023

I realized i saved the dumps from before i reformatted:

zbook · Dec 16, 2023

Was DDU used to clean install the prior Nvidia drivers?

If there is a BSOD caused by misbehaving Nvidia GPU drivers with the newest replaced driver then plan to swap test the GPU card.

Code:

nvlddmkm.sys Thu Nov  9 13:35:30 2023 (654D50A2)
Wed Nov 29 04:10:46.987 2023 (UTC - 6:00)
Wed Nov 29 04:07:03.293 2023 (UTC - 6:00)
Fri Dec  1 10:03:14.306 2023 (UTC - 6:00)

Code:

nvlddmkm.sys Thu Nov 30 23:56:36 2023 (656991B4)
Thu Dec  7 11:53:33.062 2023 (UTC - 6:00)
Sun Dec 10 04:59:15.256 2023 (UTC - 6:00)

Code:

nvlddmkm.sys Wed Dec  6 10:23:29 2023 (6570BC21)
Wed Dec 13 10:09:10.475 2023 (UTC - 6:00)

floskan · Dec 16, 2023

Yes, i used DDU. I already tried swapping GPU, i sent back my previous 4090 since it was still returnable and bought a new one from a different reseller, but the bluescreens continued. They only happen while in the loading or login screen to get into windows. Playing games or browsing works perfectly. I didn't find anything wrong with my RAM or nvme drives either. I just don't know why the drivers would cause the same bsod over two different GPUs..

zbook · Dec 16, 2023

That can happen with a malfunctioning motherboard.

If possible test the current GPU card in another computer to confirm that the new card is not malfunctioning.

Or if possible test a third GPU card.

floskan · Dec 16, 2023

zbook said:
That can happen with a malfunctioning motherboard.

If possible test the current GPU card in another computer to confirm that the new card is not malfunctioning.

Or if possible test a third GPU card.

I'm still within my return window so I can definitely try a third GPU. Is there no chance this could be a software issue from what I've shown so far?

zbook · Dec 16, 2023

To reduce the likelihood of a misbehaving drivers and increase the likelihood of malfunctioning hardware:
a) clean install the same driver version
b) clean install newer and older driver versions
c) clean install the operating system and install new drivers
d) clean install an alternative operating system and install new drivers
e) swap test a GPU card in the problematic computer
f) test the GPU card from the problematic computer in another computer
f) try an alternative motherboard port
etc.

floskan · Dec 16, 2023

zbook said:
To reduce the likelihood of a misbehaving drivers and increase the likelihood of malfunctioning hardware:
a) clean install the same driver version
b) clean install newer and older driver versions
c) clean install the operating system and install new drivers
d) clean install an alternative operating system and install new drivers
e) swap test a GPU card in the problematic computer
f) test the GPU card from the problematic computer in another computer
f) try an alternative motherboard port
etc.

I will try clean installing new drivers to begin with. I doubt i can get a new gpu before christmas to test..

floskan · Dec 20, 2023

zbook said:
To reduce the likelihood of a misbehaving drivers and increase the likelihood of malfunctioning hardware:
a) clean install the same driver version
b) clean install newer and older driver versions
c) clean install the operating system and install new drivers
d) clean install an alternative operating system and install new drivers
e) swap test a GPU card in the problematic computer
f) test the GPU card from the problematic computer in another computer
f) try an alternative motherboard port
etc.

Three days in with the latest 546.33 driver, and i was greeted by the log-in screen with a white line across the screen, looking like this:

https://imgur.com/a/bONpcJV

And when i tried logging in i got another bsod attached here. At the same time i got Nvlddmkm errors in my log with the descriptor "
The description for Event ID 0 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video3

Error occurred on GPUID: 100

The message resource is present but the message was not found in the message table"

Attaching logs too

floskan · Dec 20, 2023

Sorry, something went wrong with the first log, here's a new one

x BlueRobot · Dec 20, 2023

You mentioned in your initial post that the issue doesn't occur with a particular driver version, therefore it would seem logical that the issue lies with a particular driver version. I would just revert back to the version which wasn't causing a problem and then wait for the bug to be patched.

Here's a write up of what Stop 0x119 means etc: Debugging Stop 0x119 – VIDEO_SCHEDULER_INTERNAL_ERROR

x BlueRobot · Dec 20, 2023

Notes:

Rich (BB code):

9: kd> dc ffffa58a26b7fc20
ffffa58a`26b7fc20  36616956 00000000 00000000 00000000  Via6............
ffffa58a`26b7fc30  00000000 00000000 00000000 00000000  ................
ffffa58a`26b7fc40  00000000 00000000 00000000 00000000  ................
ffffa58a`26b7fc50  1cb3f8a0 ffffa58a 2c99f010 ffffa58a  ...........,....
ffffa58a`26b7fc60  2373b5b0 ffffa58a 00000009 00000000  ..s#............
ffffa58a`26b7fc70  00001659 00000000 00000001 00002421  Y...........!$..
ffffa58a`26b7fc80  00005737 00000000 00001fcc 00000000  7W..............
ffffa58a`26b7fc90  000000af 00000000 b2ee0000 fffff804  ................

Rich (BB code):

9: kd> !pooltag Via6
Pooltag Via6
Description: GPU scheduler DMA packet
Driver!Module: dxgmms2.sys

With a full kernel memory dump (%systemroot%\MEMORY.DMP), we may be able to run !pool against this address and get additional information about the DMA packet. I suspect that it is malformed in some way.

floskan · Dec 20, 2023

x BlueRobot said:

Notes:

Rich (BB code):

9: kd> dc ffffa58a26b7fc20
ffffa58a`26b7fc20  36616956 00000000 00000000 00000000  Via6............
ffffa58a`26b7fc30  00000000 00000000 00000000 00000000  ................
ffffa58a`26b7fc40  00000000 00000000 00000000 00000000  ................
ffffa58a`26b7fc50  1cb3f8a0 ffffa58a 2c99f010 ffffa58a  ...........,....
ffffa58a`26b7fc60  2373b5b0 ffffa58a 00000009 00000000  ..s#............
ffffa58a`26b7fc70  00001659 00000000 00000001 00002421  Y...........!$..
ffffa58a`26b7fc80  00005737 00000000 00001fcc 00000000  7W..............
ffffa58a`26b7fc90  000000af 00000000 b2ee0000 fffff804  ................

Rich (BB code):

9: kd> !pooltag Via6
Pooltag Via6
Description: GPU scheduler DMA packet
Driver!Module: dxgmms2.sys

With a full kernel memory dump (%systemroot%\MEMORY.DMP), we may be able to run !pool against this address and get additional information about the DMA packet. I suspect that it is malformed in some way.

Here's a link to the full memory dump : MEMORY.zip

floskan · Dec 20, 2023

x BlueRobot said:
You mentioned in your initial post that the issue doesn't occur with a particular driver version, therefore it would seem logical that the issue lies with a particular driver version. I would just revert back to the version which wasn't causing a problem and then wait for the bug to be patched.

Here's a write up of what Stop 0x119 means etc: Debugging Stop 0x119 – VIDEO_SCHEDULER_INTERNAL_ERROR

The only big difference between the older driver i'm using and the newer ones are "WDDM 3.0 feature 'Hardware Flip Queues' is supported in 545.xx and later drivers"

floskan · Dec 20, 2023

x BlueRobot said:

Notes:

Rich (BB code):

9: kd> dc ffffa58a26b7fc20
ffffa58a`26b7fc20  36616956 00000000 00000000 00000000  Via6............
ffffa58a`26b7fc30  00000000 00000000 00000000 00000000  ................
ffffa58a`26b7fc40  00000000 00000000 00000000 00000000  ................
ffffa58a`26b7fc50  1cb3f8a0 ffffa58a 2c99f010 ffffa58a  ...........,....
ffffa58a`26b7fc60  2373b5b0 ffffa58a 00000009 00000000  ..s#............
ffffa58a`26b7fc70  00001659 00000000 00000001 00002421  Y...........!$..
ffffa58a`26b7fc80  00005737 00000000 00001fcc 00000000  7W..............
ffffa58a`26b7fc90  000000af 00000000 b2ee0000 fffff804  ................

Rich (BB code):

9: kd> !pooltag Via6
Pooltag Via6
Description: GPU scheduler DMA packet
Driver!Module: dxgmms2.sys

With a full kernel memory dump (%systemroot%\MEMORY.DMP), we may be able to run !pool against this address and get additional information about the DMA packet. I suspect that it is malformed in some way.

I assumed i could figure out what DMA packets meant in this scenario but i couldn't find anything. Would them being malformed be a GPU issue or something else?

floskan · Dec 21, 2023

Can also mention i've had random monitor black screens, and it only happens for a second and goes back to working. No error logs or anything when that happens.

x BlueRobot · Dec 23, 2023

The change log is only going to mention new features which they've added, if a older version wasn't causing you any issues, then revert back to that version. You've already tried two different graphics cards and the issue still persisted, so I doubt that there is a hardware issue at fault here. You could boot into Safe Mode with Networking for a couple of days and see if the crashes persist, in order to fully determine if there is a hardware fault.