Critical mass
Hectopat
- Katılım
- 19 Ocak 2022
- Mesajlar
- 1.707
- Makaleler
- 1
- Çözümler
- 4
Arkadaşlar iki kere mavi ekran hatası aldım. İki gün arayla. İkisinde de farklı oyunları oynuyordum. Hata almadan önce RAM takviyesi yaptım ama o şekilde bayağı bir süre sorunsuz kullandım. RAM'den olduğunu sanmıyorum. Aynı Chip marka model, CL vs. araştırıp aldım. İkinci şüpheli daha önce HDD spin stopper gibi tam adını hatırlamadığım bir programla ikinci diskim olan HDD'yi spin sesi yüzünden kapatıyordum. Sonra programı sildim ama Disk Yönetiminden devre dışı bıraktığımda hala program etkinmiş gibi (ya da ne ayar değiştirdiyse) HDD kapanıyor. O şekilde kullanıyorum bir süredir. İhtiyacım olduğunda Disk Yönetiminden açıyorum.
DMP dosyasının içeriğini gönderiyorum.
Arkadaşlar "KERNEL_DATA_INPAGE_ERROR (7a)-KERNEL_STACK_INPAGE_ERROR."
desede bu sorun belirli bir oyun kaynaklı olabilir mi? Çünkü sadece Far Cry 6'da oluyor.
Birde sorunun Far Cry 6 kaynaklı olup olmadığını anlamak için, mavi ekranı tetiklemek için bir yol varmı oyun oynamadan?
DMP dosyasının içeriğini gönderiyorum.
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (C) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol Search path is: Srv*
Executable Search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free X64
Product: WinNt, Suite: TerminalServer SingleUserTS
Edition Build lab: 19041.1.AMD64fre. Vb_release. 191206-1406
Machine Name:
Kernel base = 0xfffff801`27600000 PsLoadedModuleList = 0xfffff801`2822a270
Debug session time: Mon Nov 7 21:12:45.045 2022 (UTC + 3:00)
System Uptime: 0 days 1:40:59.676
Loading Kernel Symbols
Page 84E683 not present in the dump file. Type ".hh dbgerr004" for details
Page 862EF0 not present in the dump file. Type ".hh dbgerr004" for details
Page 86213C not present in the dump file. Type ".hh dbgerr004" for details
Page 867DD5 not present in the dump file. Type ".hh dbgerr004" for details
Page 865C9F not present in the dump file. Type ".hh dbgerr004" for details
Loading User Symbols
PEB is paged out (Peb. Ldr = 00000027'D6b4F018). Type ".hh dbgerr001" for details
Loading unloaded module list
For analysis of this file, run! Analyze -v
NT! KeBugCheckEx:
Fffff801'279F90F0 48894C2408 mov qword ptr [rsp+8],rcx SS:0018:ffff8786'B03F6940 = 000000000000007A
2: Kd>!analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
A bad block in the paging file or disk Controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
İt means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
A filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000001, lock type that was held (Value 1, 2, 3, or PTE address)
Arg2: FffffffFC0000005, error status (normally i/o status code)
Arg3: FffFC902105D50C0, current process (Virtual address for lock type 3, or PTE)
Arg4: FffFF47CCD80b000, Virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
Page 196905 not present in the dump file. Type ".hh dbgerr004" for details
KEY_VALUES_STRING: 1
Key: Analysis. CPU. MSec
Value: 2718
Key: Analysis. DebugAnalysisManager
Value: Create
Key: Analysis. Elapsed. MSec
Value: 10123
Key: Analysis. IO. Other. MB
Value: 19
Key: Analysis. IO. Read. MB
Value: 0
Key: Analysis. IO. Write. MB
Value: 26
Key: Analysis. Init. CPU. MSec
Value: 702
Key: Analysis. Init. Elapsed. MSec
Value: 63471
Key: Analysis. Memory.commitPeak. MB
Value: 100
Key: Bugcheck. Code. DumpHeader
Value: 0x7a
Key: Bugcheck. Code. KiBugCheckData
Value: 0x7a
Key: Bugcheck. Code. Register
Value: 0x7a
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
FILE_IN_CAB: MEMORY.DMP
BUGCHECK_CODE: 7A
BUGCHECK_P1: 1
BUGCHECK_P2: FffffffFC0000005
BUGCHECK_P3: FFFFC902105D50C0
BUGCHECK_P4: FffFF47CCD80B000
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.
PROCESS_NAME: svchost.exe
STACK_TEXT:
Ffff8786'B03F6938 fffff801'27a2bbca: 00000000'0000007A 00000000'00000001 ffffffff'C0000005 ffffc902'105D50C0: NT! KeBugCheckEx
Ffff8786'B03F6940 fffff801'278388CB: 00000000'00000001 ffffc902'00000000 00000000'00000016 00010000'00000000: NT! MiGetNextPageTablePte+0x1F28ca
Ffff8786'B03F6990 fffff801'27838B7B: Fffff47a'00000000 ffffc902'105D5740 ffff8786'00000001 ffff8786'B03F6D70: NT! MiWalkPageTablesRecursively+0x5dB
Ffff8786'B03F6a30 fffff801'27838B7B: Fffff47a'3D1F3000 ffffc902'105D5740 ffff8786'00000002 ffff8786'B03F6D80: NT! MiWalkPageTablesRecursively+0x88b
Ffff8786'B03F6ad0 fffff801'2780B7DB: 00000000'00000000 ffffc902'105D5740 00000000'00000003 ffff8786'B03F6D90: NT! MiWalkPageTablesRecursively+0x88b
Ffff8786'B03F6b70 fffff801'278C47C1: Ffff8786'B03F6D10 ffffc902'00000001 00000002'00000002 ffff8b0a'00000000: NT! MiWalkPageTables+0x36b
Ffff8786'B03F6C70 fffff801'27caa124: 00000000'00000000 00000000'00000000 00000000'00000000 ffffc901'e4ee9100: NT! MiDeletePagablePteRange+0x4F1
Ffff8786'B03F6F80 fffff801'2790 AF64: Ffffc902'105D50C0 00000000'08450010 00000000'00000002 fffff801'00000000: NT! MiDeleteVadBitmap+0x8C
Ffff8786'B03F7010 fffff801'27ca9fa0: Ffffc902'105D50C0 ffffc902'105D5800 ffffc902'105D5740 ffffc902'0D99A080: NT! MiDeleteFinalPageTables+0xc8
Ffff8786'B03F70D0 fffff801'27ca742F: Ffffc902'105D50C0 ffff8786'B03F7190 ffffc902'0D99A080 ffffc902'105D5508: NT! MmDeleteProcessAddressSpace+0x64
Ffff8786'B03F7120 fffff801'27C13D50: Ffffc902'105D5090 ffffc902'105D5090 00000000'00000000 ffffc901'e4ecf0C0: NT! PspProcessDelete+0x13F
Ffff8786'B03F71b0 fffff801'2780EC07: 00000000'00000000 00000000'00000000 ffff8786'B03F7339 ffffc902'105D50C0: NT! ObpRemoveObjectRoutine+0x80
Ffff8786'B03F7210 fffff801'27C01299: Ffffc902'105D5090 00000000'00000000 00000000'00000000 ffffc902'0be75200: NT! ObfDereferenceObjectWithTag+0xc7
Ffff8786'B03F7250 fffff801'27C050CC: 00000000'00000CCC ffff8786'B03F7480 ffffc902'00000000 ffffc902'105D50C0: NT! ObCloseHandleTableEntry+0x6C9
Ffff8786'B03F7390 fffff801'27a0aab5: Ffffc902'0D99A000 ffffc902'00000000 ffff8786'B03F7480 ffffffff'F4143E00: NT! NtClose+0xec
Ffff8786'B03F7400 00007FFC'A796D2A4: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: NT! KiSystemServiceCopyEnd+0x25
00000066'F5e7F6C8 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: 0x00007ffc`a796d2a4
SYMBOL_NAME: NT! MiGetNextPageTablePte+1F28ca
MODULE_NAME: NT
STACK_COMMAND: Cxr. Ecxr; KB
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID_FUNC_OFFSET: 1F28ca
FAILURE_BUCKET_ID: 0x7a_C0000005_nt! MiGetNextPageTablePte
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: Vb_release
OSPLATFORM_TYPE: X64
OSNAME: Windows 10
FAILURE_ID_HASH: {D4584103-842D-CAC6-0C84-edfb0F8FE0b3}
Followup: MachineOwner
---------
Copyright (C) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol Search path is: Srv*
Executable Search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free X64
Product: WinNt, Suite: TerminalServer SingleUserTS
Edition Build lab: 19041.1.AMD64fre. Vb_release. 191206-1406
Machine Name:
Kernel base = 0xfffff801`27600000 PsLoadedModuleList = 0xfffff801`2822a270
Debug session time: Mon Nov 7 21:12:45.045 2022 (UTC + 3:00)
System Uptime: 0 days 1:40:59.676
Loading Kernel Symbols
Page 84E683 not present in the dump file. Type ".hh dbgerr004" for details
Page 862EF0 not present in the dump file. Type ".hh dbgerr004" for details
Page 86213C not present in the dump file. Type ".hh dbgerr004" for details
Page 867DD5 not present in the dump file. Type ".hh dbgerr004" for details
Page 865C9F not present in the dump file. Type ".hh dbgerr004" for details
Loading User Symbols
PEB is paged out (Peb. Ldr = 00000027'D6b4F018). Type ".hh dbgerr001" for details
Loading unloaded module list
For analysis of this file, run! Analyze -v
NT! KeBugCheckEx:
Fffff801'279F90F0 48894C2408 mov qword ptr [rsp+8],rcx SS:0018:ffff8786'B03F6940 = 000000000000007A
2: Kd>!analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
A bad block in the paging file or disk Controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
İt means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
A filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000001, lock type that was held (Value 1, 2, 3, or PTE address)
Arg2: FffffffFC0000005, error status (normally i/o status code)
Arg3: FffFC902105D50C0, current process (Virtual address for lock type 3, or PTE)
Arg4: FffFF47CCD80b000, Virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
Page 196905 not present in the dump file. Type ".hh dbgerr004" for details
KEY_VALUES_STRING: 1
Key: Analysis. CPU. MSec
Value: 2718
Key: Analysis. DebugAnalysisManager
Value: Create
Key: Analysis. Elapsed. MSec
Value: 10123
Key: Analysis. IO. Other. MB
Value: 19
Key: Analysis. IO. Read. MB
Value: 0
Key: Analysis. IO. Write. MB
Value: 26
Key: Analysis. Init. CPU. MSec
Value: 702
Key: Analysis. Init. Elapsed. MSec
Value: 63471
Key: Analysis. Memory.commitPeak. MB
Value: 100
Key: Bugcheck. Code. DumpHeader
Value: 0x7a
Key: Bugcheck. Code. KiBugCheckData
Value: 0x7a
Key: Bugcheck. Code. Register
Value: 0x7a
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
FILE_IN_CAB: MEMORY.DMP
BUGCHECK_CODE: 7A
BUGCHECK_P1: 1
BUGCHECK_P2: FffffffFC0000005
BUGCHECK_P3: FFFFC902105D50C0
BUGCHECK_P4: FffFF47CCD80B000
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.
PROCESS_NAME: svchost.exe
STACK_TEXT:
Ffff8786'B03F6938 fffff801'27a2bbca: 00000000'0000007A 00000000'00000001 ffffffff'C0000005 ffffc902'105D50C0: NT! KeBugCheckEx
Ffff8786'B03F6940 fffff801'278388CB: 00000000'00000001 ffffc902'00000000 00000000'00000016 00010000'00000000: NT! MiGetNextPageTablePte+0x1F28ca
Ffff8786'B03F6990 fffff801'27838B7B: Fffff47a'00000000 ffffc902'105D5740 ffff8786'00000001 ffff8786'B03F6D70: NT! MiWalkPageTablesRecursively+0x5dB
Ffff8786'B03F6a30 fffff801'27838B7B: Fffff47a'3D1F3000 ffffc902'105D5740 ffff8786'00000002 ffff8786'B03F6D80: NT! MiWalkPageTablesRecursively+0x88b
Ffff8786'B03F6ad0 fffff801'2780B7DB: 00000000'00000000 ffffc902'105D5740 00000000'00000003 ffff8786'B03F6D90: NT! MiWalkPageTablesRecursively+0x88b
Ffff8786'B03F6b70 fffff801'278C47C1: Ffff8786'B03F6D10 ffffc902'00000001 00000002'00000002 ffff8b0a'00000000: NT! MiWalkPageTables+0x36b
Ffff8786'B03F6C70 fffff801'27caa124: 00000000'00000000 00000000'00000000 00000000'00000000 ffffc901'e4ee9100: NT! MiDeletePagablePteRange+0x4F1
Ffff8786'B03F6F80 fffff801'2790 AF64: Ffffc902'105D50C0 00000000'08450010 00000000'00000002 fffff801'00000000: NT! MiDeleteVadBitmap+0x8C
Ffff8786'B03F7010 fffff801'27ca9fa0: Ffffc902'105D50C0 ffffc902'105D5800 ffffc902'105D5740 ffffc902'0D99A080: NT! MiDeleteFinalPageTables+0xc8
Ffff8786'B03F70D0 fffff801'27ca742F: Ffffc902'105D50C0 ffff8786'B03F7190 ffffc902'0D99A080 ffffc902'105D5508: NT! MmDeleteProcessAddressSpace+0x64
Ffff8786'B03F7120 fffff801'27C13D50: Ffffc902'105D5090 ffffc902'105D5090 00000000'00000000 ffffc901'e4ecf0C0: NT! PspProcessDelete+0x13F
Ffff8786'B03F71b0 fffff801'2780EC07: 00000000'00000000 00000000'00000000 ffff8786'B03F7339 ffffc902'105D50C0: NT! ObpRemoveObjectRoutine+0x80
Ffff8786'B03F7210 fffff801'27C01299: Ffffc902'105D5090 00000000'00000000 00000000'00000000 ffffc902'0be75200: NT! ObfDereferenceObjectWithTag+0xc7
Ffff8786'B03F7250 fffff801'27C050CC: 00000000'00000CCC ffff8786'B03F7480 ffffc902'00000000 ffffc902'105D50C0: NT! ObCloseHandleTableEntry+0x6C9
Ffff8786'B03F7390 fffff801'27a0aab5: Ffffc902'0D99A000 ffffc902'00000000 ffff8786'B03F7480 ffffffff'F4143E00: NT! NtClose+0xec
Ffff8786'B03F7400 00007FFC'A796D2A4: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: NT! KiSystemServiceCopyEnd+0x25
00000066'F5e7F6C8 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: 0x00007ffc`a796d2a4
SYMBOL_NAME: NT! MiGetNextPageTablePte+1F28ca
MODULE_NAME: NT
STACK_COMMAND: Cxr. Ecxr; KB
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID_FUNC_OFFSET: 1F28ca
FAILURE_BUCKET_ID: 0x7a_C0000005_nt! MiGetNextPageTablePte
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: Vb_release
OSPLATFORM_TYPE: X64
OSNAME: Windows 10
FAILURE_ID_HASH: {D4584103-842D-CAC6-0C84-edfb0F8FE0b3}
Followup: MachineOwner
---------
Arkadaşlar "KERNEL_DATA_INPAGE_ERROR (7a)-KERNEL_STACK_INPAGE_ERROR."
desede bu sorun belirli bir oyun kaynaklı olabilir mi? Çünkü sadece Far Cry 6'da oluyor.
Birde sorunun Far Cry 6 kaynaklı olup olmadığını anlamak için, mavi ekranı tetiklemek için bir yol varmı oyun oynamadan?
Son düzenleme: