BlueStacks kurarken mavi ekran hatası

Tarihe göre sırala Puana göre sırala
Döküm paylaşın, sorunu daha iyi anlarız.

Minidump Dosyalarını Paylaşın

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 ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...
www.technopat.net www.technopat.net
 
Artı 0 Eksi
Anakart sanırım B450M-A PRO MAX. 7C52v3G sürüm BIOS'a geçip dener misin?

tr.msi.com

B450M-A PRO MAX | Motherboard | MSI Global

Best AMD AM4 B450 Micro-ATX motherboard, Turbo M.2, USB 3.2 Gen 1, MSI PRO
tr.msi.com tr.msi.com

Olmazsa BIOS'a gir > OC > CPU Features > SVM Mode > Enabled

Ek olarak Windows 10 sürümün eski. 22H2 sürümüne geçip dene.

Windows 10 Yükleme Yardımcısı

Adım adım Windows 10 işletim sisteminizi en son sürüme güncelleyin.
www.technopat.net www.technopat.net

Kod: 
Machine ID Information [From Smbios 2.8, DMIVersion 0, Size=2386]
BiosMajorRelease = 5
BiosMinorRelease = 17
BiosVendor = American Megatrends International, LLC.
BiosVersion = 3.E0
BiosReleaseDate = 03/29/2022
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = MS-7C52
SystemFamily = To be filled by O.E.M.
SystemVersion = 1.0
SystemSKU = To be filled by O.E.M.
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = B450M-A PRO MAX (MS-7C52)
BaseBoardVersion = 1.0

Kod: 
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffcc005a595180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 827

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 16853

    Key  : Analysis.IO.Other.Mb
    Value: 6

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 27

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x101

    Key  : Bugcheck.Code.Register
    Value: 0x101

    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


FILE_IN_CAB:  121722-29375-01.dmp

BUGCHECK_CODE:  101

BUGCHECK_P1: 10

BUGCHECK_P2: 0

BUGCHECK_P3: ffffcc005a595180

BUGCHECK_P4: 2

FAULTING_PROCESSOR: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

STACK_TEXT: 
ffffcc00`5a4f3c88 fffff804`1345bd6a     : 00000000`00000101 00000000`00000010 00000000`00000000 ffffcc00`5a595180 : nt!KeBugCheckEx
ffffcc00`5a4f3c90 fffff804`132d844d     : 00000000`00000000 ffffcc00`5a4da180 00000000`00000246 00000000`000021de : nt!KeAccumulateTicks+0x186b3a
ffffcc00`5a4f3cf0 fffff804`132d89f1     : 00000000`00001f00 00000000`0000142f ffffcc00`5a4da180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffcc00`5a4f3d40 fffff804`132d2863     : ffffcc00`5a4da180 00000000`00000000 fffff804`13c31930 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffcc00`5a4f3e80 fffff804`132db222     : ffff800b`b9bd1580 ffff800b`b9bd1600 ffff800b`b9bd1600 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
ffffcc00`5a4f3f30 fffff804`13208aa5     : 00000000`50e3da32 ffffa30d`d85025a0 ffffa30d`d8502650 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
ffffcc00`5a4f3f60 fffff804`133fb23a     : ffff800b`b9bd1600 ffffa30d`d85025a0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffcc00`5a4f3fb0 fffff804`133fba07     : 00000000`29657e2b ffffcc00`5a4dd088 ffff800b`b9bd16b1 00000000`00000003 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff800b`b9bd1580 fffff804`132bb9d6     : 00000001`1bd7d088 fffff804`35245f3e 00000000`00000001 ffffa30d`ebb6a000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff800b`b9bd1710 fffff804`132da90c     : 00000000`00000000 00000000`00000002 ffff800b`b9bd18e0 fffff804`34bc299a : nt!KiIpiSendRequestEx+0xb6
ffff800b`b9bd1750 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0x1bc


SYMBOL_NAME:  nt!KeAccumulateTicks+186b3a

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.2364

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  186b3a

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup:     MachineOwner
---------
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffb28197395180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1031

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 17759

    Key  : Analysis.IO.Other.Mb
    Value: 7

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 29

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x101

    Key  : Bugcheck.Code.Register
    Value: 0x101

    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


FILE_IN_CAB:  121722-27968-01.dmp

BUGCHECK_CODE:  101

BUGCHECK_P1: 10

BUGCHECK_P2: 0

BUGCHECK_P3: ffffb28197395180

BUGCHECK_P4: 2

FAULTING_PROCESSOR: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff804`61a83c88 fffff804`5b45bd6a     : 00000000`00000101 00000000`00000010 00000000`00000000 ffffb281`97395180 : nt!KeBugCheckEx
fffff804`61a83c90 fffff804`5b2d844d     : 00000000`00000000 fffff804`596d6180 00000000`00000246 00000000`0000e974 : nt!KeAccumulateTicks+0x186b3a
fffff804`61a83cf0 fffff804`5b2d89f1     : 00000000`0000e700 00000000`00008b26 fffff804`596d6180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff804`61a83d40 fffff804`5b2d2863     : fffff804`596d6180 00000000`00000000 fffff804`5bc317f8 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff804`61a83e80 fffff804`5b2db222     : fffff588`2e569d90 fffff588`2e569e10 fffff588`2e569e00 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
fffff804`61a83f30 fffff804`5b208aa5     : 00000002`2cbd7237 fffff804`5bcf3a20 fffff804`5bcf3ad0 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
fffff804`61a83f60 fffff804`5b3fb23a     : fffff588`2e569e10 fffff804`5bcf3a20 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff804`61a83fb0 fffff804`5b3fba07     : 00000000`25f40e35 fffff804`596d6180 00000000`00000002 fffff804`596d9130 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff588`2e569d90 fffff804`5b2bc516     : 00000000`00000000 00000000`00000002 00000000`00000002 fffffb54`2fba8000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff588`2e569f20 fffff804`5b2dc41f     : fffff588`2e56a520 00000000`00000000 fffff9fd`aa17dd00 fffff588`2e56a520 : nt!KeFlushMultipleRangeTb+0x166
fffff588`2e569fc0 fffff804`5b238fbd     : 00000000`00000004 00000000`00000000 ffffb281`9a91d100 01000004`02f08021 : nt!MiAgeWorkingSetTail+0xef
fffff588`2e56a000 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiWalkPageTablesRecursively+0xc6d


SYMBOL_NAME:  nt!KeAccumulateTicks+186b3a

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.2364

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  186b3a

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup:     MachineOwner
---------
 
Artı 0 Eksi

Benzer konular

ardacn60
  • Soru
BlueStacks kurarken mavi ekran hatası
Mesaj
3
Görüntüleme
881
ardacn60
ardacn60
Vorfey
  • Soru
BlueStacks 5 kurarken mavi ekran hatası
2
Mesaj
10
Görüntüleme
289
claus
claus
B
  • Çözüldü
Çözüldü  BlueStacks 5 kurarken mavi ekran hatası
Mesaj
2
Görüntüleme
188
BnHasan
B
480164
  • Soru
BlueStacks Android 11 kurarken gelen mavi ekran
Mesaj
2
Görüntüleme
128
480164
480164
Joseph37
  • Soru
Bluestacks mavi ekran hatası
Mesaj
2
Görüntüleme
3B
ecihan145
ecihan145

Yeni konular

Yeni mesajlar

Geri
Yukarı