Çözüldü ASUS TUF Gaming A15 FA506NF sistemde çeşitli mavi ekran hataları

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.

fthkhrmn

Centipat
Katılım
4 Ağustos 2024
Mesajlar
315
Çözümler
1
Yer
Bursa
Daha fazla  
Sistem Özellikleri
AMD Ryzen 7 7800X3D NVİDİA Geforce RTX4080 32GB Ram 1TB M2.ssd
Cinsiyet
Erkek
Meslek
Teknik Destek.
Arkadaşlar merhaba. Bilgisayarımı üç kez formatlarım neredeyse başlattığımda en az 2-3 kez mavi ekran yiyorum. Donanımsal bir arızam yok hepsini test ettim sağlıklı. Şu minidumplara bir bakar mısınız? KMODE_EXCEPTİON_NOT_HANDLED, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, IRQL_NOT_LESS_OR_EQUAL ve PAGE_FAULT_İN_NOT_PAGE_AREA. Dediğim gibi donanımsal bir sorun yok. Memtest ile test ettim CrystalDiskInfo'da HD Tuneda sorun yok. CPU GPU iyi durumda.
ASUS TUF Gaming A15 FA506NF
Windows 11
Eğer sorun hala çözülemiyorsas flash bellek ile Windows 10 temiz kurulum yapacağım.

Diğer dumpı gönderemiyorum o yüzden WinDbg'deki analizi yapıştıracağım.
(Sadece bilgisayarı ilk başlattığımda yiyorum bilginiz olsun)

MODE_EXCEPTION_NOT_HANDLED (1e)
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: FffffffFC000001D, The exception code that was not handled
Arg2: FffFF8026C83e032, The address that the exception occurred at
Arg3: 000000000000002F, Parameter 0 of the exception
Arg4: 0000FFFFF8026CB3, Parameter 1 of the exception

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

*** WARNING: Unable to verify timestamp for rt68cx21x64.sys
*************************************************************************
* *
  • *
  • 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: ExceptionRecord *
  • *

*************************************************************************
*************************************************************************
* *
  • *
  • 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: ContextRecord *
  • *

*************************************************************************
*************************************************************************
* *
  • *
  • 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: ExceptionRecord *
  • *

*************************************************************************
*************************************************************************
* *
  • *
  • 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: ContextRecord *
  • *

*************************************************************************

KEY_VALUES_STRING: 1

Key: Analysis. CPU. MSec
Value: 1796

Key: Analysis. Elapsed. MSec
Value: 25692

Key: Analysis. IO. Other. MB
Value: 12

Key: Analysis. IO. Read. MB
Value: 1

Key: Analysis. IO. Write. MB
Value: 16

Key: Analysis. Init. CPU. MSec
Value: 359

Key: Analysis. Init. Elapsed. MSec
Value: 11613

Key: Analysis. Memory.commitPeak. MB
Value: 128

Key: Analysis. Version. DbgEng
Value: 10.0.27829.1001

Key: Analysis. Version. Description
Value: 10.2503.24.01 AMD64fre

Key: Analysis. Version. Ext
Value: 1.2503.24.1

Key: Bugcheck. Code. KiBugCheckData
Value: 0x1e

Key: Bugcheck. Code. LegacyAPI
Value: 0x1e

Key: Bugcheck. Code. TargetModel
Value: 0x1e

Key: Failure. Bucket
Value: 0x1E_C000001D_BAD_IP_NetAdapterCx!ExecutionContext::QueueWorkerThread

Key: Failure. Exception. IP. Address
Value: 0xfffff8026c83e032

Key: Failure. Exception. IP. Module
Value: NT

Key: Failure. Exception. IP. Offset
Value: 0x23e032

Key: Failure. Hash
Value: {A7092D73-FC7C-49A4-6A51-F4CC1076C527}

Key: Failure. Source.commitId
Value: 7F292DAA20052A308C6b4AD310BB7319EC319A80

