Çözüldü Valorant 1.09 güncellemesi WHEA_UNCORRECTABLE_ERROR mavi ekran hatası

pulse0827 · 3 Ekim 2020

Arkadaşlar merhaba,

Valorant oyununda son güncellemeden sonra 2 gündür mavi ekran hatasıyla karşı karşıya kalıyorum. Başka oyunlardan mavi ekran almayınca hatanın Riot'un 1.09 güncellemesi ile meydana geldiğini düşündüm. Mavi ekranda WHEA_UNCORRECTABLE_ERROR şeklinde uyarı verdi. Hatta PC her oyuna girdiğimde hep aynı zaman diliminde hataya geçiyor. Yaklaşık 12-15 dk civarında. Yani hemen de gerçekleşmiyor bu sorun.

Konu ile alakalı yardımcı olabilecek arkadaşlar varsa sevinirim. Denemediğim yöntem kalmadı

pulse0827 · 9 Ekim 2020

Enes3078 dedi:
Neden böyle bir şey yaptınız? İşletim sistemi sürümünü düşürmeye gerek yok. Uygun sürücüler kurulu olması yeterli. Ayrıca @pulse0827 benim yazdıklarımı uyguladıktan sonra sorun çözüldü mü çözülmedi mi? Çözülmediyse yeni minidump dosyalarını atarsınız.

Hocam söylediklerinizi BIOS dışında harfiyen yaptım ancak yine hata verdi.

Bence de işletim sistemini düşürmeye gerek yok. Çünkü galiba ben çözdüm olayı 1 saattir neredeyse oyun açık oynadım ve mavi ekran almadım . Buradan Riot Games ekibine çoooookkk teşekkür ediyorum. Helal olsun vallahi

Şimdi bilet attığım kişi benden birkaç kişisel dosya istedi ve yapmamı istediği birkaç şey vardı ama bunların arasında en çok dikkatimi çeken "sentinel Security solution antivirüs yazılımı" 'nı kaldırmamı istemesiydi. Muhtemelen bu yazılım 1.09 güncellemesiyle çakıştı devre dışı bıraktım ve sorunum düzeldi diye düşünüyorum siz de deneyin .

Bu yazılım aslında zararlı değil ancak güvenlik setifikaları nedeniyle Vanguard dosyaları ile uyumsuz çalıştığını sanıyorum. Uninstall yapmayın çünkü bu bir şeyi değiştirmez. Windows Update bunu güncelleyecektir. Sadece şunu yapın:

1)Görev yöneticisinden sentinel LDK license Manager'ı bulup kapatın.

2)Windows + r tuşlarına basarak çalıştır'ı açın.

3)Gelen ekranda MSConfig yazıp enter'layın.

4)üstteki sekmelerden Hizmetler'e gelin.

5)Sentinel LDK license Manager'ı bulup tikini kaldırın. Uygula ve tamam dedikten sonra PC'yi yeniden başlatın.

Böylece bilgisayarı her açtığınızda otomatik olarak başlamayacaktır.

Arkadaşlar dönüş yapın mutlaka ona göre başlığı "çözüldü" olarak değiştireyim. İnşallah faydasını görürsünüz

codefl0w · 3 Ekim 2020

Minidump Dosyalarını Paylaşın

23.06.2025 tarihinde yapılan güncel rehbere aşağıdaki linkten erişebilirsiniz: https://www.technopat.net/sosyal/konu/minidump-nedir-nasil-paylasilir.3817531/ Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi...

www.technopat.net

Assecreed · 3 Ekim 2020

Minidump Dosyalarını Paylaşın

23.06.2025 tarihinde yapılan güncel rehbere aşağıdaki linkten erişebilirsiniz: https://www.technopat.net/sosyal/konu/minidump-nedir-nasil-paylasilir.3817531/ Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi...

www.technopat.net

Bora Dere · 3 Ekim 2020

Öncelikle Windows'u ve BIOS'u güncelleyin.

ASUS TÃ¼rkiye

ASUS, dizÃ¼stÃ¼ bilgisayarlar, anakartlar, ekran kartlarÄ±, monitÃ¶rler, masaÃ¼stÃ¼ bilgisayarlar, sunucular, kablosuz Ã§Ã¶zÃ¼mler aÄ cihazlarÄ±nÄ±n olduÄu Ã¼rÃ¼nlerinde kaliteden asla Ã¶dÃ¼n vermeyen bir Åirkettir.

www.asus.com

Son zamanlarda cihazın içini termal macun yenilemek için falan açtınız mı? Ayrıca işlemciye UV gibi bir işlem yaptınız mı, oyun içi sıcaklık durumu nasıl?

Cevabıma anlam veremeyen arkadaşlar için: Konu sahibi başka bir konuda dosyalarını paylaşmıştı.

Valorant son güncelleme sonrası mavi ekran hatası

Arkadaşlar selamlar. Valorant'ı çıktığından beri sorunsuz olarak oynuyorum. Ancak 2 gün önce gelen güncelleme sonrası oyun içinde mavi ekran hatası veriyor. Çözümü var mıdır ya da yaşayanınız?

