"Faulty hardware corrupted page" ve "video Memory management ınternal" hatası

İşletim sistemi
Windows 10
Katılım
18 Aralık 2014
Mesajlar
44
Beğeniler
10
Merhaba iyi günler. Ben başlıkta belirttiğim gibi 3-4 gün öncesinde "video Memory management ınternal" hatasını aldım üst üste. Daha sonrasında bellek testine soktum bilgisayarı bir sıkıntı çıkmadı. Ekran kartından sıkıntının olduğunu varsayarak DDU ile silip driverlarını tekrardan yükledim. Yine aynı hatayı aldım. Çözümünü temiz kurulum yapmak olarak gördüm, temiz kurulum yaptım. Sonrasında bir sıkıntı çıkarmadı. Bir kere 3-4 gün önce temiz kurulumdan sonra Call of Duty Warzone oynarken silkroad clientine Alt Tab yaptım ve "video scheduler internal error" hatası verdi. Daha sonrasında dün geceye kadar sorun yoktu. Dün gece Silkroad oynarken durup dururken "faulty hardware corrupted page" hatası verdi. Konuyu Technopat'tan araştırıp baktığımda minidump dosyasını aktarmamız istenmiş. Yardımcı olabilirseniz sevinirim. Minidump dosyamı ve kullandığım sistemi aşağıda belirttim.

Minidump dosyası: Minidump.rar

Kullandığım laptop: https://www.hepsiburada.com/lenovo-...nabilir-bilgisayar-81fv001ltx-pm-HB00000ECCHK
 
Son düzenleyen: Moderatör:

PanzerTR

Gigapat
Katılım
29 Ocak 2019
Mesajlar
7.970
Makaleler
12
Çözümler
59
Beğeniler
14.147
Yer
Gotham
1- Bellekleri test edin. (En son adım olarak)


2-DDU ile ekran akrtı sürcünüzü kaldırın ve en güncelini kurun.


3-Rehberi uygulayın.


4-NVIDIA HDMI Ses sürücüsünü güncelleyin.

5-Corsair Gaming Software yazılımını kaldırın.
 

yika38

Terapat
Katılım
17 Eylül 2017
Mesajlar
7.069
Makaleler
8
Çözümler
129
Beğeniler
9.183
Yer
Kayseri
Anlattıklarınıza göre sorun GPU kaynaklı duruyor. DDU ile sürücüleri silip yeniden kurmanız, format atmanız sorunu çözmediğine göre donanımsal. Zaten mavi ekranlarınızdan birisi GPU kaynaklı soruna işaret ediyor. Bu durumda sistemi garantiye göndermeniz iyi olacaktır.

Belki alttakileri deneyebilirsiniz ama çözüleceğini zannetmiyorum:
Kod:
FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
This bugcheck indicates that a single bit error was found in this page.  This is a hardware memory error.
Arguments:
Arg1: ffffffffc00002c4, virtual address mapping the corrupted page
Arg2: 0000000000000a17, physical page number
Arg3: 000001df0b38f190, zero
Arg4: ffffe08083de6000, zero

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5968

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 35672

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : BlackBox.SmDecompressionFailure.CompressedSize
    Value: 0xa17

    Key  : BlackBox.SmDecompressionFailure.CompressionFormat
    Value: 0x3

    Key  : BlackBox.SmDecompressionFailure.SourceDataHash
    Value: 0x7ae786a1

    Key  : BlackBox.SmDecompressionFailure.SourceDataOffset
    Value: 0xf190

    Key  : BlackBox.SmDecompressionFailure.SourcePFN1
    Value: 0x3645f

    Key  : BlackBox.SmDecompressionFailure.SourcePFN2
    Value: 0xffffffffffffffff

    Key  : BlackBox.SmDecompressionFailure.TargetPFN
    Value: 0xc7a0

    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:  12b

BUGCHECK_P1: ffffffffc00002c4

BUGCHECK_P2: a17

BUGCHECK_P3: 1df0b38f190

BUGCHECK_P4: ffffe08083de6000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MemCompression