Key: Failure. Source. ControlType
Value: Git

Key: Failure. Source. FileLine
Value: 1143

Key: Failure. Source. FilePath
Value: minio\netcx\ec\lib\executioncontext.cpp

Key: Failure. Source. Project
Value: OS

Key: Failure. Source. RepoId
Value: OS. 2020

Key: Failure. Source. RepoUrl
Value: https://dev.azure.com/microsoft

Key: Failure. Source. SourceServerCommand
Value: dev.azure.com/microsoft/OS/_apis/git/repositories/os.2020/items?path=/minio/netcx/ec/lib/executioncontext.cpp&versionDescriptor.versionType=commit&versionDescriptor.version=7f292daa20052a308c6b4ad310bb7319ec319a80&versionDescriptor.options=none&download=true&api-version=2.0

Key: Stack. Pointer
Value: PRCBException

Key: WER. OS. Branch
Value: Ni_release

Key: WER. OS. Version
Value: 10.0.22621.1

BUGCHECK_CODE: 1E

BUGCHECK_P1: FffffffFC000001D

BUGCHECK_P2: FFFFF8026C83E032

BUGCHECK_P3: 2F

BUGCHECK_P4: FFFFF8026CB3

FILE_IN_CAB: 052325-8812-01.dmp

FAULTING_THREAD: FffFF8026D34C6C0

EXCEPTION_PARAMETER1: 000000000000002F

EXCEPTION_PARAMETER2: 0000FFFFF8026CB3

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

FAILED_INSTRUCTION_ADDRESS:
NT! KiExitDispatcher+252
Fffff802'6C83E032 0F84DC030000 je NT! KiExitDispatcher+0x634 (fffff802'6C83E414)

