SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) Mavi Ekran Hatası

Katılım
14 Ağustos 2010
Mesajlar
79.057
Makaleler
289
Çözümler
2.268
Yer
İstanbul
Daha fazla  
Cinsiyet
Erkek
Profil Kapağı
1522743131
Bu hatadaki sorun nvhda64v.sys dosyasından kaynaklanıyor gibi. Bu dosya NVIDIA High Definition Audio sürücüsü. Sorunu gidermek için:
  • DDU ile ekran kartı sürücüsünü kaldırın.
  • Güncel NVIDIA sürücüsünü temiz kurulum ile kurun.
  • Komut satırını açıp şu komutla bilgisayarı kapatın: shutdown.exe /s /t 0
  • Bilgisayarı açtığınızda sorun kalmamalı.

Kod:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80569105e0e, The address that the exception occurred at
Arg3: fffff887b7b825b8, Exception Record Address
Arg4: fffff887b7b81e00, Context Record Address

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


KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullPtr

    Key  : AV.Fault
    Value: Read


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  17763.1.amd64fre.rs5_release.180914-1434

DUMP_TYPE:  2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80569105e0e

BUGCHECK_P3: fffff887b7b825b8

BUGCHECK_P4: fffff887b7b81e00

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

FAULTING_IP:
nvhda64v+25e0e
fffff805`69105e0e 488b01          mov     rax,qword ptr [rcx]

EXCEPTION_RECORD:  fffff887b7b825b8 -- (.exr 0xfffff887b7b825b8)
ExceptionAddress: fffff80569105e0e (nvhda64v+0x0000000000025e0e)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT:  fffff887b7b81e00 -- (.cxr 0xfffff887b7b81e00)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=ffffdf8a2a1a2010
rip=fffff80569105e0e rsp=fffff887b7b827f0 rbp=ffffdf8a2a1a2588
 r8=0000000000000000  r9=0000000000000000 r10=fffff8056acceb08
r11=fffff887b7b82968 r12=ffffdf8a345dd000 r13=ffffdf8a2a1a2010
r14=ffffdf8a2a1a24f8 r15=ffffdf8a345dd060
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nvhda64v+0x25e0e:
fffff805`69105e0e 488b01          mov     rax,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

PROCESS_NAME:  System

CURRENT_IRQL:  0

FOLLOWUP_IP:
nvhda64v+25e0e
fffff805`69105e0e 488b01          mov     rax,qword ptr [rcx]

BUGCHECK_STR:  AV

READ_ADDRESS: GetUlongFromAddress: unable to read from fffff806426d54c0
fffff80642750390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
 0000000000000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ANALYSIS_SESSION_HOST:  DESKTOP-NG9H4F5

ANALYSIS_SESSION_TIME:  02-24-2019 11:43:51.0327

ANALYSIS_VERSION: 10.0.18317.1001 amd64fre

LAST_CONTROL_TRANSFER:  from ffffdf8a2a1a24f8 to fffff80569105e0e

STACK_TEXT: 
fffff887`b7b827f0 ffffdf8a`2a1a24f8 : fffff887`00000000 fffff805`690e3900 fffff805`6acceb00 00000000`00000000 : nvhda64v+0x25e0e
fffff887`b7b827f8 fffff887`00000000 : fffff805`690e3900 fffff805`6acceb00 00000000`00000000 fffff805`69105dba : 0xffffdf8a`2a1a24f8
fffff887`b7b82800 fffff805`690e3900 : fffff805`6acceb00 00000000`00000000 fffff805`69105dba 00000000`00000000 : 0xfffff887`00000000
fffff887`b7b82808 fffff805`6acceb00 : 00000000`00000000 fffff805`69105dba 00000000`00000000 ffffdf8a`318d2010 : nvhda64v+0x3900
fffff887`b7b82810 00000000`00000000 : fffff805`69105dba 00000000`00000000 ffffdf8a`318d2010 ffffdf8a`345dd000 : portcls!CXdvPortWaveRT::`vftable'+0x28


THREAD_SHA1_HASH_MOD_FUNC:  71126ea9bf2a74f4665dd26c1721cc60e785c7d7

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  2e27dded3665b012b510923e1aeb1bb5b699293c

THREAD_SHA1_HASH_MOD:  baa88f4894224ecd0f9a1c5d85db6847354723fc

FAULT_INSTR_CODE:  ff018b48

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvhda64v+25e0e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvhda64v

IMAGE_NAME:  nvhda64v.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5c3ed2c0

STACK_COMMAND:  .cxr 0xfffff887b7b81e00 ; kb

BUCKET_ID_FUNC_OFFSET:  25e0e

FAILURE_BUCKET_ID:  AV_nvhda64v!unknown_function

BUCKET_ID:  AV_nvhda64v!unknown_function

PRIMARY_PROBLEM_CLASS:  AV_nvhda64v!unknown_function

TARGET_TIME:  2019-02-22T18:56:18.000Z

OSBUILD:  17763

OSSERVICEPACK:  316

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  180914-1434

BUILDLAB_STR:  rs5_release

BUILDOSVER_STR:  10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME:  1a7f0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_nvhda64v!unknown_function

FAILURE_ID_HASH:  {c13eb64a-9cde-4879-da51-f7aaf1513c01}

Followup:     MachineOwner
---------
 
Selamlar Recep hocam. Aynı sorunu AMD'nin kartlarında da verebiliyor ve malesef AMD'nin kartlarında bu hatayı chipset arızasından dolayı veriyor.
 
Son düzenleyen: Moderatör:
Uyarı! Bu konu 6 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.

Yeni konular

Geri
Yukarı