Çözüldü The disk subsystem returned corrupt data while reading from the hibernation file

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

Arda Kozan

Hectopat
Katılım
15 Kasım 2016
Mesajlar
10
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
Yaklaşık 1 ay önce bir kasa topladım ve 1 aydan itibaren yaklaşık 6 kere mavi ekran hatası aldım. Bunların minidump dosyalarını da aşağıda paylaştım. Çoğunda memory corruption hatası yazdığı için hata bellekte olabilir deyip test ettim. Memtest86 sonuçları ve Windows Memory Diagnostic testinin sonuçlarını da paylaştım, ikisi de temiz gözüküyor. Bundan 1-2 hafta önce de aynı şekilde test yapmıştım, sonuçlar yine bu şekildeydi.

Windows 10'u 2-3 kere kurdum temiz bir şekilde, hiçbir etkisi yok.
Driverlarla ilgili bir sıkıntı olabilir mi bilmiyorum ama üçüncü parti yazılım (Driver Booster gibi yazılımlar) kullanmadım. Windows Update ile tüm driverları kurdum. Chipsetin, ekran kartının driverlarını manuel olarak yükledim.
Lütfen yardım edin. Elim kolum bağlandı ve ne yapacağımı bilmiyorum.

Minidump dosyaları Google Drive linki: Minidump.rar.
 

Dosya Ekleri

  • 1.png
    1.png
    238,9 KB · Görüntüleme: 92
  • 2.png
    2.png
    14,5 KB · Görüntüleme: 45
Son düzenleyen: Moderatör:
Çözüm
Sorun hangi donanımda çıktı acaba? SSD arızasından mı kaynaklanıyor? Bilgi verirseniz teşekkürler.
Henüz sistemde bir değişiklik yapamadım ama kısa sürede Windows'u yeni alacağım SSD'ye kurmayı planlıyorum. Yeni bir SSD aldıktan sonra bilgilendirmek için yazarım.
Sisteme James Donkey haricinde ek olarak görseldeki SSD'yi ekleyip Windows'u oraya kurdum. Ama buna rağmen aynı mavi ekranı almaya devam ediyorum yeni bir konu açacağım sanırım güncel minidump verilerinin analizi için. Her şey için teşekkürler.

Screenshot_1.png

Henüz sistemde bir değişiklik yapamadım ama kısa sürede Windows'u yeni alacağım SSD'ye kurmayı planlıyorum. Yeni bir SSD aldıktan sonra bilgilendirmek için yazarım.

Sisteme James Donkey haricinde ek olarak görseldeki SSD'yi ekleyip Windows'u oraya kurdum. Ama buna rağmen aynı mavi ekranı almaya devam ediyorum yeni bir konu açacağım sanırım güncel minidump verilerinin analizi için. Her şey için teşekkürler.

Screenshot_1.png
Sorun çözüldü. Bunun için yeni bir konu açtım. Detaylı bilgi için konuya buradan ulaşabilirsiniz. Kısaca söylemek gerekirse; XMP kapatınca düzeldi. Frekans değerine yeterli voltaj değeri gelmemesinden kaynaklanıyor sanırım. Herhangi bir donanım kaynaklı sorun yokmuş. Bağlantıdakileri uyguladığımda sorun düzeldi.
Evet 2x8 dual kit olarak aldım. Bu da istediğiniz bilgiler.
 

Dosya Ekleri

  • Screenshot_2.png
    Screenshot_2.png
    10,8 KB · Görüntüleme: 39
  • Screenshot_3.png
    Screenshot_3.png
    10,8 KB · Görüntüleme: 30
Birakç hatada sorunun depolama biriminizde olduğu gözükmekte. Sistemdeki SSD/HDD'leri belirtin. Varsa Firmware güncellemelerini yapın.
Memtest hata vermese dahi belleklerinizde sorun olma ihtimali var. Bir de dediğim gibi depolama biriminizde.

Kod:
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: ffffca672e26c03f, Address of the instruction which caused the bugcheck
Arg3: ffffcc0d8f35cd30, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4796

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 5231

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

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

BUGCHECK_P1: c000001d

BUGCHECK_P2: ffffca672e26c03f

BUGCHECK_P3: ffffcc0d8f35cd30

BUGCHECK_P4: 0

