AMD A10 7890K Sistem Chrome kullanırken mavi ekran hatası

Katılım
22 Ağustos 2015
Mesajlar
1.826
Makaleler
2
Çözümler
13
  • AMD A10 7890K soket FM2+ Wraith soğutucu 4.1GHz 4MB önbellek 95W 28nm işlemci.
  • ASUS A68HM-K AMD A68H 2400 MHz(OC) DDR3 soket FM2+ mATX anakart.
  • Corsair CP-9020096 VS450 builderseries 450W 80+PSU.
  • Kingston Savage 4 GB DDR3 2400MHz RAM.
  • WD Blue WD2500JS 250 GB.
  • Windows 10 2004.

321313.JPG


Ekran Alıntısı2.JPG
Chrome kullanırken bu hata ile karşılaşıyorum.
 
Son düzenleme:
  • AMD A10 7890K soket FM2+ Wraith soğutucu 4.1GHz 4MB önbellek 95W 28nm işlemci.
  • ASUS A68HM-K AMD A68H 2400 MHz(OC) DDR3 soket FM2+ mATX anakart.
  • Corsair CP-9020096 VS450 builderseries 450W 80+PSU.
  • Kingston Savage 4 GB DDR3 2400MHz RAM.
  • WD Blue WD2500JS 250 GB.
  • Windows 10 2004.

Eki Görüntüle 647607

Eki Görüntüle 647608
Chrome kullanırken bu hata ile karşılaşıyorum.

Windows 10'u 64 bite geçirin. Yine hata alırsanız donanımsal bir sorun olabilir.
 
Sistemimde 4 GB RAM var. 64 biti daha önce kullandım ve sistemde HDD olmasından dolayı yavaşlamalar oldu.
32 bit gayet stabil ve 64 bit gereksinimi duyan programlar veya oyunlar çalıştırmadığım için 64 bite geçmek istemiyorum.
Minidump dosyalarına güvendiğim için ekran görüntüsü almadım.
Eklediğim dosyalardan 64 bite geçin mi çıkıyor? 🤔
 
Ekran kartınızda görünüyor sorun. Tabi sizin durumunuzda işlemcideki grafik birimine yöneliyoruz. DDU ile mevcut olanı kaldırıp WHQL diye belirtilen sürücüsünü kurun. Kaspersky'yi de güncelleyin.
 
AMD GPU sürücünü güncelle.
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: c0000005, The exception code that was not handled
Arg2: 969e7fc0, The address that the exception occurred at
Arg3: b3c2f878, Exception Record Address
Arg4: b3c2f420, Context Record Address

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

ReadVirtual: 80507288 not properly sign extended
ReadVirtual: 80507288 not properly sign extended
ReadVirtual: 80507288 not properly sign extended
ReadVirtual: 80507288 not properly sign extended
ReadVirtual: 80507288 not properly sign extended
ReadVirtual: 80507288 not properly sign extended
ReadVirtual: 80507288 not properly sign extended
ReadVirtual: 80507288 not properly sign extended
ReadVirtual: 80507288 not properly sign extended
ReadVirtual: 80507288 not properly sign extended
ReadVirtual: 80507288 not properly sign extended
ReadVirtual: 80507288 not properly sign extended
ReadVirtual: 80507288 not properly sign extended
ReadVirtual: 80507288 not properly sign extended
ReadVirtual: 80507288 not properly sign extended
ReadVirtual: 80507288 not properly sign extended
ReadVirtual: 80507288 not properly sign extended

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Write


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  19041.1.x86fre.vb_release.191206-1406

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  2012

BIOS_DATE:  07/06/2020

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  A68HM-K

BASEBOARD_VERSION:  Rev X.0x

DUMP_TYPE:  2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: ffffffff969e7fc0

BUGCHECK_P3: ffffffffb3c2f878

BUGCHECK_P4: ffffffffb3c2f420

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

FAULTING_IP: 
dxgmms2!VIDMM_GLOBAL::DestroyOneAllocation+184
969e7fc0 8954241c        mov     dword ptr [esp+1Ch],edx

EXCEPTION_RECORD:  b3c2f878 -- (.exr 0xffffffffb3c2f878)
ExceptionAddress: 969e7fc0 (dxgmms2!VIDMM_GLOBAL::DestroyOneAllocation+0x00000184)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 0000001c
Attempt to write to address 0000001c

