F5F Stay Refreshed Software PC Gaming The computer restarted after a bugcheck. The identified issue was 0x00000119 with specific details provided.

The computer restarted after a bugcheck. The identified issue was 0x00000119 with specific details provided.

The computer restarted after a bugcheck. The identified issue was 0x00000119 with specific details provided.

Pages (3): Previous 1 2 3 Next
T
TheWolf123
Junior Member
17
01-08-2026, 05:42 AM
#11
No problem at all, just restarting again.
T
TheWolf123
01-08-2026, 05:42 AM #11

No problem at all, just restarting again.

N
Nastayy
Member
69
01-08-2026, 05:42 AM
#12
Use DDU to remove the graphics drivers and install the new ones.
N
Nastayy
01-08-2026, 05:42 AM #12

Use DDU to remove the graphics drivers and install the new ones.

O
Olly_is_Epic
Member
127
01-08-2026, 05:42 AM
#13
I managed that, but the graphics card remains slow and doesn't meet expectations.
O
Olly_is_Epic
01-08-2026, 05:42 AM #13

I managed that, but the graphics card remains slow and doesn't meet expectations.

K
Keira703
Junior Member
45
01-08-2026, 05:42 AM
#14
In Event Viewer I also see this message:
The description for Event ID 153 from source nvlddmkm isn't available. It seems the software that triggers this event isn't installed on your machine or the installation might be damaged. You can reinstall or fix the software locally.
If the event happened on a different device, the details had to be saved with it.
The following data was attached to the event:
\Device\Video3
Error occurred on GPUID: 100
The message resource exists but isn't found in the message table
K
Keira703
01-08-2026, 05:42 AM #14

In Event Viewer I also see this message:
The description for Event ID 153 from source nvlddmkm isn't available. It seems the software that triggers this event isn't installed on your machine or the installation might be damaged. You can reinstall or fix the software locally.
If the event happened on a different device, the details had to be saved with it.
The following data was attached to the event:
\Device\Video3
Error occurred on GPUID: 100
The message resource exists but isn't found in the message table

N
Notional
Junior Member
48
01-08-2026, 05:42 AM
#15
Nevertheless, the document mentioned is stored at "C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_34f9511bafd21ff9\nvlddmkm.sys" and its access rights are hidden, even though an admin account is used.
N
Notional
01-08-2026, 05:42 AM #15

Nevertheless, the document mentioned is stored at "C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_34f9511bafd21ff9\nvlddmkm.sys" and its access rights are hidden, even though an admin account is used.

