Çözüldü notskrnl.exe Mavi Ekran hatası

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

altuwl

Decapat
Katılım
5 Mart 2021
Mesajlar
66
Herkese selamlar,
Son bir ay içerisinde çok fazla kez mavi ekran hatası aldım. Başlarda aldığım kodlar yüzünden format atmıştım, artık farklı hata kodlarını sürekli almaya başladım. Paylaştığım linkteki ekran resmi son aldığım hata içindir. O resimin üzerine neredeyse her gün hata almaya devam ettim. Sebebini tam olarak çözebilmiş değilim. Her türlü güncelleştirmeyi denediğimi düşünüyorum. Monster Abra A5 v15.8.3 kullanıyorum, sorunlar için destek talebi aldım ama çözümleri işe yaramadı. Aynı sorunu yaşayan insanların konularına rastladım ama çözümlenmediğini görüp bu başlığı açıyorum.

Sizler için minidumplar.
Hata kodlarım:
Netwtw08.sys
ntoskrnl.exe
 
Son düzenleyen: Moderatör:
Çözüm
Aynı sorunu yaşayan insanların konularına rastladım ama çözümlenmediğini görüp bu başlığı açıyorum.

İyi ki açmışsınız çünkü herkesin sorunu farklı oluyor. Lütfen farklı konularda sunduğumuz çözüm önerilerini direkt olarak uygulamayınız.

Şimdi gelelim çözüm adımlarına.

1) Aşağıdaki sürücüyü indirip kurun. (Wi-Fi)

2) Aşağıdaki sürücüyü indirip kurun. (LAN)

3) Bilgisayara takılı tüm USB aygıtlarını çıkartın.

4) Aşağıdaki sürücüyü indirip kurun. (Dahili grafik birimi)

5) NVIDIA ekran kartınızın sürücüsünü güncelleyin.

6) Monster Kontrol Merkezi'ni bir süre açmayın ve kullanmayın. Yaptığınız bir ayar varsa varsayılan ayarlara döndürün.

7) Vanguard kaldırın.

8) Aşağıdaki rehberi uygulayıp sonucun ekran alıntısını paylaşın.


Lütfen sorununuz çözülürse geri bildirimde bulunmayı unutmayın. :)

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_DXGKRNL_FATAL_ERROR (113)
The dxgkrnl has detected that a violation has occurred. This resulted
in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl
is attempting to get enough information into the minidump such that somebody
can pinpoint the crash cause. Any other values after parameter 1 must be
individually examined according to the subtype.
Arguments:
Arg1: 000000000000002b, The subtype of the bugcheck:
Arg2: ffffc6855a14d820
Arg3: 0000000000000000
Arg4: 0000000000000000

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 8546

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-5QPUIS0

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 38666

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

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

BUGCHECK_P1: 2b

BUGCHECK_P2: ffffc6855a14d820

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