STACK_TEXT:
fffff508`d39af0f8 fffff801`4e1958d2     : 00000000`0000012b ffffffff`c00002c4 00000000`00000a17 000001df`0b38f190 : nt!KeBugCheckEx
fffff508`d39af100 fffff801`4e02d141     : 00000000`00000001 00000000`c00002c4 ffffe080`83de6000 00000000`00083de5 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0x10a
fffff508`d39af160 fffff801`4de471b5     : 00000000`00000004 fffff801`4de46d1e 00000000`00000000 00000000`00000001 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x1e5f69
fffff508`d39af220 fffff801`4de46a84     : 00000000`00000001 00000000`0000f190 ffffc904`f094e000 ffffc904`00001000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa5
fffff508`d39af270 fffff801`4de9271c     : fffff801`ffffffff ffffc904`f1889000 fffff508`d39af350 ffffc904`f80d7cd0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x180
fffff508`d39af310 fffff801`4de92569     : ffffe080`7faf7730 00000000`00000001 00000000`00000000 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc8
fffff508`d39af3c0 fffff801`4de92421     : ffffc904`f094e000 ffffc904`f80d7cd0 ffffc904`f1889000 ffffc904`f094f9c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
fffff508`d39af440 fffff801`4de0d468     : ffffc904`fbcfb640 ffffc904`f094e000 00000000`00000000 ffffc904`fc9401d0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
fffff508`d39af470 fffff801`4de938f7     : fffff801`4de92400 fffff508`d39af510 00000000`00000003 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
fffff508`d39af4e0 fffff801`4de4db74     : fffff508`d39af5e0 00000000`31526d73 00000000`000003ff fffff801`4e9239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xc7
fffff508`d39af5b0 fffff801`4de4d5a8     : 00000000`0000000c 00000000`000003ff fffff508`d39af660 fffff801`4e9239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ac
fffff508`d39af600 fffff801`4de92b57     : 00000000`0000000c 00000000`00000001 ffffc904`f80d7cd0 ffffc904`fc9401d0 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xc0
fffff508`d39af690 fffff801`4dea840b     : ffffc904`00000001 ffffc904`fc940290 00000000`00000000 ffffc904`f094e000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167
fffff508`d39af700 fffff801`4df172f8     : 0000007f`00000100 00000000`00000000 fffff508`d39af958 fffff801`4df17a70 : nt!SmPageRead+0x33
fffff508`d39af750 fffff801`4df175cd     : 00000000`00000002 fffff508`d39af7e0 fffff508`d39af958 ffffc904`fc940180 : nt!MiIssueHardFaultIo+0x10c
fffff508`d39af7a0 fffff801`4deea508     : 00000000`c0033333 00000000`00000001 00000000`228e72d4 00000000`00000000 : nt!MiIssueHardFault+0x29d
fffff508`d39af860 fffff801`4e00335e     : 00000000`011aa4bc 00000000`00000000 00000000`00000000 ffffc904`00000000 : nt!MmAccessFault+0x468
fffff508`d39afa00 00000000`006af87a     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
00000000`0019da68 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6af87a


SYMBOL_NAME:  nt!ST_STORE<SM_TRAITS>::StDmPageError+10a

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.630

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  10a

FAILURE_BUCKET_ID:  0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}

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

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: fffffd0c5c597860
Arg4: ffffd003f9b3b750

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6311

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 32972

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

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

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: fffffd0c5c597860

BUGCHECK_P4: ffffd003f9b3b750

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffffd0c`5c597788 fffff803`569b3ad0     : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffffd0c`5c597860 : nt!KeBugCheckEx
fffffd0c`5c597790 fffff803`5adebba1     : 00000000`00000000 ffffd003`f9b38000 fffffd0c`5c597899 ffffd003`f9b38000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffffd0c`5c5977d0 fffff803`5ae530bd     : ffffd003`00000000 ffffd003`f9b3b750 ffffd003`f9b40000 ffffd004`02d33010 : dxgmms2!VidSchiSendToExecutionQueue+0x12761
fffffd0c`5c597900 fffff803`5ae5ae8a     : ffffd004`02d33010 ffffd003`e9ceb180 00000000`00000000 fffff803`5ae5ac30 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
fffffd0c`5c597a80 fffff803`5ae5acfa     : ffffd003`f9b40400 fffff803`5ae5ac30 ffffd003`f9b40000 ffffe600`61948100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
fffffd0c`5c597ad0 fffff803`3eca29a5     : ffffd004`02ed8040 fffff803`00000001 ffffd003`f9b40000 00000000`00000001 : dxgmms2!VidSchiWorkerThread+0xca
fffffd0c`5c597b10 fffff803`3edfc868     : ffffe600`61948180 ffffd004`02ed8040 fffff803`3eca2950 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffd0c`5c597b60 00000000`00000000     : fffffd0c`5c598000 fffffd0c`5c591000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+12761

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.546

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  12761

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9a11bf9c-270e-962e-7a82-3efdab93c10e}

Followup:     MachineOwner
---------
 
KS
Salih Emir Yazgan
Katılım
18 Aralık 2014
Mesajlar
44
Beğeniler
10
Anlattıklarınıza göre sorun GPU kaynaklı duruyor. DDU ile sürücüleri silip yeniden kurmanız, format atmanız sorunu çözmediğine göre donanımsal. Zaten mavi ekranlarınızdan birisi GPU kaynaklı soruna işaret ediyor. Bu durumda sistemi garantiye göndermeniz iyi olacaktır.

Belki alttakileri deneyebilirsiniz ama çözüleceğini zannetmiyorum:
Kod:
FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error.
Arguments:
Arg1: ffffffffc00002c4, virtual address mapping the corrupted page.
Arg2: 0000000000000a17, physical page number.
Arg3: 000001df0b38f190, zero.
Arg4: ffffe08083de6000, zero.

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

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

KEY_VALUES_STRING: 1.

Key : Analysis.CPU.mSec.
Value: 5968.

Key : Analysis.DebugAnalysisProvider.CPP.
Value: Create: 8007007e on DESKTOP-62N06FT.

Key : Analysis.DebugData.
Value: CreateObject.

Key : Analysis.DebugModel.
Value: CreateObject.

Key : Analysis.Elapsed.mSec.
Value: 35672.

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

Key : Analysis.System.
Value: CreateObject.

Key : BlackBox.SmDecompressionFailure.CompressedSize.
Value: 0xa17.

Key : BlackBox.SmDecompressionFailure.CompressionFormat.
Value: 0x3.

Key : BlackBox.SmDecompressionFailure.SourceDataHash.
Value: 0x7ae786a1.

Key : BlackBox.SmDecompressionFailure.SourceDataOffset.
Value: 0xf190.

Key : BlackBox.SmDecompressionFailure.SourcePFN1.
Value: 0x3645f.

Key : BlackBox.SmDecompressionFailure.SourcePFN2.
Value: 0xffffffffffffffff.

Key : BlackBox.SmDecompressionFailure.TargetPFN.
Value: 0xc7a0.

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: 12b.

BUGCHECK_P1: ffffffffc00002c4.

BUGCHECK_P2: a17.

BUGCHECK_P3: 1df0b38f190.

BUGCHECK_P4: ffffe08083de6000.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1.

CUSTOMER_CRASH_COUNT: 1.

PROCESS_NAME: MemCompression.

STACK_TEXT:
fffff508`d39af0f8 fffff801`4e1958d2 : 00000000`0000012b ffffffff`c00002c4 00000000`00000a17 000001df`0b38f190 : nt!KeBugCheckEx.
fffff508`d39af100 fffff801`4e02d141 : 00000000`00000001 00000000`c00002c4 ffffe080`83de6000 00000000`00083de5 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0x10a.
fffff508`d39af160 fffff801`4de471b5 : 00000000`00000004 fffff801`4de46d1e 00000000`00000000 00000000`00000001 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x1e5f69.
fffff508`d39af220 fffff801`4de46a84 : 00000000`00000001 00000000`0000f190 ffffc904`f094e000 ffffc904`00001000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa5.
fffff508`d39af270 fffff801`4de9271c : fffff801`ffffffff ffffc904`f1889000 fffff508`d39af350 ffffc904`f80d7cd0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x180.
fffff508`d39af310 fffff801`4de92569 : ffffe080`7faf7730 00000000`00000001 00000000`00000000 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc8.
fffff508`d39af3c0 fffff801`4de92421 : ffffc904`f094e000 ffffc904`f80d7cd0 ffffc904`f1889000 ffffc904`f094f9c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85.
fffff508`d39af440 fffff801`4de0d468 : ffffc904`fbcfb640 ffffc904`f094e000 00000000`00000000 ffffc904`fc9401d0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21.
fffff508`d39af470 fffff801`4de938f7 : fffff801`4de92400 fffff508`d39af510 00000000`00000003 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78.
fffff508`d39af4e0 fffff801`4de4db74 : fffff508`d39af5e0 00000000`31526d73 00000000`000003ff fffff801`4e9239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xc7.
fffff508`d39af5b0 fffff801`4de4d5a8 : 00000000`0000000c 00000000`000003ff fffff508`d39af660 fffff801`4e9239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ac.
fffff508`d39af600 fffff801`4de92b57 : 00000000`0000000c 00000000`00000001 ffffc904`f80d7cd0 ffffc904`fc9401d0 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xc0.
fffff508`d39af690 fffff801`4dea840b : ffffc904`00000001 ffffc904`fc940290 00000000`00000000 ffffc904`f094e000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167.
fffff508`d39af700 fffff801`4df172f8 : 0000007f`00000100 00000000`00000000 fffff508`d39af958 fffff801`4df17a70 : nt!SmPageRead+0x33.
fffff508`d39af750 fffff801`4df175cd : 00000000`00000002 fffff508`d39af7e0 fffff508`d39af958 ffffc904`fc940180 : nt!MiIssueHardFaultIo+0x10c.
fffff508`d39af7a0 fffff801`4deea508 : 00000000`c0033333 00000000`00000001 00000000`228e72d4 00000000`00000000 : nt!MiIssueHardFault+0x29d.
fffff508`d39af860 fffff801`4e00335e : 00000000`011aa4bc 00000000`00000000 00000000`00000000 ffffc904`00000000 : nt!MmAccessFault+0x468.
fffff508`d39afa00 00000000`006af87a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e.
00000000`0019da68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6af87a.

SYMBOL_NAME: nt!ST_STORE<SM_TRAITS>::StDmPageError+10a.

MODULE_NAME: nt.

IMAGE_NAME: ntkrnlmp.exe.

IMAGE_VERSION: 10.0.19041.630.

STACK_COMMAND: .thread ; .cxr ; kb.

BUCKET_ID_FUNC_OFFSET: 10a.

FAILURE_BUCKET_ID: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError.

OS_VERSION: 10.0.19041.1.

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}

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

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted.
in a condition that video scheduler can no longer progress. Any other values after.
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d.
Arg3: fffffd0c5c597860.
Arg4: ffffd003f9b3b750.

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

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

KEY_VALUES_STRING: 1.

Key : Analysis.CPU.mSec.
Value: 6311.

Key : Analysis.DebugAnalysisProvider.CPP.
Value: Create: 8007007e on DESKTOP-62N06FT.

Key : Analysis.DebugData.
Value: CreateObject.

Key : Analysis.DebugModel.
Value: CreateObject.

Key : Analysis.Elapsed.mSec.
Value: 32972.

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

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: 119.

BUGCHECK_P1: 2.

BUGCHECK_P2: ffffffffc000000d.

BUGCHECK_P3: fffffd0c5c597860.

BUGCHECK_P4: ffffd003f9b3b750.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1.

CUSTOMER_CRASH_COUNT: 1.

PROCESS_NAME: System.

STACK_TEXT:
fffffd0c`5c597788 fffff803`569b3ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffffd0c`5c597860 : nt!KeBugCheckEx.
fffffd0c`5c597790 fffff803`5adebba1 : 00000000`00000000 ffffd003`f9b38000 fffffd0c`5c597899 ffffd003`f9b38000 : watchdog!WdLogEvent5_WdCriticalError+0xe0.
fffffd0c`5c5977d0 fffff803`5ae530bd : ffffd003`00000000 ffffd003`f9b3b750 ffffd003`f9b40000 ffffd004`02d33010 : dxgmms2!VidSchiSendToExecutionQueue+0x12761.
fffffd0c`5c597900 fffff803`5ae5ae8a : ffffd004`02d33010 ffffd003`e9ceb180 00000000`00000000 fffff803`5ae5ac30 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed.
fffffd0c`5c597a80 fffff803`5ae5acfa : ffffd003`f9b40400 fffff803`5ae5ac30 ffffd003`f9b40000 ffffe600`61948100 : dxgmms2!VidSchiRun_PriorityTable+0x17a.
fffffd0c`5c597ad0 fffff803`3eca29a5 : ffffd004`02ed8040 fffff803`00000001 ffffd003`f9b40000 00000000`00000001 : dxgmms2!VidSchiWorkerThread+0xca.
fffffd0c`5c597b10 fffff803`3edfc868 : ffffe600`61948180 ffffd004`02ed8040 fffff803`3eca2950 00000000`00000000 : nt!PspSystemThreadStartup+0x55.
fffffd0c`5c597b60 00000000`00000000 : fffffd0c`5c598000 fffffd0c`5c591000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28.

SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+12761.

MODULE_NAME: dxgmms2.

IMAGE_NAME: dxgmms2.sys.

IMAGE_VERSION: 10.0.19041.546.

STACK_COMMAND: .thread ; .cxr ; kb.

BUCKET_ID_FUNC_OFFSET: 12761.

FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue.

OS_VERSION: 10.0.19041.1.

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}

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

Windows bellek testinde bir sıkıntı çıkmadı, bugün Memtest86 ile test yaptığımda yine bir hata oluşmadı. Donanımsal olarak ne gibi bir sıkıntı çıkarıyor olabilir ekran kartı.
 

yika38

Terapat
Katılım
17 Eylül 2017
Mesajlar
7.069
Makaleler
8
Çözümler
129
Beğeniler
9.183
Yer
Kayseri
KS
Salih Emir Yazgan
Katılım
18 Aralık 2014
Mesajlar
44
Beğeniler
10
1- Bellekleri test edin. (En son adım olarak)


2-DDU ile ekran akrtı sürcünüzü kaldırın ve en güncelini kurun.


3-Rehberi uygulayın.


4-NVIDIA HDMI ses sürücüsünü güncelleyin.

5-Corsair Gaming software yazılımını kaldırın.

NVIDIA HDMI ses sürücüsünü nasıl güncelleyeceğim.
VRAM arızasından şüphelenmiyor değilim.

VRAM için test yapabileceğim bir şey var mıdır.
 

yika38

Terapat
Katılım
17 Eylül 2017
Mesajlar
7.069
Makaleler
8
Çözümler
129
Beğeniler
9.183
Yer
Kayseri
VRAM için test yapabileceğim bir şey var mıdır?
Furmark veya OCCT deneyebilirsiniz ancak sentetik testlerden bir şey çıkar mı, bilmiyorum.

 
KS
Salih Emir Yazgan
Katılım
18 Aralık 2014
Mesajlar
44
Beğeniler
10
FurMark veya OCCT deneyebilirsiniz ancak sentetik testlerden bir şey çıkar mı, bilmiyorum.


Denedim testi bir sıkıntı çıkmadı ama bilemiyorum şimdi aklım çok karışık. Hiç sorun çıkmıyor yaptığım testlerde. En son dün gece faulty hardware corrupted page hatası yedim o zamandan beri bir sıkıntı oluşmadı hala. Siz kesinlikle garantiye yollamamı mı öneriyorsunuz?
 

yika38

Terapat
Katılım
17 Eylül 2017
Mesajlar
7.069
Makaleler
8
Çözümler
129
Beğeniler
9.183
Yer
Kayseri
@Salih Emir Yazgan bir mavi ekran daha alırsanız o zaman gönderirsiniz. Ondan önce yeni Minidump dosyalarını paylaşmayı unutmayın.
 
KS
Salih Emir Yazgan
Katılım
18 Aralık 2014
Mesajlar
44
Beğeniler
10
@Salih Emir Yazgan bir mavi ekran daha alırsanız o zaman gönderirsiniz. Ondan önce yeni minidump dosyalarını paylaşmayı unutmayın.

Tamamdır teşekkür ederim yardımınız için.
@Salih Emir Yazgan bir mavi ekran daha alırsanız o zaman gönderirsiniz. Ondan önce yeni minidump dosyalarını paylaşmayı unutmayın.

Merhaba iyi günler @yika38 yeniden mavi ekran almış bulunmaktayım. Minidump dosyası ektedir.

 
Son düzenleme:
Yukarı