OBS, frequent GPU Encoder crashes,

P

PupekHere

New Member
Hey, lately I stumped at the problem with GPU encoding, frequent crashes during a stream, overloading without any reason etc.

I can't find the reason or any clue what is happening, also some of the crashes are accompanied by blue screen 41(63) and at this point, I'm pretty sure that it's related to OBS Encoding or GPU

my crashdump in attachment

I'm running RTX 3070 Ti, Ryzen 5 5600X and 16Gb of DDR4 ram 3200Mhz.
 

Attachments

Read of latest dump file, changing encoding to CPU solves problem of bluescreens and crashes BUT I would prefer nvenc encoding and would love to fix it.


Microsoft (R) Windows Debugger Version 10.0.22415.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\090421-6109-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`18c00000 PsLoadedModuleList = 0xfffff804`1982a190
Debug session time: Sat Sep 4 00:39:36.666 2021 (UTC + 2:00)
System Uptime: 0 days 7:44:32.309
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`18ff71d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffcd00`67296d30=000000000000000a
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8042ae1496a, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3983

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 46659

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

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

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

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


BUGCHECK_CODE: d1

BUGCHECK_P1: 8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8042ae1496a

READ_ADDRESS: fffff804198fa390: 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
0000000000000008

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: DOOMEternalx64vk.exe

TRAP_FRAME: ffffcd0067296e70 -- (.trap 0xffffcd0067296e70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffaa0ba8b1b130 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffaa0ba8b1b010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8042ae1496a rsp=ffffcd0067297000 rbp=ffffcd0067297001
r8=ffffcd0067297101 r9=ffffaa0baa6f6010 r10=0000000000000001
r11=ffffaa0ba1664000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
dxgmms2!VidSchiUnblockUnorderedWaitQueuePacket+0x36:
fffff804`2ae1496a 48394108 cmp qword ptr [rcx+8],rax ds:00000000`00000008=????????????????
Resetting default scope

STACK_TEXT:
ffffcd00`67296d28 fffff804`19009169 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffcd00`67296d30 fffff804`19005469 : 00000000`00000000 ffffaa0b`99010340 00000000`ffffffff 00000000`00000001 : nt!KiBugCheckDispatch+0x69
ffffcd00`67296e70 fffff804`2ae1496a : 00000000`400061c0 00000000`4b677844 00000000`00000160 00000000`00000799 : nt!KiPageFault+0x469
ffffcd00`67297000 fffff804`2ae3170f : ffffaa0b`b191e520 00000000`00000000 ffffaa0b`99010100 fffff804`18e89412 : dxgmms2!VidSchiUnblockUnorderedWaitQueuePacket+0x36
ffffcd00`67297030 fffff804`2ae213dd : ffffaa0b`b191e520 ffffcd00`672970c0 ffff988d`31e27de0 00000000`00000001 : dxgmms2!VidSchiUnblockUnorderedWaiter+0xa7
ffffcd00`67297060 fffff804`2ae81d33 : ffffaa0b`b191e520 00000000`00000000 00000000`0000012d 00000000`00000000 : dxgmms2!VidSchTimeoutSyncObject+0xc351
ffffcd00`672970d0 fffff804`29f1ec7d : ffffaa0b`a4931c00 ffffaa0b`a4931c00 00000000`40006280 ffff988d`31e27ed0 : dxgmms2!VidSchDestroySyncObject+0x203
ffffcd00`67297190 fffff804`29f1eb6d : ffffaa0b`9f642160 ffffcd00`67297240 ffff988d`31e27de0 ffff988d`31e27de0 : dxgkrnl!DXGSYNCOBJECT::Destroy+0x81
ffffcd00`672971d0 fffff804`29f226cc : ffffaa0b`a4931c00 ffff988d`18374820 ffffaa0b`a4931c00 ffff988d`18374820 : dxgkrnl!DXGGLOBAL::DestroySyncObject+0x285
ffffcd00`67297280 fffff804`29f21fc5 : ffff988d`31e27de0 ffff988d`3515d3a0 ffff988d`31e27de0 00000000`00000000 : dxgkrnl!DXGPROCESS::Destroy+0x328
ffffcd00`672974f0 fffff804`29e0b151 : 00000000`00000000 ffffaa0b`af94e520 00000000`00000000 fffff804`1d27a0b8 : dxgkrnl!DXGPROCESS::DestroyDxgProcess+0x105
ffffcd00`67297640 fffff804`1920244f : 00000000`00000000 ffffaa0b`9f523dc0 ffffaa0b`afdf4080 ffffaa0b`b0c23200 : dxgkrnl!DxgkProcessNotify+0x1a1
ffffcd00`67297690 fffff804`1921d264 : ffffaa0b`afdf4000 ffffaa0b`afdf4080 00000000`00000000 00000000`00000000 : nt!PspCallProcessNotifyRoutines+0x213
ffffcd00`67297760 fffff804`192b05c2 : ffffaa0b`b19044b8 00000000`00000000 ffffcd00`67297950 00000000`00000000 : nt!PspExitProcess+0x70
ffffcd00`67297790 fffff804`192f4e98 : 00000000`00000000 00000000`00000001 ffffcd00`672979a0 000000b4`b96a6000 : nt!PspExitThread+0x5b2
ffffcd00`67297890 fffff804`18e0f0d7 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff804`192b07cb : nt!KiSchedulerApcTerminate+0x38
ffffcd00`672978d0 fffff804`18ffb770 : 00000000`00000000 ffffcd00`67297980 ffffcd00`67297b40 000001c1`00000000 : nt!KiDeliverApc+0x487
ffffcd00`67297980 fffff804`19008c5f : ffffaa0b`b1904080 ffffaa0b`a7f97560 00000000`00000000 00000000`00000000 : nt!KiInitiateUserApc+0x70
ffffcd00`67297ac0 00007ff8`1e28cea4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
000000b4`d7fffde8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`1e28cea4


SYMBOL_NAME: dxgmms2!VidSchiUnblockUnorderedWaitQueuePacket+36

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.1165

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 36

FAILURE_BUCKET_ID: AV_dxgmms2!VidSchiUnblockUnorderedWaitQueuePacket

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {aea5b55d-c332-e911-4144-de2eeeb1273f}

Followup: MachineOwner
---------
 
This is LATEST, after that i switched to cpu encoding.

0: 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: 0000000000000010, The subtype of the BugCheck:
Arg2: ffffb68ba10dc000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3453

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 95359

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

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

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

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


BUGCHECK_CODE: 119

BUGCHECK_P1: 10

BUGCHECK_P2: ffffb68ba10dc000

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: NewWorld.exe

STACK_TEXT:
fffff803`2767d548 fffff803`32d23ad0 : 00000000`00000119 00000000`00000010 ffffb68b`a10dc000 00000000`00000000 : nt!KeBugCheckEx
fffff803`2767d550 fffff803`327fd5dd : ffffb68b`a1139000 ffffb68b`a10dc000 00000000`00000000 fffff803`327fdafa : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffff803`2767d590 fffff803`327ec3b1 : fffff803`00000000 00000000`00000001 ffffb68b`a10b3000 fffff803`35a80527 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x111ed
fffff803`2767d5f0 fffff803`3297d833 : ffffb68b`9e0f9030 ffffb68b`a3086b60 00000000`00000001 00000000`00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0xd1
fffff803`2767d640 fffff803`35ac8c3e : ffffb68b`9e0f9030 fffff803`2767d749 fffff803`2767d7d0 ffffb68b`9e202000 : dxgkrnl!DxgNotifyInterruptCB+0x93
fffff803`2767d670 ffffb68b`9e0f9030 : fffff803`2767d749 fffff803`2767d7d0 ffffb68b`9e202000 fffff803`35ac8bce : nvlddmkm+0x58c3e
fffff803`2767d678 fffff803`2767d749 : fffff803`2767d7d0 ffffb68b`9e202000 fffff803`35ac8bce ffffb68b`9e202000 : 0xffffb68b`9e0f9030
fffff803`2767d680 fffff803`2767d7d0 : ffffb68b`9e202000 fffff803`35ac8bce ffffb68b`9e202000 00000000`00000000 : 0xfffff803`2767d749
fffff803`2767d688 ffffb68b`9e202000 : fffff803`35ac8bce ffffb68b`9e202000 00000000`00000000 00000000`00000000 : 0xfffff803`2767d7d0
fffff803`2767d690 fffff803`35ac8bce : ffffb68b`9e202000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffb68b`9e202000
fffff803`2767d698 ffffb68b`9e202000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x58bce
fffff803`2767d6a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffb68b`9e0f9030 : 0xffffb68b`9e202000


SYMBOL_NAME: dxgmms2!VidSchDdiNotifyInterruptWorker+111ed

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.1288

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 111ed

FAILURE_BUCKET_ID: 0x119_10_UNKNOWN_dxgmms2!VidSchDdiNotifyInterruptWorker

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {0b9b4acb-5a00-5ef1-87f0-24a902851ee5}

Followup: MachineOwner
---------
 
Looks like a GPU failure, make sure it isn't overheating or overclocked and you have the latest BIOS on your motherboard.
 
R1CH said:
Looks like a GPU failure, make sure it isn't overheating or overclocked and you have the latest BIOS on your motherboard.
Click to expand...
temperatures are below 70 degrees, I updated Bios and I even underclocked my gpu

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8072a1cfa86, address which referenced memory

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3562

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 52867

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

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

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

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


BUGCHECK_CODE: d1

BUGCHECK_P1: 10

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8072a1cfa86

READ_ADDRESS: fffff807174fa390: 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
0000000000000010

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: obs64.exe

DPC_STACK_BASE: FFFFF8071C476FB0

TRAP_FRAME: fffff8071c4762d0 -- (.trap 0xfffff8071c4762d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffcd06bca04c80 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8072a1cfa86 rsp=fffff8071c476460 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=fffff80716abec40
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
dxgmms2!VidSchiUnwaitWaitQueuePacket+0x1044e:
fffff807`2a1cfa86 488b7110 mov rsi,qword ptr [rcx+10h] ds:00000000`00000010=????????????????
Resetting default scope

STACK_TEXT:
fffff807`1c476188 fffff807`16c09169 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff807`1c476190 fffff807`16c05469 : ffffcd06`bf1ae010 00000000`00000000 00000000`00000007 fffff807`1c476340 : nt!KiBugCheckDispatch+0x69
fffff807`1c4762d0 fffff807`2a1cfa86 : 00000000`00000103 00000000`00000000 4030aaaa`9f7b5aea 00000000`00000000 : nt!KiPageFault+0x469
fffff807`1c476460 fffff807`2a1cc8d6 : ffffcd06`c4e678e0 ffffcd06`b2ebe000 fffff807`1c476550 ffffcd06`c1e37340 : dxgmms2!VidSchiUnwaitWaitQueuePacket+0x1044e
fffff807`1c4764a0 fffff807`2a1b87c5 : 00000000`00000000 fffff807`1c4765f0 00000000`00000000 ffffcd06`c58f1010 : dxgmms2!VidSchiCompleteSignalSyncObject+0x11816
fffff807`1c4764f0 fffff807`2a1b823c : ffffcd06`b2ebe602 fffff807`00000000 ffffcd06`00000000 ffffcd06`00000000 : dxgmms2!VidSchiProcessCompletedQueuePacketInternal+0x1e5
fffff807`1c476690 fffff807`2a1b5265 : ffffcd06`b2f74b02 fffff807`16a86c4a ffffcd06`b2dcd001 00000001`00000000 : dxgmms2!VidSchiProcessDpcCompletedPacket+0x70c
fffff807`1c4767f0 fffff807`2680d561 : fffff807`1c4768e9 00000000`00000000 fffff807`1c476e70 000033e1`3482b0c2 : dxgmms2!VidSchDdiNotifyDpc+0x225
fffff807`1c4768a0 fffff807`2a698afb : ffffcd06`afeba030 00000000`00000000 ffffcd06`afeba030 ffffcd06`b1033000 : dxgkrnl!DxgNotifyDpcCB+0x91
fffff807`1c476950 ffffcd06`afeba030 : 00000000`00000000 ffffcd06`afeba030 ffffcd06`b1033000 fffff807`2a698a8e : nvlddmkm+0x58afb
fffff807`1c476958 00000000`00000000 : ffffcd06`afeba030 ffffcd06`b1033000 fffff807`2a698a8e ffffcd06`b1033000 : 0xffffcd06`afeba030


SYMBOL_NAME: dxgmms2!VidSchiUnwaitWaitQueuePacket+1044e

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.1288

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1044e

FAILURE_BUCKET_ID: AV_dxgmms2!VidSchiUnwaitWaitQueuePacket

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {8ff2a907-c2d2-904f-ea83-dd563e653e75}

Followup: MachineOwner
---------
 
Last edited:
You must log in or register to reply here.
Back
Top