Dpc watchdog violation mavi ekran hatası

cxecpuerrer

Hectopat
Katılım
2 Nisan 2020
Mesajlar
121
Yer
Trabzon
Daha fazla  
Cinsiyet
Erkek
Meslek
Öğrenci
Dün bilgisayarıma Valorant yüklemiştim ama hiç açmamıştım, ondan sonra bilgisayarımı kapattıktan sonra bilgisayar açılırken donmalar ve mavi ekran geliyordu.
 
Bilgisayarı açıyorum, ya donmalar oluyor ya da dpc watchdog violation hatası alıyorum.

Minidump dosyası:

Google Drive ya da OneDrive'dan atamıyordum, MediaFire'dan atabildim.
 
3 dosya tam oluşmamış 2 tanesini yakalayabildim.
Diskinizde muhtemelen arıza var. Ayrıca ekran kartınız NVIDIA nForce mu? Çünkü bir hata NVIDIA nForce ile alakalı olarak oluşmuş. Ekran kartı sürücünüzü güncelleyin. Karta ait SATA Performance Driver adlı dosya hata veriyor.

Vanguard kaldırın.

Kaspersky Antivirüs yazılını kaldırın.

BIOS sürümü güncel mi onu kontrol edelim.

HD Tune ile "Error Scan" yapacaksınız ama "Quick Scan" kapalı olacak. "Health" yani sağlık yazan yerin fotoğrafını da test sonucu ile birlikte atın.
 
3 dosya tam oluşmamış 2 tanesini yakalayabildim.
Diskinizde muhtemelen arıza var. Ayrıca ekran kartınız NVIDIA nforce mu? Çünkü bir hata NVIDIA nforce ile alakalı olarak oluşmuş. Ekran kartı sürücünüzü güncelleyin. Karta ait SATA performance driver adlı dosya hata veriyor.

Vanguard kaldırın.

Kaspersky antivirüs yazılını kaldırın.

BIOS sürümü güncel mi onu kontrol edelim.

HD Tune ile "error scan" yapacaksınız ama "quick scan" kapalı olacak. "health" yani sağlık yazan yerin fotoğrafını da test sonucu ile birlikte atın.

Öncelikle Vanguard'ı kaldırdım peki sonra yüklesem sorun olur mu?

Kaspersky antivirüs da kaldırdım kendi VPN'i ile birlikte.

BIOS nasıl güncelleyebilirim hiçbir fikrim yok.

HD Tune test sonuçları.

Ekran kartı sürücüsünden hangisini yüklemeleyim ki.

Ekran kartı modeli: AMD Radeon 5450.
 

Dosya Ekleri

  • hd tune.PNG
    hd tune.PNG
    25,6 KB · Görüntüleme: 34
  • ekrankartı.PNG
    ekrankartı.PNG
    21,3 KB · Görüntüleme: 32
Öncelikle Vanguard'ı kaldırdım peki sonra yüklesem sorun olur mu?

Kaspersky antivirüs da kaldırdım kendi VPN'i ile birlikte.

BIOS nasıl güncelleyebilirim hiçbir fikrim yok.

HD Tune test sonuçları.

Ekran kartı sürücüsünden hangisini yüklemeleyim ki.

O zaman neden NVIDIA nforce sürücüsü mavi ekran verdirmiş? WHQL sertifikalı AMD sürücüsü yüklenecek. HDD iyi görünüyor.
Ekran kartı AMD ve hataya sebep olan NVIDIA nforce ekran kartı sürücüsü. Bir daha kontrol eder misiniz ekran kartınızı?

Görüntü bağdaştırıcılarımda sadece Radeon 5450 var NVIDIA ile ilgili bir driver kurmadım
 

Dosya Ekleri

  • Ekran Alıntısı.PNG
    Ekran Alıntısı.PNG
    2 KB · Görüntüleme: 26