STACK_TEXT:
ffffc586`fbdfa638 fffff804`6efb3ad0 : 00000000`00000113 00000000`0000002b ffffc685`5a14d820 00000000`00000000 : nt!KeBugCheckEx
ffffc586`fbdfa640 fffff804`6ed8b3a4 : ffffc685`5a14d820 ffffc685`5a14da01 ffffc685`5a14da01 ffffc586`fbdfa740 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffc586`fbdfa680 fffff804`6ecd979c : ffffc685`5a14d820 ffffc685`5d2c0280 ffffc685`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyAllDeviceState+0xb1584
ffffc586`fbdfa6c0 fffff804`6ecd9443 : ffffc685`5a14d820 ffffd78b`c38d36e0 ffffc685`5a14d820 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::DestroyDevice+0xd8
ffffc586`fbdfa6f0 fffff804`6ecd92e2 : ffffc685`5a14d820 ffffd78b`00000001 ffffc685`5a14d820 ffffc685`5a14d820 : dxgkrnl!ADAPTER_RENDER::DestroyDeviceNoLocksInternal+0x83
ffffc586`fbdfa800 fffff804`6ecd91f4 : ffffc685`5a14d820 ffffc586`fbdfaa80 00000000`00000166 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::DestroyDeviceNoLocks+0x92
ffffc586`fbdfa830 fffff804`6ecd8ecb : 01d6fcbf`9ff319d5 ffffd78b`c8c82040 00000000`00000000 00000000`00000020 : dxgkrnl!DxgkDestroyDeviceImpl+0x31c
ffffc586`fbdfa9d0 fffff804`57e071b5 : ffffd78b`c8c82040 ffffd78b`c8c82040 00000000`00000000 ffffd78b`d7aa6be0 : dxgkrnl!DxgkDestroyDevice+0xb
ffffc586`fbdfaa00 00007ffa`40a24a24 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000057`5507c908 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`40a24a24


SYMBOL_NAME: dxgkrnl!DXGDEVICE::DestroyAllDeviceState+b1584

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.19041.746

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: b1584

FAILURE_BUCKET_ID: 0x113_dxgkrnl!DXGDEVICE::DestroyAllDeviceState

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {8911b1bb-618c-613a-9115-07ff1adc5545}

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8058b1011d6, address which referenced memory

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

*** WARNING: Unable to verify timestamp for Netwtw08.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 8702

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-5QPUIS0

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 29957

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

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

BUGCHECK_P1: 30

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8058b1011d6

READ_ADDRESS: fffff80573afb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80573a0f330: Unable to get Flags value from nt!KdVersionBlock
fffff80573a0f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000030

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: WmiPrvSE.exe

DPC_STACK_BASE: FFFFF80576C75FB0

TRAP_FRAME: fffff80576c756f0 -- (.trap 0xfffff80576c756f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8058b2228f0
rdx=0000000000000010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8058b1011d6 rsp=fffff80576c75880 rbp=fffff8058b1e3428
r8=0000000000000040 r9=fffff8058b2228f0 r10=fffff8058b1a14d0
r11=fffff8058b15fd40 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
Netwtw08+0x4811d6:
fffff805`8b1011d6 80783000 cmp byte ptr [rax+30h],0 ds:00000000`00000030=??
Resetting default scope

STACK_TEXT:
fffff805`76c755a8 fffff805`73207a69 : 00000000`0000000a 00000000`00000030 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff805`76c755b0 fffff805`73203d69 : 0000ffff`00030016 00000000`00000000 fffff805`00000000 fffff805`8af044b2 : nt!KiBugCheckDispatch+0x69
fffff805`76c756f0 fffff805`8b1011d6 : fffff805`8b101120 00001950`0000000f fffff805`8b127b94 00000000`00000002 : nt!KiPageFault+0x469
fffff805`76c75880 fffff805`8b101120 : 00001950`0000000f fffff805`8b127b94 00000000`00000002 fffff805`76c75920 : Netwtw08+0x4811d6
fffff805`76c75888 00001950`0000000f : fffff805`8b127b94 00000000`00000002 fffff805`76c75920 00000000`00000004 : Netwtw08+0x481120
fffff805`76c75890 fffff805`8b127b94 : 00000000`00000002 fffff805`76c75920 00000000`00000004 00000000`00000000 : 0x00001950`0000000f
fffff805`76c75898 00000000`00000002 : fffff805`76c75920 00000000`00000004 00000000`00000000 00000000`00000007 : Netwtw08+0x4a7b94
fffff805`76c758a0 fffff805`76c75920 : 00000000`00000004 00000000`00000000 00000000`00000007 00000000`00010006 : 0x2
fffff805`76c758a8 00000000`00000004 : 00000000`00000000 00000000`00000007 00000000`00010006 fffff805`8b15fd40 : 0xfffff805`76c75920
fffff805`76c758b0 00000000`00000000 : 00000000`00000007 00000000`00010006 fffff805`8b15fd40 fffff805`8b1a14d0 : 0x4


SYMBOL_NAME: Netwtw08+4811d6

MODULE_NAME: Netwtw08

IMAGE_NAME: Netwtw08.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 4811d6

FAILURE_BUCKET_ID: AV_Netwtw08!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a952742b-cdaa-1618-647d-b14a244b91d9}

Followup: MachineOwner
---------[/CODE]
Aynı sorunu yaşayan insanların konularına rastladım ama çözümlenmediğini görüp bu başlığı açıyorum.

İyi ki açmışsınız çünkü herkesin sorunu farklı oluyor. Lütfen farklı konularda sunduğumuz çözüm önerilerini direkt olarak uygulamayınız.

Şimdi gelelim çözüm adımlarına.

1) Aşağıdaki sürücüyü indirip kurun. (Wi-Fi)

2) Aşağıdaki sürücüyü indirip kurun. (LAN)

3) Bilgisayara takılı tüm USB aygıtlarını çıkartın.

4) Aşağıdaki sürücüyü indirip kurun. (Dahili grafik birimi)

5) NVIDIA ekran kartınızın sürücüsünü güncelleyin.

6) Monster Kontrol Merkezi'ni bir süre açmayın ve kullanmayın. Yaptığınız bir ayar varsa varsayılan ayarlara döndürün.

7) Vanguard kaldırın.

8) Aşağıdaki rehberi uygulayıp sonucun ekran alıntısını paylaşın.


Lütfen sorununuz çözülürse geri bildirimde bulunmayı unutmayın. :)

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_DXGKRNL_FATAL_ERROR (113)
The dxgkrnl has detected that a violation has occurred. This resulted
in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl
is attempting to get enough information into the minidump such that somebody
can pinpoint the crash cause. Any other values after parameter 1 must be
individually examined according to the subtype.
Arguments:
Arg1: 000000000000002b, The subtype of the bugcheck:
Arg2: ffffc6855a14d820
Arg3: 0000000000000000
Arg4: 0000000000000000

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 8546

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-5QPUIS0

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 38666

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

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

BUGCHECK_P1: 2b

BUGCHECK_P2: ffffc6855a14d820

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

STACK_TEXT:
ffffc586`fbdfa638 fffff804`6efb3ad0 : 00000000`00000113 00000000`0000002b ffffc685`5a14d820 00000000`00000000 : nt!KeBugCheckEx
ffffc586`fbdfa640 fffff804`6ed8b3a4 : ffffc685`5a14d820 ffffc685`5a14da01 ffffc685`5a14da01 ffffc586`fbdfa740 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffc586`fbdfa680 fffff804`6ecd979c : ffffc685`5a14d820 ffffc685`5d2c0280 ffffc685`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyAllDeviceState+0xb1584
ffffc586`fbdfa6c0 fffff804`6ecd9443 : ffffc685`5a14d820 ffffd78b`c38d36e0 ffffc685`5a14d820 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::DestroyDevice+0xd8
ffffc586`fbdfa6f0 fffff804`6ecd92e2 : ffffc685`5a14d820 ffffd78b`00000001 ffffc685`5a14d820 ffffc685`5a14d820 : dxgkrnl!ADAPTER_RENDER::DestroyDeviceNoLocksInternal+0x83
ffffc586`fbdfa800 fffff804`6ecd91f4 : ffffc685`5a14d820 ffffc586`fbdfaa80 00000000`00000166 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::DestroyDeviceNoLocks+0x92
ffffc586`fbdfa830 fffff804`6ecd8ecb : 01d6fcbf`9ff319d5 ffffd78b`c8c82040 00000000`00000000 00000000`00000020 : dxgkrnl!DxgkDestroyDeviceImpl+0x31c
ffffc586`fbdfa9d0 fffff804`57e071b5 : ffffd78b`c8c82040 ffffd78b`c8c82040 00000000`00000000 ffffd78b`d7aa6be0 : dxgkrnl!DxgkDestroyDevice+0xb
ffffc586`fbdfaa00 00007ffa`40a24a24 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000057`5507c908 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`40a24a24


