Çözüldü Windows 10 Pro sistem mavi ekran hatası

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

ALİ DEMİRCİ23

Femtopat
Katılım
19 Kasım 2022
Mesajlar
4
Daha fazla  
Cinsiyet
Erkek
RAM
8gb ddr4 3200mhz
SSD veya HDD modeli
ssd 256gb
Ekran kartı
irıs xe
Anakart
hp ama modelini bilmiyorum
İşlemci
i5 1135g7 2.4ghz 4core 8 thread
Windows 10 Pro 22H2 kullanıyorum, işlemcim i51135G7 2.4GHz 4 çekirdek 8 thread, ekran kartım Intel irıs Xe, ekran 60Hertz, 8 GB DDR4 RAM var, bugün arkadaşlarımla konuşurken bilgisayarı boşta bıraktım ve 10-20dakikalığına gittikden sonra geldiğimde bilgisayardan ses gelmiyordu ve kısa sürede mavi ekran verdi ancak ben bu mavi ekran koduna bakamadım. Bilgisayarım ilk kez mavi ekran veriyor, endişeliyim dump dosyasını okuyamadığım için sizden yardım istiyorum, bilgisayarımın neden mavi ekran verdiğini öğrenmek istiyorum. Son zamanlarda performans düşüşüde yaşıyorum, yardımcı olursanız sevinirim.Ayrıca açık mavi renkte bir mavi ekrandı.
Minidumpdosyası;
 
Son düzenleme:
Çözüm
Sorunu Intel SST sürücüsü çıkarıyor.

BIOS ve diğer tüm sürücüleri buradan güncelleyin.


Örneğin; Realtek Ethernet sürücüsünü eski kalmış bayağı.

Intel ile alakalı tüm sürücüler için;


Kod:
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffffba0606a9ade0, Physical Device Object of the stack
Arg3: ffff978fef067ba0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffba0604b285a0, The blocked IRP

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

Implicit thread is now ffffba05`e5b18240
*** WARNING: Unable to verify timestamp for IntcUSB.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2967

    Key  : Analysis.Elapsed.mSec
    Value: 8935

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x9f

    Key  : Failure.Bucket
    Value: 0x9F_3_IntcUSB!unknown_function

    Key  : Failure.Hash
    Value: {3a940f2c-6166-2b30-7924-191a072ab027}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffba0606a9ade0

BUGCHECK_P3: ffff978fef067ba0

BUGCHECK_P4: ffffba0604b285a0

FILE_IN_CAB:  062123-7500-01.dmp

DRVPOWERSTATE_SUBCODE:  3

FAULTING_THREAD:  ffffba05e5b18240

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

DPC_STACK_BASE:  FFFF978FEF067FB0

STACK_TEXT: 
ffff978f`ef01e090 fffff803`2281c9c0     : 00000000`00000009 00000000`ffffffff 00000000`00000000 ffffba06`163bc158 : nt!KiSwapContext+0x76
ffff978f`ef01e1d0 fffff803`2281beef     : 00000001`000180bb 00000000`00000000 ffff978f`ef01e390 ffff978f`ef01e600 : nt!KiSwapThread+0x500
ffff978f`ef01e280 fffff803`2281b793     : 00000000`00000000 00000000`00000000 ffffba06`18de0200 ffffba05`e5b18380 : nt!KiCommitThreadWait+0x14f
ffff978f`ef01e320 fffff803`56565946     : ffff978f`ef01e4c8 ffffba06`00000000 ffffba06`10fa0a00 ffffba06`0bac5a00 : nt!KeWaitForSingleObject+0x233
ffff978f`ef01e410 ffff978f`ef01e4c8     : ffffba06`00000000 ffffba06`10fa0a00 ffffba06`0bac5a00 00000000`00000000 : IntcUSB+0x55946
ffff978f`ef01e418 ffffba06`00000000     : ffffba06`10fa0a00 ffffba06`0bac5a00 00000000`00000000 00000000`00000001 : 0xffff978f`ef01e4c8
ffff978f`ef01e420 ffffba06`10fa0a00     : ffffba06`0bac5a00 00000000`00000000 00000000`00000001 00000000`00001001 : 0xffffba06`00000000
ffff978f`ef01e428 ffffba06`0bac5a00     : 00000000`00000000 00000000`00000001 00000000`00001001 00000000`00000fff : 0xffffba06`10fa0a00
ffff978f`ef01e430 00000000`00000000     : 00000000`00000001 00000000`00001001 00000000`00000fff ffff978f`ef01e620 : 0xffffba06`0bac5a00


SYMBOL_NAME:  IntcUSB+55946

MODULE_NAME: IntcUSB

IMAGE_NAME:  IntcUSB.sys

STACK_COMMAND:  .process /r /p 0xffffba05e5ad4080; .thread 0xffffba05e5b18240 ; kb

BUCKET_ID_FUNC_OFFSET:  55946

FAILURE_BUCKET_ID:  0x9F_3_IntcUSB!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3a940f2c-6166-2b30-7924-191a072ab027}

Followup:     MachineOwner
---------
Sorunu Intel SST sürücüsü çıkarıyor.

BIOS ve diğer tüm sürücüleri buradan güncelleyin.


Örneğin; Realtek Ethernet sürücüsünü eski kalmış bayağı.

Intel ile alakalı tüm sürücüler için;


Kod:
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffffba0606a9ade0, Physical Device Object of the stack
Arg3: ffff978fef067ba0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffba0604b285a0, The blocked IRP

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

Implicit thread is now ffffba05`e5b18240
*** WARNING: Unable to verify timestamp for IntcUSB.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2967

    Key  : Analysis.Elapsed.mSec
    Value: 8935

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x9f

    Key  : Failure.Bucket
    Value: 0x9F_3_IntcUSB!unknown_function

    Key  : Failure.Hash
    Value: {3a940f2c-6166-2b30-7924-191a072ab027}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffba0606a9ade0