www.technopat.net

pulse0827 · 3 Ekim 2020

Minidump dosyası şu şekilde :

MiniDump-pulse.rar

drive.google.com

Assecreed · 3 Ekim 2020

Farklı marka RAM'ler kullanıyorsunuz. Bir tanesini çıkarıp RAM'lerin oyuna girin. Tekrar yerseniz takarsınız.

Kod:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error.
source that reported the error. Parameter 2 holds the address of the.
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception.
Arg2: ffffca8240d6f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000041136, Low order 32-bits of the MCi_STATUS value.

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

BUGCHECK_STR: 0x124_GenuineIntel.

CUSTOMER_CRASH_COUNT: 1.

DEFAULT_BUCKET_ID: CODE_CORRUPTION.

PROCESS_NAME: VALORANT-Win64.

CURRENT_IRQL: f.

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

STACK_TEXT:
fffff805`59882918 fffff805`566ff188 : 00000000`00000124 00000000`00000000 ffffca82`40d6f028 00000000`be200000 : nt!KeBugCheckEx.
fffff805`59882920 fffff805`57f81920 : ffffca82`405da350 00000000`00000000 ffffca82`40d6f028 00000000`00000000 : hal!HalBugCheckSystem+0xd8.
fffff805`59882960 fffff805`55f410a2 : ffffca82`405da350 fffff805`598829e9 00000000`00000000 ffffca82`40d6f028 : PSHED!PshedBugCheckSystem+0x10.
fffff805`59882990 fffff805`56700ae6 : fffff805`59882ab0 00000000`00000000 ffffca82`405da3a0 ffffca82`405da350 : nt!WheaReportHwError+0x382.
fffff805`59882a50 fffff805`56700f7a : 00000000`00000010 ffffca82`405da3a0 fffff805`59882c08 fffff805`59882e50 : hal!HalpMcaReportError+0x72.
fffff805`59882bb0 fffff805`56700e54 : ffffca82`3ecc96f0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2.
fffff805`59882c00 fffff805`567010c0 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0.
fffff805`59882c40 fffff805`56700168 : 00000000`00000000 fffff805`59882ed0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4.
fffff805`59882c70 fffff805`56701347 : ffffca82`3ecc96f0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c.
fffff805`59882ca0 fffff805`55ea4e40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37.
fffff805`59882cd0 fffff805`55dd13ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10.
fffff805`59882d00 fffff805`55dd106f : 00000000`00000000 00000000`00000000 0000021c`4ae3ff10 00000000`00000000 : nt!KxMcheckAbort+0x7a.
fffff805`59882e40 00007ff9`b0276d2b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x26f.
000000dc`5e71f880 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`b0276d2b.

STACK_COMMAND: kb.

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kbase.
ffff8dadfbc971f9-ffff8dadfbc971fe 6 bytes - win32kbase!DirectComposition::CAnimationMarshaler::SetReferenceProperty+49.
[ ff 15 b1 f5 19 00:e8 a2 f0 20 00 90 ]
ffff8dadfbc97269-ffff8dadfbc9726a 2 bytes - win32kbase!SfmSignalTokenEvent+19 (+0x70)
[ 48 ff:4c 8b ]
ffff8dadfbc97270-ffff8dadfbc97273 4 bytes - win32kbase!SfmSignalTokenEvent+20 (+0x07)
[ 0f 1f 44 00:e8 ab f1 20 ]
ffff8dadfbc983d5-ffff8dadfbc983d6 2 bytes - win32kbase!GreSfmDwmShutdown+35 (+0x1165)
[ 48 ff:4c 8b ]
ffff8dadfbc983dc-ffff8dadfbc983df 4 bytes - win32kbase!GreSfmDwmShutdown+3c (+0x07)
[ 0f 1f 44 00:e8 3f e0 20 ]
ffff8dadfbc983e5-ffff8dadfbc983e6 2 bytes - win32kbase!GreSfmDwmShutdown+45 (+0x09)
[ 48 ff:4c 8b ]
ffff8dadfbc983ec-ffff8dadfbc983ef 4 bytes - win32kbase!GreSfmDwmShutdown+4c (+0x07)
[ 0f 1f 44 00:e8 2f e0 20 ]
24 errors : !win32kbase (ffff8dadfbc971f9-ffff8dadfbc983ef)

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 *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error.
source that reported the error. Parameter 2 holds the address of the.
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception.
Arg2: ffffa98702f7f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000041136, Low order 32-bits of the MCi_STATUS value.

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

BUGCHECK_STR: 0x124_GenuineIntel.

CUSTOMER_CRASH_COUNT: 1.

DEFAULT_BUCKET_ID: CODE_CORRUPTION.

PROCESS_NAME: vgc.exe.

CURRENT_IRQL: f.

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