SYMBOL_NAME: dxgkrnl!DXGDEVICE::DestroyAllDeviceState+b1584

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.19041.746

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: b1584

FAILURE_BUCKET_ID: 0x113_dxgkrnl!DXGDEVICE::DestroyAllDeviceState

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {8911b1bb-618c-613a-9115-07ff1adc5545}

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8058b1011d6, address which referenced memory

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

*** WARNING: Unable to verify timestamp for Netwtw08.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 8702

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-5QPUIS0

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 29957

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

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

BUGCHECK_P1: 30

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8058b1011d6

READ_ADDRESS: fffff80573afb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80573a0f330: Unable to get Flags value from nt!KdVersionBlock
fffff80573a0f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000030

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: WmiPrvSE.exe

DPC_STACK_BASE: FFFFF80576C75FB0

TRAP_FRAME: fffff80576c756f0 -- (.trap 0xfffff80576c756f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8058b2228f0
rdx=0000000000000010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8058b1011d6 rsp=fffff80576c75880 rbp=fffff8058b1e3428
r8=0000000000000040 r9=fffff8058b2228f0 r10=fffff8058b1a14d0
r11=fffff8058b15fd40 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
Netwtw08+0x4811d6:
fffff805`8b1011d6 80783000 cmp byte ptr [rax+30h],0 ds:00000000`00000030=??
Resetting default scope

STACK_TEXT:
fffff805`76c755a8 fffff805`73207a69 : 00000000`0000000a 00000000`00000030 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff805`76c755b0 fffff805`73203d69 : 0000ffff`00030016 00000000`00000000 fffff805`00000000 fffff805`8af044b2 : nt!KiBugCheckDispatch+0x69
fffff805`76c756f0 fffff805`8b1011d6 : fffff805`8b101120 00001950`0000000f fffff805`8b127b94 00000000`00000002 : nt!KiPageFault+0x469
fffff805`76c75880 fffff805`8b101120 : 00001950`0000000f fffff805`8b127b94 00000000`00000002 fffff805`76c75920 : Netwtw08+0x4811d6
fffff805`76c75888 00001950`0000000f : fffff805`8b127b94 00000000`00000002 fffff805`76c75920 00000000`00000004 : Netwtw08+0x481120
fffff805`76c75890 fffff805`8b127b94 : 00000000`00000002 fffff805`76c75920 00000000`00000004 00000000`00000000 : 0x00001950`0000000f
fffff805`76c75898 00000000`00000002 : fffff805`76c75920 00000000`00000004 00000000`00000000 00000000`00000007 : Netwtw08+0x4a7b94
fffff805`76c758a0 fffff805`76c75920 : 00000000`00000004 00000000`00000000 00000000`00000007 00000000`00010006 : 0x2
fffff805`76c758a8 00000000`00000004 : 00000000`00000000 00000000`00000007 00000000`00010006 fffff805`8b15fd40 : 0xfffff805`76c75920
fffff805`76c758b0 00000000`00000000 : 00000000`00000007 00000000`00010006 fffff805`8b15fd40 fffff805`8b1a14d0 : 0x4


SYMBOL_NAME: Netwtw08+4811d6

MODULE_NAME: Netwtw08

IMAGE_NAME: Netwtw08.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 4811d6

FAILURE_BUCKET_ID: AV_Netwtw08!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a952742b-cdaa-1618-647d-b14a244b91d9}

