Question Microsoft Edge BSODs my PC

Mouldread

Distinguished
Apr 17, 2013
985
0
19,360
159
Hello guys,

I usually solve my problems on my own but I can't seem to find a solution to this one.

Every time I try watching a film on Netflix using Microsoft Edge I get BSOD and my PC restarts.
I have tried watching Netflix with Opera and Brave browsers and I never have problems with them. But the very moment I try Edge and my PC restarts.

None of my components is overclocked. I am using Windows 10 Home with latest updates.
I have tried clean installation of my GPU drivers using a drive sweeper. I have tried using CCleaner to remove all traces of cookies etc. Nothing helps. All my temps are normal, nothing is overheating etc... Plus it won't make any difference due to how specific my issue is.

Any ideas?

Hardware specs below:
CPU: i5 9600K
MoBo: Gigabyte Z390 Gaming X-CF
RAM: 16GB (2x8GB) Corsair Vengeance LPX DDR4
GPU: Palit GeForce RTX 2070 SUPER JetStream 8 GB
SDD: Samsung EVO 500GB, Crucial CT240BX200SSD1 BX200 240 GB
Monitor: AG352UCG - Agon 35" 3440x1440@100Hz


Here is a log from WhoCrashed

On Sat 24/07/2021 16:08:05 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072421-11062-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x3AD0)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFFD80568E0860, 0xFFFFD08FB6C329F0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
 

Colif

Win 10 Master
Moderator
I have tried clean installation of my GPU drivers using a drive sweeper. I
was that like doing this
did you try older gpu drivers?

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
 

Mouldread

Distinguished
Apr 17, 2013
985
0
19,360
159
was that like doing this
did you try older gpu drivers?

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
Hey,

yes, that's exactly how I did a clean install of the GPU drivers.
Trying an older version is of no help as I've gone through 3 nvidia driver versions and it doesn't change anything.

My minidump folder is empty, probably due to the fact I recently used CCleaner. I could try Netflix again and after the crash I can post the minidump.
 

Mouldread

Distinguished
Apr 17, 2013
985
0
19,360
159
don't run ccleaner until we figured out problem as it does remove dumps. Counter productive :)
Just tried Netflix and got BSOD restart.

Used WinDbg and got this. Not sure it helps.


5: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff801970c40e7, The address that the exception occurred at
Arg3: fffffe0deaaaf128, Exception Record Address
Arg4: fffffe0deaaae960, Context Record Address

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


KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullClassPtr

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 2592

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 38773

Key : Analysis.Init.CPU.mSec
Value: 1061

Key : Analysis.Init.Elapsed.mSec
Value: 124682

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


DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff801970c40e7

BUGCHECK_P3: fffffe0deaaaf128

BUGCHECK_P4: fffffe0deaaae960

EXCEPTION_RECORD: fffffe0deaaaf128 -- (.exr 0xfffffe0deaaaf128)
ExceptionAddress: fffff801970c40e7 (dxgmms2!VidSchMarkDeviceAsError+0x0000000000000017)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000020
Attempt to read from address 0000000000000020

CONTEXT: fffffe0deaaae960 -- (.cxr 0xfffffe0deaaae960)
rax=ffffa38dc5cba001 rbx=ffffb583f5f2ece0 rcx=0000000000000000
rdx=0000000000000018 rsi=ffffb583f5f2ee00 rdi=ffffa38dcd866dd0
rip=fffff801970c40e7 rsp=fffffe0deaaaf360 rbp=fffffe0deaaaf3c0
r8=0000000000000000 r9=0000000000000000 r10=fffff80195ea3760
r11=fffffe0deaaaf3c0 r12=ffffb583f5f2eeb8 r13=ffffb583f5f2ed68
r14=ffffb583f4a074b8 r15=ffffb583f4a074b8
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
dxgmms2!VidSchMarkDeviceAsError+0x17:
fffff801970c40e7 488b4120 mov rax,qword ptr [rcx+20h] ds:002b:0000000000000020=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