STACK_TEXT:
ffffd201`1b66ca58 fffff807`591a4188 : 00000000`00000124 00000000`00000000 ffffa987`02f7f028 00000000`be200000 : nt!KeBugCheckEx.
ffffd201`1b66ca60 fffff807`5d581920 : ffffa987`020f85e0 00000000`00000000 ffffa987`02f7f028 00000000`00000000 : hal!HalBugCheckSystem+0xd8.
ffffd201`1b66caa0 fffff807`595410a2 : ffffa987`020f85e0 ffffd201`1b66cb29 00000000`00000000 ffffa987`02f7f028 : PSHED!PshedBugCheckSystem+0x10.
ffffd201`1b66cad0 fffff807`591a5ae6 : ffffd201`1b66cbf0 00000000`00000001 ffffa987`020f8630 ffffa987`020f85e0 : nt!WheaReportHwError+0x382.
ffffd201`1b66cb90 fffff807`591a5f7a : 00000000`00000010 ffffa987`020f8630 ffffd201`1b66cd48 ffffd201`1b66cf90 : hal!HalpMcaReportError+0x72.
ffffd201`1b66ccf0 fffff807`591a5e54 : ffffa987`01ec97a0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2.
ffffd201`1b66cd40 fffff807`591a60c0 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0.
ffffd201`1b66cd80 fffff807`591a5168 : 00000000`00000000 ffffd201`1b66d010 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4.
ffffd201`1b66cdb0 fffff807`591a6347 : ffffa987`01ec97a0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c.
ffffd201`1b66cde0 fffff807`594a4e40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37.
ffffd201`1b66ce10 fffff807`593d13ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10.
ffffd201`1b66ce40 fffff807`593d106f : 00000000`00000000 00000000`00000000 00000000`fff6b6a1 00000000`00000000 : nt!KxMcheckAbort+0x7a.
ffffd201`1b66cf80 00007ff6`45627f38 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x26f.
00000033`605ff550 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`45627f38.

STACK_COMMAND: kb.

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kbase.
ffffa36180e971f9-ffffa36180e971fe 6 bytes - win32kbase!DirectComposition::CAnimationMarshaler::SetReferenceProperty+49.
[ ff 15 b1 f5 19 00:e8 a2 f0 20 00 90 ]
ffffa36180e97269-ffffa36180e9726a 2 bytes - win32kbase!SfmSignalTokenEvent+19 (+0x70)
[ 48 ff:4c 8b ]
ffffa36180e97270-ffffa36180e97273 4 bytes - win32kbase!SfmSignalTokenEvent+20 (+0x07)
[ 0f 1f 44 00:e8 ab f1 20 ]
ffffa36180e983d5-ffffa36180e983d6 2 bytes - win32kbase!GreSfmDwmShutdown+35 (+0x1165)
[ 48 ff:4c 8b ]
ffffa36180e983dc-ffffa36180e983df 4 bytes - win32kbase!GreSfmDwmShutdown+3c (+0x07)
[ 0f 1f 44 00:e8 3f e0 20 ]
ffffa36180e983e5-ffffa36180e983e6 2 bytes - win32kbase!GreSfmDwmShutdown+45 (+0x09)
[ 48 ff:4c 8b ]
ffffa36180e983ec-ffffa36180e983ef 4 bytes - win32kbase!GreSfmDwmShutdown+4c (+0x07)
[ 0f 1f 44 00:e8 2f e0 20 ]
24 errors : !win32kbase (ffffa36180e971f9-ffffa36180e983ef)

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 *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error.
source that reported the error. Parameter 2 holds the address of the.
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception.
Arg2: ffff930ab715b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fe200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000041136, Low order 32-bits of the MCi_STATUS value.

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

BUGCHECK_STR: 0x124_GenuineIntel.

CUSTOMER_CRASH_COUNT: 1.

DEFAULT_BUCKET_ID: CODE_CORRUPTION.

PROCESS_NAME: VALORANT-Win64.

CURRENT_IRQL: f.

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

STACK_TEXT:
ffffc901`5f130a58 fffff804`2dba4188 : 00000000`00000124 00000000`00000000 ffff930a`b715b028 00000000`fe200000 : nt!KeBugCheckEx.
ffffc901`5f130a60 fffff804`2ed81920 : ffff930a`b42f88c0 00000000`00000000 ffff930a`b715b028 00000000`00000000 : hal!HalBugCheckSystem+0xd8.
ffffc901`5f130aa0 fffff804`2df410a2 : ffff930a`b42f88c0 ffffc901`5f130b29 00000000`00000000 ffff930a`b715b028 : PSHED!PshedBugCheckSystem+0x10.
ffffc901`5f130ad0 fffff804`2dba5ae6 : ffffc901`5f130bf0 00000000`00000003 ffff930a`b42f8910 ffff930a`b42f88c0 : nt!WheaReportHwError+0x382.
ffffc901`5f130b90 fffff804`2dba5f7a : 00000000`00000010 ffff930a`b42f8910 ffffc901`5f130d48 ffffc901`5f130f90 : hal!HalpMcaReportError+0x72.
ffffc901`5f130cf0 fffff804`2dba5e54 : ffff930a`b40c9900 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2.
ffffc901`5f130d40 fffff804`2dba60c0 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0.
ffffc901`5f130d80 fffff804`2dba5168 : 00000000`00000000 ffffc901`5f131010 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4.
ffffc901`5f130db0 fffff804`2dba6347 : ffff930a`b40c9900 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c.
ffffc901`5f130de0 fffff804`2dea4e40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37.
ffffc901`5f130e10 fffff804`2ddd13ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10.
ffffc901`5f130e40 fffff804`2ddd106f : 00000000`00000000 00000000`00000000 00000031`202cda70 00000000`00000000 : nt!KxMcheckAbort+0x7a.
ffffc901`5f130f80 00007ff7`86530936 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x26f.
00000031`202cd9b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff7`86530936.