STACK_TEXT:
Fffff802'69F6a0e8 fffff802'6cb650AA: 00000000'0000001E ffffffff'C000001D fffff802'6C83E032 00000000'0000002F: NT! KeBugCheckEx
Fffff802'69F6a0F0 fffff802'6ca37362: Fffff802'69F6A900 fffff802'69F6a1C0 fffff802'6C600000 fffff802'6ca30eee: NT! HvlpVtlCallExceptionHandler+0x22
Fffff802'69F6A130 fffff802'6C84DA03: Fffff802'69F54950 fffff802'69F53be8 fffff802'6ca30eee fffff802'6C6F2FB8: NT! RtlpExecuteHandlerForException+0x12
Fffff802'69F6A160 fffff802'6C8CF15e: Ffffffff'ffffffff fffff802'69F53C90 fffff802'69F53C90 fffff802'69F6A900: NT! RtlDispatchException+0x2F3
Fffff802'69F6a8D0 fffff802'6ca2D2b2: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: NT! KiDispatchException+0x1AE
Fffff802'69F6afb0 fffff802'6ca2D280: Fffff802'6ca418F5 00000000'00000000 0000000B'0000000B 00000000'00000000: NT! KxExceptionDispatchOnExceptionStack+0x12
Fffff802'69F53AA8 fffff802'6ca418F5: 00000000'00000000 0000000B'0000000B 00000000'00000000 00000000'00000001: NT! KiExceptionDispatchOnExceptionStackContinue
Fffff802'69F53AB0 fffff802'6ca3AE2D: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: NT! KiExceptionDispatch+0x135
Fffff802'69F53C90 fffff802'6C83E032: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: NT! KiInvalidOpcodeFault+0x32D
Fffff802'69F53e20 fffff802'6C83D86B: Ffffa98a'03FC94e8 ffffa98a'00000000 00000000'00000000 fffff802'6C898FF7: NT! KiExitDispatcher+0x252
Fffff802'69F541D0 fffff802'B3987E90: Fffff802'00000000 00000000'00000000 fffff802'6C96A540 ffffa98a'0bde01C0: NT! KeSetEvent+0xeb
(Inline Function) ---------------- : ---------------- ---------------- ---------------- --------'--------: NetAdapterCx! KWaitEventBase<wistd: İntegral_constant<enum _EVENT_TYPE, 1> >:Set+0x18 [onecore\internal\minwin\priv_sdk\inc\net\ndis\rtl\kwaitevent.h @ 42]
Fffff802'69F54260 fffff802'B3987337: Fffff780'00000340 0000007D'1CF8122a 00000000'0061B502 fffff802'6C898FF7: NetAdapterCx! ExecutionContext: QueueWorkerThread+0x2C [minio\netcx\ec\lib\executioncontext.cpp @ 1143]
(Inline Function) ---------------- : ---------------- ---------------- ---------------- --------'--------: NetAdapterCx! KAcquireSpinLock: IsAcquired+0x1F [onecore\internal\minwin\priv_sdk\inc\net\ndis\rtl\kspinlock.h @ 148]
(Inline Function) ---------------- : ---------------- ---------------- ---------------- --------'--------: NetAdapterCx! KAcquireSpinLock:{dtor}+0x1F [onecore\internal\minwin\priv_sdk\inc\net\ndis\rtl\kspinlock.h @ 121]
Fffff802'69F54290 fffff802'B3987243: 00000000'00000000 ffffa98a'03FC9050 00000000'00000000 00000000'00000001: NetAdapterCx! ExecutionContext: NotifyCommon+0xb3 [minio\netcx\ec\lib\executioncontext.cpp @ 694]
(Inline Function) ---------------- : ---------------- ---------------- ---------------- --------'--------: NetAdapterCx! ExecutionContext: NotifyEx+0x34 [minio\netcx\ec\lib\executioncontext.cpp @ 587]
Fffff802'69F542D0 fffff802'B396EC05: Fffff802'6C96A760 00000002'00000008 00000000'00000000 fffff802'68a7ff80: NetAdapterCx! ExecutionContext: Notify+0x57 [minio\netcx\ec\lib\executioncontext.cpp @ 569]
(Inline Function) ---------------- : ---------------- ---------------- ---------------- --------'--------: NetAdapterCx! NxQueue: NotifyMorePacketsAvailable+0xc [minio\netcx\adapter\nxqueue.cpp @ 577]
Fffff802'69F54300 fffff802'B38D5580: Ffffa989'F549EDF0 0000007D'1CF842be 00000000'0061B504 fffff802'6C898FF7: NetAdapterCx! İmp_NetRxQueueNotifyMoreReceivedPacketsAvailable+0x55 [minio\netcx\adapter\nxqueueapi.cpp @ 175]
Fffff802'69F54330 ffffa989'F549EDF0: 0000007D'1CF842be 00000000'0061B504 fffff802'6C898FF7 ffffa989'F549EBF0: RT68CX21x64+0x45580
Fffff802'69F54338 0000007D'1CF842be: 00000000'0061B504 fffff802'6C898FF7 ffffa989'F549EBF0 fffff802'B38D33df: 0xffffa989`f549edf0
Fffff802'69F54340 00000000'0061B504: Fffff802'6C898FF7 ffffa989'F549EBF0 fffff802'B38D33df 00000000'00000000: 0x0000007d`1cf842be
Fffff802'69F54348 fffff802'6C898FF7: Ffffa989'F549EBF0 fffff802'B38D33df 00000000'00000000 fffff802'68A77180: 0x61b504
Fffff802'69F54350 fffff802'6F8D6D2D: Ffffa989'F549EBF0 fffff802'69F54A50 ffffc000'16b7be70 00000000'00000006: NT! KeQueryInterruptTimePrecise+0x57
Fffff802'69F543a0 fffff802'6F8D6CD5: 00000003'0000231A 00000000'00000000 ffffa989'F549EBF0 fffff802'69F54670: Wdf01000! FxInterrupt: DpcHandler+0x49 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 75]
Fffff802'69F543D0 fffff802'6C8b3F6C: 00000000'00000000 ffffc000'16b7be70 fffff802'00000000 fffff802'D69b3C4b: Wdf01000! FxInterrupt: _InterruptDpcThunk+0x35 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 410]
Fffff802'69F54410 fffff802'6C8b2F5a: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: NT! KiExecuteAllDpcs+0x42C
Fffff802'69F54950 fffff802'6ca30eee: 00000000'00000000 fffff802'68A77180 fffff802'6D34C6C0 ffffa989'FC599080: NT! KiRetireDpcList+0x1ba
Fffff802'69F54C00 00000000'00000000: Fffff802'69F55000 fffff802'69F4e000 00000000'00000000 00000000'00000000: NT! KiIdleLoop+0x9e

