Bluescreen when opening Netflix SYSTEM_THREAD_EXCEPTION_NOT_HANDLED - win10 1909

Anonymous
2020-04-06T20:18:46+00:00

Hi,

I can run stuff all day (AWS/Vbox/Games), but as soon as I open netflix, machine blue screens with stop code : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

in dxgmms2.sys

its the netflix windows app - I think when I press play it happens, probably happened 6-7 times now.  Quite consistent.

After a reboot, its fine.  I have not been able to cause a bluescreen doing other things.

Winver : 1909 18363.720

GTX 1070ti

I9-9900

Can anyone help?

MEMORY.DMP and msinfo32 here: (i hope)

https://1drv.ms/u/s!AojoZMyTZ1lwgZFZ52vZhGF\_uqKL6w?e=EmJ87X

Im not used to windbg with crashes, snippets from a minidump

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

READ_ADDRESS: fffff806601733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8066002a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff8066002a3c8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 00000000000001f8 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.2: kd> k
 # Child-SP          RetAddr           Call Site
00 ffffb10e`39fd64b8 fffff806`5fddb416 nt!KeBugCheckEx
01 ffffb10e`39fd64c0 fffff806`5fd9d369 nt!PspSystemThreadStartup$filt$0+0x44
02 ffffb10e`39fd6500 fffff806`5fdcb1af nt!_C_specific_handler+0xa9
03 ffffb10e`39fd6570 fffff806`5fcfa2d5 nt!RtlpExecuteHandlerForException+0xf
04 ffffb10e`39fd65a0 fffff806`5fcfe86e nt!RtlDispatchException+0x4a5
05 ffffb10e`39fd6cf0 fffff806`5fdd431d nt!KiDispatchException+0x16e
06 ffffb10e`39fd73a0 fffff806`5fdd0505 nt!KiExceptionDispatch+0x11d
07 ffffb10e`39fd7580 fffff806`7a700300 nt!KiPageFault+0x445
08 ffffb10e`39fd7718 fffff806`7a70830d dxgmms2!VIDMM_SEGMENT::IsMovableResourceCB
09 ffffb10e`39fd7720 fffff806`7a6fdc09 dxgmms2!VIDMM_LINEAR_POOL::DefragmentRange+0xf5
0a ffffb10e`39fd7790 fffff806`7a6eb440 dxgmms2!VIDMM_MEMORY_SEGMENT::Defragment+0xa9
0b ffffb10e`39fd7890 fffff806`7a6c88b0 dxgmms2!VIDMM_GLOBAL::Defragment+0x148
0c ffffb10e`39fd78e0 fffff806`7a6c6ee9 dxgmms2!VIDMM_WORKER_THREAD::Run+0x19b0
0d ffffb10e`39fd7ae0 fffff806`5fc6bce5 dxgmms2!VidMmWorkerThreadProc+0x9
0e ffffb10e`39fd7b10 fffff806`5fdc99ca nt!PspSystemThreadStartup+0x55
0f ffffb10e`39fd7b60 00000000`00000000 nt!KiStartSystemThread+0x2aI am even more lost in this new windbg :>
Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2020-05-09T21:58:49+00:00

Hi,

Like so many people I experienced the Blue Screen with the Netflix App. Everything else was running fine.

I noticed it was only happening after a cold boot of the PC.

If I immediately restarted the PC the Netflix App would run fine.

Recently I solved an other problem with my PC where on cold boot it would sometimes not fully turn on ( the screen would remain dark). 

This was solved by changing a setting in the Windows control panel:

under Power Options/ System settings

disable "turn on fast startup".

Since I disabled this I also did not get the Blue Screen in the Netflix App anymore.

Worth a try perhaps.

Hardware 

CPU AMD Ryzen 9 3950X

GPU NVIDIA GeForce GTX 1080 Ti

Was this answer helpful?

10+ people found this answer helpful.
0 comments

52 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-04-08T15:30:03+00:00

    Did you use ALL of the other methods I posted? Those are a check list and not a menu.

    Even though the Nvidia drivers were definitely implicated there can be other factors in play. So you need to use an "All Inclusive" approach. Often, using such methods, you will fix the issue without really knowing the cause because there were two or more factors in play.

    Please do keep me in the loop and I will help all that I can.

    Rob

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-04-08T14:55:51+00:00

    Spoke to Nvidia, still waiting.

    Will let you know if I ever get it fixed :>  might be a while though.

    Thanks Rob :)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-04-08T14:38:42+00:00

    HI,

    Were you able to resolve the issue? Did you contact Nvidia Support and that of the other device makers?

    Please provide feedback as you can which really does help me help you and others.

    Here to help,

    Rob

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-04-06T22:34:36+00:00

    Did you run memtest 4+ hours (over-night is best).

    Try reducing the memory down to the minimum or original and see what happens.

    The only driver it pointed to was the Nvidia driver though the issue could be the GPU, memory, or other hardware. Be sure to contact Nvidia Support and Forums.

    Please run DriverView exactly as I indicated which may help identify drivers that can be updated at the actual device maker's site.

    Another thing I would do is to remove ALL power then re-seat the cards, memory, and cables (on both ends when possible) - actually remove and replace - do not just snug.

    Parts and connections get loosened and can cause these strange issues.

    Here to help,

    Rob

    Was this answer helpful?

    0 comments