STACK_COMMAND: kb.

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kfull.
ffff8b10cfea8604-ffff8b10cfea8605 2 bytes - win32kfull!xxxSendTransformableMessageTimeout+664.
[ 48 ff:4c 8b ]
ffff8b10cfea860b-ffff8b10cfea860e 4 bytes - win32kfull!xxxSendTransformableMessageTimeout+66b (+0x07)
[ 0f 1f 44 00:e8 10 9e 2f ]
6 errors : !win32kfull (ffff8b10cfea8604-ffff8b10cfea860e)

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 *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error.
source that reported the error. Parameter 2 holds the address of the.
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception.
Arg2: ffff88013b35e028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fe200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000041136, Low order 32-bits of the MCi_STATUS value.

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

BUGCHECK_STR: 0x124_GenuineIntel.

CUSTOMER_CRASH_COUNT: 1.

DEFAULT_BUCKET_ID: CODE_CORRUPTION.

PROCESS_NAME: VALORANT-Win64.

CURRENT_IRQL: f.

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

STACK_TEXT:
fffff805`32682918 fffff805`2c9a4188 : 00000000`00000124 00000000`00000000 ffff8801`3b35e028 00000000`fe200000 : nt!KeBugCheckEx.
fffff805`32682920 fffff805`30d81920 : ffff8801`38be9350 00000000`00000000 ffff8801`3b35e028 00000000`00000000 : hal!HalBugCheckSystem+0xd8.
fffff805`32682960 fffff805`2cd410a2 : ffff8801`38be9350 fffff805`326829e9 00000000`00000000 ffff8801`3b35e028 : PSHED!PshedBugCheckSystem+0x10.
fffff805`32682990 fffff805`2c9a5ae6 : fffff805`32682ab0 00000000`00000000 ffff8801`38be93a0 ffff8801`38be9350 : nt!WheaReportHwError+0x382.
fffff805`32682a50 fffff805`2c9a5f7a : 00000000`00000010 ffff8801`38be93a0 fffff805`32682c08 fffff805`32682e50 : hal!HalpMcaReportError+0x72.
fffff805`32682bb0 fffff805`2c9a5e54 : ffff8801`382c96f0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2.
fffff805`32682c00 fffff805`2c9a60c0 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0.
fffff805`32682c40 fffff805`2c9a5168 : 00000000`00000000 fffff805`32682ed0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4.
fffff805`32682c70 fffff805`2c9a6347 : ffff8801`382c96f0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c.
fffff805`32682ca0 fffff805`2cca4e40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37.
fffff805`32682cd0 fffff805`2cbd13ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10.
fffff805`32682d00 fffff805`2cbd106f : 00000000`00000000 00000000`00000000 0000016f`a4376db8 00000000`00000000 : nt!KxMcheckAbort+0x7a.
fffff805`32682e40 00007ff6`cade5f27 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x26f.
00000012`28e9f340 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`cade5f27.

STACK_COMMAND: kb.

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kbase.
ffff835db22471f9-ffff835db22471fe 6 bytes - win32kbase!DirectComposition::CAnimationMarshaler::SetReferenceProperty+49.
[ ff 15 b1 f5 19 00:e8 a2 f0 20 00 90 ]
ffff835db2247269-ffff835db224726a 2 bytes - win32kbase!SfmSignalTokenEvent+19 (+0x70)
[ 48 ff:4c 8b ]
ffff835db2247270-ffff835db2247273 4 bytes - win32kbase!SfmSignalTokenEvent+20 (+0x07)
[ 0f 1f 44 00:e8 ab f1 20 ]
ffff835db22483d5-ffff835db22483d6 2 bytes - win32kbase!GreSfmDwmShutdown+35 (+0x1165)
[ 48 ff:4c 8b ]
ffff835db22483dc-ffff835db22483df 4 bytes - win32kbase!GreSfmDwmShutdown+3c (+0x07)
[ 0f 1f 44 00:e8 3f e0 20 ]
ffff835db22483e5-ffff835db22483e6 2 bytes - win32kbase!GreSfmDwmShutdown+45 (+0x09)
[ 48 ff:4c 8b ]
ffff835db22483ec-ffff835db22483ef 4 bytes - win32kbase!GreSfmDwmShutdown+4c (+0x07)
[ 0f 1f 44 00:e8 2f e0 20 ]
24 errors : !win32kbase (ffff835db22471f9-ffff835db22483ef)

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.
---------