Euzubillahimine. O zaman bu NVIDIA sürücüsü bilgisayarda nasıl bulunabiliyor? Ama gerçekten hataya sebep olan şey NVIDIA nForce ekran kartı sürücüsü.
Hatta dosyanın analizini de atayım kendiniz de görün.
Kod:
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\hazar\AppData\Local\Temp\7zO8DE95AD4\022521-132500-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`30600000 PsLoadedModuleList = 0xfffff805`3122a390
Debug session time: Thu Feb 25 14:17:20.690 2021 (UTC + 3:00)
System Uptime: 0 days 0:01:56.453
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`309f5a80 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffff805`35a7ac90=0000000000000133
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff805312fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 8061

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on VOSTRO-5468

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 12582

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

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

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff805312fb320

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff80535a73750 -- (.trap 0xfffff80535a73750)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000070b11aae rbx=0000000000000000 rcx=fffff80535a73940
rdx=ffffcf8ce5ac0b30 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80530844565 rsp=fffff80535a738e0 rbp=fffff80535a73cb0
r8=ffffe181ca070010  r9=0000000000000000 r10=0000000000000002
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeYieldProcessorEx+0x15:
fffff805`30844565 f390            pause
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

DPC_STACK_BASE:  FFFFF80535A73FB0

STACK_TEXT:
fffff805`35a7ac88 fffff805`30a3ac88     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff805`35a7ac90 fffff805`3087541d     : 00000086`f3c796e5 fffff805`2d882180 00000000`00000246 00000000`00001d1d : nt!KeAccumulateTicks+0x1c8a88
fffff805`35a7acf0 fffff805`308759c1     : 00000000`00001d1b 00000000`0000115a fffff805`2d882180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff805`35a7ad40 fffff805`3086f833     : fffff805`2d882180 00000000`00000000 fffff805`31231658 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff805`35a7ae80 fffff805`308781f2     : fffff805`35a73750 fffff805`35a737d0 fffff805`35a73700 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff805`35a7af30 fffff805`30927ef5     : 00000000`457eb86c fffff805`312f39e0 fffff805`312f3a90 ffff95e5`168b0349 : nt!HalpTimerClockInterrupt+0xe2
fffff805`35a7af60 fffff805`309f752a     : fffff805`35a737d0 fffff805`312f39e0 00000077`fa26ec5a 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff805`35a7afb0 fffff805`309f7a97     : 00000000`00000000 00000000`00000000 fffff805`35a73aa8 fffff805`309f7aa4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff805`35a73750 fffff805`30844565     : 00000000`00000010 00000000`00000202 fffff805`35a73908 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff805`35a738e0 fffff805`3082e09a     : 00000000`00000000 ffff9ea6`d6f0846e 00000000`00140001 00000000`00000002 : nt!KeYieldProcessorEx+0x15
fffff805`35a73910 fffff805`3082e05f     : 00000000`70b11aae 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip+0x2a
fffff805`35a73940 fffff805`34a5d33a     : fffff805`35a73aa0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAcquireInStackQueuedSpinLock+0x7f
fffff805`35a73970 fffff805`34a38b40     : fffff805`35a73cb0 ffffe181`ca070010 00000000`00000002 00000000`00000000 : storport!StorPortNotification+0x10a
fffff805`35a73a40 fffff805`34a2511e     : fffff780`00000340 00000000`00000000 fffff805`312f3a90 fffff805`31220fe0 : nvstor!NvStorSpinLockAcquire+0x60
fffff805`35a73a80 fffff805`34a24609     : ffff9200`ac995440 fffff805`35a73e70 fffff805`35a73b50 fffff805`34a38b40 : nvstor!NvStorProtocolAtaSendCommandAndBusyWaitInterrupt+0x152
fffff805`35a73ad0 fffff805`34a23c95     : ffffe181`ca078000 ffffe181`ca072948 fffff805`35a73b50 00000000`00000002 : nvstor!NvStorProtocolAtaDmaInterrupt+0xa5
fffff805`35a73b00 fffff805`34a32db5     : 00400a02`00000010 ffffe181`ca070010 ffffe181`c79d5928 ffffe181`c78e2040 : nvstor!NvStorProtocolAtaNonQueuedHandleInterrupt+0xdd
fffff805`35a73b30 fffff805`34a35abd     : 00000000`00000000 00000077`fa00a665 fffff805`2d882180 00000000`00000004 : nvstor!NvStorIntPortDpcSingleDevice+0x59
fffff805`35a73b80 fffff805`3080781e     : fffff805`2d885240 ffffe181`c79c9000 00000000`00000000 ffffe181`00000002 : nvstor!NvStorDpcForIsr+0x11
fffff805`35a73bb0 fffff805`30806b04     : 00000000`00000000 00000000`00000000 00000000`0000002a 00000000`00000e76 : nt!KiExecuteAllDpcs+0x30e
fffff805`35a73d20 fffff805`309fcac5     : 00000000`00000000 fffff805`2d882180 ffff9200`ac551c80 00000000`00270000 : nt!KiRetireDpcList+0x1f4
fffff805`35a73fb0 fffff805`309fc8b0     : 000000e5`0d87f3ec fffff805`308ec5ca 00000000`00000000 000000e5`0d87f688 : nt!KxRetireDpcList+0x5
ffffcf8c`e6b33c00 fffff805`309fc165     : 00000000`00270000 fffff805`309f6dd1 000002c4`c583c958 ffffe181`00000000 : nt!KiDispatchInterruptContinue
ffffcf8c`e6b33c30 fffff805`309f6dd1     : 000002c4`c583c958 ffffe181`00000000 ffffcf8c`e6b33cc0 ffffcf8c`e6b33cc0 : nt!KiDpcInterruptBypass+0x25
ffffcf8c`e6b33c40 00007ffc`33c2dae7     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiChainedDispatch+0xb1
000000e5`0d87f160 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`33c2dae7