G
gamb1no
Member
226
01-08-2026, 05:42 AM
#16
Via WhoCrashed:
System Information (local)
Computer name:
ROG-DESKTOP
Windows version:
Windows 11, 10.0, version 2009, build: 22631 (x64)
Windows dir:
C:\WINDOWS
Hardware:
ASUS, ASUSTeK COMPUTER INC., ROG STRIX Z790-H GAMING WIFI
CPU:
GenuineIntel 12th Gen Intel® Core™ i7-12700K 8664, level: 6
Processor count:
20 logical processors, active mask: 1048575
RAM:
65277.3MB
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Wed 8/7/2024 6:42:44 AM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\080724-12218-01.dmp (Minidump)
Bugcheck code:
0x119(0x2, 0xFFFFFFFFC000000D, 0xFFFFF88957E57860, 0xFFFFA68F50570FA0)
Bugcheck name:
VIDEO_SCHEDULER_INTERNAL_ERROR
Driver or module in which error occurred:
watchdog.sys
(
watchdog+0x5745
)
File path:
C:\WINDOWS\System32\drivers\watchdog.sys
Description:
Watchdog Driver
Product:
Microsoft® Windows® Operating System
Company:
Microsoft Corporation
Bug check description:
This indicates that the video scheduler has detected a fatal violation.
Analysis:
This is a video related crash.
On Wed 8/7/2024 6:42:44 AM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\MEMORY.DMP (Kernel memory dump)
Bugcheck code:
0x119(0x2, 0xFFFFFFFFC000000D, 0xFFFFF88957E57860, 0xFFFFA68F50570FA0)
Bugcheck name:
VIDEO_SCHEDULER_INTERNAL_ERROR
Driver or module in which error occurred:
dxgmms2.sys
(
dxgmms2+0x22DCB
)
File path:
C:\WINDOWS\System32\drivers\dxgmms2.sys
Description:
DirectX Graphics MMS
Product:
Microsoft® Windows® Operating System
Company:
Microsoft Corporation
Bug check description:
This indicates that the video scheduler has detected a fatal violation.
Analysis:
This is a video related crash. A DirectX driver was identified on the stack. Since there is no other responsible driver detected, it is suggested that you look for an updated driver for your graphics hardware. It's also possible that your graphics hardware was non-functional or overheated.
On Wed 8/7/2024 6:38:21 AM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\080724-8656-01.dmp (Minidump)
Bugcheck code:
0x113(0x19, 0x1, 0x10DE, 0x2704)
Bugcheck name:
VIDEO_DXGKRNL_FATAL_ERROR
Driver or module in which error occurred:
watchdog.sys
(
watchdog+0x5745
)
File path:
C:\WINDOWS\System32\drivers\watchdog.sys
Description:
Watchdog Driver
Product:
Microsoft® Windows® Operating System
Company:
Microsoft Corporation
Bug check description:
This indicates that the dxg kernel has detected a violation.
Analysis:
This is a video related crash.
On Tue 8/6/2024 4:44:45 PM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\080624-12640-01.dmp (Minidump)
Bugcheck code:
0x119(0x2, 0xFFFFFFFFC000000D, 0xFFFFEB88B85D7860, 0xFFFFA404DD31D320)
Bugcheck name:
VIDEO_SCHEDULER_INTERNAL_ERROR
Driver or module in which error occurred:
watchdog.sys
(
watchdog+0x5745
)
File path:
C:\WINDOWS\System32\drivers\watchdog.sys
Description:
Watchdog Driver
Product:
Microsoft® Windows® Operating System
Company:
Microsoft Corporation
Bug check description:
This indicates that the video scheduler has detected a fatal violation.
Analysis:
This is a video related crash.
On Tue 8/6/2024 4:43:19 PM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\080624-10843-01.dmp (Minidump)
Bugcheck code:
0x119(0x2, 0xFFFFFFFFC000000D, 0xFFFFA400A9217860, 0xFFFFC68138169940)
Bugcheck name:
VIDEO_SCHEDULER_INTERNAL_ERROR
Driver or module in which error occurred:
watchdog.sys
(
watchdog+0x5745
)
File path:
C:\WINDOWS\System32\drivers\watchdog.sys
Description:
Watchdog Driver
Product:
Microsoft® Windows® Operating System
Company:
Microsoft Corporation
Bug check description:
This indicates that the video scheduler has detected a fatal violation.
Analysis:
This is a video related crash.
On Tue 8/6/2024 4:42:32 PM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\080624-12875-01.dmp (Minidump)
Bugcheck code:
0x119(0x2, 0xFFFFFFFFC000000D, 0xFFFF92883074F860, 0xFFFFA085393CFCC0)
Bugcheck name:
VIDEO_SCHEDULER_INTERNAL_ERROR
Driver or module in which error occurred:
watchdog.sys
(
watchdog+0x5745
)
File path:
C:\WINDOWS\System32\drivers\watchdog.sys
Description:
Watchdog Driver
Product:
Microsoft® Windows® Operating System
Company:
Microsoft Corporation
Bug check description:
This indicates that the video scheduler has detected a fatal violation.
Analysis:
This is a video related crash.
G
gamb1no
01-08-2026, 05:42 AM #16