FAULTING_SOURCE_LINE: minio\netcx\ec\lib\executioncontext.cpp

FAULTING_SOURCE_FILE: minio\netcx\ec\lib\executioncontext.cpp

FAULTING_SOURCE_LINE_NUMBER: 1143

FAULTING_SOURCE_SRV_COMMAND: https://dev.azure.com/microsoft/OS/...or.options=none&download=true&api-version=2.0

FAULTING_SOURCE_COMMIT_ID: 7F292DAA20052A308C6b4AD310BB7319EC319A80

FAULTING_SOURCE_CONTROL_TYPE: Git

FAULTING_SOURCE_PROJECT: OS

FAULTING_SOURCE_REPO_ID: OS. 2020

FAULTING_SOURCE_REPO_URL: https://dev.azure.com/microsoft

FAULTING_SOURCE_CODE:
No Source found for 'minio\netcx\ec\lib\executioncontext.cpp'

SYMBOL_NAME: NetAdapterCx! ExecutionContext: QueueWorkerThread+2C

MODULE_NAME: NetAdapterCx

IMAGE_NAME: NetAdapterCx.sys

IMAGE_VERSION: 10.0.22621.1989

STACK_COMMAND: Process /r /p 0xfffff8026d348f40;.thread 0xfffff8026d34c6c0; KB

BUCKET_ID_FUNC_OFFSET: 2C

FAILURE_BUCKET_ID: 0x1E_C000001D_BAD_IP_NetAdapterCx!ExecutionContext::QueueWorkerThread

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: Ni_release

OSPLATFORM_TYPE: X64

OSNAME: Windows 10

FAILURE_ID_HASH: {A7092D73-FC7C-49A4-6A51-F4CC1076C527}

Followup: MachineOwner
 
Son düzenleyen: Moderatör:
Çözüm
Bu testleri'de yap ama dediğim gibi çok yüksek donanımsal sorun var. Anakart değişmesi gerekecek.

@turko35408 Hocam yine verdi. Okunamadığından direkt analizi atıyorum.

Windbg
SYMBOL_NAME: nt!RtlGetInterruptTimePrecise+16

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.26100.4061

STACK_COMMAND: .process /r /p 0xfffff803d69cdf80; .thread 0xfffff803d69d0640 ; kb

BUCKET_ID_FUNC_OFFSET: 16

FAILURE_BUCKET_ID: AV_nt!RtlGetInterruptTimePrecise

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5dd2e292-1d62-5c15-5ff7-8e7b6af374e7}

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


Windbg
SYMBOL_NAME: nt!MiUpdateLargePageCandidateValue+1e

MODULE_NAME: nt

IMAGE_VERSION: 10.0.26100.4061

STACK_COMMAND: .cxr 0xfffff8033fcc48d0 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 1e

FAILURE_BUCKET_ID: AV_nt!MiUpdateLargePageCandidateValue

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {47d6c9d8-5d94-3e07-9301-698c7043f1bb}

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


Eğer bu iki hatayıda çözebilirsek komple çözülmüş olacak. Yinemi bellekle alakalı çıktı ya. Orjinal Ramdeyim şu an

@turko35408 Hocam yine verdi. Okunamadığından direkt analizi atıyorum.

