Çözüldü KERNEL_DATA_INPAGE_ERROR (7a) mavi ekran

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
Durum
Mesaj gönderimine kapalı.
İşletim sistemi
Windows 10
Çözüm
Recep Baltaş
SSD sorunu gibi. Garantiye gönderin.


Kod: 
CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffffa78f4823c140, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3671

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 7606

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

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

BUGCHECK_P1: ffffa78f4823c140

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME:  csrss.exe

CRITICAL_PROCESS:  csrss.exe

EXCEPTION_RECORD:  0000000000001000 -- (.exr 0x1000)
Cannot read Exception record @ 0000000000001000

ERROR_CODE: (NTSTATUS) 0x497e0080 - <Unable to get error code text>

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

TRAP_FRAME:  ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT: 
ffffe108`92ad0d88 fffff801`3e7068e2     : 00000000`000000ef ffffa78f`4823c140 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffe108`92ad0d90 fffff801`3e649b39     : 00000000`00000001 fffff801`3e15971d 00000000`00000002 fffff801`3e158d37 : nt!PspCatchCriticalBreak+0x10e
ffffe108`92ad0e30 fffff801`3e509724     : ffffa78f`00000000 00000000`00000000 ffffa78f`4823c140 ffffa78f`4823c578 : nt!PspTerminateAllThreads+0x140b4d
ffffe108`92ad0ea0 fffff801`3e509a4c     : ffffa78f`4823c140 00000000`00000001 ffffffff`ffffffff 00000000`00000000 : nt!PspTerminateProcess+0xe0
ffffe108`92ad0ee0 fffff801`3e2071b8     : ffffa78f`4823c140 ffffa78f`497e0080 ffffe108`92ad0fd0 fffff801`3e51da92 : nt!NtTerminateProcess+0x9c
ffffe108`92ad0f50 fffff801`3e1f95e0     : fffff801`3e291307 ffffe108`92ad1a58 ffffe108`92ad1a58 ffffffff`ffffffff : nt!KiSystemServiceCopyEnd+0x28
ffffe108`92ad10e8 fffff801`3e291307     : ffffe108`92ad1a58 ffffe108`92ad1a58 ffffffff`ffffffff 00007ffc`0afc3000 : nt!KiServiceLinkage
ffffe108`92ad10f0 fffff801`3e2078ac     : 00000000`00001000 ffffe108`92ad1b00 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x166907
ffffe108`92ad1920 fffff801`3e203a43     : 00007ffc`0d92fe3e 00000000`00000000 ffffe108`92ad1b80 ffffa78f`497e0080 : nt!KiExceptionDispatch+0x12c
ffffe108`92ad1b00 00007ffc`0d8db3de     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x443
000000fa`3cac0eb0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`0d8db3de


SYMBOL_NAME:  nt!PspCatchCriticalBreak+10e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.685

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  10e

FAILURE_BUCKET_ID:  0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_497e0080_nt!PspCatchCriticalBreak

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f675ca05-0aff-fb30-f6f7-79e7272cdd81}

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

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,
it 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: ffffd5852f289da8, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000000b3552860, current process (virtual address for lock type 3, or PTE)
Arg4: ffff8453269b5f60, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3843

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 4857

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

BUGCHECK_P1: ffffd5852f289da8

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: b3552860

BUGCHECK_P4: ffff8453269b5f60

ERROR_CODE: (NTSTATUS) 0xc000000e - Varolmayan bir ayg t belirtildi.

DISK_HARDWARE_ERROR: There was error with disk hardware

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  csrss.exe