SYMBOL_NAME:  nvstor!NvStorSpinLockAcquire+60

MODULE_NAME: nvstor

IMAGE_NAME:  nvstor.sys

IMAGE_VERSION:  10.6.0.23

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  60

FAILURE_BUCKET_ID:  0x133_DPC_nvstor!NvStorSpinLockAcquire

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {eba06ed9-d58e-aea9-1ac7-ff753a2eebb0}

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

0: kd> lmvm nvstor
Browse full module list
start             end                 module name
fffff805`34a20000 fffff805`34a4a000   nvstor   # (pdb symbols)          C:\ProgramData\Dbg\sym\nvstor.pdb\232DE2BB1F114159816A0AA31CBCFC201\nvstor.pdb
    Loaded symbol image file: nvstor.sys
    Mapped memory image file: C:\ProgramData\Dbg\sym\nvstor.sys\5355649B2a000\nvstor.sys
    Image path: \SystemRoot\System32\drivers\nvstor.sys
    Image name: nvstor.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Apr 21 21:34:03 2014 (5355649B)
    CheckSum:         000345F3
    ImageSize:        0002A000
    File version:     10.6.0.23
    Product version:  10.6.0.23
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      NVIDIA Corporation
        ProductName:      NVIDIA nForce(TM) SATA Driver
        InternalName:     NVIDIA nForce(TM) SATA Driver
        OriginalFilename: nvstor.sys
        ProductVersion:   10.6.0.23
        FileVersion:      10.6.0.23 (PART_L3.131021-1012)
        FileDescription:  NVIDIA® nForce(TM) Sata Performance Driver
        LegalCopyright:   Copyright(C) 2001-2011 NVIDIA Corporation

Diskten kaynaklı bir problem var halihazırda. Diskinizi biraz gözlemleyin. Acaba depolama ile alakalı bir hata alacak mı diye.
@Enes3078 hocam çok ilginç bir vaka ile karşı karşıyayız. İki hatanın da oluşmasını tetikleyen şey aslında NVIDIA nForce sürücüsü. Storport tabanlı olduğu için bu kart "Storage Port" Driver hata vermiş. Yardımcı olur musunuz?
 
