ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY mavi ekran hatası

Belleklere test yapın.

Memtest86 USB'den Çalışan RAM Test Programı

RAM'lerinizi test etmek için kullanabileceğiniz en kapsamlı yazılım Memtest86'dır. Aracı USB belleğe yazmak için: Bu video rehberde Memtest86 ile belleklerinizi nasıl test edeceğinizi öğrenebilirsiniz: Adım adım: Öncelikle yazılımı buradan indirin. UEFI desteği olmayan eski sistemler...
www.technopat.net www.technopat.net

Disklerinize HD Tune ile hata ve sağlık testi yapın. Quick scan kapalı olsun. Vanguard kaldırın ve BIOS güncelleyin.

Kod: 
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffc20194c43180, Virtual address for the attempted execute.
Arg2: 8a00000004d15963, PTE contents.
Arg3: fffffd8c8db17230, (reserved)
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5186

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 5289

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  fc

BUGCHECK_P1: ffffc20194c43180

BUGCHECK_P2: 8a00000004d15963

BUGCHECK_P3: fffffd8c8db17230

BUGCHECK_P4: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  ui32.exe

TRAP_FRAME:  fffffd8c8db17230 -- (.trap 0xfffffd8c8db17230)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000009f rbx=0000000000000000 rcx=000000000000003f
rdx=00000000000000b0 rsi=0000000000000000 rdi=0000000000000000
rip=ffffc20194c43180 rsp=fffffd8c8db173c0 rbp=fffffd8c8db174c0
 r8=0000000000000000  r9=00000000000000b0 r10=00000000000000b0
r11=00000000000000e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
ffffc201`94c43180 801f00          sbb     byte ptr [rdi],0 ds:00000000`00000000=??
Resetting default scope