Murat5038 · 3 Ekim 2020

Valorant zaten sorunluydu şimdi olan bir durum değil. Dosyayı incelemedim.

pulse0827 · 3 Ekim 2020

Bora Dere dedi:
Öncelikle Windows'u ve BIOS'u güncelleyin.

ASUS TÃ¼rkiye

ASUS, dizÃ¼stÃ¼ bilgisayarlar, anakartlar, ekran kartlarÄ±, monitÃ¶rler, masaÃ¼stÃ¼ bilgisayarlar, sunucular, kablosuz Ã§Ã¶zÃ¼mler aÄ cihazlarÄ±nÄ±n olduÄu Ã¼rÃ¼nlerinde kaliteden asla Ã¶dÃ¼n vermeyen bir Åirkettir.

www.asus.com

Son zamanlarda cihazın içini termal macun yenilemek için falan açtınız mı? Ayrıca işlemciye UV gibi bir işlem yaptınız mı, oyun içi sıcaklık durumu nasıl?

Cevabıma anlam veremeyen arkadaşlar için: Konu sahibi başka bir konuda dosyalarını paylaşmıştı.

https://www.technopat.net/sosyal/ko...si-mavi-ekran-hatasi.1093731/#post-7285253[/U

Windows güncel ancak bios güncellemesi yapmadım.

PC'nin termal macununu 1 ay kadar oldu olmadı komple temizleyip kaliteli macun kullandım.
UV işlemi yapmadım ama adaptörden şüphelenmiştim. Başka bir adaptör kullanarak sorunun oradan da kaynaklanmadığına kanaat getirdim.

Oyun içi değerler şu şekilde :

Degerler.png

drive.google.com

Assecreed dedi:

Farklı marka Ramler kullanıyorsunuz. Bir tanesini çıkarıp Ramlerin oyuna girin. Tekrar yerseniz takarsınız.

Kod:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffca8240d6f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000041136, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  VALORANT-Win64

CURRENT_IRQL:  f

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

STACK_TEXT:
fffff805`59882918 fffff805`566ff188 : 00000000`00000124 00000000`00000000 ffffca82`40d6f028 00000000`be200000 : nt!KeBugCheckEx
fffff805`59882920 fffff805`57f81920 : ffffca82`405da350 00000000`00000000 ffffca82`40d6f028 00000000`00000000 : hal!HalBugCheckSystem+0xd8
fffff805`59882960 fffff805`55f410a2 : ffffca82`405da350 fffff805`598829e9 00000000`00000000 ffffca82`40d6f028 : PSHED!PshedBugCheckSystem+0x10
fffff805`59882990 fffff805`56700ae6 : fffff805`59882ab0 00000000`00000000 ffffca82`405da3a0 ffffca82`405da350 : nt!WheaReportHwError+0x382
fffff805`59882a50 fffff805`56700f7a : 00000000`00000010 ffffca82`405da3a0 fffff805`59882c08 fffff805`59882e50 : hal!HalpMcaReportError+0x72
fffff805`59882bb0 fffff805`56700e54 : ffffca82`3ecc96f0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2
fffff805`59882c00 fffff805`567010c0 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0
fffff805`59882c40 fffff805`56700168 : 00000000`00000000 fffff805`59882ed0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff805`59882c70 fffff805`56701347 : ffffca82`3ecc96f0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
fffff805`59882ca0 fffff805`55ea4e40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
fffff805`59882cd0 fffff805`55dd13ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10
fffff805`59882d00 fffff805`55dd106f : 00000000`00000000 00000000`00000000 0000021c`4ae3ff10 00000000`00000000 : nt!KxMcheckAbort+0x7a
fffff805`59882e40 00007ff9`b0276d2b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x26f
000000dc`5e71f880 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`b0276d2b


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kbase
    ffff8dadfbc971f9-ffff8dadfbc971fe  6 bytes - win32kbase!DirectComposition::CAnimationMarshaler::SetReferenceProperty+49
    [ ff 15 b1 f5 19 00:e8 a2 f0 20 00 90 ]
    ffff8dadfbc97269-ffff8dadfbc9726a  2 bytes - win32kbase!SfmSignalTokenEvent+19 (+0x70)
    [ 48 ff:4c 8b ]
    ffff8dadfbc97270-ffff8dadfbc97273  4 bytes - win32kbase!SfmSignalTokenEvent+20 (+0x07)
    [ 0f 1f 44 00:e8 ab f1 20 ]
    ffff8dadfbc983d5-ffff8dadfbc983d6  2 bytes - win32kbase!GreSfmDwmShutdown+35 (+0x1165)
    [ 48 ff:4c 8b ]
    ffff8dadfbc983dc-ffff8dadfbc983df  4 bytes - win32kbase!GreSfmDwmShutdown+3c (+0x07)
    [ 0f 1f 44 00:e8 3f e0 20 ]
    ffff8dadfbc983e5-ffff8dadfbc983e6  2 bytes - win32kbase!GreSfmDwmShutdown+45 (+0x09)
    [ 48 ff:4c 8b ]
    ffff8dadfbc983ec-ffff8dadfbc983ef  4 bytes - win32kbase!GreSfmDwmShutdown+4c (+0x07)
    [ 0f 1f 44 00:e8 2f e0 20 ]