Euzubillahimine. O zaman bu NVIDIA sürücüsü bilgisayarda nasıl bulunabiliyor? Ama gerçekten hataya sebep olan şey NVIDIA nForce ekran kartı sürücüsü.
Hatta dosyanın analizini de atayım kendiniz de görün.
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\hazar\AppData\Local\Temp\7zO8DE95AD4\022521-132500-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`30600000 PsLoadedModuleList = 0xfffff805`3122a390
Debug session time: Thu Feb 25 14:17:20.690 2021 (UTC + 3:00)
System Uptime: 0 days 0:01:56.453
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`309f5a80 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff805`35a7ac90=0000000000000133
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff805312fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 8061

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on VOSTRO-5468

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 12582

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

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

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff805312fb320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff80535a73750 -- (.trap 0xfffff80535a73750)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000070b11aae rbx=0000000000000000 rcx=fffff80535a73940
rdx=ffffcf8ce5ac0b30 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80530844565 rsp=fffff80535a738e0 rbp=fffff80535a73cb0
r8=ffffe181ca070010 r9=0000000000000000 r10=0000000000000002
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KeYieldProcessorEx+0x15:
fffff805`30844565 f390 pause
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

DPC_STACK_BASE: FFFFF80535A73FB0

STACK_TEXT:
fffff805`35a7ac88 fffff805`30a3ac88 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff805`35a7ac90 fffff805`3087541d : 00000086`f3c796e5 fffff805`2d882180 00000000`00000246 00000000`00001d1d : nt!KeAccumulateTicks+0x1c8a88
fffff805`35a7acf0 fffff805`308759c1 : 00000000`00001d1b 00000000`0000115a fffff805`2d882180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff805`35a7ad40 fffff805`3086f833 : fffff805`2d882180 00000000`00000000 fffff805`31231658 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff805`35a7ae80 fffff805`308781f2 : fffff805`35a73750 fffff805`35a737d0 fffff805`35a73700 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff805`35a7af30 fffff805`30927ef5 : 00000000`457eb86c fffff805`312f39e0 fffff805`312f3a90 ffff95e5`168b0349 : nt!HalpTimerClockInterrupt+0xe2
fffff805`35a7af60 fffff805`309f752a : fffff805`35a737d0 fffff805`312f39e0 00000077`fa26ec5a 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff805`35a7afb0 fffff805`309f7a97 : 00000000`00000000 00000000`00000000 fffff805`35a73aa8 fffff805`309f7aa4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff805`35a73750 fffff805`30844565 : 00000000`00000010 00000000`00000202 fffff805`35a73908 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff805`35a738e0 fffff805`3082e09a : 00000000`00000000 ffff9ea6`d6f0846e 00000000`00140001 00000000`00000002 : nt!KeYieldProcessorEx+0x15
fffff805`35a73910 fffff805`3082e05f : 00000000`70b11aae 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip+0x2a
fffff805`35a73940 fffff805`34a5d33a : fffff805`35a73aa0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAcquireInStackQueuedSpinLock+0x7f
fffff805`35a73970 fffff805`34a38b40 : fffff805`35a73cb0 ffffe181`ca070010 00000000`00000002 00000000`00000000 : storport!StorPortNotification+0x10a
fffff805`35a73a40 fffff805`34a2511e : fffff780`00000340 00000000`00000000 fffff805`312f3a90 fffff805`31220fe0 : nvstor!NvStorSpinLockAcquire+0x60
fffff805`35a73a80 fffff805`34a24609 : ffff9200`ac995440 fffff805`35a73e70 fffff805`35a73b50 fffff805`34a38b40 : nvstor!NvStorProtocolAtaSendCommandAndBusyWaitInterrupt+0x152
fffff805`35a73ad0 fffff805`34a23c95 : ffffe181`ca078000 ffffe181`ca072948 fffff805`35a73b50 00000000`00000002 : nvstor!NvStorProtocolAtaDmaInterrupt+0xa5
fffff805`35a73b00 fffff805`34a32db5 : 00400a02`00000010 ffffe181`ca070010 ffffe181`c79d5928 ffffe181`c78e2040 : nvstor!NvStorProtocolAtaNonQueuedHandleInterrupt+0xdd
fffff805`35a73b30 fffff805`34a35abd : 00000000`00000000 00000077`fa00a665 fffff805`2d882180 00000000`00000004 : nvstor!NvStorIntPortDpcSingleDevice+0x59
fffff805`35a73b80 fffff805`3080781e : fffff805`2d885240 ffffe181`c79c9000 00000000`00000000 ffffe181`00000002 : nvstor!NvStorDpcForIsr+0x11
fffff805`35a73bb0 fffff805`30806b04 : 00000000`00000000 00000000`00000000 00000000`0000002a 00000000`00000e76 : nt!KiExecuteAllDpcs+0x30e
fffff805`35a73d20 fffff805`309fcac5 : 00000000`00000000 fffff805`2d882180 ffff9200`ac551c80 00000000`00270000 : nt!KiRetireDpcList+0x1f4
fffff805`35a73fb0 fffff805`309fc8b0 : 000000e5`0d87f3ec fffff805`308ec5ca 00000000`00000000 000000e5`0d87f688 : nt!KxRetireDpcList+0x5
ffffcf8c`e6b33c00 fffff805`309fc165 : 00000000`00270000 fffff805`309f6dd1 000002c4`c583c958 ffffe181`00000000 : nt!KiDispatchInterruptContinue
ffffcf8c`e6b33c30 fffff805`309f6dd1 : 000002c4`c583c958 ffffe181`00000000 ffffcf8c`e6b33cc0 ffffcf8c`e6b33cc0 : nt!KiDpcInterruptBypass+0x25
ffffcf8c`e6b33c40 00007ffc`33c2dae7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiChainedDispatch+0xb1
000000e5`0d87f160 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`33c2dae7