BUGCHECK_P3: ffff978fef067ba0

BUGCHECK_P4: ffffba0604b285a0

FILE_IN_CAB:  062123-7500-01.dmp

DRVPOWERSTATE_SUBCODE:  3

FAULTING_THREAD:  ffffba05e5b18240

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

DPC_STACK_BASE:  FFFF978FEF067FB0

STACK_TEXT: 
ffff978f`ef01e090 fffff803`2281c9c0     : 00000000`00000009 00000000`ffffffff 00000000`00000000 ffffba06`163bc158 : nt!KiSwapContext+0x76
ffff978f`ef01e1d0 fffff803`2281beef     : 00000001`000180bb 00000000`00000000 ffff978f`ef01e390 ffff978f`ef01e600 : nt!KiSwapThread+0x500
ffff978f`ef01e280 fffff803`2281b793     : 00000000`00000000 00000000`00000000 ffffba06`18de0200 ffffba05`e5b18380 : nt!KiCommitThreadWait+0x14f
ffff978f`ef01e320 fffff803`56565946     : ffff978f`ef01e4c8 ffffba06`00000000 ffffba06`10fa0a00 ffffba06`0bac5a00 : nt!KeWaitForSingleObject+0x233
ffff978f`ef01e410 ffff978f`ef01e4c8     : ffffba06`00000000 ffffba06`10fa0a00 ffffba06`0bac5a00 00000000`00000000 : IntcUSB+0x55946
ffff978f`ef01e418 ffffba06`00000000     : ffffba06`10fa0a00 ffffba06`0bac5a00 00000000`00000000 00000000`00000001 : 0xffff978f`ef01e4c8
ffff978f`ef01e420 ffffba06`10fa0a00     : ffffba06`0bac5a00 00000000`00000000 00000000`00000001 00000000`00001001 : 0xffffba06`00000000
ffff978f`ef01e428 ffffba06`0bac5a00     : 00000000`00000000 00000000`00000001 00000000`00001001 00000000`00000fff : 0xffffba06`10fa0a00
ffff978f`ef01e430 00000000`00000000     : 00000000`00000001 00000000`00001001 00000000`00000fff ffff978f`ef01e620 : 0xffffba06`0bac5a00


SYMBOL_NAME:  IntcUSB+55946

MODULE_NAME: IntcUSB

IMAGE_NAME:  IntcUSB.sys

STACK_COMMAND:  .process /r /p 0xffffba05e5ad4080; .thread 0xffffba05e5b18240 ; kb

BUCKET_ID_FUNC_OFFSET:  55946

FAILURE_BUCKET_ID:  0x9F_3_IntcUSB!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3a940f2c-6166-2b30-7924-191a072ab027}

Followup:     MachineOwner
---------
 
Çözüm

Geri
Yukarı