Question The computer has rebooted from a bugcheck. The bugcheck was: 0x00000119 (0x0000000000000002, 0xffffffffc000000d, 0xffffd18f417df860, 0xffff890d94958c

[Randy53215]

Hello Tom's Hardware Community,

I have a friend who I'm trying to help out with his 'gaming rig', however he was having an issue where his machine will randomly reboot (this still happens). I'm looking to get to the bottom of this for him. I believe this is going to be a driver/GPU issue. He's currently got a Nvidia 4090.

The title is showing up under Event Viewer.

Here is what dumpstack.log is showing:

###############################################
DLOGFILE00010000DUMP
&
Dump stack initialized at UTC: 2024/08/06 20:22:36, local time: 2024/08/06 13:22:36.
#BugCheckCode 0x0000000000000119
#BugCheckP1 0x0000000000000002
#BugCheckP2 0xFFFFFFFFC000000D
#BugCheckP3 0xFFFFD18F417DF860
#BugCheckP4 0xFFFF890D94958CC0
Progress 0x00000042
Elapsed BugCheck duration 00001414ms
Starting get secondary dump callbacks size.
Progress 0x00000052
Finish get secondary dump callbacks size.
Dump Type: 6, Total Dump Size: 2226683537, Secondary Dump Size: 2621073.
Starting write of dump header.
Finish write of dump header.
Starting write of kernel bitmap dump header.
Finish write of bitmap dump header.
Starting write of memory dump data.
Elapsed BugCheck duration 00001464ms
Dumping physical memory to disk: 0%
Dumping physical memory to disk: 5%
Dumping physical memory to disk: 10%
Dumping physical memory to disk: 15%
Dumping physical memory to disk: 20%
Dumping physical memory to disk: 25%
Dumping physical memory to disk: 30%
Dumping physical memory to disk: 35%
Dumping physical memory to disk: 40%
Dumping physical memory to disk: 45%
Dumping physical memory to disk: 50%
Dumping physical memory to disk: 55%
Dumping physical memory to disk: 60%
Dumping physical memory to disk: 65%
Dumping physical memory to disk: 70%
Dumping physical memory to disk: 75%
Dumping physical memory to disk: 80%
Dumping physical memory to disk: 85%
Dumping physical memory to disk: 90%
Dumping physical memory to disk: 95%
Dumping physical memory to disk: 100%
Finish write of bitmap dump data. Total pages:542454 Pages written:542454
Progress 0x00000043
Elapsed BugCheck duration 00005231ms
Starting invoking secondary dump callbacks.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling CRASHDUMP secondary callback.
Return from CRASHDUMP secondary callback.
Writing CRASHDUMP secondary callback data.
Writing CRASHDUMP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling ibtdrv secondary callback.
Return from ibtdrv secondary callback.
Writing ibtdrv secondary callback data.
Writing ibtdrv secondary callback data done.
Calling Intel Wireless WiFi Link Adapter secondary callback.
Return from Intel Wireless WiFi Link Adapter secondary callback.
Writing Intel Wireless WiFi Link Adapter secondary callback data.
Writing Intel Wireless WiFi Link Adapter secondary callback data done.
Calling e2fnexpress secondary callback.
Return from e2fnexpress secondary callback.
Writing e2fnexpress secondary callback data.
Writing e2fnexpress secondary callback data done.
Calling wdiwifi secondary callback.
Return from wdiwifi secondary callback.
Writing wdiwifi secondary callback data.
Writing wdiwifi secondary callback data done.
Calling wdiwifi secondary callback.
Return from wdiwifi secondary callback.
Writing wdiwifi secondary callback data.
Writing wdiwifi secondary callback data done.
Calling nvlddmkm.sys secondary callback.
Return from nvlddmkm.sys secondary callback.
Writing nvlddmkm.sys secondary callback data.
Writing nvlddmkm.sys secondary callback data done.
Calling \Device\DxgKrnl secondary callback.
Return from \Device\DxgKrnl secondary callback.
Writing \Device\DxgKrnl secondary callback data.
Writing \Device\DxgKrnl secondary callback data done.
Calling PortDriverStandard secondary callback.
Return from PortDriverStandard secondary callback.
Writing PortDriverStandard secondary callback data.
Writing PortDriverStandard secondary callback data done.
Calling Wdf01000 secondary callback.
Return from Wdf01000 secondary callback.
Writing Wdf01000 secondary callback data.
Writing Wdf01000 secondary callback data done.
Calling blackbox - CI secondary callback.
Return from blackbox - CI secondary callback.
Writing blackbox - CI secondary callback data.
Writing blackbox - CI secondary callback data done.
Calling blackbox - Explorer logon tasks secondary callback.
Return from blackbox - Explorer logon tasks secondary callback.
Writing blackbox - Explorer logon tasks secondary callback data.
Writing blackbox - Explorer logon tasks secondary callback data done.
Calling blackbox - Winlogon secondary callback.
Return from blackbox - Winlogon secondary callback.
Writing blackbox - Winlogon secondary callback data.
Writing blackbox - Winlogon secondary callback data done.
Calling blackbox - NTFS secondary callback.
Return from blackbox - NTFS secondary callback.
Writing blackbox - NTFS secondary callback data.
Writing blackbox - NTFS secondary callback data done.
Calling blackbox - PNP secondary callback.
Return from blackbox - PNP secondary callback.
Writing blackbox - PNP secondary callback data.
Writing blackbox - PNP secondary callback data done.
Calling blackbox - BSD secondary callback.
Return from blackbox - BSD secondary callback.
Writing blackbox - BSD secondary callback data.
Writing blackbox - BSD secondary callback data done.
Calling secondary multi-part dump callbacks.
Starting TRIAGEDUMPDATA multi-part secondary callback.
Finish TRIAGEDUMPDATA multi-part secondary callback.
Starting SMBiosData multi-part secondary callback.
Finish SMBiosData multi-part secondary callback.
Starting SMBiosRegistry multi-part secondary callback.
Finish SMBiosRegistry multi-part secondary callback.
Starting SMBiosRegisters multi-part secondary callback.
Finish SMBiosRegisters multi-part secondary callback.
Starting SMBiosDataACPI multi-part secondary callback.
Finish SMBiosDataACPI multi-part secondary callback.
Starting PCI multi-part secondary callback.
Finish PCI multi-part secondary callback.
Starting Etw multi-part secondary callback.
Finish Etw multi-part secondary callback.
Finish calling secondary multi-part dump callbacks.
Progress 0x00000045
Finish invoking secondary dump callbacks.
Starting invoking dump complete callbacks.
Progress 0x00000046
Finish invoking dump complete callbacks.
Dump ended at UTC: 2024/08/06 20:22:36, local time: 2024/08/06 13:22:36.
Elapsed BugCheck duration 00005280ms
Dump completed successfully.
Progress 0x00000053

#############################################

Any help on this matter would be greatly appreciated, obviously feel free to ask any questions and I will do my best to provide answers.

Kind Regards,

Randy

 

[helper800]

Hello Tom's Hardware Community,

I have a friend who I'm trying to help out with his 'gaming rig', however he was having an issue where his machine will randomly reboot (this still happens). I'm looking to get to the bottom of this for him. I believe this is going to be a driver/GPU issue. He's currently got a Nvidia 4090.

The title is showing up under Event Viewer.

Here is what dumpstack.log is showing:

Spoiler: Error code

###############################################
DLOGFILE00010000DUMP
&
Dump stack initialized at UTC: 2024/08/06 20:22:36, local time: 2024/08/06 13:22:36.
#BugCheckCode 0x0000000000000119
#BugCheckP1 0x0000000000000002
#BugCheckP2 0xFFFFFFFFC000000D
#BugCheckP3 0xFFFFD18F417DF860
#BugCheckP4 0xFFFF890D94958CC0
Progress 0x00000042
Elapsed BugCheck duration 00001414ms
Starting get secondary dump callbacks size.
Progress 0x00000052
Finish get secondary dump callbacks size.
Dump Type: 6, Total Dump Size: 2226683537, Secondary Dump Size: 2621073.
Starting write of dump header.
Finish write of dump header.
Starting write of kernel bitmap dump header.
Finish write of bitmap dump header.
Starting write of memory dump data.
Elapsed BugCheck duration 00001464ms
Dumping physical memory to disk: 0%
Dumping physical memory to disk: 5%
Dumping physical memory to disk: 10%
Dumping physical memory to disk: 15%
Dumping physical memory to disk: 20%
Dumping physical memory to disk: 25%
Dumping physical memory to disk: 30%
Dumping physical memory to disk: 35%
Dumping physical memory to disk: 40%
Dumping physical memory to disk: 45%
Dumping physical memory to disk: 50%
Dumping physical memory to disk: 55%
Dumping physical memory to disk: 60%
Dumping physical memory to disk: 65%
Dumping physical memory to disk: 70%
Dumping physical memory to disk: 75%
Dumping physical memory to disk: 80%
Dumping physical memory to disk: 85%
Dumping physical memory to disk: 90%
Dumping physical memory to disk: 95%
Dumping physical memory to disk: 100%
Finish write of bitmap dump data. Total pages:542454 Pages written:542454
Progress 0x00000043
Elapsed BugCheck duration 00005231ms
Starting invoking secondary dump callbacks.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling CRASHDUMP secondary callback.
Return from CRASHDUMP secondary callback.
Writing CRASHDUMP secondary callback data.
Writing CRASHDUMP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling Win32kWPP secondary callback.
Return from Win32kWPP secondary callback.
Writing Win32kWPP secondary callback data.
Writing Win32kWPP secondary callback data done.
Calling ibtdrv secondary callback.
Return from ibtdrv secondary callback.
Writing ibtdrv secondary callback data.
Writing ibtdrv secondary callback data done.
Calling Intel Wireless WiFi Link Adapter secondary callback.
Return from Intel Wireless WiFi Link Adapter secondary callback.
Writing Intel Wireless WiFi Link Adapter secondary callback data.
Writing Intel Wireless WiFi Link Adapter secondary callback data done.
Calling e2fnexpress secondary callback.
Return from e2fnexpress secondary callback.
Writing e2fnexpress secondary callback data.
Writing e2fnexpress secondary callback data done.
Calling wdiwifi secondary callback.
Return from wdiwifi secondary callback.
Writing wdiwifi secondary callback data.
Writing wdiwifi secondary callback data done.
Calling wdiwifi secondary callback.
Return from wdiwifi secondary callback.
Writing wdiwifi secondary callback data.
Writing wdiwifi secondary callback data done.
Calling nvlddmkm.sys secondary callback.
Return from nvlddmkm.sys secondary callback.
Writing nvlddmkm.sys secondary callback data.
Writing nvlddmkm.sys secondary callback data done.
Calling \Device\DxgKrnl secondary callback.
Return from \Device\DxgKrnl secondary callback.
Writing \Device\DxgKrnl secondary callback data.
Writing \Device\DxgKrnl secondary callback data done.
Calling PortDriverStandard secondary callback.
Return from PortDriverStandard secondary callback.
Writing PortDriverStandard secondary callback data.
Writing PortDriverStandard secondary callback data done.
Calling Wdf01000 secondary callback.
Return from Wdf01000 secondary callback.
Writing Wdf01000 secondary callback data.
Writing Wdf01000 secondary callback data done.
Calling blackbox - CI secondary callback.
Return from blackbox - CI secondary callback.
Writing blackbox - CI secondary callback data.
Writing blackbox - CI secondary callback data done.
Calling blackbox - Explorer logon tasks secondary callback.
Return from blackbox - Explorer logon tasks secondary callback.
Writing blackbox - Explorer logon tasks secondary callback data.
Writing blackbox - Explorer logon tasks secondary callback data done.
Calling blackbox - Winlogon secondary callback.
Return from blackbox - Winlogon secondary callback.
Writing blackbox - Winlogon secondary callback data.
Writing blackbox - Winlogon secondary callback data done.
Calling blackbox - NTFS secondary callback.
Return from blackbox - NTFS secondary callback.
Writing blackbox - NTFS secondary callback data.
Writing blackbox - NTFS secondary callback data done.
Calling blackbox - PNP secondary callback.
Return from blackbox - PNP secondary callback.
Writing blackbox - PNP secondary callback data.
Writing blackbox - PNP secondary callback data done.
Calling blackbox - BSD secondary callback.
Return from blackbox - BSD secondary callback.
Writing blackbox - BSD secondary callback data.
Writing blackbox - BSD secondary callback data done.
Calling secondary multi-part dump callbacks.
Starting TRIAGEDUMPDATA multi-part secondary callback.
Finish TRIAGEDUMPDATA multi-part secondary callback.
Starting SMBiosData multi-part secondary callback.
Finish SMBiosData multi-part secondary callback.
Starting SMBiosRegistry multi-part secondary callback.
Finish SMBiosRegistry multi-part secondary callback.
Starting SMBiosRegisters multi-part secondary callback.
Finish SMBiosRegisters multi-part secondary callback.
Starting SMBiosDataACPI multi-part secondary callback.
Finish SMBiosDataACPI multi-part secondary callback.
Starting PCI multi-part secondary callback.
Finish PCI multi-part secondary callback.
Starting Etw multi-part secondary callback.
Finish Etw multi-part secondary callback.
Finish calling secondary multi-part dump callbacks.
Progress 0x00000045
Finish invoking secondary dump callbacks.
Starting invoking dump complete callbacks.
Progress 0x00000046
Finish invoking dump complete callbacks.
Dump ended at UTC: 2024/08/06 20:22:36, local time: 2024/08/06 13:22:36.
Elapsed BugCheck duration 00005280ms
Dump completed successfully.
Progress 0x00000053

#############################################

Any help on this matter would be greatly appreciated, obviously feel free to ask any questions and I will do my best to provide answers.

Kind Regards,

Randy

Please post the PC specs like below:

CPU:
CPU Cooler:
Motherboard:
RAM Kit:
Graphics Card:
Storage Devices:
PSU:
Case:
OS:

 

[Randy53215]

Please post the PC specs like below:

CPU: Intel Core i7-12700K
CPU Cooler: ROG liquid cooled with a screen that repeatedly shows ROG
Motherboard: ASUS ROG STRIX Z790-H GAMING WIFI (Chipset: Intel Z790 (Raptor Lake-S PCH))
RAM Kit: DDR5-6000 / PC5-48000 DDR5 SDRAM UDIMM
Graphics Card: ASUS ROG STRIX RTX 4080 GAMING
Storage Devices: Samsung SSD 980 Pro 1TB
PSU: ROG PSU.
Case: Case is a Open Concept Thermaltake
OS: Windows 11 Home

Also See below from a generated report.

https://pastebin.com/8uN4Xdqt

 

[helper800]

Also See below from a generated report.

https://pastebin.com/8uN4Xdqt

I can see their PC is atrociously out of date with regards to the BIOS version. He is on BIOS version 0816. Latest version is 2402.

 

[helper800]

It also shows that he has an ASUS ROG STRIX RTX 4080 GAMING and not a 4090.

 

[helper800]

Also See below from a generated report.

https://pastebin.com/8uN4Xdqt

Do you know the exact PSU model?

 

[Randy53215]

I can see their PC is atrociously out of date with regards to the BIOS version. He is on BIOS version 0816. Latest version is 2402.

Ok I flashed the new BIOS, and sorry I must've hit 9 when I meant to hit 8.

I'm working on getting you the model of the PSU.

 

[Randy53215]

Do you know the exact PSU model?

ROG Strix 1000W

 

[helper800]

ROG Strix 1000W

Which one of these is the exact model? All 3 are good units, but just for perspective.

 

[Randy53215]

Which one of these is the exact model? All 3 are good units, but just for perspective.

ROG-STRIX-1000G | Power Supply Units | ROG Global

The ROG Strix 1000W Gold PSU brings premium cooling performance to the mainstream with ROG Heatsinks and Axial-tech fan design. Low temps keep the ROG Strix incredibly quiet, even under full load.

rog.asus.com

 

[helper800]

ROG-STRIX-1000G | Power Supply Units | ROG Global

The ROG Strix 1000W Gold PSU brings premium cooling performance to the mainstream with ROG Heatsinks and Axial-tech fan design. Low temps keep the ROG Strix incredibly quiet, even under full load.

rog.asus.com

Did updating the BIOS help at all?

 

[Randy53215]

Nope, still randomly rebooting.

 

[helper800]

Nope, still randomly rebooting.

Try using DDU to get rid of the graphics drivers and install the new ones .

 

[Randy53215]

Try using DDU to get rid of the graphics drivers and install the new ones .

Ok I did that, however the graphics card being what it is still seems sluggish/not performing to spec.

 

[Randy53215]

In Event Viewer I'm also getting this:

The description for Event ID 153 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

 

[Randy53215]

However, the file that it's saying is located at "C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_34f9511bafd21ff9\nvlddmkm.sys"

and the permissions are grayed out, even while being an admin account.

However this site: https://www.minitool.com/news/the-d...153-from-source-nvlddmkm-cannot-be-found.html

suggests the file should be in the system32 folder.

 

[Randy53215]

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(R) Core(TM) 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.

 

[Randy53215]

I'm also wondering if the PSU is not providing sufficient power, doing some research says the GPU could be using up to 750W, that doesn't leave much buffer for everything else.

 

[helper800]

I'm also wondering if the PSU is not providing sufficient power, doing some research says the GPU could be using up to 750W, that doesn't leave much buffer for everything else.

The GPU only uses 500+ watts for a few miliseconds and that 1k watt PSU is definitely up to the task. If it were the PSU you would be getting black screen shutdowns with no BSOD errors. This is because if the PSU could not provide the power the entire PC shuts down with no time for windows to compile a BSOD report or error.

Have you tried reseating the Graphics Card? Is the Graphics card using a riser cable? In the BIOS is the PCIe slot set to PCIe 4.0 spec?

 

[Randy53215]

The GPU only uses 500+ watts for a few miliseconds and that 1k watt PSU is definitely up to the task. If it were the PSU you would be getting black screen shutdowns with no BSOD errors. This is because if the PSU could not provide the power the entire PC shuts down with no time for windows to compile a BSOD report or error.

Have you tried reseating the Graphics Card? Is the Graphics card using a riser cable? In the BIOS is the PCIe slot set to PCIe 4.0 spec?

Ok, doing research it said 750W, I'm certainly not a hardware guy. Don't get me wrong, I'm not 100% ignorant but I'm more software/networking/development/etc.

I did reseat the graphics card. I even installed my 2080 and it seemed to work fine, but I didn't use it for an extended time with it installed.

I don't believe it's using a riser cable, it does have a cable that connects the power from 3 dongles to a single input into the board. I will have to wait until I'm home to check the BIOS setting you've mentioned above.

Also, thanks for your continued effort in trying to resolve this.

 

[helper800]

Ok, doing research it said 750W, I'm certainly not a hardware guy. Don't get me wrong, I'm not 100% ignorant but I'm more software/networking/development/etc.

All good. I am just an IT professional that has been a hobbiest for about 17 years. You are the type guys that make everything work assuming the hardware is sound.

The reason why these GPUs can pull more wattage than they are rated for is because of a phenominon known as transient power spikes. These power requests usually only last for a few milliseconds at a time. This usually does not have any effect on modern design PSUs. There were instances when the 3000 series Nvidia GPUs came out when the transient spikes were greatly amplified, and falsely triggered Over Volt Protection (OVP) on PSUs designed prior to their release.

I did reseat the graphics card. I even installed my 2080 and it seemed to work fine, but I didn't use it for an extended time with it installed.

This greatly implicates the graphics card itself if you swapped in a known working card and then the issues disappeared. Your friend may have a faulty card.

I don't believe it's using a riser cable, it does have a cable that connects the power from 3 dongles to a single input into the board. I will have to wait until I'm home to check the BIOS setting you've mentioned above.

Also, thanks for your continued effort in trying to resolve this.

Riser cables can cause a lot of different types of issues for various reasons. Riser cables are connected to the PCIe slot on the bottom of the graphics card and then connects to the PCIe slot on the motherboard, and is a flexible or hard PCB cable meant to allow a user to mount their GPU vertically or parallel with the motherboard versus being perpendicular to it.

The cable that you are describing is normal for all 4000 series Nvidia cards to have. It is an adapter cable to allow three 8-pin PCIe power cables to one 12-pin HPWR. These come with all 4000 series cards that have a 12-pin connector.

No problem, thanks for filling my down time at work!

 

[Randy53215]

All good. I am just an IT professional that has been a hobbiest for about 17 years. You are the type guys that make everything work assuming the hardware is sound.

The reason why these GPUs can pull more wattage than they are rated for is because of a phenominon known as transient power spikes. These power requests usually only last for a few milliseconds at a time. This usually does not have any effect on modern design PSUs. There were instances when the 3000 series Nvidia GPUs came out when the transient spikes were greatly amplified, and falsely triggered Over Volt Protection (OVP) on PSUs designed prior to their release.


This greatly implicates the graphics card itself if you swapped in a known working card and then the issues disappeared. Your friend may have a faulty card.


Riser cables can cause a lot of different types of issues for various reasons. Riser cables are connected to the PCIe slot on the bottom of the graphics card and then connects to the PCIe slot on the motherboard, and is a flexible or hard PCB cable meant to allow a user to mount their GPU vertically or parallel with the motherboard versus being perpendicular to it.

The cable that you are describing is normal for all 4000 series Nvidia cards to have. It is an adapter cable to allow three 8-pin PCIe power cables to one 12-pin HPWR. These come with all 4000 series cards that have a 12-pin connector.

No problem, thanks for filling my down time at work!

Just wanted to let you know that ASUS is doing an RMA replacement and I have to send out the unit. I worked with NVIDIA and they had me reach out to ASUS for replacement. Thanks again for your help.

- Randy

 

[helper800]

Just wanted to let you know that ASUS is doing an RMA replacement and I have to send out the unit. I worked with NVIDIA and they had me reach out to ASUS for replacement. Thanks again for your help.

- Randy

Post back if you have any issues with the RMAed card.

 

[Randy53215]

Post back if you have any issues with the RMAed card.

Fairly certain they sent back the same card, as they documented that everything passes their tests. I will note that after looking into this further, there is a riser connection for the graphics card for vertical mount.

Is that something that you would suspect could be the problem? I'm lost as to what it could be for now.

Kind Regards,

Randy

 

[helper800]

Fairly certain they sent back the same card, as they documented that everything passes their tests. I will note that after looking into this further, there is a riser connection for the graphics card for vertical mount.

Is that something that you would suspect could be the problem? I'm lost as to what it could be for now.

Kind Regards,

Randy

Yes, riser cables can plague you with issues unless they are very high quality. Its best to eliminate them as a test.