BSoD olmasının sebebi nedir?

Tarihe göre sırala Puana göre sırala
Merhaba.

Sorun ekran kartı sürücüsü kaynaklı oluşmuş. Video Memory Management mekanizması, bellek yönetimi için gereken Page table bilgisinin alınması esnasında hataya düşüyor.

Sistemde hangi ekran kartı/kartları bulunuyor?

Kod: 
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000002d, The subtype of the BugCheck:
Arg2: ffff8309d0739e30
Arg3: ffff8309e6efbbc0
Arg4: ffffb70f326fea50

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1484

    Key  : Analysis.Elapsed.mSec
    Value: 8969

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29507.1001

    Key  : Analysis.Version.Description
    Value: 10.2511.5.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2511.5.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x10e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x10e

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x10e_2d_dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress

    Key  : Failure.Hash
    Value: {ca00cb12-3ce5-2e41-c763-7f0f8a8fbadd}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 1

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 38670575

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x24e10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x3f7

    Key  : WER.System.BIOSRevision
    Value: 15.11.0.0


BUGCHECK_CODE:  10e

BUGCHECK_P1: 2d

BUGCHECK_P2: ffff8309d0739e30

BUGCHECK_P3: ffff8309e6efbbc0

BUGCHECK_P4: ffffb70f326fea50

FILE_IN_CAB:  021726-33578-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff9302a50f8340

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffb70f`326fe958 fffff807`18fb1316     : 00000000`0000010e 00000000`0000002d ffff8309`d0739e30 ffff8309`e6efbbc0 : nt!KeBugCheckEx
ffffb70f`326fe960 fffff807`314b77ee     : ffffb70f`326fea38 ffff8309`d0739e30 ffff830a`1c4c5ab0 00000000`00000000 : watchdog!WdLogSingleEntry5+0x156
ffffb70f`326fe9f0 fffff807`314b67ca     : ffff8309`00010000 ffff9302`a4e0eb00 ffffb70f`326febd0 ffff830a`133f45b0 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+0x57e
ffffb70f`326fead0 fffff807`314b6650     : ffff9302`995548e0 00000000`00000002 ffff8309`eddf8280 ffff9302`a529f000 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetDriverUpdateAddress+0x66
ffffb70f`326feb40 fffff807`314f51f3     : ffff8309`00000000 00000000`00000000 00000000`00000000 ffffb70f`326ff080 : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTableInvalidate+0x50
ffffb70f`326fec10 fffff807`314f61b3     : 00000000`00040000 00000000`00000002 00000000`00000100 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x563
ffffb70f`326fecb0 fffff807`314f636b     : 00000000`00000002 ffff8309`eddf8280 ffffb70f`326ff080 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0xc93
ffffb70f`326fee30 fffff807`314b9362     : 00000000`00040000 ffff8309`eddf8280 ffffb70f`326ff080 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0xe4b
ffffb70f`326fefb0 fffff807`314f9311     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff0ace`87dfbb48 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x972
ffffb70f`326ff140 fffff807`314e1768     : 00000000`00000000 00000000`00000000 00000000`00000004 ffffb70f`326ff310 : dxgmms2!VIDMM_GLOBAL::InitPagingProcessVaSpace+0x205
ffffb70f`326ff2f0 fffff807`314dfbbf     : ffff8309`e8f08c80 ffff8309`eddf85f0 ffff8309`eddf85f0 ffff8309`e8f08c80 : dxgmms2!VIDMM_GLOBAL::ProcessSystemCommand+0x500
ffffb70f`326ff3f0 fffff807`314f1571     : ffff8309`ea0df000 ffffb70f`326ff509 fffff807`3145e490 ffff9302`a52a8c20 : dxgmms2!VidMmSubmitPacket+0x15f
ffffb70f`326ff450 fffff807`8748966a     : ffff9302`a50f8301 fffff807`314f0e00 ffffa380`4e000100 025fe07f`b8bbbd02 : dxgmms2!VidMmWorkerThreadProc+0x681
ffffb70f`326ff570 fffff807`876ab774     : ffffa380`4e000180 ffff9302`a50f8340 fffff807`87489610 2765a7d9`fb68c723 : nt!PspSystemThreadStartup+0x5a
ffffb70f`326ff5c0 00000000`00000000     : ffffb70f`32700000 ffffb70f`326f9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+57e

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.26100.7705

