Tulpar T7 21.8 yayın yaparken mavi ekran hatası

Emily Kaldwin

Decapat
Katılım
22 Şubat 2019
Mesajlar
636
Makaleler
2
Çözümler
5
Yer
Karnaca
OBS üzerinden R6 yayını yapabilir miyim diye bir deneme yayını açtım 40-50 dakika 1080p 60FPS 6000 bitrate yayın verirken birden mavi ekran (W11 ile siyah ekran) hatası aldım ve bilgisayar normal bir şekilde kapanıp yeniden açıldı.

Yayında hiçbir şekilde bir kayıp olmadı gayet akıcı ve kaliteliydi sizce sorun ne olabilir?

"2K Ultra ayarlarda oynuyorum yayındayken ortalama 70-100FPS arası alıyorum drop yok sıcaklık bir laptop için normal seviyelerde 80'i geçmiyor neredeyse.
Monster Tulpar T7 21.8 (W11 / i7-11800h / 64 GB RAM / RTX 3070 8 GB)"




Bugün aynı hatayı tekrar aldım. OBS üzerinden yayın yaparken Twitch'de sadece 1080p 60FPS seçeneği gözüküyor daha düşük çözünürlük seçeneklerini nasıl verebilirim?
Bugün aynı hatayı tekrar aldım bu sefer yayında değildim fakat yine R6 oynuyordum minidump dosyasını bıraktım bu sorunu nasıl çözerim?

---
Konu yazım hatası doldu ve ne ben düzenleyebildim ne adminler kısa kesiyorum aşağıya minidump dosyalarının kodlarını bırakıyorum 3 defa mavi ekran aldım allah aşkına biri artık yardım etsin 2-3 haftalık cihazda mavi ekran nedir ya.

Mavi ekran 1 (2.12.21):
Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\ataka_3tjgmdv\Desktop\120221-18453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff800`62400000 PsLoadedModuleList = 0xfffff800`630296b0
Debug session time: Thu Dec  2 19:38:06.637 2021 (UTC + 3:00)
System Uptime: 1 days 20:29:31.172
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`62815590 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffae81`bab7ade0=0000000000000133
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff80063105330, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4061

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 7564

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

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

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

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  120221-18453-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80063105330

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffff880c7c2378c0 -- (.trap 0xffff880c7c2378c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000001990c626 rbx=0000000000000000 rcx=ffff880c7c237aa0
rdx=ffffe605cf6c9010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800627574dc rsp=ffff880c7c237a50 rbp=ffff880c7c237ac0
 r8=ffff880c8482edc0  r9=ffff880c8482edd0 r10=fffff80062964540
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeYieldProcessorEx+0x1c:
fffff800`627574dc 4883c420        add     rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  RainbowSix.exe

STACK_TEXT:
ffffae81`bab7add8 fffff800`626db5de     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffae81`bab7ade0 fffff800`626db061     : 0000958e`be838bd3 ffffae81`00000500 00000000`00000002 fffff800`626d6788 : nt!KeAccumulateTicks+0x39e
ffffae81`bab7ae50 fffff800`626d924a     : ffffae81`bab68200 ffff880c`7c2378c0 ffffae81`bab683d8 00000000`00000848 : nt!KiUpdateRunTime+0x61
ffffae81`bab7aeb0 fffff800`626d9036     : ffffe605`cf744240 ffffe605`cf7442f0 ffffae81`00000000 ffffae81`bab7afc0 : nt!KeClockInterruptNotify+0x11a
ffffae81`bab7af40 fffff800`6268d6a0     : 00000000`00000010 ffff0dc0`290e3539 ffff880c`8482edd0 fffff800`62816f3b : nt!HalpTimerClockIpiRoutine+0x16
ffffae81`bab7af70 fffff800`6281719a     : ffff880c`7c237940 ffffe605`cf744240 00009584`945aba97 ffffae81`bab66fe0 : nt!KiCallInterruptServiceRoutine+0xa0
ffffae81`bab7afb0 fffff800`62817767     : 00000000`00000013 ffffe605`e59f7880 ffff880c`7c237aa0 fffff800`62817774 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff880c`7c2378c0 fffff800`627574dc     : ffffffff`ffffffd2 fffff800`629645f5 00000000`00000010 00000000`00000a87 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff880c`7c237a50 fffff800`629645fa     : 00400a02`00000010 00009584`0247aeb3 ffffe605`cf9fc810 ffffe605`cfaf4040 : nt!KeYieldProcessorEx+0x1c
ffff880c`7c237a80 fffff800`626cb451     : ffff880c`7c237e70 ffffe605`cf6c9010 ffff880c`8482edc0 ffff880c`8482edd0 : nt!KiConfigureHeteroProcessorsTarget+0xba
ffff880c`7c237b00 fffff800`626ca452     : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00000004 : nt!KiExecuteAllDpcs+0x491
ffff880c`7c237d00 fffff800`6281d325     : 00000000`00000000 ffffae81`bab5f180 00000000`00000000 00000190`7fa8ef80 : nt!KiRetireDpcList+0x2a2
ffff880c`7c237fb0 fffff800`6281d100     : 00000000`00000000 0000018f`c7e60118 00000000`00000000 0000018f`00000000 : nt!KxRetireDpcList+0x5
ffff880c`8541f3b0 fffff800`6281c726     : ffffe605`f5dc9080 ffffe606`172bd160 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
ffff880c`8541f3e0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x326


SYMBOL_NAME:  nt!KeAccumulateTicks+39e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22000.318

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  39e

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {88dc98ce-f842-4daa-98d0-858621db6b0f}

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

---

Mavi ekran 2 (3.12.21):
Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\ataka_3tjgmdv\Desktop\120321-18281-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff803`5fa00000 PsLoadedModuleList = 0xfffff803`606296b0
Debug session time: Fri Dec  3 19:45:25.156 2021 (UTC + 3:00)
System Uptime: 1 days 0:06:09.531
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
...............................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`5fe15590 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffc880`150ac9f0=0000000000000133
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff80360705330, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1905

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 8400

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

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

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

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  120321-18281-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80360705330

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffffb83b683ee50 -- (.trap 0xfffffb83b683ee50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000001c49d152 rbx=0000000000000000 rcx=fffffb83b683f030
rdx=ffffb685731209e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8035fd574dc rsp=fffffb83b683efe0 rbp=fffffb83b683f050
 r8=fffffb83bf4bedc0  r9=fffffb83bf4bedd0 r10=fffff8035ff64540
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeYieldProcessorEx+0x1c:
fffff803`5fd574dc 4883c420        add     rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffc880`150ac9e8 fffff803`5fcdb5de     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffc880`150ac9f0 fffff803`5fcdb061     : 00005943`f3597b12 ffffc880`00000500 00000000`00000297 fffff803`5fd98255 : nt!KeAccumulateTicks+0x39e
ffffc880`150aca60 fffff803`5fcd8096     : 00000000`0054bc62 00000000`003281aa 000000ca`06abc83f 00000000`00000000 : nt!KiUpdateRunTime+0x61
ffffc880`150acac0 fffff803`5fcd93a2     : fffffb83`b683ee50 00000000`00000000 fffff803`6062b4e0 00000000`00000000 : nt!KiUpdateTime+0x686
ffffc880`150aceb0 fffff803`5fcd6cd2     : fffffb83`b683ee50 ffffb685`73134f50 ffffb685`00000000 00000000`00000002 : nt!KeClockInterruptNotify+0x272
ffffc880`150acf40 fffff803`5fc8d6a0     : 000000ca`080eca8a ffffb685`73134ea0 00000000`00000001 fffff803`5fe16f3b : nt!HalpTimerClockInterrupt+0xe2
ffffc880`150acf70 fffff803`5fe1719a     : fffffb83`b683eed0 ffffb685`73134ea0 00005943`f3030608 ffffc880`15047fe0 : nt!KiCallInterruptServiceRoutine+0xa0
ffffc880`150acfb0 fffff803`5fe17767     : ffffc880`15040180 fffff803`5fcdb260 fffffb83`b683f030 fffff803`5fe17774 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffb83`b683ee50 fffff803`5fd574dc     : 00000000`00000010 00000000`00000286 fffffb83`b683f000 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffb83`b683efe0 fffff803`5ff645fa     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx+0x1c
fffffb83`b683f010 fffff803`5fccb451     : fffffb83`b683f400 ffffb685`731209e0 fffffb83`bf4bedc0 fffffb83`bf4bedd0 : nt!KiConfigureHeteroProcessorsTarget+0xba
fffffb83`b683f090 fffff803`5fcca452     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x491
fffffb83`b683f290 fffff803`5fe194de     : 00000000`00000000 ffffc880`15040180 ffffc880`1504c440 ffffb685`bad92080 : nt!KiRetireDpcList+0x2a2
fffffb83`b683f540 00000000`00000000     : fffffb83`b6840000 fffffb83`b6839000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  nt!KeAccumulateTicks+39e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22000.318

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  39e

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {88dc98ce-f842-4daa-98d0-858621db6b0f}

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

---

Mavi ekran 3 (3.12.21):
Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\ataka_3tjgmdv\Desktop\120321-17937-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff807`51c00000 PsLoadedModuleList = 0xfffff807`528296b0
Debug session time: Fri Dec  3 21:33:45.674 2021 (UTC + 3:00)
System Uptime: 0 days 1:47:19.047
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`52015590 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffff9a01`3a37ade0=0000000000000133
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff80752905330, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1968

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 1958

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

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

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

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  120321-17937-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80752905330

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffffd10ab3e378c0 -- (.trap 0xffffd10ab3e378c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000001b3d6930 rbx=0000000000000000 rcx=ffffd10ab3e37aa0
rdx=ffff890d4cee4870 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80751f574dc rsp=ffffd10ab3e37a50 rbp=ffffd10ab3e37ac0
 r8=ffffd10ab9e86dc0  r9=ffffd10ab9e86dd0 r10=fffff80752164540
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KeYieldProcessorEx+0x1c:
fffff807`51f574dc 4883c420        add     rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  RainbowSix.exe

STACK_TEXT: 
ffff9a01`3a37add8 fffff807`51edb5de     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9a01`3a37ade0 fffff807`51edb061     : 00000d83`61275710 ffff9a01`00000500 00000000`00000002 fffff807`51ed6788 : nt!KeAccumulateTicks+0x39e
ffff9a01`3a37ae50 fffff807`51ed924a     : ffff9a01`3a368200 ffffd10a`b3e378c0 ffff9a01`3a3684f0 00000000`00000130 : nt!KiUpdateRunTime+0x61
ffff9a01`3a37aeb0 fffff807`51ed9036     : ffff890d`4cf44240 ffff890d`4cf442f0 ffff9a01`00000006 ffff9a01`3a37afc0 : nt!KeClockInterruptNotify+0x11a
ffff9a01`3a37af40 fffff807`51e8d6a0     : 00000000`00000010 ffffc0e7`2b0d4e32 ffffd10a`b9e86dd0 fffff807`52016f3b : nt!HalpTimerClockIpiRoutine+0x16
ffff9a01`3a37af70 fffff807`5201719a     : ffffd10a`b3e37940 ffff890d`4cf44240 00000d78`a726651c ffff9a01`3a366fe0 : nt!KiCallInterruptServiceRoutine+0xa0
ffff9a01`3a37afb0 fffff807`52017767     : ffffd10a`b3e37950 ffff890d`5ab33e50 00000000`80000000 fffff807`52017774 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffd10a`b3e378c0 fffff807`51f574dc     : 00000000`00000010 00000000`00000a87 ffffd10a`b3e37a78 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffd10a`b3e37a50 fffff807`521645fa     : 00400a02`00000010 00000d78`a50f6dfe ffff890d`4d2fe0f8 ffff890d`4d2f2640 : nt!KeYieldProcessorEx+0x1c
ffffd10a`b3e37a80 fffff807`51ecb451     : ffffd10a`b3e37e70 ffff890d`4cee4870 ffffd10a`b9e86dc0 ffffd10a`b9e86dd0 : nt!KiConfigureHeteroProcessorsTarget+0xba
ffffd10a`b3e37b00 fffff807`51eca452     : 00000000`00000000 00000000`00000001 00000000`0006414a 00000000`0000000f : nt!KiExecuteAllDpcs+0x491
ffffd10a`b3e37d00 fffff807`5201d325     : 00000000`00000000 ffff9a01`3a35f180 00000000`00000000 00000284`d61ada20 : nt!KiRetireDpcList+0x2a2
ffffd10a`b3e37fb0 fffff807`5201d100     : 00000000`00000360 00000284`eda15720 00000000`0d5c09df fffff807`5201c945 : nt!KxRetireDpcList+0x5
ffffd10a`b9cad3b0 fffff807`5201c726     : 00000000`0d5c09df 00000284`86fadbd0 00000000`00000000 ffff890d`00000000 : nt!KiDispatchInterruptContinue
ffffd10a`b9cad3e0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x326


SYMBOL_NAME:  nt!KeAccumulateTicks+39e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22000.318

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  39e

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {88dc98ce-f842-4daa-98d0-858621db6b0f}

Followup:     MachineOwner
---------
 
Son düzenleme:

Lindorie Miriel

Hectopat
Katılım
3 Ekim 2017
Mesajlar
627
Çözümler
15
Öncelikli olarak sizden SYS onarımı yapmanızı istiyorum. CMD'yi yönetici hakları ile açıp, aşağıdaki kodları sırası ile tek tek olacak şekilde en üstten başlayarak yazıp enterlayıp bitene kadar bekleyin ve diğerine geçip tüm süreci tamamlayın.

Konu rehberi : Rehber: Eksik ve bozuk SYS dosyalarını onarmak

SFC /scannow DISM /Online /Cleanup-Image /CheckHealth DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth

İkinci olarak, grafik sürücünüzü, DDU yazılımı ile temizlik yaptıktan sonra tekrar kurmanızda fayda var. Bunun için gerekli konular ve linkler:

DDU : DDU ile Sürücü Kaldırma Rehberi

Ekran kartı sürücüsü : https://tr.download.nvidia.com/Wind...book-win10-win11-64bit-international-whql.exe

Üçüncü olarak sorun olan modüllerden biri olan "BEDaisy.sys" tespit etmekteyim. Bu da BattleEye Anti-Cheat'e ait bir modül. Lütfen kaldırıp tekrar kurun.

Bunun için de resmi sitesinde sunulan kaldırma yöntemini paylaşıyorum:

I no longer want to have BattlEye on my system. How can I completely uninstall it?
Note that BE only installs into your system on Windows (as a system service), so you don’t need to uninstall it on any other OS. Also, BE is only ever active when you are playing a BE-protected game with BE enabled, any other time it will never run in any way. If you would still like to uninstall it, please go to the “BattlEye” folder in your game directory and check if there is a file called “Uninstall_BattlEye.bat”, which is present in many games. If it exists, simply run it to completely uninstall the BE Service. Otherwise or if you have already removed all game files from your system, you can start a command prompt as administator and simply enter “sc delete BEService” to do so. Note that some games automatically uninstall BE when they are being uninstalled as well.

Çevirisi :

Artık sistemimde BattlEye olmasını istemiyorum. Tamamen nasıl kaldırabilirim?
BE'nin sisteminize yalnızca Windows'ta (bir sistem hizmeti olarak) kurulduğunu, dolayısıyla başka bir işletim sisteminde kaldırmanız gerekmediğini unutmayın. Ayrıca BE, yalnızca BE etkinleştirilmiş BE korumalı bir oyun oynarken aktif olur, başka herhangi bir zamanda hiçbir şekilde çalışmayacaktır. Yine de kaldırmak istiyorsanız, lütfen oyun dizininizdeki “BattlEye” klasörüne gidin ve birçok oyunda bulunan “Uninstall_BattlEye.bat” adlı bir dosya olup olmadığını kontrol edin. Varsa, BE Hizmetini tamamen kaldırmak için çalıştırın. Aksi takdirde veya tüm oyun dosyalarını sisteminizden zaten kaldırmışsanız, yönetici olarak bir komut istemi başlatabilir ve bunu yapmak için "sc delete BEService" yazmanız yeterlidir. Bazı oyunların, kaldırılırken BE'yi otomatik olarak kaldırdığını unutmayın.

Umarım sorununuz çözülür.

Kod:
KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5749

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 19505

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

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

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

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  120221-18453-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80063105330

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffff880c7c2378c0 -- (.trap 0xffff880c7c2378c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000001990c626 rbx=0000000000000000 rcx=ffff880c7c237aa0
rdx=ffffe605cf6c9010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800627574dc rsp=ffff880c7c237a50 rbp=ffff880c7c237ac0
 r8=ffff880c8482edc0  r9=ffff880c8482edd0 r10=fffff80062964540
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeYieldProcessorEx+0x1c:
fffff800`627574dc 4883c420        add     rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  RainbowSix.exe

STACK_TEXT:
ffffae81`bab7add8 fffff800`626db5de     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffae81`bab7ade0 fffff800`626db061     : 0000958e`be838bd3 ffffae81`00000500 00000000`00000002 fffff800`626d6788 : nt!KeAccumulateTicks+0x39e
ffffae81`bab7ae50 fffff800`626d924a     : ffffae81`bab68200 ffff880c`7c2378c0 ffffae81`bab683d8 00000000`00000848 : nt!KiUpdateRunTime+0x61
ffffae81`bab7aeb0 fffff800`626d9036     : ffffe605`cf744240 ffffe605`cf7442f0 ffffae81`00000000 ffffae81`bab7afc0 : nt!KeClockInterruptNotify+0x11a
ffffae81`bab7af40 fffff800`6268d6a0     : 00000000`00000010 ffff0dc0`290e3539 ffff880c`8482edd0 fffff800`62816f3b : nt!HalpTimerClockIpiRoutine+0x16
ffffae81`bab7af70 fffff800`6281719a     : ffff880c`7c237940 ffffe605`cf744240 00009584`945aba97 ffffae81`bab66fe0 : nt!KiCallInterruptServiceRoutine+0xa0
ffffae81`bab7afb0 fffff800`62817767     : 00000000`00000013 ffffe605`e59f7880 ffff880c`7c237aa0 fffff800`62817774 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff880c`7c2378c0 fffff800`627574dc     : ffffffff`ffffffd2 fffff800`629645f5 00000000`00000010 00000000`00000a87 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff880c`7c237a50 fffff800`629645fa     : 00400a02`00000010 00009584`0247aeb3 ffffe605`cf9fc810 ffffe605`cfaf4040 : nt!KeYieldProcessorEx+0x1c
ffff880c`7c237a80 fffff800`626cb451     : ffff880c`7c237e70 ffffe605`cf6c9010 ffff880c`8482edc0 ffff880c`8482edd0 : nt!KiConfigureHeteroProcessorsTarget+0xba
ffff880c`7c237b00 fffff800`626ca452     : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00000004 : nt!KiExecuteAllDpcs+0x491
ffff880c`7c237d00 fffff800`6281d325     : 00000000`00000000 ffffae81`bab5f180 00000000`00000000 00000190`7fa8ef80 : nt!KiRetireDpcList+0x2a2
ffff880c`7c237fb0 fffff800`6281d100     : 00000000`00000000 0000018f`c7e60118 00000000`00000000 0000018f`00000000 : nt!KxRetireDpcList+0x5
ffff880c`8541f3b0 fffff800`6281c726     : ffffe605`f5dc9080 ffffe606`172bd160 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
ffff880c`8541f3e0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x326


SYMBOL_NAME:  nt!KeAccumulateTicks+39e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22000.318

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  39e

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {88dc98ce-f842-4daa-98d0-858621db6b0f}

Followup:     MachineOwner
 
KS
KS
Emily Kaldwin

Emily Kaldwin

Decapat
Katılım
22 Şubat 2019
Mesajlar
636
Makaleler
2
Çözümler
5
Yer
Karnaca
Bilgisayarı teknik servise bıraktım ve fotmat ile çözdüler o zamandan beri bir sorunum yok fakat OBS yüklemedim. Açıkçası yayın işini de denemek isterim ama OBS kaynaklı olmasından korkuyorum.
Bu mavi ekran olayının OBS ile alakası var mıdır?

R6 ve Rocket League oyunlarını yükledim ve uzun süredir oynuyorum bir sorunum yok şu anlık.
 
Son düzenleyen: Moderatör:
Yukarı