CONTEXT:  b3c2f420 -- (.cxr 0xffffffffb3c2f420)
eax=00000000 ebx=d1715b90 ecx=00000000 edx=95f84188 esi=cb086104 edi=d07fe918
eip=969e7fc0 esp=b3c2f9d0 ebp=b3c2faa8 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
dxgmms2!VIDMM_GLOBAL::DestroyOneAllocation+0x184:
969e7fc0 8954241c        mov     dword ptr [esp+1Ch],edx ss:0010:b3c2f9ec=d1715b90
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: 1004

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 38

CPU_STEPPING: 1

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

FOLLOWUP_IP: 
dxgmms2!VIDMM_GLOBAL::DestroyOneAllocation+184
969e7fc0 8954241c        mov     dword ptr [esp+1Ch],edx

BUGCHECK_STR:  AV

WRITE_ADDRESS: Unable to read MiSystemVaType memory at 82ed8d54
 0000001c 

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

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

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  00000001

EXCEPTION_PARAMETER2:  0000001c

ANALYSIS_SESSION_HOST:  DESKTOP-GULEPCP

ANALYSIS_SESSION_TIME:  08-25-2020 08:38:14.0321

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from 969fde8c to 969e7fc0

STACK_TEXT:  
b3c2faa8 969fde8c cd246968 d1715b90 00000000 dxgmms2!VIDMM_GLOBAL::DestroyOneAllocation+0x184
b3c2fabc 969b31ec cd246968 d1715b90 b3c2fba4 dxgmms2!VIDMM_GLOBAL::DestroyAllocation+0x12
b3c2facc 94cef6d9 cd246968 00000000 d1715b90 dxgmms2!VidMmDestroyAllocation+0x1a
b3c2fba4 94cf1a85 c6edd2a0 85564940 855f2680 dxgkrnl!DXGDEVICE::DestroyDeferredAllocations+0x3c9
b3c2fbe8 82d04de8 979b7490 00000000 855f2680 dxgkrnl!DxgkpDeferredDestructionWork+0x77
b3c2fc38 82ce291a 85564940 b6b3f2ac 00000000 nt!ExpWorkerThread+0xf8
b3c2fc70 82d8d9cd 82d04cf0 85564940 00000000 nt!PspSystemThreadStartup+0x4a
b3c2fc7c 00000000 00000000 00000001 00000000 nt!KiThreadStartup+0x15


THREAD_SHA1_HASH_MOD_FUNC:  ad9d3476f84d73ed70f373b21ce5d9a07394f80c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  adfe5d229c6719f81f949e129609e62e26f75054

THREAD_SHA1_HASH_MOD:  4dfdfbfdc4dd488ab99fa5b2dd182292bd6e83ca

FAULT_INSTR_CODE:  1c245489

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms2!VIDMM_GLOBAL::DestroyOneAllocation+184

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  31045d4e

IMAGE_VERSION:  10.0.19041.450

STACK_COMMAND:  .cxr 0xffffffffb3c2f420 ; kb

BUCKET_ID_FUNC_OFFSET:  184

FAILURE_BUCKET_ID:  AV_dxgmms2!VIDMM_GLOBAL::DestroyOneAllocation

BUCKET_ID:  AV_dxgmms2!VIDMM_GLOBAL::DestroyOneAllocation

PRIMARY_PROBLEM_CLASS:  AV_dxgmms2!VIDMM_GLOBAL::DestroyOneAllocation

TARGET_TIME:  2020-08-20T10:17:51.000Z

OSBUILD:  19041

OSSERVICEPACK:  450

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x86

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  191206-1406

BUILDLAB_STR:  vb_release

BUILDOSVER_STR:  10.0.19041.1.x86fre.vb_release.191206-1406

ANALYSIS_SESSION_ELAPSED_TIME:  b29c

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_dxgmms2!vidmm_global::destroyoneallocation

FAILURE_ID_HASH:  {4e73fa52-c790-a648-4bd4-084a2b509fd0}

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

ReadVirtual: 80507288 not properly sign extended
 
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.

Technopat Haberler

Geri
Yukarı