CONTEXT:  ffffcc0d8f35cd30 -- (.cxr 0xffffcc0d8f35cd30)
rax=ffffca672d4f7dc0 rbx=ffffca1840911000 rcx=0000000004e3f7ef
rdx=ffffca1844649a60 rsi=0000000000000000 rdi=ffffca18443cc580
rip=ffffca672e26c03f rsp=ffffcc0d8f35d730 rbp=ffffcc0d8f35d830
 r8=0000000000000000  r9=0000000000000000 r10=0000ffffca672d4f
r11=ffffcc0d8f35d720 r12=0000000080000022 r13=0000000000000000
r14=ffffca1843e33a20 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050286
win32kbase!SURFACE::bDeleteSurface+0x6ff:
ffffca67`2e26c03f 2f              ???
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dwm.exe

STACK_TEXT: 
ffffcc0d`8f35d730 ffffca67`2d4ae4ae     : 00000000`00000000 00000000`00000000 ffffca18`00000001 ffffca18`00000001 : win32kbase!SURFACE::bDeleteSurface+0x6ff
ffffcc0d`8f35d900 ffffca67`2d4d07e1     : ffffca18`447d6090 00000000`00000000 00000000`001206f1 00000000`00000001 : win32kfull!GreDereferenceObject+0x7e
ffffcc0d`8f35d940 ffffca67`2d4ce373     : ffffca18`443cc580 00000000`00000000 00000000`001206f1 00000000`00000001 : win32kfull!SFMLOGICALSURFACE::CleanupShape+0x29
ffffcc0d`8f35d970 ffffca67`2d473e98     : 00000000`00000000 00000000`001206f1 00000000`00000000 ffffca18`00000000 : win32kfull!SFMLOGICALSURFACE::DeInitialize+0x83
ffffcc0d`8f35d9b0 ffffca67`2d4cdb04     : 00000000`00000000 ffffcc0d`8f35da20 ffffca18`40911000 ffffca18`447d6090 : win32kfull!bhLSurfDestroyLogicalSurfaceObject+0x80
ffffcc0d`8f35d9f0 ffffca67`2d4cd8b7     : ffffa60f`00000001 00000000`c000000d 00000000`00000000 00000000`001206f1 : win32kfull!GreSfmCloseCompositorRef+0xfc
ffffcc0d`8f35da40 ffffca67`2d33c2a5     : ffffa60f`29355080 0000027d`bd278430 01d69234`1ab1bf98 0000027d`b2c12f10 : win32kfull!NtGdiHLSurfSetInformation+0x277
ffffcc0d`8f35dac0 fffff800`3e2058b8     : ffffa60f`29355080 ffffa60f`29355080 00000000`00000001 ffffa60f`00000000 : win32k!NtGdiHLSurfSetInformation+0x15
ffffcc0d`8f35db00 00007ffb`6b966c04     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000088`baf7f148 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`6b966c04


CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kbase
    ffffca672e26c03f - win32kbase!SURFACE::bDeleteSurface+6ff
    [ 0f:2f ]
1 error : !win32kbase (ffffca672e26c03f)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr 0xffffcc0d8f35cd30 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup:     memory_corruption
---------

6: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.8, DMIVersion 0, Size=2563]
BiosMajorRelease = 5
BiosMinorRelease = 17
BiosVendor = American Megatrends Inc.
BiosVersion = 1.30
BiosReleaseDate = 08/31/2020
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = MS-7C94
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 = MAG B550M MORTAR (MS-7C94)
BaseBoardVersion = 1.0
INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 0000000000000107, A data mismatch has occurred in the internal hibernation data
    structures.
Arg2: 000000000000000a
Arg3: ffffc4834abd6410, POP_HIBER_CONTEXT
Arg4: 0000000000000000, PO_MEMORY_RANGE_ARRAY

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2499

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 2493

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

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

DUMP_FILE_ATTRIBUTES: 0x9
  Hiber Crash Dump
  Kernel Generated Triage Dump

BUGCHECK_CODE:  a0

BUGCHECK_P1: 107

BUGCHECK_P2: a

BUGCHECK_P3: ffffc4834abd6410

BUGCHECK_P4: 0

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT: 
ffff918e`8aa61488 fffff804`6b59fa2f     : 00000000`000000a0 00000000`00000107 00000000`0000000a ffffc483`4abd6410 : nt!KeBugCheckEx
ffff918e`8aa61490 fffff804`6b59085e     : ffffdc01`9d195180 fffff804`6af80444 00070106`00070106 00000000`00000001 : nt!PopDecompressHiberBlocks+0x11157
ffff918e`8aa616b0 fffff804`6b5905c0     : 00000000`00000000 00000000`00000000 00000000`00000039 00000000`00000000 : nt!PopRestoreHiberContext+0x146
ffff918e`8aa61740 fffff804`6b590383     : fffff804`6b850460 ffff918e`8aa61960 ffff918e`8aa61b20 ffffc483`4c6697b0 : nt!PopHandleNextState+0x210
ffff918e`8aa61790 fffff804`6aee9a3e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PopInvokeStateHandlerTargetProcessor+0x53
ffff918e`8aa61860 fffff804`6aee8d24     : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
ffff918e`8aa619d0 fffff804`6aff7a0e     : ffffffff`00000000 ffffdc01`9d195180 00000000`00000000 ffffdc01`9d1a0340 : nt!KiRetireDpcList+0x1f4
ffff918e`8aa61c60 00000000`00000000     : ffff918e`8aa62000 ffff918e`8aa5c000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  nt!PopDecompressHiberBlocks+11157

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  11157

FAILURE_BUCKET_ID:  0xa0_107_nt!PopDecompressHiberBlocks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5d9c83f4-ef2e-05d6-286b-9d88881fdb2f}

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

5: kd> !sysinfo machineid
sysinfo: could not find necessary interfaces.
sysinfo: note that mssmbios.sys must be loaded (XPSP2+).
NTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 000000000000010e, The disk subsystem returned corrupt data while reading from the
    hibernation file.
Arg2: 000000000000000a
Arg3: 0000000000005258, Incorrect checksum
Arg4: 000000000000189c, Previous disk read's checksum

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2671

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 4414

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

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

DUMP_FILE_ATTRIBUTES: 0x9
  Hiber Crash Dump
  Kernel Generated Triage Dump

BUGCHECK_CODE:  a0

BUGCHECK_P1: 10e

BUGCHECK_P2: a

BUGCHECK_P3: 5258

BUGCHECK_P4: 189c

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT: 
ffffcd09`5693a2e8 fffff801`34fa1696     : 00000000`000000a0 00000000`0000010e 00000000`0000000a 00000000`00005258 : nt!KeBugCheckEx
ffffcd09`5693a2f0 fffff801`34faec91     : 00000000`00000001 ffffce8a`e59e7230 00000000`00000028 ffffce8a`ff8e3000 : nt!PopHiberChecksumHiberFileData+0x10266
ffffcd09`5693a350 fffff801`34fae646     : 00000000`00000000 ffffa584`56135f38 ffffcd09`5693a450 00000000`00000002 : nt!PopRequestRead+0x7d
ffffcd09`5693a3c0 fffff801`34984804     : ffffa584`56135dd0 00000000`00000000 fffff801`45bf1010 fffff801`4300905f : nt!PopDecompressCallback+0x16
ffffcd09`5693a3f0 fffff801`34b8cad3     : ffffce8a`ff99300b ffff8a81`0e455008 00000000`00000000 00000000`00000000 : nt!RtlpMakeXpressCallback+0x24
ffffcd09`5693a420 fffff801`34b8bfd2     : ffff8a81`0e450000 ffff8a81`0e450000 ffffcd09`5693a600 00000000`00000000 : nt!RtlDecompressBufferXpressLzProgress+0x46b
ffffcd09`5693a4a0 fffff801`34f9f973     : 00000000`00000001 ffffcd09`5693a600 00000000`00000000 00000000`00010000 : nt!RtlDecompressBufferProgress+0x62
ffffcd09`5693a500 fffff801`34fa0c8c     : 00000000`00000000 ffffa584`56135f38 00000000`00000001 00000000`00000001 : nt!PopDecompressHiberBlocks+0x1109b
ffffcd09`5693a720 fffff801`34f905c0     : 00009fcb`04fdfaa1 ffffa584`56135f38 00000000`00000000 00000000`00000000 : nt!PopRestoreHiberContext+0x10574
ffffcd09`5693a7b0 fffff801`34f90302     : fffff801`35250460 ffffcd09`5693a930 fffff801`35250460 00000000`00000100 : nt!PopHandleNextState+0x210
ffffcd09`5693a800 fffff801`34f9007f     : 00000000`00000100 fffff801`35250460 00000066`40b1354f 00000000`00989680 : nt!PopIssueNextState+0x1a
ffffcd09`5693a830 fffff801`34f92c89     : ffffcd09`5693ab20 00000000`00000000 00000000`00000000 fffff801`34f92a0f : nt!PopInvokeSystemStateHandler+0x33b
ffffcd09`5693aa30 fffff801`34f8da6a     : ffffffff`00000000 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : nt!PopEndMirroring+0x1e9
ffffcd09`5693aaf0 fffff801`34f8d755     : 00000000`00000000 00000000`00000000 00000000`00000001 ffffce8a`df8a3040 : nt!MmDuplicateMemory+0x2be
ffffcd09`5693ab80 fffff801`34866dd5     : ffffce8a`ee274000 ffffce8a`ee274040 fffff801`34f8d620 00000000`00000001 : nt!PopTransitionToSleep+0x135
ffffcd09`5693ac10 fffff801`349fb4f8     : ffff8a81`0bad6180 ffffce8a`ee274040 fffff801`34866d80 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffffcd09`5693ac60 00000000`00000000     : ffffcd09`5693b000 ffffcd09`56935000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!PopHiberChecksumHiberFileData+10266

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  10266

FAILURE_BUCKET_ID:  0xa0_10e_nt!PopHiberChecksumHiberFileData

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {28ba2091-a476-6f77-2dec-6241bccd4685}

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff807194b28d8, The address that the exception occurred at
Arg3: ffff8289d4a30388, Exception Record Address
Arg4: ffff8289d4a2fbc0, Context Record Address

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

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

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 6233

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 43308

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

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff807194b28d8

BUGCHECK_P3: ffff8289d4a30388

BUGCHECK_P4: ffff8289d4a2fbc0

EXCEPTION_RECORD:  ffff8289d4a30388 -- (.exr 0xffff8289d4a30388)
ExceptionAddress: fffff807194b28d8 (dxgmms2!CVirtualAddressAllocator::GetNumPde)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffff8289d4a2fbc0 -- (.cxr 0xffff8289d4a2fbc0)
rax=ffffa404b03fa000 rbx=0000000000000000 rcx=ffffa404aada4650
rdx=0200000000000000 rsi=0200000000000000 rdi=0000000000000000
rip=fffff807194b28d8 rsp=ffff8289d4a305c8 rbp=0000000000000800
 r8=ffff8289d4a30460  r9=0000000000015052 r10=fffff80706ce0170
r11=ffff8289d4a30640 r12=0000000000000301 r13=ffffa404aada4650
r14=0200000000000000 r15=0000000000001808
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050282
dxgmms2!CVirtualAddressAllocator::GetNumPde:
fffff807`194b28d8 448b02          mov     r8d,dword ptr [rdx] ds:002b:02000000`00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff807076fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8070760f2e0: Unable to get Flags value from nt!KdVersionBlock
fffff8070760f2e0: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 ffffffffffffffff

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek  u olamaz %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

EXCEPTION_STR:  0xc0000005

STACK_TEXT: 
ffff8289`d4a305c8 fffff807`1955e87d     : 00000000`0000000e 00000000`00000004 00000000`02000103 00000000`00000000 : dxgmms2!CVirtualAddressAllocator::GetNumPde
ffff8289`d4a305d0 fffff807`1955e9f8     : 00000000`00000000 00000000`00000000 00000000`00000800 02000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::MapPageTablesToVaSpace+0x2d
ffff8289`d4a30670 fffff807`1954dc0f     : 00000000`00000000 00000000`00000000 ffff8289`d4a30810 ffffcc0c`cf66d000 : dxgmms2!VIDMM_PAGE_DIRECTORY::MapPageTablesToVaSpace+0x1a8
ffff8289`d4a30710 fffff807`1953f006     : 00000000`00000000 00000000`00000000 00000000`00000076 ffffa404`bb59eca0 : dxgmms2!VIDMM_GLOBAL::InitPagingProcessVaSpace+0x1aa4b
ffff8289`d4a30880 fffff807`1952a442     : ffffa404`aada4020 ffff8289`00000001 00000000`00000001 ffffa404`afe48980 : dxgmms2!VIDMM_GLOBAL::ProcessSystemCommand+0x2c4a2
ffff8289`d4a30a00 fffff807`19533d09     : ffffa404`afe48910 ffffcc0c`cf546201 00000000`00000000 00000000`06930000 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1462
ffff8289`d4a30be0 fffff807`06c66dd5     : ffffcc0c`cf546280 fffff807`19533d00 ffffa404`afe48910 000f8067`bcbbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
ffff8289`d4a30c10 fffff807`06dfb4f8     : ffffdc01`cdfc0180 ffffcc0c`cf546280 fffff807`06c66d80 00730073`0061006c : nt!PspSystemThreadStartup+0x55
ffff8289`d4a30c60 00000000`00000000     : ffff8289`d4a31000 ffff8289`d4a2b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!CVirtualAddressAllocator::GetNumPde+0

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .cxr 0xffff8289d4a2fbc0 ; kb

