Çözüldü SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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

Arocyn

Hectopat
Katılım
28 Mart 2018
Mesajlar
2.050
Çözümler
18
Yer
Burdur Krallığı
Bugün canlı dersteyken mavi ekran yedim. Hatanın isminin fotoğrafını çekemeden PC yeniden başlattı. Arka planda; mining yazılımı, MSI Afterburner, Adobe Connect, Streamlabs OBS aktif olarak çalışıyordu.
Sistem Özelliklerim:
-AMD R7 3700X
-Asus TUF B450M-Plus
-Team TUF 3200 MHz 2*8 RAM
-Asus ROG Strix RTX 2060
-Adata SU630 480GB SSD
-Corsair VS550W 80+ PSU
MiniDUMP dosyam:
 
Çözüm
1) Ekran kartı sürücünüzü DDU ile kaldırıp güncel ve WHQL logolu sürücü kurun. DDU kullanım rehberi ve indirmeniz gereken sürücünün linki aşağıda yer alıyor.



2) BIOS güncelleyin. 3002 sürümlü en güncel BIOS dosyasının indirme linki aşağıda yer alıyor.


Sorun çözülürse belirtmeyi unutmayın.

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: fffff8014fa7f7d8, The address that the exception occurred at
Arg3: ffff98821dc44ef8, Exception Record Address
Arg4: ffff98821dc44730, Context Record Address

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullClassPtr

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 7405

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 36909

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

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

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

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


BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8014fa7f7d8

BUGCHECK_P3: ffff98821dc44ef8

BUGCHECK_P4: ffff98821dc44730

EXCEPTION_RECORD: ffff98821dc44ef8 -- (.exr 0xffff98821dc44ef8)
ExceptionAddress: fffff8014fa7f7d8 (dxgmms2!VIDMM_PAGE_TABLE::CommitPageTable+0x0000000000000080)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080

CONTEXT: ffff98821dc44730 -- (.cxr 0xffff98821dc44730)
rax=0000000000000000 rbx=0000000000000000 rcx=18c85e197e820000
rdx=0000000000000000 rsi=ffff98821dc455d0 rdi=ffffa90e5b8f0b00
rip=fffff8014fa7f7d8 rsp=ffff98821dc45130 rbp=00000000002ccd40
r8=0000000000000000 r9=00000000035c0000 r10=0000000000000000
r11=ffff98821dc44fa0 r12=000000000000014f r13=ffffa90e5082d110
r14=ffffce8e39dca628 r15=0000000000000140
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
dxgmms2!VIDMM_PAGE_TABLE::CommitPageTable+0x80:
fffff801`4fa7f7d8 488b8280000000 mov rax,qword ptr [rdx+80h] ds:002b:00000000`00000080=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

