Bluescreen when opening Netflix SYSTEM_THREAD_EXCEPTION_NOT_HANDLED - win10 1909

Yes its slow going, I am still going through Rob's todo list.  (also, work takes up a LOT of my time right now)

Causing it to happen is not easy.  After reboot its fine for X amount of time.

Use PC a while, no idea what makes it in a state to BS. 

Then netflix <> boom.  Happened again last night.

Tried to get through to Netflix but couldnt, will retry

So far just had 1 win update and Chipset drivers update.

Have a BIOS update to do next - just.. scares me doing that :>

@dzseti / aoshi1

What win version, graphics card? latest graphics drivers?

Thanks. Exactly what I experience: after restart (not cold start) there is no problem

Please let us know, if Netflix ever comes back

Has anyone contacted Netflix to let them know this ONLY happens with their

windows app, which means it's something wrong with them?  If so, what did

they say?

I am having the same problem. NVIDIA say that it is not their driver and that Netflix is conflicting with a file.

My memory dump:

8: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8056a830300, The address that the exception occurred at
Arg3: ffffee86b55674d8, Exception Record Address
Arg4: ffffee86b5566d20, Context Record Address

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

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on ASUS-DESKTOP

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 14

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

    Key  : Analysis.System
    Value: CreateObject

ADDITIONAL_XML: 1

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8056a830300

BUGCHECK_P3: ffffee86b55674d8

BUGCHECK_P4: ffffee86b5566d20

EXCEPTION_RECORD:  ffffee86b55674d8 -- (.exr 0xffffee86b55674d8)
ExceptionAddress: fffff8056a830300 (dxgmms2!VIDMM_SEGMENT::IsMovableResourceCB)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000001f8
Attempt to read from address 00000000000001f8

CONTEXT:  ffffee86b5566d20 -- (.cxr 0xffffee86b5566d20)
rax=fffff8056a830300 rbx=000000003b9e0000 rcx=0000000000000000
rdx=0000000000000000 rsi=ffffa700d81a3bc0 rdi=ffffee86b55677e0
rip=fffff8056a830300 rsp=ffffee86b5567718 rbp=000000004efa0000
 r8=0000000176700000  r9=0000000000000002 r10=ffff9706afe46718
r11=ffff9706b48fb010 r12=0000000000000000 r13=ffff9706afe466d0
r14=ffffa700d4391d78 r15=ffffa700d81a3be8
iopl=0         nv up ei ng nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050297
dxgmms2!VIDMM_SEGMENT::IsMovableResourceCB:
fffff805`6a830300 488b81f8010000  mov     rax,qword ptr [rcx+1F8h] ds:002b:00000000`000001f8=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

READ_ADDRESS:  00000000000001f8 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000000001f8

EXCEPTION_STR:  0xc0000005

STACK_TEXT:  
ffffee86`b5567718 fffff805`6a83830d : 00000000`00000000 00000000`00000000 00000000`00000120 fffff805`53512399 : dxgmms2!VIDMM_SEGMENT::IsMovableResourceCB
ffffee86`b5567720 fffff805`6a82dc09 : ffff9706`a9febd90 ffffa700`d8a70e01 ffffa700`00000002 00000000`00000000 : dxgmms2!VIDMM_LINEAR_POOL::DefragmentRange+0xf5
ffffee86`b5567790 fffff805`6a81b440 : 00000000`00000000 ffffee86`b55679e0 00000001`76700000 ffff9706`a9febd90 : dxgmms2!VIDMM_MEMORY_SEGMENT::Defragment+0xa9
ffffee86`b5567890 fffff805`6a7f88b0 : 00000000`004c0a56 ffffee86`b55679e0 ffff9706`a9febd90 000000b5`4b5c8e3c : dxgmms2!VIDMM_GLOBAL::Defragment+0x148
ffffee86`b55678e0 fffff805`6a7f6ee9 : ffffa700`d2917510 ffffdd00`3d48a301 ffff9706`a9d65500 00000000`00000001 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x19b0
ffffee86`b5567ae0 fffff805`5346bcd5 : ffff9706`a9d65540 fffff805`6a7f6ee0 ffffa700`d2917510 000024ef`bd9bbfff : dxgmms2!VidMmWorkerThreadProc+0x9
ffffee86`b5567b10 fffff805`535c9968 : ffffdd00`3d479180 ffff9706`a9d65540 fffff805`5346bc80 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffee86`b5567b60 00000000`00000000 : ffffee86`b5568000 ffffee86`b5561000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME:  dxgmms2!VIDMM_SEGMENT::IsMovableResourceCB+0

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.18362.752

STACK_COMMAND:  .cxr 0xffffee86b5566d20 ; kb

BUCKET_ID_FUNC_OFFSET:  0

FAILURE_BUCKET_ID:  AV_dxgmms2!VIDMM_SEGMENT::IsMovableResourceCB

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {4754091f-2450-7674-f036-f7f884cb0024}

Followup:     MachineOwner
---------