WinDbg
SYMBOL_NAME: NT! RtlGetInterruptTimePrecise+16

MODULE_NAME: NT

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.26100.4061

STACK_COMMAND: Process /r /p 0xfffff803d69cdf80;.thread 0xfffff803d69d0640; KB

BUCKET_ID_FUNC_OFFSET: 16

FAILURE_BUCKET_ID: AV_nt! RtlGetInterruptTimePrecise

OSPLATFORM_TYPE: X64

OSNAME: Windows 10

FAILURE_ID_HASH: {5dd2E292-1D62-5C15-5FF7-8E7b6af374e7}

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

WinDbg
SYMBOL_NAME: NT! MiUpdateLargePageCandidateValue+1e

MODULE_NAME: NT

IMAGE_VERSION: 10.0.26100.4061

STACK_COMMAND: Cxr 0xfffff8033fcc48d0; KB

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 1E

FAILURE_BUCKET_ID: AV_nt! MiUpdateLargePageCandidateValue

OSPLATFORM_TYPE: X64

OSNAME: Windows 10

FAILURE_ID_HASH: {47D6C9D8-5D94-3E07-9301-698C7043F1bb}

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

Eğer bu iki hatayı da çözebilirsek komple çözülmüş olacak. Yinemi bellekle alakalı çıktı ya. Orijinal Ramdeyim şu an

2 sürücü 3 Windows'tan bir hata çıktı. Büyük ihtimal orijinal RAM'im bozuk.
 
Son düzenleme:
Hocam RAM'leri tek tek test edin. Dizüstü PC'lerde RAM uyumu önemlidir.

 
Hocam RAM'leri tek tek test edin. Dizüstü PC'lerde RAM uyumu önemlidir.

@claus @turko35408 Hocam merhaba, bilgisayarı windows 10 yaptım, kullanırken herhangi bir sorun olmuyor fakat bilgisayarı başlatırken mavi ekran felan vermiyor, yüklenirken donuyor tekrar deniyor sonra onarım moduna geçiyor, sonra açılıyor. size bir minidump dosyası göndereceğim rica etsem onu inceleyebilirmisin? Sadece güvenli modda bu hatayı alıyorum SYSTEM_SERVİCE_EXCEPTiON. MEMTEST sonuçları olumlu bir sorun çıkmadı

 
Sürücü sorunu var. Ayrıca takılı olan 2 RAM var sanırım. Net modellerini belirt. Tek tek taktığında sorun oluyor mu ? Neden Win 10 kullanıyorsun ? Ayrıca yüksek ihtimal donanımsal sorun var.
Hocam Ramleri denediğimde ikisindede mavi ekran veriyordu win11 de. ramlerimin modelleri şunlar:
Ekran Alıntısı.PNG
Ekran Alıntısı2.PNG

Ayrıca Crystaldıskınfoda ssd sağlam çıktı. bilgisayar 7 aylık bilgin olsun hocam
4 kere format attım flaş bellekle windows 11. Şimidede windows 10 kullanıyorum sanki bilgisayar daha kararlı ve hızlı çalışıyor gibi.
çünkü win11 kullanırken her 15 dk de bir mavi ekran yiyordum şu an böyle bir sorun yok. @claus Sizce ne yöntemler denemeliyim 5.format. İsterseniz Hard disk sentinel ile bir test yapayım?
 
Son düzenleme:
Bu testleri'de yap ama dediğim gibi çok yüksek donanımsal sorun var. Anakart değişmesi gerekecek.

 
Çözüm
Bu Testleri'de yap ama dediğim gibi çok yüksek donanımsal sorun var. Anakart değişmesi gerekecek.


@claus Hocam sağlık %98 çıktı. 51 derecede çalışıyor SSD. Tek çare servise vermem gerekecek galiba.
 

Dosya Ekleri

  • 4.PNG
    4.PNG
    131,9 KB · Görüntüleme: 14
Son düzenleme:

Technopat Haberler

Geri
Yukarı