STACK_TEXT: 
fffffd8c`8db16f48 fffff807`3a44eaa0     : 00000000`000000fc ffffc201`94c43180 8a000000`04d15963 fffffd8c`8db17230 : nt!KeBugCheckEx
fffffd8c`8db16f50 fffff807`3a308b56     : ffffc201`94c43180 fffffd8c`8db17150 ffffd70f`00000000 ffff8000`00000000 : nt!MiCheckSystemNxFault+0x1ab7e8
fffffd8c`8db16f90 fffff807`3a2ea5e0     : fffff807`3a2755c0 00000000`00000011 fffffd8c`8db172b0 00000000`00000000 : nt!MiSystemFault+0x6c6
fffffd8c`8db17090 fffff807`3a40275e     : 00000001`ffffffff fffffff6`0000000d 00000000`00000006 00000008`00000001 : nt!MmAccessFault+0x400
fffffd8c`8db17230 ffffc201`94c43180     : ffffffff`ffffffff fffffd8c`8db174c0 00000000`000000b0 00000000`00000000 : nt!KiPageFault+0x35e
fffffd8c`8db173c0 ffffffff`ffffffff     : fffffd8c`8db174c0 00000000`000000b0 00000000`00000000 00000000`00000000 : 0xffffc201`94c43180
fffffd8c`8db173c8 fffffd8c`8db174c0     : 00000000`000000b0 00000000`00000000 00000000`00000000 00000000`00000001 : 0xffffffff`ffffffff
fffffd8c`8db173d0 00000000`000000b0     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000006 : 0xfffffd8c`8db174c0
fffffd8c`8db173d8 00000000`00000000     : 00000000`00000000 00000000`00000001 00000000`00000006 00000000`00000000 : 0xb0


SYMBOL_NAME:  nt!MiCheckSystemNxFault+1ab7e8

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  1ab7e8

FAILURE_BUCKET_ID:  0xFC_nt!MiCheckSystemNxFault

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a6ae5288-6b71-974a-9b09-23f14d998164}

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



APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 00007ff8ab46be14, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffffe90d75b72b80, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6531

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 6964

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1

BUGCHECK_P1: 7ff8ab46be14

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: ffffe90d75b72b80

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

STACK_TEXT: 
ffffe90d`75b729b8 fffff803`7e206569     : 00000000`00000001 00007ff8`ab46be14 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
ffffe90d`75b729c0 fffff803`7e206433     : ffffb28e`5488c080 00000000`00000001 ffffe90d`75b72b18 ffffffff`ffb51450 : nt!KiBugCheckDispatch+0x69
ffffe90d`75b72b00 00007ff8`ab46be14     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000069`ec1feac8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`ab46be14


SYMBOL_NAME:  nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1fe

FAILURE_BUCKET_ID:  0x1_SysCallNum_4_nt!KiSystemServiceExitPico

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {52cd694c-15ec-48c3-924a-3539560711db}

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



KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL (192)
A lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or
above.
Arguments:
Arg1: ffffe68a8f220080, The address of the thread.
Arg2: ffffb60620b82810, The lock address.
Arg3: 0000000000000000, The IRQL at which the lock was acquired.
Arg4: 0000000000000000, Reserved.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 8124

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 8670

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  192

BUGCHECK_P1: ffffe68a8f220080

BUGCHECK_P2: ffffb60620b82810

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

STACK_TEXT: 
ffffd907`71c536c8 fffff807`49cdb37b     : 00000000`00000192 ffffe68a`8f220080 ffffb606`20b82810 00000000`00000000 : nt!KeBugCheckEx
ffffd907`71c536d0 fffff807`56aad91d     : ffffb606`20b827d0 00000000`00000000 00000000`00000000 00000000`00000078 : nt!ExAcquirePushLockExclusiveEx+0x14b
ffffd907`71c53710 fffff807`56aad80d     : 00000000`00000000 0000024f`55fee9a8 ffffe68a`8f33d080 ffffe68a`8f220080 : Npfs!NpCommonWrite+0x8d
ffffd907`71c537a0 fffff807`49ccd805     : ffffe68a`8314e040 ffffe68a`8314e040 00000000`00000001 ffffe68a`8f33d080 : Npfs!NpFsdWrite+0x6d
ffffd907`71c53810 fffff807`46f64906     : 00000000`00000000 00000000`00000008 00000000`00000000 00000000`00000006 : nt!IofCallDriver+0x55
ffffd907`71c53850 fffff807`49ccd805     : ffffe68a`8f33d080 ffff8881`7f9de180 ffffe68a`8f220080 fffff807`49cdf4cf : FLTMGR!FltpDispatch+0xd6
ffffd907`71c538b0 fffff807`4a0c2528     : ffffe68a`8f33d080 00000000`00000000 ffffe68a`8f33d080 00000000`00000000 : nt!IofCallDriver+0x55
ffffd907`71c538f0 fffff807`4a0b8e7f     : ffffb606`00000000 ffffd907`71c53b80 00000085`72dfe840 ffffd907`71c53b80 : nt!IopSynchronousServiceTail+0x1a8
ffffd907`71c53990 fffff807`49e05fb8     : 00000000`00000000 00000000`00000000 00000000`00000000 0000024f`4bbb56a0 : nt!NtWriteFile+0x66f
ffffd907`71c53a90 00007fff`12fcbe94     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000085`72dfe7c8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`12fcbe94


SYMBOL_NAME:  Npfs!NpCommonWrite+8d

MODULE_NAME: Npfs

IMAGE_NAME:  Npfs.SYS

IMAGE_VERSION:  10.0.19041.1030

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  8d

FAILURE_BUCKET_ID:  0x192_Npfs!NpCommonWrite

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b7319621-14de-e629-6081-59b046fb7272}

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



APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 0000000077681cfc, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffff9c0e1f756b80, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6390

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 9163

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1

BUGCHECK_P1: 77681cfc

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: ffff9c0e1f756b80

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  ui32.exe

STACK_TEXT: 
ffff9c0e`1f7569b8 fffff802`2c606569     : 00000000`00000001 00000000`77681cfc 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
ffff9c0e`1f7569c0 fffff802`2c606433     : ffffa683`a2f5b000 00000000`00000001 ffff9c0e`1f756b18 ffffffff`ffff15a0 : nt!KiBugCheckDispatch+0x69
ffff9c0e`1f756b00 00000000`77681cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000000`051debb8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77681cfc


SYMBOL_NAME:  nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1fe

FAILURE_BUCKET_ID:  0x1_SysCallNum_d0004_nt!KiSystemServiceExitPico

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1e5e8093-a7e6-a911-7b9b-47d4229c250f}

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



APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 00007ffa18d33c54, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 0000000000000001, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffffd0c3a2b5b80, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7374

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 8986

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1

BUGCHECK_P1: 7ffa18d33c54

BUGCHECK_P2: 0

BUGCHECK_P3: 1

BUGCHECK_P4: fffffd0c3a2b5b80

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  ui32.exe