TRAP_FRAME:  ffffb182e2ca6a80 -- (.trap 0xffffb182e2ca6a80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff8c06cdbf6620 rbx=0000000000000000 rcx=ffff8417006248a0
rdx=ffff841700830930 rsi=0000000000000000 rdi=0000000000000000
rip=ffff8453269b5f60 rsp=ffffb182e2ca6c18 rbp=ffffb182e2ca6ce9
 r8=ffffb182e2ca6b50  r9=0000000000000000 r10=ffff8453269b5f60
r11=ffffb182e2ca6ae0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
win32kbase!CancelCapturedMipOverride:
ffff8453`269b5f60 4883ec28        sub     rsp,28h
Resetting default scope

STACK_TEXT: 
ffffb182`e2ca66d8 fffff803`52eb6e29     : 00000000`0000007a ffffd585`2f289da8 ffffffff`c000000e 00000000`b3552860 : nt!KeBugCheckEx
ffffb182`e2ca66e0 fffff803`52eb4b35     : ffffb182`00008000 ffffb182`e2ca6800 ffffb182`e2ca6870 fffff803`00000000 : nt!MiWaitForInPageComplete+0x7d9
ffffb182`e2ca67d0 fffff803`52e0c9c8     : 00000000`c0033333 00000000`00000000 ffff8453`269b5f60 00000000`00000000 : nt!MiIssueHardFault+0x3c5
ffffb182`e2ca68e0 fffff803`5300395e     : 00000000`00000000 ffff8c06`d60a65f0 00000000`00000000 fffff803`52e50cb9 : nt!MmAccessFault+0x468
ffffb182`e2ca6a80 ffff8453`269b5f60     : ffff8453`26c84dba 00000000`00000000 00000000`0000002e ffff8417`071e5780 : nt!KiPageFault+0x35e
ffffb182`e2ca6c18 ffff8453`26c84dba     : 00000000`00000000 00000000`0000002e ffff8417`071e5780 00000000`00000000 : win32kbase!CancelCapturedMipOverride
ffffb182`e2ca6c20 ffff8453`26bbb061     : ffff8417`006248a0 00000000`00000000 ffffffff`00000000 ffffb182`e2ca6e88 : win32kfull!xxxDoHotKeyStuff+0xc9d2a
ffffb182`e2ca6d50 ffff8453`26869100     : ffffffff`ffffffff ffff8417`006248a0 ffff8417`0462c230 ffffb182`e2ca6dd0 : win32kfull!EditionDoHotKeys+0x21
ffffb182`e2ca6d80 ffff8453`26868b78     : ffffffff`ffffffff ffffb182`e2ca6ec9 00000000`0000002e ffff8417`006248a0 : win32kbase!ApiSetEditionDoHotKeys+0xac
ffffb182`e2ca6de0 ffff8453`26868982     : ffffb182`e2ca70e0 ffffb182`e2ca6fc9 00000000`00000000 ffffb182`e2ca70e0 : win32kbase!xxxUpdateGlobalsAndSendKeyEvent+0x1b8
ffffb182`e2ca6f10 ffff8453`269b8e8a     : ffffb182`e2ca0100 ffffb182`e2ca70d0 00000000`07b9df24 00000000`00000000 : win32kbase!xxxKeyEventEx+0x1e2
ffffb182`e2ca7010 ffff8453`269b8b07     : ffff8417`00606a30 00000000`00000000 ffffb182`e2ca7190 ffff8c06`ce1520c8 : win32kbase!xxxProcessKeyEvent+0x2da
ffffb182`e2ca7090 ffff8453`269aa508     : 00000000`00000000 ffff8c06`d60a8bf0 ffff8417`00606a30 ffffa87f`50e00000 : win32kbase!ProcessKeyboardInputWorker+0x837
ffffb182`e2ca71f0 ffff8453`269aa389     : ffff8453`26a5b6d0 ffffb182`e2ca7301 00000000`00000000 ffff8c06`d0dcdf00 : win32kbase!CKeyboardProcessor::ProcessInputNoLock+0xdc
ffffb182`e2ca7220 ffff8453`269b2d3d     : ffff8417`006069e0 ffff8c06`ce152070 00000000`0000000c 00000000`00000000 : win32kbase!CKeyboardProcessor::ProcessInput+0x491
ffffb182`e2ca7360 ffff8453`269ac04a     : ffff8453`26a10700 ffffb182`e2ca74a0 ffff8417`006069e0 ffff8453`26a51970 : win32kbase!CKeyboardSensor::ProcessInput+0x5d
ffffb182`e2ca73a0 ffff8453`26864c1d     : 00000000`00000040 ffff8453`26a10700 00000000`00000001 00000000`00000000 : win32kbase!CBaseInput::OnReadNotification+0x52a
ffffb182`e2ca74e0 ffff8453`26864d52     : ffff8c06`ce219080 ffff8417`00658100 00000000`00000006 ffffaeee`955f04de : win32kbase!CBaseInput::OnDispatcherObjectSignaled+0x31d
ffffb182`e2ca7620 ffff8453`268586de     : ffff8453`26a582a0 ffff8417`00658100 ffff8453`26a51970 00000000`00000001 : win32kbase!CBaseInput::_OnDispatcherObjectSignaled+0x12
ffffb182`e2ca7650 ffff8453`26858430     : 00000000`00000006 ffff8453`26a582a0 00000000`00000001 ffff8417`00641c00 : win32kbase!LegacyInputDispatcher::Dispatch+0x52
ffffb182`e2ca7680 ffff8453`26b99e7f     : 00000000`00000010 00000000`00000001 00002000`00000000 00000000`00000004 : win32kbase!LegacyInputDispatcher::WaitAndDispatch+0x100
ffffb182`e2ca77b0 ffff8453`268c60c3     : ffff8c06`ce219080 ffff8c06`ce219080 00000000`00000000 00000000`00000005 : win32kfull!RawInputThread+0x7bf
ffffb182`e2ca7970 ffff8453`26b38d80     : ffff8c06`ce219080 00000000`00000000 00000000`00000005 00000000`00000005 : win32kbase!xxxCreateSystemThreads+0xc3
ffffb182`e2ca7aa0 ffff8453`2749474d     : ffff8c06`ce219080 ffff8c06`ce219080 00000000`00000000 00000000`00000000 : win32kfull!NtUserCallNoParam+0x70
ffffb182`e2ca7ad0 fffff803`530071b8     : ffff8c06`00000005 00000000`00000005 00000245`1d8041e0 00000000`00001d9c : win32k!NtUserCallNoParam+0x15
ffffb182`e2ca7b00 00007ff8`0ff110e4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000061`aa13fbe8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`0ff110e4


SYMBOL_NAME:  win32kfull!xxxDoHotKeyStuff+c9d2a

MODULE_NAME: win32kfull

IMAGE_NAME:  win32kfull.sys

IMAGE_VERSION:  10.0.19041.1131

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  c9d2a

FAILURE_BUCKET_ID:  0x7a_c000000e_win32kfull!xxxDoHotKeyStuff

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {aa029fec-9ea3-bc99-2cd2-7ccae0765f65}

Followup:     MachineOwner
---------
CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffff980b5ce48080, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4514

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 13023

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

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

BUGCHECK_P1: ffff980b5ce48080

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME:  csrss.exe

CRITICAL_PROCESS:  csrss.exe

EXCEPTION_RECORD:  ffff980b5ce487c0 -- (.exr 0xffff980b5ce487c0)
ExceptionAddress: 0000000000000000
   ExceptionCode: 00000000
  ExceptionFlags: 00000000
NumberParameters: 0

ERROR_CODE: (NTSTATUS) 0x59030080 - <Unable to get error code text>

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

EXCEPTION_STR:  0x0

STACK_TEXT: 
ffffce87`bde7cd88 fffff806`5d5068e2     : 00000000`000000ef ffff980b`5ce48080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffce87`bde7cd90 fffff806`5d449b39     : 00000000`00000001 fffff806`5cf5971d 00000000`00000002 fffff806`5cf58d37 : nt!PspCatchCriticalBreak+0x10e
ffffce87`bde7ce30 fffff806`5d309724     : ffff980b`00000000 00000000`00000000 ffff980b`5ce48080 ffff980b`5ce484b8 : nt!PspTerminateAllThreads+0x140b4d
ffffce87`bde7cea0 fffff806`5d309a4c     : ffff980b`5ce48080 00000000`00000001 ffffffff`ffffffff 00000000`00000000 : nt!PspTerminateProcess+0xe0
ffffce87`bde7cee0 fffff806`5d0071b8     : ffff980b`5ce48080 ffff980b`59030080 ffffce87`bde7cfd0 fffff806`5d31da92 : nt!NtTerminateProcess+0x9c
ffffce87`bde7cf50 fffff806`5cff95e0     : fffff806`5d091307 ffffce87`bde7da58 ffffce87`bde7da58 ffffffff`ffffffff : nt!KiSystemServiceCopyEnd+0x28
ffffce87`bde7d0e8 fffff806`5d091307     : ffffce87`bde7da58 ffffce87`bde7da58 ffffffff`ffffffff 00007ffa`5c9e3000 : nt!KiServiceLinkage
ffffce87`bde7d0f0 fffff806`5d0078ac     : ffff980b`5ce487c0 fffff806`5ce0ecc6 00000000`00000c00 ffffce87`bde7db00 : nt!KiDispatchException+0x166907
ffffce87`bde7d920 fffff806`5d003a43     : 00000000`00000000 00000000`00000000 ffffce87`bde7db80 ffff980b`5cdd9340 : nt!KiExceptionDispatch+0x12c
ffffce87`bde7db00 00007ffa`5f2d4042     : 00000000`00000000 00000051`00000000 00000051`f0c41700 00000051`f0c41708 : nt!KiPageFault+0x443
00000051`f0c416e0 00000000`00000000     : 00000051`00000000 00000051`f0c41700 00000051`f0c41708 00007ffa`5c9e3000 : 0x00007ffa`5f2d4042


SYMBOL_NAME:  nt!PspCatchCriticalBreak+10e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.685

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  10e

FAILURE_BUCKET_ID:  0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_59030080_nt!PspCatchCriticalBreak

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3d7cdc3d-7c70-e0e0-600c-30fe3569ecf0}

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

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,
it 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: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: ffffd083362730e0, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3343

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 38617

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

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

