Monster mavi ekran hatası

J

Jenans

Femtopat
Katılım
8 Kasım 2020
Mesajlar
9
Daha fazla  
Cinsiyet
Erkek
Monster Abra serisi laptop kullanıyorum, laptop kapalıyken çoğu zaman Power tuşuyla açmaya kalkınca açılmıyor klavye ışıkları yanıyorken ekran gelmiyor. 15-20 kez deneyince laptopun ne zaman açma isteği olursa o zaman açılıyor gibi, :) açılınca da epey kasıyor normal Google Chrome'da bile. Bir süre sonra şimdi paylaşacağım hatayı veriyor. Bana yardımcı olabilir misiniz?
 

Dosya Ekleri

  • E5431F86-B6C5-4729-8324-0F0869D72196.jpeg
    E5431F86-B6C5-4729-8324-0F0869D72196.jpeg
    175,1 KB · Görüntüleme: 62
Son düzenleyen: Moderatör:
Tarihe göre sırala Puana göre sırala

Minidump Dosyalarını Paylaşın

23.06.2025 tarihinde yapılan güncel rehbere aşağıdaki linkten erişebilirsiniz: https://www.technopat.net/sosyal/konu/minidump-nedir-nasil-paylasilir.3817531/ Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi...
www.technopat.net www.technopat.net

@Bora Dere @Assecreed
 
Artı 0 Eksi
Cihaz modeli ve seri numarasını da yazarsanız daha iyi olur.
Salih_Emre dedi:
Büyük ihtimal virus bulaşmış bence kurtarma şeçeneklerinden bilgisayarı sıfırlayın çok önemli dosyalar yoksa.
Genişletmek için tıkla...
Virüs yüzünden mavi ekran hatası göremdim...
 
Artı 3 Eksi
Recep Baltaş dedi:
Virüs yüzünden mavi ekran hatası göremdim...
Genişletmek için tıkla...

Bilgisayara virus taraması yaptığımda bir şey yoktu 1 hafta sonra yaptım virus bulundu o gün bilgisayarı kapat aç yaptığımda mavi ekran hatası almıştım virus yüzünden olduğunu düşünüyorum ama emin değilim siz daha iyi bilirsiniz.
 
Artı 0 Eksi
Recep Baltaş dedi:
Virüs yüzünden mavi ekran hatası göremdim...
Genişletmek için tıkla...
Rootkitlerde almak mümkün veya BOF, SOF yapmaya çalışan cinsten bir şey varsa.

KERNEL_SECURITY_CHECK_FAILURE olur genelde o tarz olanlar. Dökümü incelerken kendisini belli eder anti-hile veya güvenlik yazılımı değilse. Ama bu konuda durum öyle gözükmüyor zaten.
 
Artı 0 Eksi
Recep Baltaş dedi:
Cihaz modeli ve seri numarasını da yazarsanız daha iyi olur.

Virüs yüzünden mavi ekran hatası göremdim...
Genişletmek için tıkla...

Monster Abra A5 V13.1.3
Seri numarasından kastınız tam anlamadım, bilgisayarsan anlamıyorum pek. Şu anda Windows denetleme aygıtından RAM'da sorun olup olmadığına bakıyorum belki de yanlış işlem yapıyorum ama araştırdığımda öyleyapmış biri bende yapıyorum, sizin önerileriniz var mı?
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
Jenans dedi:
Monster abra a5 V13.1.3
Seri numarasından kastınız tam anlamadım , bilgisayarsan anlamıyorum pek. Şuanda Windows denetleme aygıtından RAM da sorun olup olmadığına bakıyorum belki de yanlış işlem yapıyorum ama araştırdığımda öyleyapmış biri bende yapıyorum, sizin önerileriniz var mı
Genişletmek için tıkla...
Minidump dosyalarını paylaşırsanız hata daha kolay tespit edilebilir.
 
Artı 1 Eksi
Ekran kartınızla ilgili bir sorun var. Cihazı servise yollamanızı öneririm.

Kod: 
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: ffffc885ef7df060, Physical Device Object of the stack
Arg3: fffffe07b1c3f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffc885f835ac20, The blocked IRP

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvtfi.inf_amd64_76df3410785db303\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Implicit thread is now ffffc885`ed6b4040
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6202

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 10454

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffc885ef7df060

BUGCHECK_P3: fffffe07b1c3f750

BUGCHECK_P4: ffffc885f835ac20

DRVPOWERSTATE_SUBCODE:  3

FAULTING_THREAD:  ffffc885ed6b4040

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffffe07`b1c16e20 ffffc885`f66ac000     : 00000000`00000000 ffffc885`f4e8f010 ffffc885`f66ac000 00000000`00000000 : nvlddmkm+0x518a25
fffffe07`b1c16e28 00000000`00000000     : ffffc885`f4e8f010 ffffc885`f66ac000 00000000`00000000 fffffe07`b1c16f00 : 0xffffc885`f66ac000