STACK_COMMAND: .process /r /p 0xffff93027155a040; .thread 0xffff9302a50f8340 ; kb

BUCKET_ID_FUNC_OFFSET:  57e

FAILURE_BUCKET_ID:  0x10e_2d_dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ca00cb12-3ce5-2e41-c763-7f0f8a8fbadd}

Followup:     MachineOwner
---------
 
Artı 0 Eksi
KojiroHyuga04 dedi:
Merhaba.

Sorun ekran kartı sürücüsü kaynaklı oluşmuş. Video MEMORY_MANAGEMENT mekanizması, bellek yönetimi için gereken page table bilgisinin alınması esnasında hataya düşüyor.

Sistemde hangi ekran kartı/kartları bulunuyor?

Kod: 
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that.
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000002d, The subtype of the BugCheck:
Arg2: ffff8309d0739e30.
Arg3: ffff8309e6efbbc0.
Arg4: ffffb70f326fea50.

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1484.

 Key : Analysis.Elapsed.mSec
 Value: 8969.

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

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

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

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

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

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

 Key : Analysis.Version.DbgEng
 Value: 10.0.29507.1001

 Key : Analysis.Version.Description
 Value: 10.2511.5.1 amd64fre.

 Key : Analysis.Version.Ext
 Value: 1.2511.5.1

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x10e.

 Key : Bugcheck.Code.TargetModel
 Value: 0x10e.

 Key : Dump.Attributes.AsUlong
 Value: 0x21808.

 Key : Dump.Attributes.DiagDataWrittenToHeader
 Value: 1

 Key : Dump.Attributes.ErrorCode
 Value: 0x0.

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

 Key : Dump.Attributes.LastLine
 Value: Dump completed successfully.

 Key : Dump.Attributes.ProgressPercentage
 Value: 0

 Key : Failure.Bucket
 Value: 0x10e_2d_dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress

 Key : Failure.Hash
 Value: {ca00cb12-3ce5-2e41-c763-7f0f8a8fbadd}

 Key : Hypervisor.Enlightenments.ValueHex
 Value: 0x7497cf94.

 Key : Hypervisor.Flags.AnyHypervisorPresent
 Value: 1

 Key : Hypervisor.Flags.ApicEnlightened
 Value: 1

 Key : Hypervisor.Flags.ApicVirtualizationAvailable
 Value: 0

 Key : Hypervisor.Flags.AsyncMemoryHint
 Value: 0

 Key : Hypervisor.Flags.CoreSchedulerRequested
 Value: 0

 Key : Hypervisor.Flags.CpuManager
 Value: 1

 Key : Hypervisor.Flags.DeprecateAutoEoi
 Value: 0

 Key : Hypervisor.Flags.DynamicCpuDisabled
 Value: 1

 Key : Hypervisor.Flags.Epf
 Value: 0

 Key : Hypervisor.Flags.ExtendedProcessorMasks
 Value: 1

 Key : Hypervisor.Flags.HardwareMbecAvailable
 Value: 1

 Key : Hypervisor.Flags.MaxBankNumber
 Value: 0

 Key : Hypervisor.Flags.MemoryZeroingControl
 Value: 1

 Key : Hypervisor.Flags.NoExtendedRangeFlush
 Value: 0

 Key : Hypervisor.Flags.NoNonArchCoreSharing
 Value: 1

 Key : Hypervisor.Flags.Phase0InitDone
 Value: 1

 Key : Hypervisor.Flags.PowerSchedulerQos
 Value: 0

 Key : Hypervisor.Flags.RootScheduler
 Value: 0

 Key : Hypervisor.Flags.SynicAvailable
 Value: 1

 Key : Hypervisor.Flags.UseQpcBias
 Value: 0

 Key : Hypervisor.Flags.Value
 Value: 38670575.

 Key : Hypervisor.Flags.ValueHex
 Value: 0x24e10ef.

 Key : Hypervisor.Flags.VpAssistPage
 Value: 1

 Key : Hypervisor.Flags.VsmAvailable
 Value: 1

 Key : Hypervisor.RootFlags.AccessStats
 Value: 1

 Key : Hypervisor.RootFlags.CrashdumpEnlightened
 Value: 1

 Key : Hypervisor.RootFlags.CreateVirtualProcessor
 Value: 1

 Key : Hypervisor.RootFlags.DisableHyperthreading
 Value: 0

 Key : Hypervisor.RootFlags.HostTimelineSync
 Value: 1

 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
 Value: 0

 Key : Hypervisor.RootFlags.IsHyperV
 Value: 1

 Key : Hypervisor.RootFlags.LivedumpEnlightened
 Value: 1

 Key : Hypervisor.RootFlags.MapDeviceInterrupt
 Value: 1

 Key : Hypervisor.RootFlags.MceEnlightened
 Value: 1

 Key : Hypervisor.RootFlags.Nested
 Value: 0

 Key : Hypervisor.RootFlags.StartLogicalProcessor
 Value: 1

 Key : Hypervisor.RootFlags.Value
 Value: 1015.

 Key : Hypervisor.RootFlags.ValueHex
 Value: 0x3f7.

 Key : WER.System.BIOSRevision
 Value: 15.11.0.0

BUGCHECK_CODE: 10e.

BUGCHECK_P1: 2d.

BUGCHECK_P2: ffff8309d0739e30.

BUGCHECK_P3: ffff8309e6efbbc0.

BUGCHECK_P4: ffffb70f326fea50.

FILE_IN_CAB: 021726-33578-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b.

DUMP_FILE_ATTRIBUTES: 0x21808.
 Kernel Generated Triage Dump.

FAULTING_THREAD: ffff9302a50f8340.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1 (!blackboxwinlogon)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

STACK_TEXT:
ffffb70f`326fe958 fffff807`18fb1316 : 00000000`0000010e 00000000`0000002d ffff8309`d0739e30 ffff8309`e6efbbc0 : nt!KeBugCheckEx
ffffb70f`326fe960 fffff807`314b77ee : ffffb70f`326fea38 ffff8309`d0739e30 ffff830a`1c4c5ab0 00000000`00000000 : watchdog!WdLogSingleEntry5+0x156
ffffb70f`326fe9f0 fffff807`314b67ca : ffff8309`00010000 ffff9302`a4e0eb00 ffffb70f`326febd0 ffff830a`133f45b0 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+0x57e
ffffb70f`326fead0 fffff807`314b6650 : ffff9302`995548e0 00000000`00000002 ffff8309`eddf8280 ffff9302`a529f000 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetDriverUpdateAddress+0x66
ffffb70f`326feb40 fffff807`314f51f3 : ffff8309`00000000 00000000`00000000 00000000`00000000 ffffb70f`326ff080 : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTableInvalidate+0x50
ffffb70f`326fec10 fffff807`314f61b3 : 00000000`00040000 00000000`00000002 00000000`00000100 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x563
ffffb70f`326fecb0 fffff807`314f636b : 00000000`00000002 ffff8309`eddf8280 ffffb70f`326ff080 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0xc93
ffffb70f`326fee30 fffff807`314b9362 : 00000000`00040000 ffff8309`eddf8280 ffffb70f`326ff080 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0xe4b
ffffb70f`326fefb0 fffff807`314f9311 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff0ace`87dfbb48 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x972
ffffb70f`326ff140 fffff807`314e1768 : 00000000`00000000 00000000`00000000 00000000`00000004 ffffb70f`326ff310 : dxgmms2!VIDMM_GLOBAL::InitPagingProcessVaSpace+0x205
ffffb70f`326ff2f0 fffff807`314dfbbf : ffff8309`e8f08c80 ffff8309`eddf85f0 ffff8309`eddf85f0 ffff8309`e8f08c80 : dxgmms2!VIDMM_GLOBAL::ProcessSystemCommand+0x500
ffffb70f`326ff3f0 fffff807`314f1571 : ffff8309`ea0df000 ffffb70f`326ff509 fffff807`3145e490 ffff9302`a52a8c20 : dxgmms2!VidMmSubmitPacket+0x15f
ffffb70f`326ff450 fffff807`8748966a : ffff9302`a50f8301 fffff807`314f0e00 ffffa380`4e000100 025fe07f`b8bbbd02 : dxgmms2!VidMmWorkerThreadProc+0x681
ffffb70f`326ff570 fffff807`876ab774 : ffffa380`4e000180 ffff9302`a50f8340 fffff807`87489610 2765a7d9`fb68c723 : nt!PspSystemThreadStartup+0x5a
ffffb70f`326ff5c0 00000000`00000000 : ffffb70f`32700000 ffffb70f`326f9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+57e