BUGCHECK_P1: 20

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: ffffd083362730e0

BUGCHECK_P4: 0

ERROR_CODE: (NTSTATUS) 0xc000000e - Varolmayan bir ayg t belirtildi.

DISK_HARDWARE_ERROR: There was error with disk hardware

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffb809`71a613f8 fffff806`7849e336     : 00000000`0000007a 00000000`00000020 ffffffff`c000000e ffffd083`362730e0 : nt!KeBugCheckEx
ffffb809`71a61400 fffff806`78320afb     : 00000000`00000000 ffffb809`c000000e 00000000`00000000 fffff806`00002000 : nt!MiWriteComplete+0x14a9f6
ffffb809`71a614b0 fffff806`78267ce0     : ffffd083`36214580 ffffd083`38cbc9d8 ffffe381`3a791730 00000000`00000000 : nt!IopCompletePageWrite+0x4b
ffffb809`71a614e0 fffff806`783f9ae0     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd083`423ff000 : nt!KiDeliverApc+0x1b0
ffffb809`71a61590 fffff806`783449d9     : ffffd083`00000000 00000000`0000001f 00000000`00000000 00000000`00000000 : nt!KiApcInterrupt+0x2f0
ffffb809`71a61720 fffff806`7834e23c     : ffffffff`0039f1b2 ffffffff`ffffff00 ffffd083`361c21a0 0002a2e5`00000100 : nt!MiStoreUpdatePagefileHash+0xc9
ffffb809`71a617b0 fffff806`7834fe8d     : ffffd083`361c20d0 ffffd083`37851bb8 fffff380`0039f2b2 fffff806`00000000 : nt!MiStoreWriteModifiedPages+0x670
ffffb809`71a618e0 fffff806`783baf59     : ffffd083`361c20d0 fffff806`00000100 fffff806`00000100 ffffe381`00000100 : nt!MiGatherPagefilePages+0x455
ffffb809`71a619e0 fffff806`78317e25     : ffffd083`36214580 ffffd083`36214580 00000000`00000080 fffff806`783bacc0 : nt!MiModifiedPageWriter+0x299
ffffb809`71a61c10 fffff806`783fcdd8     : fffff806`73291180 ffffd083`36214580 fffff806`78317dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffb809`71a61c60 00000000`00000000     : ffffb809`71a62000 ffffb809`71a5c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!MiWriteComplete+14a9f6

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.685

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  14a9f6

FAILURE_BUCKET_ID:  0x7a_c000000e_nt!MiWriteComplete

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {fcc12098-ee04-35bd-5cea-593a2c6ec31d}

Followup:     MachineOwner
---------
Tarihe göre sırala Puana göre sırala
Artı 0 Eksi
Öncelikle ilgilendiğiniz için teşekkür ederim.
1.Bende sadece Gigabyte sıv ve easytune programları var. O yüzden dediğiniz yazılımı kaldıramadım.
2.Genellikle ben WHQL sertifikalı güncel sürüm indiririm ama ne zaman isteğe bağlı olan güncelleme olduysa o zaman mavi ekran veya WattMan hatası aldım. Sanırım hiç indirmemeliyim. WHQL sertifikalı güncellemeyle devam etmeliyim.
3.Attığınız ZIP içindeki setup ile ses sürücümü güncelledim.
4.BattlEye yüklü olmadığı için bir şey yapmadım.
5.SFC rehberini uyguladım 2.fotoğraftaki gibi bir şey yazdı.
 
Artı 0 Eksi
Muzaffer İLİŞİK dedi:
1. Bende sadece GigaByte SIV ve EasyTune programları var. O yüzden dediğiniz yazılımı kaldıramadım.
Genişletmek için tıkla...
Kullanmıyorsanız kaldırın. Belki onlardan birinin içinde On/Off Charge özelliği vardır.
Muzaffer İLİŞİK dedi:
2. Genellikle ben WHQL sertifikalı güncel sürüm indiririm ama ne zaman isteğe bağlı olan güncelleme olduysa o zaman mavi ekran veya WattMan hatası aldım. Sanırım hiç indirmemeliyim. WHQL sertifikalı güncellemeyle devam etmeliyim.
Genişletmek için tıkla...
Kullandığınız sürümü DDU ile kaldırıp tekrar yüklemenizi öneririm.
Muzaffer İLİŞİK dedi:
4. BattlEye yüklü olmadığı için bir şey yapmadım.
Genişletmek için tıkla...
BattlEye Anti-Cheat yazılımını kullanan oyunların klasöründe olur genellikle. Oradan kaldırın, gerektiğinde yüklersiniz veya oyuna girince kendisi yüklenir.
Muzaffer İLİŞİK dedi:
5. SFC rehberini uyguladım, 2. fotoğraftaki gibi bir şey yazdı.
Genişletmek için tıkla...
Maalesef fotoğraf gözükmemekte.
 