SYMBOL_NAME: nvstor!NvStorSpinLockAcquire+60

MODULE_NAME: nvstor

IMAGE_NAME: nvstor.sys

IMAGE_VERSION: 10.6.0.23

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 60

FAILURE_BUCKET_ID: 0x133_DPC_nvstor!NvStorSpinLockAcquire

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {eba06ed9-d58e-aea9-1ac7-ff753a2eebb0}

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

0: kd> lmvm nvstor
Browse full module list
start end module name
fffff805`34a20000 fffff805`34a4a000 nvstor # (pdb symbols) C:\ProgramData\Dbg\sym\nvstor.pdb\232DE2BB1F114159816A0AA31CBCFC201\nvstor.pdb
Loaded symbol image file: nvstor.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\nvstor.sys\5355649B2a000\nvstor.sys
Image path: \SystemRoot\System32\drivers\nvstor.sys
Image name: nvstor.sys
Browse all global symbols functions data
Timestamp: Mon Apr 21 21:34:03 2014 (5355649B)
CheckSum: 000345F3
ImageSize: 0002A000
File version: 10.6.0.23
Product version: 10.6.0.23
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: NVIDIA Corporation
ProductName: NVIDIA nForce(TM) SATA Driver
InternalName: NVIDIA nForce(TM) SATA Driver
OriginalFilename: nvstor.sys
ProductVersion: 10.6.0.23
FileVersion: 10.6.0.23 (PART_L3.131021-1012)
FileDescription: NVIDIA® nForce(TM) Sata Performance Driver
LegalCopyright: Copyright(C) 2001-2011 NVIDIA Corporation
Diskten kaynaklı bir problem var halihazırda. Diskinizi biraz gözlemleyin. Acaba depolama ile alakalı bir hata alacak mı diye.
@Enes3078 hocam çok ilginç bir vaka ile karşı karşıyayız. İki hatanın da oluşmasını tetikleyen şey aslında NVIDIA nForce sürücüsü. Storport tabanlı olduğu için bu kart "Storage Port" Driver hata vermiş. Yardımcı olur musunuz?
nForce ağ bağdaştırıcılarında gösteriyor.
 

Dosya Ekleri

  • nforce.PNG
    nforce.PNG
    7,3 KB · Görüntüleme: 24

Geri
Yukarı