Lenovo V14-ADA mavi ekran

İşletim sistemi
Windows 10

canpikachu

Hectopat
Katılım
24 Haziran 2019
Mesajlar
322
Çözümler
4
Biraz önce laptop da aldığım mavi ekran hatasının analiz edilmiş hali.
Uğraşlarınız için şimdiden teşekkür ederim.
Kod:
Microsoft (R) Windows Debugger Version 10.0.22415.1002 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Users\Arda\Desktop\Minidump\073021-9281-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 19041 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff800`3a000000 PsLoadedModuleList = 0xfffff800`3ac2a1d0

Debug session time: Fri Jul 30 11:33:43.951 2021 (UTC + 3:00)

System Uptime: 1 days 1:13:37.876

Loading Kernel Symbols

...............................................................

................................................................

................................................................

..

Loading User Symbols

Loading unloaded module list

.........................

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff800`3a3f6f20 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff810d`f3e30b70=000000000000009f

1: 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: ffffa507bbf0ede0, Physical Device Object of the stack

Arg3: ffff810df3e30ba0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack

Arg4: ffffa507bdd79010, The blocked IRP



Debugging Details:

------------------



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



KEY_VALUES_STRING: 1



    Key  : Analysis.CPU.mSec

    Value: 13859



    Key  : Analysis.DebugAnalysisManager

    Value: Create



    Key  : Analysis.Elapsed.mSec

    Value: 52694



    Key  : Analysis.Init.CPU.mSec

    Value: 1093



    Key  : Analysis.Init.Elapsed.mSec

    Value: 4297



    Key  : Analysis.Memory.CommitPeak.Mb

    Value: 83



    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:  9f



BUGCHECK_P1: 3



BUGCHECK_P2: ffffa507bbf0ede0



BUGCHECK_P3: ffff810df3e30ba0



BUGCHECK_P4: ffffa507bdd79010



DRVPOWERSTATE_SUBCODE:  3



DRIVER_OBJECT: ffffa507bde82d50



IMAGE_NAME:  HDAudBus.sys



MODULE_NAME: HDAudBus



FAULTING_MODULE: fffff8004f620000 HDAudBus



BLACKBOXACPI: 1 (!blackboxacpi)





BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXNTFS: 1 (!blackboxntfs)





BLACKBOXPNP: 1 (!blackboxpnp)





BLACKBOXWINLOGON: 1



CUSTOMER_CRASH_COUNT:  1



PROCESS_NAME:  LNBITSSvc.exe



DPC_STACK_BASE:  FFFF810DF3E30FB0



STACK_TEXT:

ffff810d`f3e30b68 fffff800`3a55fb47     : 00000000`0000009f 00000000`00000003 ffffa507`bbf0ede0 ffff810d`f3e30ba0 : nt!KeBugCheckEx

ffff810d`f3e30b70 fffff800`3a55fa61     : ffffa507`bde8d7f8 00000000`00000000 ffffa507`cc1bb1f0 00000000`00000000 : nt!PopIrpWatchdogBugcheck+0xdf

ffff810d`f3e30be0 fffff800`3a281782     : ffffa507`bde8d830 ffffd000`f4fa8180 ffffd000`f4fa8180 ffffa507`00000002 : nt!PopIrpWatchdog+0x31

ffff810d`f3e30c30 fffff800`3a299a8d     : ffffd000`f4fa8180 00490020`00000000 00000000`00000000 00000000`0034dd03 : nt!KiProcessExpiredTimerList+0x172

ffff810d`f3e30d20 fffff800`3a3fdf65     : 0075006f`00520020 ffffd000`f4fa8180 ffffa507`bbcd25a0 ffffd000`f55dc0b8 : nt!KiRetireDpcList+0x5dd

ffff810d`f3e30fb0 fffff800`3a3fdd50     : fffff800`3a3f3010 fffff800`3a325e2a ffffa507`bc880feb 00000000`00000000 : nt!KxRetireDpcList+0x5

ffff810d`f53bec20 fffff800`3a3fd605     : ffffd000`f55dc0b8 fffff800`3a3f8fb1 ffffffff`ffffffff ffffa507`ceecf930 : nt!KiDispatchInterruptContinue

ffff810d`f53bec50 fffff800`3a3f8fb1     : ffffffff`ffffffff ffffa507`ceecf930 ffffa507`bc880feb ffffa507`bc880fe1 : nt!KiDpcInterruptBypass+0x25

ffff810d`f53bec60 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1





IMAGE_VERSION:  10.0.19041.1151



STACK_COMMAND:  .thread ; .cxr ; kb



FAILURE_BUCKET_ID:  0x9F_3_IMAGE_HDAudBus.sys



OS_VERSION:  10.0.19041.1



BUILDLAB_STR:  vb_release



OSPLATFORM_TYPE:  x64



OSNAME:  Windows 10



FAILURE_ID_HASH:  {360d077d-1208-9ef3-2358-6a66e420c674}



Followup:     MachineOwner
 
Son düzenleme:

Geri
Yukarı