Çözüldü Kmode Exceptıon Not Handled mavi ekran hatası

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

nues

Femtopat
Katılım
9 Ekim 2020
Mesajlar
10
Daha fazla  
Cinsiyet
Erkek
İşlemci Ryzen7 3700X.
Ekran kartı: MSI RTX 2070 Super OC.
Anakart MSI X570-A PRO.

2 Adet mavi ekran hatası aldım ve minidump dosyalarını aşağı tarafta sizinle paylaştım bu konu hakkında yardımcı olabilirseniz çok sevinirim.

minidump.rar

drive.google.com drive.google.com
 
Çözüm
Murat5038
nues dedi:
Sonlara doğru PC'de donma meydana geldi.
Genişletmek için tıkla...
Sıkıntı yok mavi ekran vermediyse.

BIOS güncellememişsin.
Temiz önyükleme yapın, zamanlanmış görevleri de kapatın.

Aeldra Metin2 kulalnıyorsun o sorun çıkarıyor. İmzamdan KIS 2021 ile sistemi tam tarama yapın.
Windows da güncel değil 2004 sürümüne geçin.
Tarihe göre sırala Puana göre sırala
MSI Afterburner kaldırın. CPU-Z kaldırın. Memtest86 ile bellek testi yapınız.
Bu içeriği görüntülemek için üçüncü taraf çerezlerini yerleştirmek için izninize ihtiyacımız olacak.
Daha detaylı bilgi için, çerezler sayfamıza bakınız.
Kod: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff805685ca877, The address that the exception occurred at
Arg3: fffff48956770f18, Parameter 0 of the exception
Arg4: ffffb70017338930, Parameter 1 of the exception

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


WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffb70017338930

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba

FAULTING_IP:
nt!ExpInterlockedPopEntrySListFault+0
fffff805`685ca877 498b08          mov     rcx,qword ptr [r8]

EXCEPTION_PARAMETER1:  fffff48956770f18

EXCEPTION_PARAMETER2:  ffffb70017338930

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  obs64.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

EXCEPTION_RECORD:  0000008400041000 -- (.exr 0x8400041000)
Cannot read Exception record @ 0000008400041000

TRAP_FRAME:  0003709600017069 -- (.trap 0x3709600017069)
Unable to read trap frame at 00037096`00017069

LAST_CONTROL_TRANSFER:  from fffff805686a5de7 to fffff805685c2990

STACK_TEXT: 
ffffb700`17338088 fffff805`686a5de7 : 00000000`0000001e ffffffff`c0000005 fffff805`685ca877 fffff489`56770f18 : nt!KeBugCheckEx
ffffb700`17338090 fffff805`685da5c6 : fffff805`685ca877 fffff805`6850c1fb fffff489`56771150 ffffb700`17338930 : nt!KiFatalFilter+0x1f
ffffb700`173380d0 fffff805`6859d97c : fffff805`00000002 fffff489`56772220 fffff489`5676d000 fffff489`56773000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16
ffffb700`17338110 fffff805`685cb782 : fffff489`56772220 ffffb700`173386f0 00000000`00000000 00000000`0010001f : nt!_C_specific_handler+0xac
ffffb700`17338180 fffff805`68489555 : 00000000`00000024 00000000`00000000 ffffb700`173386f0 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0x12
ffffb700`173381b0 fffff805`6848d66e : fffff489`56770f18 ffffb700`17338e30 fffff489`56770f18 ffffc982`2280ccc0 : nt!RtlDispatchException+0x4a5
ffffb700`17338900 fffff805`685c3802 : 00000084`00041000 0004504a`0001700f 00037096`00017069 000f718c`000410f5 : nt!KiDispatchException+0x16e
ffffb700`17338fb0 fffff805`685c37d0 : fffff805`685d4956 ffffc982`2d732fac 00000000`00000000 00000000`00000003 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff489`56770dd8 fffff805`685d4956 : ffffc982`2d732fac 00000000`00000000 00000000`00000003 fffff805`6c9dd046 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff489`56770de0 fffff805`685d06e0 : a3d70a3d`70a3d701 fffff805`766ebf11 ffffc982`24430b00 ffffc982`24430bd0 : nt!KiExceptionDispatch+0x116
fffff489`56770fc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x320


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kbase
    ffff825132e476a9-ffff825132e476ae  6 bytes - win32kbase!DirectComposition::CAnimationMarshaler::SetReferenceProperty+49
    [ ff 15 01 e1 19 00:e8 f2 db 20 00 90 ]
    ffff825132e47729-ffff825132e4772a  2 bytes - win32kbase!SfmSignalTokenEvent+19 (+0x80)
    [ 48 ff:4c 8b ]
    ffff825132e47730-ffff825132e47733  4 bytes - win32kbase!SfmSignalTokenEvent+20 (+0x07)
    [ 0f 1f 44 00:e8 eb dc 20 ]
