Unsolved

1 Rookie

 • 

39 Posts

1486

December 21st, 2020 01:00

17 R4, BSOD after windows 20H2 upgrade

I am getting BSOD after upgrading to Windows 10 20H2.
This happened before when upgrading to 1809 to 1909 windows 10.
After a few months a GPU driver update fixed the issue. So anyone know a workaround to the issue.
Here's my spec:
Alienware 17 R4 -
GTX 1080 factory OC,
G-sync 1440p display,
I7-7820Hk CPU,
32gb RAM,
330 watt PSU,
P.S: I also did a clean install of windows 10 already. It still didn't got rid of the issue.
And GPU passed the stress test in Pre boot environment. Since windows was causing the issue.

Here is the Bugcheck results :

For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`525f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9700`949c7790=0000000000000119
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffff9700949c7860
Arg4: ffffe004015e0cd0

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5765

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on AERONEX-R9

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 64581

Key : Analysis.Memory.CommitPeak.Mb
Value: 86

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffff9700949c7860

BUGCHECK_P4: ffffe004015e0cd0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff9700`949c7788 fffff804`69dc3ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff9700`949c7860 : nt!KeBugCheckEx
ffff9700`949c7790 fffff804`6d49bbe1 : 00000000`00000000 ffffe004`015de000 ffff9700`949c7899 ffffe004`015de000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff9700`949c77d0 fffff804`6d50351d : ffffe004`00000000 ffffe004`015e0cd0 ffffe004`014e6000 ffffe004`06f4ab20 : dxgmms2!VidSchiSendToExecutionQueue+0x127a1
ffff9700`949c7900 fffff804`6d50b2ea : ffffe004`06f4ab20 ffffe004`014e6000 00000000`00000000 ffffe004`0158e620 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffff9700`949c7a80 fffff804`6d50b15a : ffffe004`014e6400 fffff804`6d50b090 ffffe004`014e6000 ffffb600`0b240100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffff9700`949c7ad0 fffff804`52517e25 : ffffe004`014e9280 fffff804`00000001 ffffe004`014e6000 000fa4ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff9700`949c7b10 fffff804`525fcdd8 : ffffb600`0b240180 ffffe004`014e9280 fffff804`52517dd0 701b0097`574dc3f3 : nt!PspSystemThreadStartup+0x55
ffff9700`949c7b60 00000000`00000000 : ffff9700`949c8000 ffff9700`949c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+127a1

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.662

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 127a1

FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}

Followup: MachineOwner
---------
[here’s the progress so far but no solution ](https://www.nvidia.com/en-us/geforce/forums/geforce-graphics-cards/5/419231/span-classhighlightalienwarespan-17-r4-bsod-videos/)

2 Intern

 • 

387 Posts

December 21st, 2020 03:00

If you have other GPU drivers then dell, you can try to set them back.

Here is you drivers from dell:

NVIDIA Graphics Driver: https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=cp1wm&oscode=wt64a&productcode=alienware-17-laptop 

Intel HID Event Filter Driver: https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=33cdy&oscode=wt64a&productcode=alienware-17-laptop 

1 Rookie

 • 

39 Posts

December 21st, 2020 03:00

@ThomasAAT  Everything is up to date, bios, drivers you name it. I even tried the dell specific gpu driver on the support site. 
see the last link of my post for the solutions I have tried thus far.

link : https://www.nvidia.com/en-us/geforce/forums/geforce-graphics-cards/5/419231/span-classhighlightalienwarespan-17-r4-bsod-videos/

2 Intern

 • 

387 Posts

December 21st, 2020 03:00

Okay.

Some more options to try: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x119---video-scheduler-internal-error 

Run DDU  after booting Windows into Safe Mode  to completely remove any trace of the old GPU drivers. Use Clean and Restart. Then download fresh GPU drivers from the manufacturer's website.

If that does not help I would think it's a faulty GPU.

1 Rookie

 • 

39 Posts

December 21st, 2020 04:00

@ThomasAAT I did run DDU and the driver is doing a mathematical error. Did you even look at the link before posting !? Look at it. It will tell you what I did so far. And if its was gpu, then how come it got fixed before !?

1 Rookie

 • 

3 Posts

December 22nd, 2020 17:00

I'm experiencing the same issue as described above. Alienware 17 R2 here.

No Events found!

Top