STACK_TEXT: 
fffffd0c`3a2b59b8 fffff800`1a206569     : 00000000`00000001 00007ffa`18d33c54 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx
fffffd0c`3a2b59c0 fffff800`1a206433     : ffffa301`738350c0 ffffa301`738350c0 00000000`00000000 ffffa301`00000000 : nt!KiBugCheckDispatch+0x69
fffffd0c`3a2b5b00 00007ffa`18d33c54     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000000`0123ded8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`18d33c54


SYMBOL_NAME:  nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1fe

FAILURE_BUCKET_ID:  0x1_SysCallNum_11e8_nt!KiSystemServiceExitPico

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a7ddfb5c-67c7-e920-9c0a-27f59d9bbb7d}

Followup:     MachineOwner
---------
 
kerobey dedi:
Kahin misin sen? Minidump dosyasına gerek yok diyorsun. Bu arada sorunun ekran kartı kaynaklı olduğunu nereden biliyorsun?
Genişletmek için tıkla...

Evet kahinim. Aynı sorunu bende yaşadım. Aylarca uğraştım. Bu sitedede 10 defa konu açmışımdır. AMD RX serisi kartların kronik sorunu bu. İyi günler dilerim.
 
Son düzenleyen: Moderatör:
Bora Dere dedi:
Belleklere test yapın.

Memtest86 USB'den Çalışan RAM Test Programı

RAM'lerinizi test etmek için kullanabileceğiniz en kapsamlı yazılım Memtest86'dır. Aracı USB belleğe yazmak için: Bu video rehberde Memtest86 ile belleklerinizi nasıl test edeceğinizi öğrenebilirsiniz: Adım adım: Öncelikle yazılımı buradan indirin. UEFI desteği olmayan eski sistemler...
www.technopat.net www.technopat.net

Disklerinize HD Tune ile hata ve sağlık testi yapın. Quick scan kapalı olsun. Vanguard kaldırın ve BIOS güncelleyin.
Genişletmek için tıkla...

BIOS'umu güncelledim zaten.
Belleklere test yapayım.
 
Son düzenleyen: Moderatör:
Ventolas dedi:
Evet kahinim. Aynı sorunu bende yaşadım. Aylarca uğraştım. Bu sitedede 10 defa konu açmışımdır. AMD RX serisi kartların kronik sorunu bu. İyi günler dilerim.
Genişletmek için tıkla...

Dostum tahmin yürüterek genelleme yaparak sorun çözeceksek çok işimiz var. Mavi ekranın bir sürü nedeni var bunlardan hangi biri olduğunu DMP dosyasını incelemeden cevaplayamazsın.

  • Örneğin OS Windows 7. Windows 10 sürücüsü kurarsan stabilite vs. yüzünden mavi ekran verebilir.
  • Microsoft tarafından yayınlanan güncellemede hata varsa mavi ekran alabilirsiniz.
  • Stabilitesi tam olmayan beta sürücüler.
  • Bazı zararlı yazılımlar yüzünden gelen mavi ekran.
  • Bozuk RAM veya RAM slotu olabilir. (Memtest86 ile RAM testi yapılabilir.)
  • HDD'deki bad sector veya sağlık %0 olması.
  • Bozuk anakart.
  • Bozuk işlemci.
  • Eğer işlemcide igpu yoksa ve harici GPU varsa harici GPU'nun bozuk olması.
  • Yüksek sıcaklık değerleri.
  • Wi-Fi kartı varsa bozuk olması.
  • %100 RAM kullanımıyla gelen mavi ekran.
 
Dosyanızda BIOS güncel görünmüyordu, şu anki BIOS'un sürümü nedir? Ya sonradan güncellediniz ya da güncellediğinizi sanıyorsunuz.
 

Benzer konular

kerioooo
Mavi ekran hatası
Mesaj
0
Görüntüleme
245
kerioooo
kerioooo
spartakboskova
Mavi ekran hatası
Mesaj
2
Görüntüleme
409
spartakboskova
spartakboskova
senasb
Mavi ekran hatası neden olur?
2 3
Mesaj
23
Görüntüleme
2B
senasb
senasb
Bora55
DRIVER_POWER_STATE_FAILURE mavi ekran hatası
Mesaj
0
Görüntüleme
179
Bora55
Bora55
K
  • Soru
UNEXPECTED_STORE_EXCEPTION mavi ekran hatası
Mesaj
6
Görüntüleme
451
Enes3078
Enes3078

Yeni konular

Yeni mesajlar

Geri
Yukarı