BUCKET_ID_FUNC_OFFSET:  0

FAILURE_BUCKET_ID:  AV_dxgmms2!CVirtualAddressAllocator::GetNumPde

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {06124d67-36c5-3cc3-3955-15b6ae3258fb}

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8055bfff73d, The address that the exception occurred at
Arg3: ffff9c0c063e0748, Exception Record Address
Arg4: ffff9c0c063dff80, Context Record Address

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

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

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 5264

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 7511

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

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8055bfff73d

BUGCHECK_P3: ffff9c0c063e0748

BUGCHECK_P4: ffff9c0c063dff80

EXCEPTION_RECORD:  ffff9c0c063e0748 -- (.exr 0xffff9c0c063e0748)
ExceptionAddress: fffff8055bfff73d (dxgmms2!VIDMM_GLOBAL::ProcessSystemMemoryOfferList+0x000000000000011d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 000000000000002d
Attempt to read from address 000000000000002d

CONTEXT:  ffff9c0c063dff80 -- (.cxr 0xffff9c0c063dff80)
rax=0000000000000000 rbx=ffffe18ae1858000 rcx=ffffe18ae1726318
rdx=ffffe18ae1861c20 rsi=ffffe18ae1861c50 rdi=ffffe18ae1858000
rip=fffff8055bfff73d rsp=ffff9c0c063e0980 rbp=ffffe18ae1861c20
 r8=ffff9c0c063e0948  r9=000000000000002e r10=ffffe18ae1861c20
r11=ffff9c0c063e09d0 r12=0000000000000000 r13=ffff8c040a7aa910
r14=ffffe18ae1861c20 r15=00000001e3ac1ecd
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202
dxgmms2!VIDMM_GLOBAL::ProcessSystemMemoryOfferList+0x11d:
fffff805`5bfff73d 418379ff74      cmp     dword ptr [r9-1],74h ds:002b:00000000`0000002d=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff8054acfa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8054ac0f2e0: Unable to get Flags value from nt!KdVersionBlock
fffff8054ac0f2e0: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 000000000000002d

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek  u olamaz %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  000000000000002d

EXCEPTION_STR:  0xc0000005

STACK_TEXT: 
ffff9c0c`063e0980 fffff805`5c0299d8     : ffff9c0c`063e0b00 ffffe18a`e1861c10 ffffe18a`e1858000 ffffe18a`e1861c10 : dxgmms2!VIDMM_GLOBAL::ProcessSystemMemoryOfferList+0x11d
ffff9c0c`063e0a00 fffff805`5c033d09     : ffff8c04`0a7aa910 ffffe18a`e1726200 00000000`00000000 00000000`06dde000 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x9f8
ffff9c0c`063e0be0 fffff805`4a266dd5     : ffffe18a`e1726280 fffff805`5c033d00 ffff8c04`0a7aa910 000f8067`bcbbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
ffff9c0c`063e0c10 fffff805`4a3fb4f8     : ffffc081`f31c0180 ffffe18a`e1726280 fffff805`4a266d80 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff9c0c`063e0c60 00000000`00000000     : ffff9c0c`063e1000 ffff9c0c`063db000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxgmms2
    fffff8055bfff73f - dxgmms2!VIDMM_GLOBAL::ProcessSystemMemoryOfferList+11f
    [ f9:79 ]
1 error : !dxgmms2 (fffff8055bfff73f)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr 0xffff9c0c063dff80 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup:     memory_corruption
---------

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff913cbc13ae7, Address of the instruction which caused the bugcheck
Arg3: ffff95096099b910, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5312

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 42324

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

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

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff913cbc13ae7

BUGCHECK_P3: ffff95096099b910

BUGCHECK_P4: 0

CONTEXT:  ffff95096099b910 -- (.cxr 0xffff95096099b910)
rax=fffff913cbc13ac0 rbx=0800000000000000 rcx=0800000000000000
rdx=fffff913cbe1b220 rsi=fffff9474061f190 rdi=0000000000000001
rip=fffff913cbc13ae7 rsp=ffff95096099c310 rbp=ffff95096099c5d0
 r8=ffff95096099c064  r9=ffff95096099c060 r10=0000fffff913cbc1
r11=ffffd5fffd400000 r12=fffff913cba186f0 r13=fffff94740608620
r14=00000000c00000bb r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
win32kfull!DestroyInputHangInfo+0x27:
fffff913`cbc13ae7 488b1b          mov     rbx,qword ptr [rbx] ds:002b:08000000`00000000=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  csrss.exe

STACK_TEXT: 
ffff9509`6099c310 fffff913`cb86e67c     : 00000000`00000000 fffff947`4061f190 00000000`00000000 00000000`00004d2c : win32kfull!DestroyInputHangInfo+0x27
ffff9509`6099c340 fffff913`cb867923     : fffff947`4061f190 00000000`00000000 ffffaa8a`504fe080 fffff913`cba5b270 : win32kbase!xxxDestroyThreadInfo+0xab8
ffff9509`6099c4d0 fffff913`cbb1982b     : 00000000`00000001 00000000`00000001 ffffaa8a`504fe080 00000000`00000000 : win32kbase!UserThreadCallout+0x553
ffff9509`6099c6c0 fffff913`cb88d49c     : 00000000`00000001 ffff9509`6099c7f0 00000000`c000001c ffff9509`00000009 : win32kfull!W32pThreadCallout+0x7b
ffff9509`6099c6f0 fffff913`cc3610d0     : 00000000`c000001c ffffaa8a`504fe080 ffffaa8a`504fe080 ffff9509`6099ca08 : win32kbase!W32CalloutDispatch+0x44c
ffff9509`6099c900 fffff804`4ba9c6a5     : 00000000`00000001 fffff804`4c01deb0 ffffaa8a`49c56550 00000000`00000001 : win32k!W32CalloutDispatchThunk+0x30
ffff9509`6099c940 fffff804`4ba9e949     : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!PsInvokeWin32Callout+0x55
ffff9509`6099c970 fffff804`4b9f4623     : 00000000`00000000 ffffaa8a`54e88b00 00000000`00000000 00000000`00000000 : nt!PspExitThread+0x4b5
ffff9509`6099ca70 fffff804`4b9f45aa     : 00000000`00000000 00000000`00000000 ffffaa8a`504fe080 ffffaa8a`54e88be0 : nt!PspTerminateThreadByPointer+0x53
ffff9509`6099cab0 fffff804`4b8058b8     : 00000000`00000000 ffffaa8a`504fe080 ffff9509`6099cb80 ffffaa8a`00000000 : nt!NtTerminateThread+0x4a
ffff9509`6099cb00 00007ff8`3256c824     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000010`616bf968 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`3256c824


SYMBOL_NAME:  win32kfull!DestroyInputHangInfo+27

MODULE_NAME: win32kfull

IMAGE_NAME:  win32kfull.sys

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .cxr 0xffff95096099b910 ; kb

BUCKET_ID_FUNC_OFFSET:  27

FAILURE_BUCKET_ID:  0x3B_c0000005_win32kfull!DestroyInputHangInfo

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {0604c5d0-d206-0e11-4d0a-759edafb4c13}

Followup:     MachineOwner
---------
 
SSD'den ben de şüphelenmiştim sıcaklık değerinden kaynaklı olabilir mi acaba çünkü bazen yük altında soğutucu plaka olmasına rağmen 60 dereceyi görüyor.

Screenshot_2.png
 
Evet Windows kurulu olan bu tek depolama birimi kullanıyorum. Mavi ekranı sadece sistemi açarken veya kapatırken yiyorum. Sizce ne yapmalıyım? Sistemi böyle kullanmak herhangi bir donanımı yıpratır mı ?
 

Geri
Yukarı