Followup: MachineOwner
---------[/CODE]
 
Çözüm
Peki o halde bekliyor olacağım. Lütfen sorun çözülünce ya da yeniden olunda yeni dumplarla beraber mesajınızı yazın. Bu mesajı yazıyorum ki bir dahaki mesajınız üst üste binmesin ve bildirimi bana gelsin. Bu saatten sonra yalnızca çözülüp çözülmediği hakkında mesaj yazarsanız sevinirim.
 
Peki o halde bekliyor olacağım. Lütfen sorun çözülünce ya da yeniden olunda yeni dumplarla beraber mesajınızı yazın. Bu mesajı yazıyorum ki bir dahaki mesajınız üst üste binmesin ve bildirimi bana gelsin. Bu saatten sonra yalnızca çözülüp çözülmediği hakkında mesaj yazarsanız sevinirim.
Selamlar, dediğiniz şekilde ve sırada işlemleri yaptım. Komutu yazdıktan sonra da şu şekil bir çıktı aldım. Tekrar mavi ekran hatası almam durumunda ne yapmamı önerirsiniz? Bu başlıktan size yanıt atabilir miyim?
 

Dosya Ekleri

  • Ekran görüntüsü 2021-03-09 094902.png
    Ekran görüntüsü 2021-03-09 094902.png
    39,8 KB · Görüntüleme: 31
Sorun artık çözüldüyse de çözüldüğünü mesajınızda belirtip çözüm içerikli mesajı çözüm olarak seçebilirsiniz. Şimdilik bir sorun görünmüyor. :)
 

Yeni konular

Geri
Yukarı