Şimdi Ara

GenuineIntel.sys İşlemci Kaynaklı Mavi Ekran Hatası

Daha Fazla
Bu Konudaki Kullanıcılar: Daha Az
2 Misafir (1 Mobil) - 1 Masaüstü1 Mobil
5 sn
3
Cevap
0
Favori
81
Tıklama
Daha Fazla
İstatistik
  • Konu İstatistikleri
  • Son Yorum 2 ay
  • Cevaplayan Üyeler 2
  • Konu Sahibinin Yazdıkları 2
  • Ortalama Mesaj Aralığı 2 gün 1 saat 39 dakika
  • Son 1 Saatteki Mesajlar 1
  • Konuya En Çok Yazanlar
  • myo_1433 (2 mesaj) potti34 (1 mesaj)
  • Konuya Yazanların Platform Dağılımı
  • Masaüstü (3 mesaj)
  • @
0 oy
Öne Çıkar
Tüm Forumlar >> Donanım / Hardware >> Teknik Yardım >> GenuineIntel.sys İşlemci Kaynaklı Mavi Ekran Hatası
Sayfaya Git:
Sayfa:
1
Giriş
Mesaj
  • Binbaşı
    1392 Mesaj
    Konu Sahibine Özel

    Selam arkadaşlar toshiba satallite l750 1ml laptop mevcut, bende windows 10 pro yüklü idi ve bu mavi ekran hatası kendiliğinden düzelmişti lakin windows 10 pro crackli idi ve bendede windows home orjinal key olduğu için laptobu sıfırladım formatladım ve windows 10 home kurdum. Kurduktan sonra bu lanet mavi ekran hatası yeniden peydahladı, bazı yabancı forumlar da güç planını dengeliden yükseğe alarak çözmüşler ama bende işe yaramadı. Sistemim şu şekilde


    core i7 2670qm işlemci

    8 gb ram

    nvidia gt525m ekran kartı


    Altta minidump analiz sonuçlarını bırakıyorum bir türlü şu lanet şeyden kurtulamadım arkadaşlar.


    Kod

    Yığını:
    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 condition. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffac01a496d028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000bb800000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000175, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** 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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *** *** *** ************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 10218 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 12729 Key : Analysis.Init.CPU.mSec Value: 859 Key : Analysis.Init.Elapsed.mSec Value: 19264 Key : Analysis.Memory.CommitPeak.Mb Value: 79 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: 124 BUGCHECK_P1: 0 BUGCHECK_P2: ffffac01a496d028 BUGCHECK_P3: bb800000 BUGCHECK_P4: 175 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: MsMpEng.exe STACK_TEXT: ffff9a80`a065b8e8 fffff804`51eb448a : 00000000`00000124 00000000`00000000 ffffac01`a496d028 00000000`bb800000 : nt!KeBugCheckEx ffff9a80`a065b8f0 fffff804`4f3d15b0 : 00000000`00000000 ffffac01`a496d028 ffffac01`a23ff830 ffffac01`a496d028 : nt!HalBugCheckSystem+0xca ffff9a80`a065b930 fffff804`51fb612e : 00000000`00000000 ffff9a80`a065b9d9 ffffac01`a496d028 ffffac01`a23ff830 : PSHED!PshedBugCheckSystem+0x10 ffff9a80`a065b960 fffff804`51eb5db1 : ffffac01`a2324ac0 ffffac01`a2324ac0 ffffac01`a23ff880 ffffac01`a23ff830 : nt!WheaReportHwError+0x46e ffff9a80`a065ba40 fffff804`51eb6123 : 00000000`00000003 ffffac01`a23ff880 ffffac01`a23ff830 00000000`00000003 : nt!HalpMcaReportError+0xb1 ffff9a80`a065bbb0 fffff804`51eb6000 : ffffac01`a22aed18 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0xef ffff9a80`a065bc00 fffff804`51eb6251 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0 ffff9a80`a065bc40 fffff804`51eb54bb : 00000000`00000000 00000000`00000000 ffff9a80`a065bed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9 ffff9a80`a065bc70 fffff804`51eb7d05 : ffffac01`a22aed18 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x5f ffff9a80`a065bca0 fffff804`51f0d419 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35 ffff9a80`a065bcd0 fffff804`51e062fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9 ffff9a80`a065bd00 fffff804`51e05fb7 : 00000000`00000000 00000000`00000000 00000000`0000000f 00000000`00000000 : nt!KxMcheckAbort+0x7a ffff9a80`a065be40 00007ff8`5b65c1a2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277 000000fd`7307e660 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`5b65c1a2 MODULE_NAME: GenuineIntel IMAGE_NAME: GenuineIntel.sys STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2} Followup: MachineOwner



    |
    |




  • Yüzbaşı
    684 Mesaj

    öncellikle bios sürümünü varsa güncelleştir sonra temiz kurulum yapıp tüm driverları toshibanın sitesinden indir.

  • Binbaşı
    1392 Mesaj
    Konu Sahibine Özel

    Bios güncel temiz kurulum yapıldı driverlar güncel sorun büyük ihtimal yazılımsal ama ne

    |
    |
    potti34 kullanıcısının, bahsedilen mesajını gör
Sayfaya Git:
Sayfa:
1
Reklamlar
valorant points
vp satın al
bankacılar
Bu sayfanın
Mobil sürümü
Mini Sürümü

BR2
0,766
1.2.165

Reklamlar
- x
Bildirim
mesajınız kopyalandı (ctrl+v) yapıştırmak istediğiniz yere yapıştırabilirsiniz.