READ_ADDRESS: fffff8017cefa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000000020

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: 0000000000000020

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
fffffe0deaaaf360 fffff80197178b80 : ffffb583f5f2ece0 ffffb583f5f2ee00 ffffa38dcd866dd0 0000000000000001 : dxgmms2!VidSchMarkDeviceAsError+0x17
fffffe0deaaaf3d0 fffff8019717fc77 : ffffb5840323a870 ffffa38dcfec3738 0000000000000001 0000000000000001 : dxgmms2!VIDMM_SEGMENT::MoveOneResource+0x130
fffffe0deaaaf460 fffff8019717924e : ffffa38dcd866dd0 fffffe0deaaaf519 00000001f1a00000 0000000000000002 : dxgmms2!VIDMM_LINEAR_POOL::DirectedIterateAllocatedBlocksInRange+0x97
fffffe0deaaaf4b0 fffff8019714c27b : ffffb5840177bcf0 ffffb5840177bcf0 0000000000000000 ffffa38dcbb60f10 : dxgmms2!VIDMM_SEGMENT::processPendingMoves+0x17a
fffffe0deaaaf580 fffff80197116f61 : fffff801970f2c60 ffffa38dd004eb10 0000000000000004 00000000000000cb : dxgmms2!VIDMM_GLOBAL::pageInOneAllocation+0x2c2cb
fffffe0deaaaf6a0 fffff8019713c55e : 0000000000000002 0000000000989680 ffffb583e242e3d0 0000000000000001 : dxgmms2!VIDMM_GLOBAL::processDeferredCommand+0xd41
fffffe0deaaaf900 fffff80197146749 : ffffb583e242e300 ffffa38dcd817001 0000000000000000 0000000006636600 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xe5e
fffffe0deaaafae0 fffff8017c555875 : ffffa38dcd817080 fffff80197146740 ffffb583e242e300 000fa4efbd9bbfff : dxgmms2!VidMmWorkerThreadProc+0x9
fffffe0deaaafb10 fffff8017c5fe578 : fffff8017a186180 ffffa38dcd817080 fffff8017c555820 0000000000000001 : nt!PspSystemThreadStartup+0x55
fffffe0deaaafb60 0000000000000000 : fffffe0deaab0000 fffffe0deaaa9000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VidSchMarkDeviceAsError+17

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.1157

STACK_COMMAND: .cxr 0xfffffe0deaaae960 ; kb

BUCKET_ID_FUNC_OFFSET: 17

FAILURE_BUCKET_ID: AV_dxgmms2!VidSchMarkDeviceAsError

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b41efe5b-0297-61eb-4f6b-251cf97324c7}

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

Colif

Win 10 Master
Moderator
what PSU do you have?

What GPU drivers did you install? newest or older? Third choice is run Windows update and let windows find Nvidia drivers for card. it shouldn't be newest drivers since i have a 2070 Super and latest drivers.
That crash is obvious again, DirectX.

can you follow my instructions for uploading dumps as it might show us something more.

i wish it didn't add those smilies :)
 

punkncat

Dignified
Ambassador
I seriously doubt this is related to Edge, specifically.

Try Chrome or Chromium and see if it crashes. Edge is basically a Chrome clone now, so far as I understand so if the crash is related to it, it should follow on the other browsers, correct?

In regard to Netflix. IDK about browser base, but I noted at some point a bit over a year ago that while you have the App open that sound will not work on any browser window. For instance, watching Netflix in app, click to YouTube on Chrome, no sound.
I feel like this was an effort on their part to make it harder to 'pirate' via browsers/plug in/etc. I wonder if they are trying something similar in browser and it's tripping your system out?

/purespeculation
 

Colif

Win 10 Master
Moderator
Edge is victim, its what crashed. Its not like edge is an Amazon game, it doesn't kill GPU :)

I don't think windows could kill a PC. Applications can hurt parts but windows, but I digress.

Cause so far been GPU although it hadn't directly said it, but I don't know if I ever seen a BSOD that mentions DirectX and not be GPU drivers. Always a really tiny chance it can be sound... really tiny. But not here

dxgmms2!VidSchMarkDeviceAsError+ appears to me to be Video Scheduler Marked Device as Error... as thats what it says.
 

Mouldread

Distinguished
Apr 17, 2013
985
0
19,360
159
Thank you for the replies and suggestions everyone.

I very much doubt it has anything to do with hardware - reg. the question about my PSU (btw it's EVGA SuperNOVA 650 G2, 80+ GOLD 650W, Fully Modular) because I play very hardware demanding AAA titles for hours at a time) and I haven't had any issues whatsoever (no BSODs, no throttling, no drops in performance, no overheating etc.)
About GPU drivers I said I've been through at least 3 versions only due to the fact that I've had this Edge problem for so long that at least 3 (or maybe more) Nvidia drivers were released. And yes, I tried full clean installation as per the guide (DDU, Safe Mode etc.)

As I mentioned I am using Brave as my main browser which is chromium based I think and beforehand I was using Opera browser for 6 or 7 years and I haven't had any issues whatsoever. Even now (as I already mentioned) I can watch Netflix in both Brave and Opera for hours and hours with no issues. As soon as I try playing Netflix film in Edge - BSOD!

At this point I care about the Edge problem more as a "I'm curious why" than a real problem. I just want to figure out why only this browser out of hundreds of pieces of software I am using on a daily basis is causing my PC to restart.
 

Colif

Win 10 Master
Moderator
You should add PSU to sig then since its not mentioned now. Its main reason I asked.

All of the browsers mentioned are Chromium. Its likely some integration Edge has into windows that the others don't share. Its replaced IE so it likely has deep links.

https://answers.microsoft.com/en-us/windows/forum/all/bsod-on-netflix-in-edge/d4e1d78a-a9f9-452d-8108-ce9bef6b0b1f?auth=1 - no help here

 

ASK THE COMMUNITY