Via WhoCrashed:
System Information (local)
Computer name:
ROG-DESKTOP
Windows version:
Windows 11, 10.0, version 2009, build: 22631 (x64)
Windows dir:
C:\WINDOWS
Hardware:
ASUS, ASUSTeK COMPUTER INC., ROG STRIX Z790-H GAMING WIFI
CPU:
GenuineIntel 12th Gen Intel® Core™ i7-12700K 8664, level: 6
Processor count:
20 logical processors, active mask: 1048575
RAM:
65277.3MB
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Wed 8/7/2024 6:42:44 AM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\080724-12218-01.dmp (Minidump)
Bugcheck code:
0x119(0x2, 0xFFFFFFFFC000000D, 0xFFFFF88957E57860, 0xFFFFA68F50570FA0)
Bugcheck name:
VIDEO_SCHEDULER_INTERNAL_ERROR
Driver or module in which error occurred:
watchdog.sys
(
watchdog+0x5745
)
File path:
C:\WINDOWS\System32\drivers\watchdog.sys
Description:
Watchdog Driver
Product:
Microsoft® Windows® Operating System
Company:
Microsoft Corporation
Bug check description:
This indicates that the video scheduler has detected a fatal violation.
Analysis:
This is a video related crash.
On Wed 8/7/2024 6:42:44 AM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\MEMORY.DMP (Kernel memory dump)
Bugcheck code:
0x119(0x2, 0xFFFFFFFFC000000D, 0xFFFFF88957E57860, 0xFFFFA68F50570FA0)
Bugcheck name:
VIDEO_SCHEDULER_INTERNAL_ERROR
Driver or module in which error occurred:
dxgmms2.sys
(
dxgmms2+0x22DCB
)
File path:
C:\WINDOWS\System32\drivers\dxgmms2.sys
Description:
DirectX Graphics MMS
Product:
Microsoft® Windows® Operating System
Company:
Microsoft Corporation
Bug check description:
This indicates that the video scheduler has detected a fatal violation.
Analysis:
This is a video related crash. A DirectX driver was identified on the stack. Since there is no other responsible driver detected, it is suggested that you look for an updated driver for your graphics hardware. It's also possible that your graphics hardware was non-functional or overheated.
On Wed 8/7/2024 6:38:21 AM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\080724-8656-01.dmp (Minidump)
Bugcheck code:
0x113(0x19, 0x1, 0x10DE, 0x2704)
Bugcheck name:
VIDEO_DXGKRNL_FATAL_ERROR
Driver or module in which error occurred:
watchdog.sys
(
watchdog+0x5745
)
File path:
C:\WINDOWS\System32\drivers\watchdog.sys
Description:
Watchdog Driver
Product:
Microsoft® Windows® Operating System
Company:
Microsoft Corporation
Bug check description:
This indicates that the dxg kernel has detected a violation.
Analysis:
This is a video related crash.
On Tue 8/6/2024 4:44:45 PM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\080624-12640-01.dmp (Minidump)
Bugcheck code:
0x119(0x2, 0xFFFFFFFFC000000D, 0xFFFFEB88B85D7860, 0xFFFFA404DD31D320)
Bugcheck name:
VIDEO_SCHEDULER_INTERNAL_ERROR
Driver or module in which error occurred:
watchdog.sys
(
watchdog+0x5745
)
File path:
C:\WINDOWS\System32\drivers\watchdog.sys
Description:
Watchdog Driver
Product:
Microsoft® Windows® Operating System
Company:
Microsoft Corporation
Bug check description:
This indicates that the video scheduler has detected a fatal violation.
Analysis:
This is a video related crash.
On Tue 8/6/2024 4:43:19 PM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\080624-10843-01.dmp (Minidump)
Bugcheck code:
0x119(0x2, 0xFFFFFFFFC000000D, 0xFFFFA400A9217860, 0xFFFFC68138169940)
Bugcheck name:
VIDEO_SCHEDULER_INTERNAL_ERROR
Driver or module in which error occurred:
watchdog.sys
(
watchdog+0x5745
)
File path:
C:\WINDOWS\System32\drivers\watchdog.sys
Description:
Watchdog Driver
Product:
Microsoft® Windows® Operating System
Company:
Microsoft Corporation
Bug check description:
This indicates that the video scheduler has detected a fatal violation.
Analysis:
This is a video related crash.
On Tue 8/6/2024 4:42:32 PM your computer crashed or a problem was reported
Crash dump file:
C:\WINDOWS\Minidump\080624-12875-01.dmp (Minidump)
Bugcheck code:
0x119(0x2, 0xFFFFFFFFC000000D, 0xFFFF92883074F860, 0xFFFFA085393CFCC0)
Bugcheck name:
VIDEO_SCHEDULER_INTERNAL_ERROR
Driver or module in which error occurred:
watchdog.sys
(
watchdog+0x5745
)
File path:
C:\WINDOWS\System32\drivers\watchdog.sys
Description:
Watchdog Driver
Product:
Microsoft® Windows® Operating System
Company:
Microsoft Corporation
Bug check description:
This indicates that the video scheduler has detected a fatal violation.
Analysis:
This is a video related crash.