12 errors : !win32kbase (ffff825132e476a9-ffff825132e47733)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8071dbca877, The address that the exception occurred at
Arg3: fffffc8bc735bf18, Parameter 0 of the exception
Arg4: ffffe581d95e6930, Parameter 1 of the exception

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


WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffe581d95e6930

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba

FAULTING_IP:
nt!ExpInterlockedPopEntrySListFault+0
fffff807`1dbca877 498b08          mov     rcx,qword ptr [r8]

EXCEPTION_PARAMETER1:  fffffc8bc735bf18

EXCEPTION_PARAMETER2:  ffffe581d95e6930

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  obs64.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER:  from fffff8071dca5de7 to fffff8071dbc2990

STACK_TEXT: 
ffffe581`d95e6088 fffff807`1dca5de7 : 00000000`0000001e ffffffff`c0000005 fffff807`1dbca877 fffffc8b`c735bf18 : nt!KeBugCheckEx
ffffe581`d95e6090 fffff807`1dbda5c6 : fffff807`1dbca877 fffff807`1db0c1fb fffffc8b`c735c150 ffffe581`d95e6930 : nt!KiFatalFilter+0x1f
ffffe581`d95e60d0 fffff807`1db9d97c : fffff807`00000002 fffffc8b`c735d220 fffffc8b`c7358000 fffffc8b`c735e000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16
ffffe581`d95e6110 fffff807`1dbcb782 : fffffc8b`c735d220 ffffe581`d95e66f0 00000000`00000000 00000000`0010001f : nt!_C_specific_handler+0xac
ffffe581`d95e6180 fffff807`1da89555 : 00000000`00000024 00000000`00000000 ffffe581`d95e66f0 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0x12
ffffe581`d95e61b0 fffff807`1da8d66e : fffffc8b`c735bf18 ffffe581`d95e6e30 fffffc8b`c735bf18 ffffa589`4e527e80 : nt!RtlDispatchException+0x4a5
ffffe581`d95e6900 fffff807`1dbc3802 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16e
ffffe581`d95e6fb0 fffff807`1dbc37d0 : fffff807`1dbd4956 ffffa589`4d91045c 00000000`00000000 00000000`00000003 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffffc8b`c735bdd8 fffff807`1dbd4956 : ffffa589`4d91045c 00000000`00000000 00000000`00000003 fffff807`205dd046 : nt!KiExceptionDispatchOnExceptionStackContinue
fffffc8b`c735bde0 fffff807`1dbd06e0 : a3d70a3d`70a3d701 fffff807`2a2ebf11 ffffa589`4e44e600 ffffa589`4e44e600 : nt!KiExceptionDispatch+0x116
fffffc8b`c735bfc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x320


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8071dbca5b6-fffff8071dbca5ba  5 bytes - nt!tcpxsum+96
    [ 41 ff e1 cc cc:e8 05 8c 18 00 ]
    fffff8071dbca969-fffff8071dbca96d  5 bytes - nt!RtlpCaptureContext+9 (+0x3b3)
    [ ff e2 cc cc cc:e8 72 87 18 00 ]
    fffff8071dbcaace-fffff8071dbcaad2  5 bytes - nt!RtlpCaptureContext2+e (+0x165)
    [ ff e2 cc cc cc:e8 0d 86 18 00 ]
15 errors : !nt (fffff8071dbca5b6-fffff8071dbcaad2)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
---------
 
Artı 0 Eksi
Assecreed dedi:
MSI Afterburner kaldırın. CPU-Z kaldırın. Memtest86 ile bellek testi yapınız.
Bu içeriği görüntülemek için üçüncü taraf çerezlerini yerleştirmek için izninize ihtiyacımız olacak.
Daha detaylı bilgi için, çerezler sayfamıza bakınız.
Kod: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff805685ca877, The address that the exception occurred at
Arg3: fffff48956770f18, Parameter 0 of the exception
Arg4: ffffb70017338930, Parameter 1 of the exception

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


WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffffb70017338930

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba

FAULTING_IP:
nt!ExpInterlockedPopEntrySListFault+0
fffff805`685ca877 498b08          mov     rcx,qword ptr [r8]

EXCEPTION_PARAMETER1:  fffff48956770f18

EXCEPTION_PARAMETER2:  ffffb70017338930

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  obs64.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

EXCEPTION_RECORD:  0000008400041000 -- (.exr 0x8400041000)
Cannot read Exception record @ 0000008400041000