STACK_COMMAND:  .thread 0xffffc885ed6b4040 ; kb

SYMBOL_NAME:  nvlddmkm+518a25

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

BUCKET_ID_FUNC_OFFSET:  518a25

FAILURE_BUCKET_ID:  0x9F_3_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8b257f08-e34e-7c26-3880-084b82f90c48}

Followup:     MachineOwner
---------
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: ffffaf03e41e0570, Physical Device Object of the stack
Arg3: ffff91066c23f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffaf03e9b6fc30, The blocked IRP

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvtfi.inf_amd64_76df3410785db303\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Implicit thread is now ffffaf03`e10e2040
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5968

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 12875

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffaf03e41e0570

BUGCHECK_P3: ffff91066c23f750

BUGCHECK_P4: ffffaf03e9b6fc30

DRVPOWERSTATE_SUBCODE:  3

FAULTING_THREAD:  ffffaf03e10e2040

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffff9106`6c21ee18 fffff805`799b89a8     : ffff9106`6c21ee60 00000000`00000000 00000000`00000000 ffffaf03`ea079000 : nvlddmkm+0x1094cf
ffff9106`6c21ee20 ffff9106`6c21ee60     : 00000000`00000000 00000000`00000000 ffffaf03`ea079000 00000000`00000000 : nvlddmkm+0x5189a8
ffff9106`6c21ee28 00000000`00000000     : 00000000`00000000 ffffaf03`ea079000 00000000`00000000 ffff9106`6c21ef00 : 0xffff9106`6c21ee60


STACK_COMMAND:  .thread 0xffffaf03e10e2040 ; kb

SYMBOL_NAME:  nvlddmkm+1094cf

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

BUCKET_ID_FUNC_OFFSET:  1094cf

FAILURE_BUCKET_ID:  0x9F_3_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8b257f08-e34e-7c26-3880-084b82f90c48}

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

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: ffffd20e418e45b0, Physical Device Object of the stack
Arg3: fffff8810423f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffd20e4888b790, The blocked IRP

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvtfi.inf_amd64_76df3410785db303\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Implicit thread is now ffffd20e`3f8e3040
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6030

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 13860

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffd20e418e45b0

BUGCHECK_P3: fffff8810423f750

BUGCHECK_P4: ffffd20e4888b790

DRVPOWERSTATE_SUBCODE:  3

FAULTING_THREAD:  ffffd20e3f8e3040

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff881`04216df0 ffffd20e`46f08550     : fffff881`04216e90 ffffd20e`46f08550 00000000`00000000 00000000`00000000 : nvlddmkm+0x5231d5
fffff881`04216df8 fffff881`04216e90     : ffffd20e`46f08550 00000000`00000000 00000000`00000000 fffff807`869b8a9f : 0xffffd20e`46f08550
fffff881`04216e00 ffffd20e`46f08550     : 00000000`00000000 00000000`00000000 fffff807`869b8a9f ffffd20e`48e69000 : 0xfffff881`04216e90
fffff881`04216e08 00000000`00000000     : 00000000`00000000 fffff807`869b8a9f ffffd20e`48e69000 ffffd20e`46f08550 : 0xffffd20e`46f08550


STACK_COMMAND:  .thread 0xffffd20e3f8e3040 ; kb

SYMBOL_NAME:  nvlddmkm+5231d5

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

BUCKET_ID_FUNC_OFFSET:  5231d5

FAILURE_BUCKET_ID:  0x9F_3_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8b257f08-e34e-7c26-3880-084b82f90c48}

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

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: ffffb80953ff0060, Physical Device Object of the stack
Arg3: fffff88e26e47ba0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffb8095b8bf0a0, The blocked IRP

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