24 errors : !win32kbase (ffff8dadfbc971f9-ffff8dadfbc983ef)

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                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffa98702f7f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000041136, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  vgc.exe

CURRENT_IRQL:  f

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

STACK_TEXT:
ffffd201`1b66ca58 fffff807`591a4188 : 00000000`00000124 00000000`00000000 ffffa987`02f7f028 00000000`be200000 : nt!KeBugCheckEx
ffffd201`1b66ca60 fffff807`5d581920 : ffffa987`020f85e0 00000000`00000000 ffffa987`02f7f028 00000000`00000000 : hal!HalBugCheckSystem+0xd8
ffffd201`1b66caa0 fffff807`595410a2 : ffffa987`020f85e0 ffffd201`1b66cb29 00000000`00000000 ffffa987`02f7f028 : PSHED!PshedBugCheckSystem+0x10
ffffd201`1b66cad0 fffff807`591a5ae6 : ffffd201`1b66cbf0 00000000`00000001 ffffa987`020f8630 ffffa987`020f85e0 : nt!WheaReportHwError+0x382
ffffd201`1b66cb90 fffff807`591a5f7a : 00000000`00000010 ffffa987`020f8630 ffffd201`1b66cd48 ffffd201`1b66cf90 : hal!HalpMcaReportError+0x72
ffffd201`1b66ccf0 fffff807`591a5e54 : ffffa987`01ec97a0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2
ffffd201`1b66cd40 fffff807`591a60c0 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0
ffffd201`1b66cd80 fffff807`591a5168 : 00000000`00000000 ffffd201`1b66d010 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
ffffd201`1b66cdb0 fffff807`591a6347 : ffffa987`01ec97a0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
ffffd201`1b66cde0 fffff807`594a4e40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
ffffd201`1b66ce10 fffff807`593d13ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10
ffffd201`1b66ce40 fffff807`593d106f : 00000000`00000000 00000000`00000000 00000000`fff6b6a1 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffd201`1b66cf80 00007ff6`45627f38 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x26f
00000033`605ff550 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`45627f38


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kbase
    ffffa36180e971f9-ffffa36180e971fe  6 bytes - win32kbase!DirectComposition::CAnimationMarshaler::SetReferenceProperty+49
    [ ff 15 b1 f5 19 00:e8 a2 f0 20 00 90 ]
    ffffa36180e97269-ffffa36180e9726a  2 bytes - win32kbase!SfmSignalTokenEvent+19 (+0x70)
    [ 48 ff:4c 8b ]
    ffffa36180e97270-ffffa36180e97273  4 bytes - win32kbase!SfmSignalTokenEvent+20 (+0x07)
    [ 0f 1f 44 00:e8 ab f1 20 ]
    ffffa36180e983d5-ffffa36180e983d6  2 bytes - win32kbase!GreSfmDwmShutdown+35 (+0x1165)
    [ 48 ff:4c 8b ]
    ffffa36180e983dc-ffffa36180e983df  4 bytes - win32kbase!GreSfmDwmShutdown+3c (+0x07)
    [ 0f 1f 44 00:e8 3f e0 20 ]
    ffffa36180e983e5-ffffa36180e983e6  2 bytes - win32kbase!GreSfmDwmShutdown+45 (+0x09)
    [ 48 ff:4c 8b ]
    ffffa36180e983ec-ffffa36180e983ef  4 bytes - win32kbase!GreSfmDwmShutdown+4c (+0x07)
    [ 0f 1f 44 00:e8 2f e0 20 ]
24 errors : !win32kbase (ffffa36180e971f9-ffffa36180e983ef)

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                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff930ab715b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fe200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000041136, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  VALORANT-Win64

CURRENT_IRQL:  f

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

STACK_TEXT:
ffffc901`5f130a58 fffff804`2dba4188 : 00000000`00000124 00000000`00000000 ffff930a`b715b028 00000000`fe200000 : nt!KeBugCheckEx
ffffc901`5f130a60 fffff804`2ed81920 : ffff930a`b42f88c0 00000000`00000000 ffff930a`b715b028 00000000`00000000 : hal!HalBugCheckSystem+0xd8
ffffc901`5f130aa0 fffff804`2df410a2 : ffff930a`b42f88c0 ffffc901`5f130b29 00000000`00000000 ffff930a`b715b028 : PSHED!PshedBugCheckSystem+0x10
ffffc901`5f130ad0 fffff804`2dba5ae6 : ffffc901`5f130bf0 00000000`00000003 ffff930a`b42f8910 ffff930a`b42f88c0 : nt!WheaReportHwError+0x382
ffffc901`5f130b90 fffff804`2dba5f7a : 00000000`00000010 ffff930a`b42f8910 ffffc901`5f130d48 ffffc901`5f130f90 : hal!HalpMcaReportError+0x72
ffffc901`5f130cf0 fffff804`2dba5e54 : ffff930a`b40c9900 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2
ffffc901`5f130d40 fffff804`2dba60c0 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0
ffffc901`5f130d80 fffff804`2dba5168 : 00000000`00000000 ffffc901`5f131010 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
ffffc901`5f130db0 fffff804`2dba6347 : ffff930a`b40c9900 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
ffffc901`5f130de0 fffff804`2dea4e40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
ffffc901`5f130e10 fffff804`2ddd13ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10
ffffc901`5f130e40 fffff804`2ddd106f : 00000000`00000000 00000000`00000000 00000031`202cda70 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffc901`5f130f80 00007ff7`86530936 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x26f
00000031`202cd9b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff7`86530936


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kfull
    ffff8b10cfea8604-ffff8b10cfea8605  2 bytes - win32kfull!xxxSendTransformableMessageTimeout+664
    [ 48 ff:4c 8b ]
    ffff8b10cfea860b-ffff8b10cfea860e  4 bytes - win32kfull!xxxSendTransformableMessageTimeout+66b (+0x07)
    [ 0f 1f 44 00:e8 10 9e 2f ]
