Çözüldü Attempted Switch from dpc mavi ekran hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
İşletim sistemi
Windows 10

Fraun

Hectopat
Katılım
2 Şubat 2020
Mesajlar
79
Merhaba, attempted Switch prom dpc mavi ekran hatası aldım. Sorun neyle ilgili olabilir? BIOS vs. güncel.
 
Çözüm
1) Öncelikle eski bir Windows sürümünü kullanıyorsunuz, lütfen Windows Update aracılığıyla 20H2 sürümüne geçiş yapın.

2) SteelSeries Engine kaldırın.

3) Ekran kartı sürücünüzü DDU ile kaldırıp güncel ve WHQL logolu bir sürücü indirin. DDU rehberi ve sürücüyü indireceğiniz website aşağıda yer alıyor.

Site: https://www.amd.com/en/support

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

[CODE title="Dökümler:"]
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Enes3078\Downloads\021521-11531-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 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff801`26a00000 PsLoadedModuleList = 0xfffff801`26e45e90
Debug session time: Mon Feb 15 13:28:01.559 2021 (UTC + 3:00)
System Uptime: 0 days 1:02:38.295
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`26bc3a90 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff801`2bdf8c20=00000000000000b8
0: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffd8092b9d2080, Original thread which is the cause of the failure
Arg2: fffff80126f8f400, New thread
Arg3: 0000000000000000, Stack address of the original thread
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4827

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-5QPUIS0

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 21496

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: b8

BUGCHECK_P1: ffffd8092b9d2080

BUGCHECK_P2: fffff80126f8f400

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD: ffffd8092b9d2080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: audiodg.exe

BAD_STACK_POINTER: fffff8012bdf8c18

DPC_STACK_BASE: FFFFF8012BDFFFB0

STACK_TEXT:
fffff801`2bdfe430 fffff801`26a5109d : fffff801`2350e180 fffff801`fffffffe fffff801`ffffffff 00000000`00000001 : nt!KiSwapContext+0x76
fffff801`2bdfe570 fffff801`26a4ff24 : ffffd809`2b9d2080 00000000`00000000 ffffd809`00000000 fffff801`00000000 : nt!KiSwapThread+0xbfd
fffff801`2bdfe610 fffff801`26a4f6c5 : 00000000`00000007 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x144
fffff801`2bdfe6b0 fffff801`2992d856 : fffff801`2bdfe7d0 fffff801`00000000 00000000`00000000 fffff801`389ab000 : nt!KeWaitForSingleObject+0x255
fffff801`2bdfe790 fffff801`2998e47c : 00000000`00000000 fffff801`00000000 ffffffff`fffe7960 00000000`00000000 : Wdf01000!FxIoTarget::SubmitSync+0x192 [minkernel\wdf\framework\shared\targets\general\fxiotarget.cpp @ 1839]
fffff801`2bdfe850 fffff801`38ab2e13 : ffffd809`26fd9240 00000000`00000000 ffffd809`2b685010 ffffd809`2f0a77f0 : Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+0x26c [minkernel\wdf\framework\shared\targets\usb\fxusbdeviceapi.cpp @ 1056]
fffff801`2bdfeb80 ffffd809`26fd9240 : 00000000`00000000 ffffd809`2b685010 ffffd809`2f0a77f0 fffff801`2bdfebd8 : sshid+0x2e13
fffff801`2bdfeb88 00000000`00000000 : ffffd809`2b685010 ffffd809`2f0a77f0 fffff801`2bdfebd8 fffff801`2bdfebc0 : 0xffffd809`26fd9240


STACK_COMMAND: .thread 0xffffd8092b9d2080 ; kb

SYMBOL_NAME: sshid+2e13

MODULE_NAME: sshid

IMAGE_NAME: sshid.sys

BUCKET_ID_FUNC_OFFSET: 2e13

FAILURE_BUCKET_ID: 0xB8_STACKPTR_ERROR_sshid!unknown_function

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {79b831c1-3dc2-4f0a-e438-f2579b777d83}

Followup: MachineOwner
---------[/CODE]
İşlemi uyguladım. Kontrol edebilir misiniz? İyi günler.
Evet işlem işe yaramış. Hatalı dosyaları bulmuş ve onarmış. Diğer dediklerimi de yaparsanız tüm sorunlarınızın ortadan kalkacağına inanıyorum.
 
Teşekkür ederim. Dediklerinizi uygulayıp çözülürse konuyu kilitleyeceğim.
 
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…