Artı 0 Eksi
Ma&#039;at dedi:
Kullanmıyorsanız kaldırın. Belki onlardan birinin içinde On/Off Charge özelliği vardır.

Kullandığınız sürümü DDU ile kaldırıp tekrar yüklemenizi öneririm.

BattlEye Anti-Cheat yazılımını kullanan oyunların klasöründe olur genellikle. Oradan kaldırın, gerektiğinde yüklersiniz veya oyuna girince kendisi yüklenir.

Maalesef fotoğraf gözükmemekte.
Genişletmek için tıkla...
Dediğiniz gibi DDU ile kaldırıp yükledim.
BattlEye kullanan oyunlara bakıcam bulabilirsem sileceğim.
2.fotoğraf derken linkini attığınız rehberin 2.fotoğrafdan bahsetmiştim.

Bana gelen mavi ekran hatası sadece yazılımsal hata değil mi ?
 
Artı 0 Eksi
Ma&#039;at dedi:
Donanımsal bir şey olduğunu düşünmüyorum. Yazılımsal gibi geldi bana. Tüm adımları uyguladıktan sonra birkaç gün bekleyin, mavi ekran alırsanız yeni dosyaları paylaşın. Almazsanız çözüldü olarak niteleyebiliriz.
Genişletmek için tıkla...

Teşekkür ederim.

Recep Baltaş dedi:
PC özelliklerinizi belirtin.
Genişletmek için tıkla...

  • Ekran kartı: MSI Armor RX570.
  • İşlemci: AMD Ryzen 5 1600 six-Core Processor 3.20 GHz.
  • RAM: 1x8GB.
  • Anakart: Gigabyte 450M S2H.
  • 125GB SSD
  • 1TB Harddisk

Ma&#039;at dedi:
Donanımsal bir şey olduğunu düşünmüyorum. Yazılımsal gibi geldi bana. Tüm adımları uyguladıktan sonra birkaç gün bekleyin, mavi ekran alırsanız yeni dosyaları paylaşın. Almazsanız çözüldü olarak niteleyebiliriz.
Genişletmek için tıkla...

1607392740092.png


SFC rehberindeki gibi böyle bir şey yazdı devamında yapmam gereken bir şey var mı?
 
Artı 0 Eksi
Aşağıdaki rehberi uygulayın.

Rehber: DISM aracı nedir ve nasıl kullanılır?

Herkese iyi günler. Bu rehberde sizlere DISM komutunun ne işe yaradığını, ne tarz durumlarda kullanılacağını ve nasıl kullanılacağını göstereceğim. İlk önce DISM nedir onu öğrenelim. DISM aracı yani “Deployment Image Servicing and Management” aracı sistemde tıpkı SFC komutunun yaptığı işlev...
www.technopat.net www.technopat.net
 
Artı 0 Eksi
Muzaffer İLİŞİK dedi:
SFC rehberindeki gibi böyle bir şey yazdı. Devamında yapmam gereken bir şey var mı?
Genişletmek için tıkla...
Bozuk dosyalar bulunup onarılmış. @maksu'nun attığı DISM rehberini uygulayabilirsiniz isterseniz. Onun dışında bir şey yapmanıza gerek yok gibi duruyor.
 
Artı 0 Eksi
Durum
Mesaj gönderimine kapalı.

Benzer konular

umut.demircii
  • Soru
KERNEL_DATA_INPAGE_ERROR (7a) Mavi Ekran Hatası
Mesaj
2
Görüntüleme
582
umut.demircii
umut.demircii
Bro4ken
  • Soru
KERNEL_DATA_INPAGE_ERROR (7a) Mavi ekran hatası
Mesaj
3
Görüntüleme
975
Bro4ken
Bro4ken
UPSDeviL
  • Çözüldü
Çözüldü  KERNEL_DATA_INPAGE_ERROR (7A) HATASI
2 3
Mesaj
21
Görüntüleme
941
181951
181951
efeeeeeeeeee
  • Soru
KERNEL_DATA_INPAGE_ERROR mavi ekran
4 5 6
Mesaj
52
Görüntüleme
2.974
KojiroHyuga04
KojiroHyuga04
tortorella
  • Soru
Mavi Ekran - KERNEL_DATA_INPAGE_ERROR
Mesaj
8
Görüntüleme
1.255
tortorella
tortorella

Technopat Haberler

Yeni konular

Yeni mesajlar

Geri
Yukarı