6 errors : !win32kfull (ffff8b10cfea8604-ffff8b10cfea860e)

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                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff88013b35e028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fe200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000041136, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  VALORANT-Win64

CURRENT_IRQL:  f

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

STACK_TEXT:
fffff805`32682918 fffff805`2c9a4188 : 00000000`00000124 00000000`00000000 ffff8801`3b35e028 00000000`fe200000 : nt!KeBugCheckEx
fffff805`32682920 fffff805`30d81920 : ffff8801`38be9350 00000000`00000000 ffff8801`3b35e028 00000000`00000000 : hal!HalBugCheckSystem+0xd8
fffff805`32682960 fffff805`2cd410a2 : ffff8801`38be9350 fffff805`326829e9 00000000`00000000 ffff8801`3b35e028 : PSHED!PshedBugCheckSystem+0x10
fffff805`32682990 fffff805`2c9a5ae6 : fffff805`32682ab0 00000000`00000000 ffff8801`38be93a0 ffff8801`38be9350 : nt!WheaReportHwError+0x382
fffff805`32682a50 fffff805`2c9a5f7a : 00000000`00000010 ffff8801`38be93a0 fffff805`32682c08 fffff805`32682e50 : hal!HalpMcaReportError+0x72
fffff805`32682bb0 fffff805`2c9a5e54 : ffff8801`382c96f0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2
fffff805`32682c00 fffff805`2c9a60c0 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0
fffff805`32682c40 fffff805`2c9a5168 : 00000000`00000000 fffff805`32682ed0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff805`32682c70 fffff805`2c9a6347 : ffff8801`382c96f0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
fffff805`32682ca0 fffff805`2cca4e40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
fffff805`32682cd0 fffff805`2cbd13ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10
fffff805`32682d00 fffff805`2cbd106f : 00000000`00000000 00000000`00000000 0000016f`a4376db8 00000000`00000000 : nt!KxMcheckAbort+0x7a
fffff805`32682e40 00007ff6`cade5f27 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x26f
00000012`28e9f340 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`cade5f27


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kbase
    ffff835db22471f9-ffff835db22471fe  6 bytes - win32kbase!DirectComposition::CAnimationMarshaler::SetReferenceProperty+49
    [ ff 15 b1 f5 19 00:e8 a2 f0 20 00 90 ]
    ffff835db2247269-ffff835db224726a  2 bytes - win32kbase!SfmSignalTokenEvent+19 (+0x70)
    [ 48 ff:4c 8b ]
    ffff835db2247270-ffff835db2247273  4 bytes - win32kbase!SfmSignalTokenEvent+20 (+0x07)
    [ 0f 1f 44 00:e8 ab f1 20 ]
    ffff835db22483d5-ffff835db22483d6  2 bytes - win32kbase!GreSfmDwmShutdown+35 (+0x1165)
    [ 48 ff:4c 8b ]
    ffff835db22483dc-ffff835db22483df  4 bytes - win32kbase!GreSfmDwmShutdown+3c (+0x07)
    [ 0f 1f 44 00:e8 3f e0 20 ]
    ffff835db22483e5-ffff835db22483e6  2 bytes - win32kbase!GreSfmDwmShutdown+45 (+0x09)
    [ 48 ff:4c 8b ]
    ffff835db22483ec-ffff835db22483ef  4 bytes - win32kbase!GreSfmDwmShutdown+4c (+0x07)
    [ 0f 1f 44 00:e8 2f e0 20 ]
24 errors : !win32kbase (ffff835db22471f9-ffff835db22483ef)

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

