Çözüldü 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
Katılım
16 Ağustos 2019
Mesajlar
2.432
Çözümler
31
Daha fazla  
Sistem Özellikleri
RTX 4060 8GB
R7 7840HS
32GB Ram
1TB M.2 SSD
Cinsiyet
Erkek
Meslek
ÇAYCI
Kod:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false
   AllowNugetMSCredentialProviderInstall : false
   AllowParallelInitializationOfLocalRepositories : true

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.203 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\090123-9843-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
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff802`02213000 PsLoadedModuleList = 0xfffff802`02e3d3d0
Debug session time: Fri Sep  1 14:28:45.013 2023 (UTC + 3:00)
System Uptime: 0 days 0:01:01.967
Loading Kernel Symbols
...............................................................
................................................................
.............................................................
Loading User Symbols

Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`0260fc40 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffd682`d4834680=000000000000007e
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80203bcf2be, The address that the exception occurred at
Arg3: ffffd682d4835678, Exception Record Address
Arg4: ffffd682d4834eb0, Context Record Address

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


KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 8296

    Key  : Analysis.Elapsed.mSec
    Value: 30405

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1000007e

    Key  : Failure.Bucket
    Value: AV_VRF_pci!PciProgramMsiXInterrupt

    Key  : Failure.Hash
    Value: {9c39d54c-2420-de54-e39e-2f11f92d7216}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80203bcf2be

BUGCHECK_P3: ffffd682d4835678

BUGCHECK_P4: ffffd682d4834eb0

FILE_IN_CAB:  090123-9843-01.dmp

EXCEPTION_RECORD:  ffffd682d4835678 -- (.exr 0xffffd682d4835678)
ExceptionAddress: fffff80203bcf2be (pci!PciProgramMsiXInterrupt+0x00000000000000ae)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT:  ffffd682d4834eb0 -- (.cxr 0xffffd682d4834eb0)
rax=00000000fee0100c rbx=ffffb50d102f41b0 rcx=0000000000000004
rdx=0000000000000000 rsi=0000000000000000 rdi=ffffd682d48358f8
rip=fffff80203bcf2be rsp=ffffd682d48358b0 rbp=ffffd682d4835920
 r8=0000000000000004  r9=0000000000000000 r10=0000000000000000
r11=ffffd682d4835770 r12=0000000000000004 r13=ffffb50d102f4538
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
pci!PciProgramMsiXInterrupt+0xae:
fffff802`03bcf2be f3a5            rep movs dword ptr [rdi],dword ptr [rsi]
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff80202f0e390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 0000000000000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek  u olamaz %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

EXCEPTION_STR:  0xc0000005

STACK_TEXT:
ffffd682`d48358b0 fffff802`03bcce42     : 00000000`00000025 ffffb50d`102f41b0 ffffb50d`102f41b0 00000000`00000000 : pci!PciProgramMsiXInterrupt+0xae
ffffd682`d4835960 fffff802`03c02751     : ffff8e00`4283ffff ffffb50d`102fffff 00000000`0000ffff ffffb50d`102f41b0 : pci!PciProgramInterruptResource+0x122
ffffd682`d48359d0 fffff802`02571355     : 00000000`00000000 ffffb50d`0fdfcfa0 00000000`00000000 fffff802`038bc5c0 : pci!PciDeviceStartWorker+0x741
ffffd682`d4835c40 fffff802`02463545     : ffffb50d`067c1080 ffffb50d`067c1080 fffff802`02571220 00000000`00000000 : nt!IopProcessWorkItem+0x135
ffffd682`d4835cb0 fffff802`025216f5     : ffffb50d`067c1080 00000000`00000080 ffffb50d`0667a0c0 00018000`a91b3ffe : nt!ExpWorkerThread+0x105
ffffd682`d4835d50 fffff802`02618878     : ffffa400`6b7e0180 ffffb50d`067c1080 fffff802`025216a0 8a61e0e2`17c78314 : nt!PspSystemThreadStartup+0x55
ffffd682`d4835da0 00000000`00000000     : ffffd682`d4836000 ffffd682`d4830000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  pci!PciProgramMsiXInterrupt+ae

MODULE_NAME: pci

IMAGE_NAME:  pci.sys

IMAGE_VERSION:  10.0.19041.3324

STACK_COMMAND:  .cxr 0xffffd682d4834eb0 ; kb

BUCKET_ID_FUNC_OFFSET:  ae

FAILURE_BUCKET_ID:  AV_VRF_pci!PciProgramMsiXInterrupt

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9c39d54c-2420-de54-e39e-2f11f92d7216}

Followup:     MachineOwner
---------
 
Son düzenleyen: Moderatör:
 

Dump dosyasanın Debug edilmiş hali atmama gerek var mı?
 

Bu konuyu görüntüleyen kullanıcılar

Technopat Haberler

Geri
Yukarı