Valorant'ta ATTEMPTED_SWITCH_FROM_DPC mavi ekran hatası

İşletim sistemi
Windows 10

waxwhine

Kilopat
Katılım
17 Temmuz 2015
Mesajlar
39
Daha fazla  
Cinsiyet
Erkek
Oyun oynarken olmaya başladı, şimdi DDU yardımı ile ekran kartını tekrar güncelleyeceğim ama sorun RAM'lerde gibi bilgilendirirseniz sevinirim.
Windows 10 64 Bit
i5 8600K
16 GB RAM
MSI GTX 1070 Ti

1629960218119.png


Minidump
 
Son düzenleyen: Moderatör:
MSI'a ait yazılımları kaldırır mısınız? Özellikle de RGB yönetim yazılımını. Sonrasında sorunun çözülmesi gerek. Sorun çözülürse belirtirseniz sevinirim.

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: ffffa886ef244080, Original thread which is the cause of the failure
Arg2: ffffa886ebae4300, New thread
Arg3: 0000000000000000, Stack address of the original thread
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 10187

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 31395

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

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

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

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

BUGCHECK_P1: ffffa886ef244080

BUGCHECK_P2: ffffa886ebae4300

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD: ffffa886ef244080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VALORANT-Win64

BAD_STACK_POINTER: ffffbf8705a3f668

DPC_STACK_BASE: FFFFBF8705437FB0

STACK_TEXT:
ffffbf87`05436420 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x76


STACK_COMMAND: .thread 0xffffa886ef244080 ; kb

SYMBOL_NAME: nt!KiSwapContext+76

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1165

BUCKET_ID_FUNC_OFFSET: 76

FAILURE_BUCKET_ID: 0xB8_STACKPTR_ERROR_nt!KiSwapContext

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c644ae9c-f8ed-3b3d-6085-7ff73fa36130}

Followup: MachineOwner
---------[/CODE]
 
Vanguard mavi ekrana sebep olabiliyor. Ama siz Memtest86 ile test edin.
Test edeceğim.

MSI'a ait yazılımları kaldırır mısınız? Özellikle de RGB yönetim yazılımını. Sonrasında sorunun çözülmesi gerek. Sorun çözülürse belirtirseniz sevinirim.

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: ffffa886ef244080, Original thread which is the cause of the failure
Arg2: ffffa886ebae4300, New thread
Arg3: 0000000000000000, Stack address of the original thread
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 10187

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 31395

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

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

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

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

BUGCHECK_P1: ffffa886ef244080

BUGCHECK_P2: ffffa886ebae4300

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD: ffffa886ef244080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VALORANT-Win64

BAD_STACK_POINTER: ffffbf8705a3f668

DPC_STACK_BASE: FFFFBF8705437FB0

STACK_TEXT:
ffffbf87`05436420 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x76


STACK_COMMAND: .thread 0xffffa886ef244080 ; kb

SYMBOL_NAME: nt!KiSwapContext+76

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1165

BUCKET_ID_FUNC_OFFSET: 76

FAILURE_BUCKET_ID: 0xB8_STACKPTR_ERROR_nt!KiSwapContext

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c644ae9c-f8ed-3b3d-6085-7ff73fa36130}

Followup: MachineOwner
---------[/CODE]
MSI'a ait sadece MSI Afterburner mevcut onu da kaldırıp deneyeceğim hiç kullanmadığım halde.


Bu konuyu açtığımdan beri mavi ekran hatası almıyordum fakat bugün tekrardan valorant oynarken mavi ekran hatası aldım dosyayı tekrardan paylaşıyorum

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: ffffd809843e65c0, Original thread which is the cause of the failure
Arg2: ffffd80984168080, New thread
Arg3: 0000000000000000, Stack address of the original thread
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2061

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 4614

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

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

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


DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: b8

BUGCHECK_P1: ffffd809843e65c0

BUGCHECK_P2: ffffd80984168080

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD: ffffd809843e65c0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VALORANT-Win64

STACK_TEXT:
fffff105`76e47598 fffff806`1effe732 : 00000000`000000b8 ffffd809`843e65c0 ffffd809`84168080 00000000`00000000 : nt!KeBugCheckEx
fffff105`76e475a0 fffff806`1effdf46 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff105`76e476dc : nt!SwapContext+0x512
fffff105`76e475e0 fffff806`1ee0c970 : ffffaf81`3996d180 fffffff6`ffffffff ffffd809`77620040 fffff806`1ee9adc6 : nt!KiSwapContext+0x76
fffff105`76e47720 fffff806`1ee0be9f : 00000000`00000001 00000000`00000005 fffff105`76e478e0 00000000`00000000 : nt!KiSwapThread+0x500
fffff105`76e477d0 fffff806`1ee0b743 : 00501802`00000000 fffff806`00000000 ffffd809`86f89600 ffffd809`841681c0 : nt!KiCommitThreadWait+0x14f
fffff105`76e47870 fffff806`1f1f7571 : ffffd809`876bd860 00000000`00000006 000001de`c3d10f01 00000000`00501800 : nt!KeWaitForSingleObject+0x233
fffff105`76e47960 fffff806`1f1f761a : ffffd809`84168080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObWaitForSingleObject+0x91
fffff105`76e479c0 fffff806`1f0090ee : ffffd809`84168080 ffffd809`876c7de0 00000000`00000000 00000000`00000000 : nt!NtWaitForSingleObject+0x6a
fffff105`76e47a00 00007ffc`70bacdf4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x2b9
000000cd`9713f7f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`70bacdf4


STACK_COMMAND: .thread 0xffffd809843e65c0 ; kb

SYMBOL_NAME: nt!SwapContext+512

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1237

BUCKET_ID_FUNC_OFFSET: 512

FAILURE_BUCKET_ID: 0xB8_nt!SwapContext

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7aaf43d6-72cc-fa8c-17fb-e140c3359586}

Followup: MachineOwner
---------
[/CODE]
Minidump 19.09.2021

@Enes3078
 
Son düzenleme:
BIOS'unuz Beta BIOS, onu stabil sürümde kullanmanız daha mantıklı olacaktır. 1A sürümünden bahsediyorum stabil derken, bilginize.


Ayrıca sistemde kullandığınız diskler nelerdir? Disklerin Health sekmesini HD Tune 5.75 indirip paylaşın.
 
BIOS'unuz Beta BIOS, onu stabil sürümde kullanmanız daha mantıklı olacaktır. 1A sürümünden bahsediyorum stabil derken, bilginize.


Ayrıca sistemde kullandığınız diskler nelerdir? Disklerin Health sekmesini HD Tune 5.75 indirip paylaşın.
BIOS'u 1A sürümüne düşürdüm dediğiniz gibi, aşağıya da health sekmesini atıyorum. ssd.png hdd.png
 
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Technopat Haberler

Yeni konular

Geri
Yukarı