TRAP_FRAME:  0003709600017069 -- (.trap 0x3709600017069)
Unable to read trap frame at 00037096`00017069

LAST_CONTROL_TRANSFER:  from fffff805686a5de7 to fffff805685c2990

STACK_TEXT:
ffffb700`17338088 fffff805`686a5de7 : 00000000`0000001e ffffffff`c0000005 fffff805`685ca877 fffff489`56770f18 : nt!KeBugCheckEx
ffffb700`17338090 fffff805`685da5c6 : fffff805`685ca877 fffff805`6850c1fb fffff489`56771150 ffffb700`17338930 : nt!KiFatalFilter+0x1f
ffffb700`173380d0 fffff805`6859d97c : fffff805`00000002 fffff489`56772220 fffff489`5676d000 fffff489`56773000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16
ffffb700`17338110 fffff805`685cb782 : fffff489`56772220 ffffb700`173386f0 00000000`00000000 00000000`0010001f : nt!_C_specific_handler+0xac
ffffb700`17338180 fffff805`68489555 : 00000000`00000024 00000000`00000000 ffffb700`173386f0 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0x12
ffffb700`173381b0 fffff805`6848d66e : fffff489`56770f18 ffffb700`17338e30 fffff489`56770f18 ffffc982`2280ccc0 : nt!RtlDispatchException+0x4a5
ffffb700`17338900 fffff805`685c3802 : 00000084`00041000 0004504a`0001700f 00037096`00017069 000f718c`000410f5 : nt!KiDispatchException+0x16e
ffffb700`17338fb0 fffff805`685c37d0 : fffff805`685d4956 ffffc982`2d732fac 00000000`00000000 00000000`00000003 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff489`56770dd8 fffff805`685d4956 : ffffc982`2d732fac 00000000`00000000 00000000`00000003 fffff805`6c9dd046 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff489`56770de0 fffff805`685d06e0 : a3d70a3d`70a3d701 fffff805`766ebf11 ffffc982`24430b00 ffffc982`24430bd0 : nt!KiExceptionDispatch+0x116
fffff489`56770fc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x320


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kbase
    ffff825132e476a9-ffff825132e476ae  6 bytes - win32kbase!DirectComposition::CAnimationMarshaler::SetReferenceProperty+49
    [ ff 15 01 e1 19 00:e8 f2 db 20 00 90 ]
    ffff825132e47729-ffff825132e4772a  2 bytes - win32kbase!SfmSignalTokenEvent+19 (+0x80)
    [ 48 ff:4c 8b ]
    ffff825132e47730-ffff825132e47733  4 bytes - win32kbase!SfmSignalTokenEvent+20 (+0x07)
    [ 0f 1f 44 00:e8 eb dc 20 ]
12 errors : !win32kbase (ffff825132e476a9-ffff825132e47733)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8071dbca877, The address that the exception occurred at
Arg3: fffffc8bc735bf18, Parameter 0 of the exception
Arg4: ffffe581d95e6930, Parameter 1 of the exception

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


WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffffe581d95e6930

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba

FAULTING_IP:
nt!ExpInterlockedPopEntrySListFault+0
fffff807`1dbca877 498b08          mov     rcx,qword ptr [r8]

EXCEPTION_PARAMETER1:  fffffc8bc735bf18

EXCEPTION_PARAMETER2:  ffffe581d95e6930

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  obs64.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER:  from fffff8071dca5de7 to fffff8071dbc2990

STACK_TEXT:
ffffe581`d95e6088 fffff807`1dca5de7 : 00000000`0000001e ffffffff`c0000005 fffff807`1dbca877 fffffc8b`c735bf18 : nt!KeBugCheckEx
ffffe581`d95e6090 fffff807`1dbda5c6 : fffff807`1dbca877 fffff807`1db0c1fb fffffc8b`c735c150 ffffe581`d95e6930 : nt!KiFatalFilter+0x1f
ffffe581`d95e60d0 fffff807`1db9d97c : fffff807`00000002 fffffc8b`c735d220 fffffc8b`c7358000 fffffc8b`c735e000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16
ffffe581`d95e6110 fffff807`1dbcb782 : fffffc8b`c735d220 ffffe581`d95e66f0 00000000`00000000 00000000`0010001f : nt!_C_specific_handler+0xac
ffffe581`d95e6180 fffff807`1da89555 : 00000000`00000024 00000000`00000000 ffffe581`d95e66f0 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0x12
ffffe581`d95e61b0 fffff807`1da8d66e : fffffc8b`c735bf18 ffffe581`d95e6e30 fffffc8b`c735bf18 ffffa589`4e527e80 : nt!RtlDispatchException+0x4a5
ffffe581`d95e6900 fffff807`1dbc3802 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16e
ffffe581`d95e6fb0 fffff807`1dbc37d0 : fffff807`1dbd4956 ffffa589`4d91045c 00000000`00000000 00000000`00000003 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffffc8b`c735bdd8 fffff807`1dbd4956 : ffffa589`4d91045c 00000000`00000000 00000000`00000003 fffff807`205dd046 : nt!KiExceptionDispatchOnExceptionStackContinue
fffffc8b`c735bde0 fffff807`1dbd06e0 : a3d70a3d`70a3d701 fffff807`2a2ebf11 ffffa589`4e44e600 ffffa589`4e44e600 : nt!KiExceptionDispatch+0x116
fffffc8b`c735bfc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x320


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8071dbca5b6-fffff8071dbca5ba  5 bytes - nt!tcpxsum+96
    [ 41 ff e1 cc cc:e8 05 8c 18 00 ]
    fffff8071dbca969-fffff8071dbca96d  5 bytes - nt!RtlpCaptureContext+9 (+0x3b3)
    [ ff e2 cc cc cc:e8 72 87 18 00 ]
    fffff8071dbcaace-fffff8071dbcaad2  5 bytes - nt!RtlpCaptureContext2+e (+0x165)
    [ ff e2 cc cc cc:e8 0d 86 18 00 ]