MODULE_NAME: dxgmms2.

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.26100.7705

STACK_COMMAND: .process /r /p 0xffff93027155a040; .thread 0xffff9302a50f8340 ; kb.

BUCKET_ID_FUNC_OFFSET: 57e.

FAILURE_BUCKET_ID: 0x10e_2d_dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {ca00cb12-3ce5-2e41-c763-7f0f8a8fbadd}

Followup: MachineOwner.
---------
Genişletmek için tıkla...

Ekran kartı olarak RTX 4060 bulunuyor.
 
Artı 0 Eksi
4060 için kullanılan sürücülerin güncellemesi sonrasında mı bu hata oluşmaya başladı?
Eğer öyleyse, DDU ile halihazırda kurulu sürücüyü silip stabil bir sürüm kuralım.

www.nvidia.com

Sürücü Ayrıntıları | NVIDIA

<dd~LanguageName> <dd~Name> indirin (<dd~OSName> sistemleri için). Çıkış tarihi: <dd~ReleaseDateTime>
www.nvidia.com

Rehber: DDU ile Sürücü Kaldırma Rehberi

Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...
www.technopat.net www.technopat.net
 
Artı 0 Eksi
KojiroHyuga04 dedi:
4060 için kullanılan sürücülerin güncellemesi sonrasında mı bu hata oluşmaya başladı?
Eğer öyleyse, DDU ile halihazırda kurulu sürücüyü silip stabil bir sürüm kuralım.

www.nvidia.com

Sürücü Ayrıntıları | NVIDIA

<dd~LanguageName> <dd~Name> indirin (<dd~OSName> sistemleri için). Çıkış tarihi: <dd~ReleaseDateTime>
www.nvidia.com

Rehber: DDU ile Sürücü Kaldırma Rehberi

Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...
www.technopat.net www.technopat.net
Genişletmek için tıkla...

Sürücüyü kuralı 2-3 gün oldu. Hiper-v yi dün açtım ve ondan sonra oldu.
 
Artı 0 Eksi
KojiroHyuga04 dedi:
Sürücü kaynaklı bir sıkıntı var, döküm özelinde olan durumu yukarıda belirttim :)

DDU ile sürücünüzü kaldırıp verdiğim linkteki sürücüyü kurarak sisteminizi 1-2 gün gözlemleyebilir misiniz?
Genişletmek için tıkla...

Tamamdır yarın ilk işim olarak bunu halledeceğim. Zaman ayırdığınız için teşekkür ederim.
 
Artı 0 Eksi

Benzer konular

H
  • Soru
Siyah ekran sebebi nedir?
Mesaj
1
Görüntüleme
135
KojiroHyuga04
KojiroHyuga04
ajust48
  • Soru
DRIVER_POWER_STATE_FAILURE hatasının sebebi nedir?
2
Mesaj
12
Görüntüleme
336
ajust48
ajust48
darkLord479
  • Soru
UNEXPECTED_KERNEL_MODE_TRAP hatasının sebebi nedir?
2
Mesaj
16
Görüntüleme
810
darkLord479
darkLord479
HIEGHY
  • Soru
DRIVER_IRQL_NOT_LESS_OR_EQUAL hatasının sebebi nedir?
Mesaj
9
Görüntüleme
406
claus
claus
N
  • Soru
Mavi ekran sebebi nedir?
Mesaj
1
Görüntüleme
289
turko35408
turko35408

Bu konuyu görüntüleyen kullanıcılar

Toplam: 2 (üye: 0, misafir: 2)

Technopat Haberler

Yeni konular

Yeni mesajlar

Geri
Yukarı