READ_ADDRESS: fffff80146efa390: 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
0000000000000080

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

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffff9882`1dc45130 fffff801`4fa94133 : 00000000`00000000 ffffa90e`646a2060 ffffce8e`39dca600 fffff801`4fa7f9ca : dxgmms2!VIDMM_PAGE_TABLE::CommitPageTable+0x80
ffff9882`1dc45180 fffff801`4fa921cd : 00000000`00000000 00000000`02f50000 00000000`00000001 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x23b
ffff9882`1dc45220 fffff801`4fabd3dc : 00000000`00000000 ffffa90e`5082d110 00000000`00000001 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x77d
ffff9882`1dc45390 fffff801`4fa9148a : 00000000`00000001 ffffa90e`5082d110 00000000`00000000 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x2b98c
ffff9882`1dc45500 fffff801`4fa90374 : ffffce8e`49e19110 ffffa90e`00000001 00000000`00000000 00000000`00000000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x2f6
ffff9882`1dc45680 fffff801`4fa8728d : ffffb901`00000000 00000000`00000000 ffff9882`00000000 ffff9882`1dc45bf0 : dxgmms2!VIDMM_GLOBAL::pageInOneAllocation+0x3b4
ffff9882`1dc457a0 fffff801`4faac56e : 00000000`00000002 00000000`00989680 ffffa90e`49c0b120 00000000`00000001 : dxgmms2!VIDMM_GLOBAL::processDeferredCommand+0x106d
ffff9882`1dc45a00 fffff801`4fab6759 : ffffa90e`49c0b050 ffffce8e`39ca7001 00000000`00000000 00000000`079a1a00 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xe5e
ffff9882`1dc45be0 fffff801`464f53b5 : ffffce8e`39ca7080 fffff801`4fab6750 ffffa90e`49c0b050 000f8067`bcbbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
ffff9882`1dc45c10 fffff801`465fe348 : ffffb901`e949c180 ffffce8e`39ca7080 fffff801`464f5360 00441f0f`fffab1ec : nt!PspSystemThreadStartup+0x55
ffff9882`1dc45c60 00000000`00000000 : ffff9882`1dc46000 ffff9882`1dc40000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VIDMM_PAGE_TABLE::CommitPageTable+80

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.964

STACK_COMMAND: .cxr 0xffff98821dc44730 ; kb

BUCKET_ID_FUNC_OFFSET: 80

FAILURE_BUCKET_ID: AV_dxgmms2!VIDMM_PAGE_TABLE::CommitPageTable

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {2121ae52-4ac6-50d9-66f4-8ed5966cd3e8}

Followup: MachineOwner
---------[/CODE]
1) Ekran kartı sürücünüzü DDU ile kaldırıp güncel ve WHQL logolu sürücü kurun. DDU kullanım rehberi ve indirmeniz gereken sürücünün linki aşağıda yer alıyor.



2) BIOS güncelleyin. 3002 sürümlü en güncel BIOS dosyasının indirme linki aşağıda yer alıyor.


Sorun çözülürse belirtmeyi unutmayın.

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: fffff8014fa7f7d8, The address that the exception occurred at
Arg3: ffff98821dc44ef8, Exception Record Address
Arg4: ffff98821dc44730, Context Record Address

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullClassPtr

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 7405

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 36909

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

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

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

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


BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8014fa7f7d8

BUGCHECK_P3: ffff98821dc44ef8

BUGCHECK_P4: ffff98821dc44730

EXCEPTION_RECORD: ffff98821dc44ef8 -- (.exr 0xffff98821dc44ef8)
ExceptionAddress: fffff8014fa7f7d8 (dxgmms2!VIDMM_PAGE_TABLE::CommitPageTable+0x0000000000000080)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080

CONTEXT: ffff98821dc44730 -- (.cxr 0xffff98821dc44730)
rax=0000000000000000 rbx=0000000000000000 rcx=18c85e197e820000
rdx=0000000000000000 rsi=ffff98821dc455d0 rdi=ffffa90e5b8f0b00
rip=fffff8014fa7f7d8 rsp=ffff98821dc45130 rbp=00000000002ccd40
r8=0000000000000000 r9=00000000035c0000 r10=0000000000000000
r11=ffff98821dc44fa0 r12=000000000000014f r13=ffffa90e5082d110
r14=ffffce8e39dca628 r15=0000000000000140
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
dxgmms2!VIDMM_PAGE_TABLE::CommitPageTable+0x80:
fffff801`4fa7f7d8 488b8280000000 mov rax,qword ptr [rdx+80h] ds:002b:00000000`00000080=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

READ_ADDRESS: fffff80146efa390: 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
0000000000000080

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

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffff9882`1dc45130 fffff801`4fa94133 : 00000000`00000000 ffffa90e`646a2060 ffffce8e`39dca600 fffff801`4fa7f9ca : dxgmms2!VIDMM_PAGE_TABLE::CommitPageTable+0x80
ffff9882`1dc45180 fffff801`4fa921cd : 00000000`00000000 00000000`02f50000 00000000`00000001 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x23b
ffff9882`1dc45220 fffff801`4fabd3dc : 00000000`00000000 ffffa90e`5082d110 00000000`00000001 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x77d
ffff9882`1dc45390 fffff801`4fa9148a : 00000000`00000001 ffffa90e`5082d110 00000000`00000000 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x2b98c
ffff9882`1dc45500 fffff801`4fa90374 : ffffce8e`49e19110 ffffa90e`00000001 00000000`00000000 00000000`00000000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x2f6
ffff9882`1dc45680 fffff801`4fa8728d : ffffb901`00000000 00000000`00000000 ffff9882`00000000 ffff9882`1dc45bf0 : dxgmms2!VIDMM_GLOBAL::pageInOneAllocation+0x3b4
ffff9882`1dc457a0 fffff801`4faac56e : 00000000`00000002 00000000`00989680 ffffa90e`49c0b120 00000000`00000001 : dxgmms2!VIDMM_GLOBAL::processDeferredCommand+0x106d
ffff9882`1dc45a00 fffff801`4fab6759 : ffffa90e`49c0b050 ffffce8e`39ca7001 00000000`00000000 00000000`079a1a00 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xe5e
ffff9882`1dc45be0 fffff801`464f53b5 : ffffce8e`39ca7080 fffff801`4fab6750 ffffa90e`49c0b050 000f8067`bcbbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
ffff9882`1dc45c10 fffff801`465fe348 : ffffb901`e949c180 ffffce8e`39ca7080 fffff801`464f5360 00441f0f`fffab1ec : nt!PspSystemThreadStartup+0x55
ffff9882`1dc45c60 00000000`00000000 : ffff9882`1dc46000 ffff9882`1dc40000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VIDMM_PAGE_TABLE::CommitPageTable+80

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.964