15 errors : !nt (fffff8071dbca5b6-fffff8071dbcaad2)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
---------
Genişletmek için tıkla...

minidump dosyasını kontrol etme şansınız varmıdır ?
 
Artı 0 Eksi
Assecreed dedi:
Dump dosyalarına bakmasam MSI Afterburner kullandığınızı nereden bileceğim. Dediklerimi yapınız.
Genişletmek için tıkla...

Şu an testi yapıyorum ,ek bilgi olarak bu iki mavi ekran hatasını AMD chipseti güncelledikten sonra sadece OBS programı yani sadece yayındayken alıyorum ( son 3 günde her yayın açtığımda )teşekkürler.
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
nues dedi:
Şuan testi yapıyorum ek bilgi olarak bu iki mavi ekran hatasını amd chipseti güncelledikten sonra sadece OBS programı yani sadece yayındayken alıyorum ( son 3 günde her yayın açtığımda )teşekkürler
Genişletmek için tıkla...
İki mavi ekranda da Obs'nin çalıştığı görünüyor zaten.
 
Artı 0 Eksi

Dosya Ekleri

  • 32D92EB0-A706-41F9-8173-154641A8A833.jpeg
    32D92EB0-A706-41F9-8173-154641A8A833.jpeg
    142,6 KB · Görüntüleme: 57
  • A7864B1F-3C51-4158-833D-DE38687DB8BB.jpeg
    A7864B1F-3C51-4158-833D-DE38687DB8BB.jpeg
    73,5 KB · Görüntüleme: 55
Son düzenleyen: Moderatör:
Artı 0 Eksi
Assecreed dedi:
O zaman sorun OBS ile ilgili olabilir. İki farklı marka RAM kullanıyorsanız birini çıkarın.
Genişletmek için tıkla...

Chipseti güncellemiştim fakat BIOS 1 yıl oncekınki kalmıştı bugun biosuda guncelledim. OBS programınada guncelleme gelmiş onu da guncelledım, şu an test ediyorum, RAM'ler G.Skill Ripjaws 16 GB Dual kit 3200MHz.
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
BIOS güncel değil güncelleyin. Güncelledim deidğiniz sürüm bu değilse bunu yükleyin.

CPUZ, MSI araçları, RyzenMaster kaldır. OSB güncellemişsin zaten.

Vanguard kaldır eğer çözülmezse veya defender yerine farklı bir AV kullan. Windows güncellemelerini de kontrol et.
 
Artı 0 Eksi
Uyarı! Bu konu 5 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.

Benzer konular

Adem Ali Karakavak
  • Soru
KMODE EXCEPTION NOT HANDLED mavi ekran hatası
2
Mesaj
12
Görüntüleme
2.799
Adem Ali Karakavak
Adem Ali Karakavak
HikmetGven4TR
  • Soru
"Kmode exceptıon not handled" mavi ekran hatası
Mesaj
4
Görüntüleme
552
HikmetGven4TR
HikmetGven4TR
C
  • Soru
Kmode Exception Not Handled Mavi Ekran
Mesaj
3
Görüntüleme
751
283156
2
V
  • Soru
Windows 10 KMODE Exception Not Handled Mavi Ekran
Mesaj
1
Görüntüleme
1.237
mouseduzeldigaliba
mouseduzeldigaliba
emirtpc
  • Soru
"KMODE EXCEPTION NOT HANDLED" Mavi Ekran Hatası
Mesaj
5
Görüntüleme
1.526
283156
2

Technopat Haberler

Yeni konular

Yeni mesajlar

Geri
Yukarı