Implicit thread is now ffffb809`52e99040
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6936

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 44008

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffb80953ff0060

BUGCHECK_P3: fffff88e26e47ba0

BUGCHECK_P4: ffffb8095b8bf0a0

DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

MODULE_NAME: pci

FAULTING_MODULE: fffff8051f060000 pci

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

DPC_STACK_BASE:  FFFFF88E26E47FB0

STACK_TEXT:
fffff88e`26e47b68 fffff805`1a35ecb7     : 00000000`0000009f 00000000`00000003 ffffb809`53ff0060 fffff88e`26e47ba0 : nt!KeBugCheckEx
fffff88e`26e47b70 fffff805`1a35ebd1     : ffffb809`5cd9b6a8 ffffb809`616f4080 00000000`00000000 00000000`0015a00a : nt!PopIrpWatchdogBugcheck+0xdf
fffff88e`26e47be0 fffff805`1a0bf682     : ffffb809`5cd9b6e0 ffffe180`def42180 fffff88e`26e47e68 ffffe180`def42180 : nt!PopIrpWatchdog+0x31
fffff88e`26e47c30 fffff805`1a0e4a2d     : ffffe180`def42180 00000000`00000000 00000000`00000000 00000000`0015a00a : nt!KiProcessExpiredTimerList+0x172
fffff88e`26e47d20 fffff805`1a1fc255     : 00000000`00000000 ffffe180`def42180 ffffb809`52ee5200 00000000`00100cd0 : nt!KiRetireDpcList+0x5dd
fffff88e`26e47fb0 fffff805`1a1fc040     : ffffb809`5aa57000 fffff805`1a07448a ffffb809`5a267010 fffff805`1a07448a : nt!KxRetireDpcList+0x5
fffff88e`26e1ec40 fffff805`1a1fb8f5     : 00000000`00100cd0 fffff805`1a1f72a1 ffffb809`5aa57000 00000000`00000000 : nt!KiDispatchInterruptContinue
fffff88e`26e1ec70 fffff805`1a1f72a1     : ffffb809`5aa57000 00000000`00000000 ffffb809`5aa57000 ffffb809`5aa581d8 : nt!KiDpcInterruptBypass+0x25
fffff88e`26e1ec80 fffff805`37ecbdb9     : fffff805`382e8a77 ffffb809`5aa57000 00000000`00000000 ffffb809`5a267010 : nt!KiInterruptDispatchNoLockNoEtw+0xb1
fffff88e`26e1ee18 fffff805`382e8a77     : ffffb809`5aa57000 00000000`00000000 ffffb809`5a267010 ffffb809`5aa57000 : nvlddmkm+0xfbdb9
fffff88e`26e1ee20 ffffb809`5aa57000     : 00000000`00000000 ffffb809`5a267010 ffffb809`5aa57000 00000000`00000020 : nvlddmkm+0x518a77
fffff88e`26e1ee28 00000000`00000000     : ffffb809`5a267010 ffffb809`5aa57000 00000000`00000020 fffff88e`26e1ee60 : 0xffffb809`5aa57000


IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x9F_3_nvlddmkm_IMAGE_pci.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a47222af-fbac-bc49-47e0-2cf5d31cc673}

Followup:     MachineOwner
---------
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: ffffa7846b773060, Physical Device Object of the stack
Arg3: ffff81091e03f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffa78471447aa0, The blocked IRP

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvtfi.inf_amd64_76df3410785db303\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Implicit thread is now ffffa784`7a5a0040
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5437

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 16595

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffa7846b773060

BUGCHECK_P3: ffff81091e03f750

BUGCHECK_P4: ffffa78471447aa0

DRVPOWERSTATE_SUBCODE:  3

FAULTING_THREAD:  ffffa7847a5a0040

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffff8109`22e0ede8 fffff800`44ab31b9     : ffffa784`6ba88a20 ffff8109`22e0ee90 ffffa784`726ca000 00000000`00000000 : nvlddmkm+0xfbdb9
ffff8109`22e0edf0 ffffa784`6ba88a20     : ffff8109`22e0ee90 ffffa784`726ca000 00000000`00000000 00000000`00000000 : nvlddmkm+0x5231b9
ffff8109`22e0edf8 ffff8109`22e0ee90     : ffffa784`726ca000 00000000`00000000 00000000`00000000 fffff800`44aa8a9f : 0xffffa784`6ba88a20
ffff8109`22e0ee00 ffffa784`726ca000     : 00000000`00000000 00000000`00000000 fffff800`44aa8a9f ffffa784`726b3000 : 0xffff8109`22e0ee90
ffff8109`22e0ee08 00000000`00000000     : 00000000`00000000 fffff800`44aa8a9f ffffa784`726b3000 ffffa784`6ba88a20 : 0xffffa784`726ca000


STACK_COMMAND:  .thread 0xffffa7847a5a0040 ; kb

SYMBOL_NAME:  nvlddmkm+fbdb9

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

BUCKET_ID_FUNC_OFFSET:  fbdb9

FAILURE_BUCKET_ID:  0x9F_3_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8b257f08-e34e-7c26-3880-084b82f90c48}

Followup:     MachineOwner
---------
 
Artı 0 Eksi
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.

Benzer konular

IHaveNoEnemies
  • Soru
Monster laptop mavi ekran sonrası "no bootable device" hatası
2
Mesaj
15
Görüntüleme
2.704
IHaveNoEnemies
IHaveNoEnemies
elifesra
  • Soru
Mavi ekran hatası
2
Mesaj
14
Görüntüleme
1.083
elifesra
elifesra
Dogaserinyel44
  • Soru
Mavi ekran hatası
Mesaj
5
Görüntüleme
273
turko35408
turko35408
Tamerks34
  • Soru
Mavi ekran hatası
Mesaj
2
Görüntüleme
420
Tamerks34
Tamerks34
pisuscosplay
  • Soru
Mavi ekran hatası
2
Mesaj
11
Görüntüleme
680
maksu
maksu

Technopat Haberler

Yeni konular

Yeni mesajlar

Geri
Yukarı