L
Lorddoom139
Posting Freak
956
01-08-2026, 05:42 AM
#17
I'm also curious about whether the PSU isn't delivering enough power, as some research indicates the GPU might be consuming up to 750W, leaving little room for other components.
L
Lorddoom139
01-08-2026, 05:42 AM #17

I'm also curious about whether the PSU isn't delivering enough power, as some research indicates the GPU might be consuming up to 750W, leaving little room for other components.

C
Crazyglo
Member
61
01-08-2026, 05:42 AM
#18
The GPU consumes only 500+ watts for a few milliseconds and that 1k watt PSU is clearly sufficient. If the PSU were the issue, you'd experience black screen shutdowns without BSOD errors. This happens because insufficient power would cause the entire PC to shut down before Windows could generate a BSOD report or error.
C
Crazyglo
01-08-2026, 05:42 AM #18

The GPU consumes only 500+ watts for a few milliseconds and that 1k watt PSU is clearly sufficient. If the PSU were the issue, you'd experience black screen shutdowns without BSOD errors. This happens because insufficient power would cause the entire PC to shut down before Windows could generate a BSOD report or error.

S
ShadowNiqht
Member
198
01-08-2026, 05:42 AM
#19
Research indicated a 750W requirement, though I'm not particularly technical. My expertise lies more in software, networking, development, etc. I replaced the graphics card and even installed my 2080, but it hasn't been used much since then. I suspect it might not be using a riser cable—it does have a connection that links power from three dongles to one input on the board. I'll need to check the BIOS settings at home once I'm there. Appreciate your ongoing efforts in resolving this issue.
S
ShadowNiqht
01-08-2026, 05:42 AM #19

Research indicated a 750W requirement, though I'm not particularly technical. My expertise lies more in software, networking, development, etc. I replaced the graphics card and even installed my 2080, but it hasn't been used much since then. I suspect it might not be using a riser cable—it does have a connection that links power from three dongles to one input on the board. I'll need to check the BIOS settings at home once I'm there. Appreciate your ongoing efforts in resolving this issue.

E
Estanga123
Junior Member
15
01-08-2026, 05:42 AM
#20
All systems are functioning well. I’m an IT specialist with about 17 years of experience as a hobbyist. People like me tend to assume the hardware is in good shape. The GPUs seem capable of drawing more power than their ratings suggest due to temporary power surges. These spikes typically last only a few milliseconds and generally don’t affect modern power supplies. There were cases where 3000 series Nvidia cards experienced amplified spikes, causing PSU OVP to trigger prematurely. This points to the graphics card being the likely culprit if you replace it with a known working model.

Riser cables can lead to various problems for several reasons. They connect the PCIe slot on the graphics card’s bottom to the motherboard’s slot, offering flexibility in orientation—vertical, parallel, or perpendicular. The cable type is standard for 4000 series cards, serving as an adapter to link three 8-pin PCIe cables to a single 12-pin HPWR connector. These adapters come with all 4000 series cards that use a 12-pin connector.

No worries, your time at work was well used!
E
Estanga123
01-08-2026, 05:42 AM #20

All systems are functioning well. I’m an IT specialist with about 17 years of experience as a hobbyist. People like me tend to assume the hardware is in good shape. The GPUs seem capable of drawing more power than their ratings suggest due to temporary power surges. These spikes typically last only a few milliseconds and generally don’t affect modern power supplies. There were cases where 3000 series Nvidia cards experienced amplified spikes, causing PSU OVP to trigger prematurely. This points to the graphics card being the likely culprit if you replace it with a known working model.

Riser cables can lead to various problems for several reasons. They connect the PCIe slot on the graphics card’s bottom to the motherboard’s slot, offering flexibility in orientation—vertical, parallel, or perpendicular. The cable type is standard for 4000 series cards, serving as an adapter to link three 8-pin PCIe cables to a single 12-pin HPWR connector. These adapters come with all 4000 series cards that use a 12-pin connector.

No worries, your time at work was well used!

Pages (3): Previous 1 2 3 Next