8 GB RAM var toplamda. Bunun dördünü sonradan aldım Kingston marka. Az önce denedim ama yine aynısı oldu sıcaklık CPU'da 82'yi gördü Yine 15 dakika oldu olmadı aynı hata. BIOS'u da bir güncelleyeyim yine yazarım.

Arkadaşlar ilginiz için teşekkür ederim bu arada sağ olun

Bora Dere · 3 Ekim 2020

Rica ederiz, son durum nedir? Güncellemeden sonra bu tarz sorunları yaşayan çok kişi var. Murat hocamın dediği gibi halihazırda sorunlu olan Vanguard daha da baş belası bir hal almış olabilir.

pulse0827 · 4 Ekim 2020

Bora Dere dedi:
Rica ederiz, son durum nedir? Güncellemeden sonra bu tarz sorunları yaşayan çok kişi var. Murat hocamın dediği gibi halihazırda sorunlu olan Vanguard daha da baş belası bir hal almış olabilir.

Hocam Vanguard'dan da şüphelenmiyor değilim. Oyunu da tekrar indirip yüklemeyi de denedim. Vanguard'ı da tekrar tekrar yükledim. Bazen PC'yi sıfırdan açtığımda oyun Vanguard hatası verip yeniden başlatma istiyordu. Konu ile alakalı Riot'a yazmayı düşünüyorum. Yabancı forumlarda da konuyla alakalı tartışmalar gördüm. Riot'a da durum bildirilmiş. Birçok kişi son güncellemeden sonra anlık FPS düşüşü yaşadığını da belirtmiş. Bakalım ne olacak.
Arkadaşlar sorunla alakalı bir çözüm bulamadım. Uğraşmaya devam ediyorum ama sizden bir ricam var. Oyuna girip de mavi ekran hatası almayan biri Vanguard dosyalarını paylaşabilir mi rica etsem? 270 MB'lık Riot Client dosyasını komple paylaşabilirseniz denemekte fayda var diye düşünüyorum
arkadaşlar sorunla alakalı bir çözüm bulamadım. Uğraşmaya devam ediyorum ama sizden bir ricam var. Oyuna girip de mavi ekran hatası almayan biri Vanguard dosyalarını paylaşabilir mi rica etsem? 270 MB'lık Riot Client dosyasını komple paylaşabilirseniz denemekte fayda var diye düşünüyorum

pulse0827 dedi:
Hocam Vanguard'dan da şüphelenmiyor değilim. Oyunu da tekrar indirip yüklemeyi de denedim. Vanguard'ı da tekrar tekrar yükledim. Bazen PC'yi sıfırdan açtığımda oyun Vanguard hatası verip yeniden başlatma istiyordu. Konu ile alakalı Riot'a yazmayı düşünüyorum. Yabancı forumlarda da konuyla alakalı tartışmalar gördüm. Riot'a da durum bildirilmiş. Birçok kişi son güncellemeden sonra anlık FPS düşüşü yaşadığını da belirtmiş. Bakalım ne olacak.
Arkadaşlar sorunla alakalı bir çözüm bulamadım. Uğraşmaya devam ediyorum ama sizden bir ricam var. Oyuna girip de mavi ekran hatası almayan biri Vanguard dosyalarını paylaşabilir mi rica etsem? 270 MB'lık Riot Client dosyasını komple paylaşabilirseniz denemekte fayda var diye düşünüyorum
arkadaşlar sorunla alakalı bir çözüm bulamadım. Uğraşmaya devam ediyorum ama sizden bir ricam var. Oyuna girip de mavi ekran hatası almayan biri Vanguard dosyalarını paylaşabilir mi rica etsem? 270 MB'lık Riot Client dosyasını komple paylaşabilirseniz denemekte fayda var diye düşünüyorum

Arkadaşlar sorunla alakalı bir çözüm bulamadım. Uğraşmaya devam ediyorum ama sizden bir ricam var. Oyuna girip de mavi ekran hatası almayan biri Vanguard dosyalarını paylaşabilir mi rica etsem? 270 MB'lık Riot Client dosyasını komple paylaşabilirseniz denemekte fayda var diye düşünüyorum

Çözüldü Valorant 1.09 güncellemesi WHEA_UNCORRECTABLE_ERROR mavi ekran hatası

Ayrıntılı düzenleme

pulse0827

Femtopat

pulse0827

codefl0w

Megapat

Minidump Dosyalarını Paylaşın

Assecreed

Megapat

Minidump Dosyalarını Paylaşın

Bora Dere

Moderasyon Ekibi Üyesi

ASUS TÃ¼rkiye

Valorant son güncelleme sonrası mavi ekran hatası

pulse0827

Femtopat

MiniDump-pulse.rar

Assecreed

Megapat

Murat5038

Yottapat!

pulse0827

Femtopat

ASUS TÃ¼rkiye

Degerler.png

Bora Dere

Moderasyon Ekibi Üyesi

pulse0827

Femtopat

Benzer konular