STACK_COMMAND: .cxr 0xffff98821dc44730 ; kb

BUCKET_ID_FUNC_OFFSET: 80

FAILURE_BUCKET_ID: AV_dxgmms2!VIDMM_PAGE_TABLE::CommitPageTable

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {2121ae52-4ac6-50d9-66f4-8ed5966cd3e8}

Followup: MachineOwner
---------[/CODE]
 
Çözüm
Kendi analizim sonucunda hatanın grafik kartı kökenli olduğunu düşünüyorum eğer doğru bir analiz yapabildiysem. Araştırdığım kadarı ile ekran kartına boyundan yüksek bir iş yükleme ile oluşabiliyormuş. Ben ise mining yaparken canlı ders de ekran kaydı alıyordum. Öneriler arasında grafik sürücüsünün silinip tekrar kurulması var. Ama dxdiag ekranında bir sorun var da demiyor. Bu da beni şüpheye düşürdü.
@Enes3078 sen de aynı şeyi dediğine göre doğru analiz yapmışım sayılır. Teşekkürler uygulayacağım dediklerini. :D
 
Evet, analiziniz doğru. Sorunun devamı halinde mesajınızın bildirimi gelsin diye bu mesajı bırakayım. Uygulayıp 2-3 gün sonra geri dönütte bulunursanız sevinirim.
 
Evet, analiziniz doğru. Sorunun devamı halinde mesajınızın bildirimi gelsin diye bu mesajı bırakayım. Uygulayıp 2-3 gün sonra geri dönütte bulunursanız sevinirim.
Hocam 2 gün oldu sıkıntı çıkaramadı. Normalde BIOS güncellemek için çekiniyordum sorun yaşarım diye bu olay ile güncellemiş de oldum. Ama her şeyi yaptıktan sonra ekran kartımda mining yaparken 125W güç tüketiyordu o 85W'a düştü MH/s değişimi yaşamadım sonra yeniden başlattığımda PC'yi tekrar 125W'lara döndü güç tüketimi. Bi o konu garibime geldi.
 

Geri
Yukarı