Mavi ekran neden alınır?

Dedektif Denyo

Hectopat
Katılım
3 Aralık 2015
Mesajlar
466
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
Arkadaşlar hata bu F8'e bastım bir şey olmadı, açma kapa tuşuna bastım yine hiçbir şey olmadı. Geçenlerde ekran kartı driver yüklemiştim onla ilgili olabilir mi? Yanlış sürücü yüklemiş olabilir miyim?
Düzenleme: Sonradan kapatmayı başarabildim, açılırken 2 seçenek sunuyor:
1- Başlangıç onarmayı başlat ( önerilen )
2- Windows'u normal olarak başlat.
Ne olur ne olmaz diye verilerimi yedeklemek için normal olarak başlattım şimdi, sonradan 1. Seçeneği mi seçmeliyim?
 
Son düzenleyen: Moderatör:
Genelde işletim sisteminin altında yatan, donanımla yazılımın arasındaki iletişimi sağlayan kernel çekirdeğinin donanımla olan bağlantısında bir sıkıntı oluştuğunda mavi ekran hataları alıyoruz. Zaten mavi ekran aslında kernel çekirdeğinde oluşmuş problemleri bize gösteriyor. Ancak buna zaman zaman donanımdan ziyade yazılım da sebep olabiliyor.
 
0x000007E hatası herhangi bir aygıt sürücüsü ya da BIOS güncellediginde çıkar diye biliyorum. Bilgisayarı başlatabiliyor isen son yüklediğin sürücüyü kaldırmak sorunu çözebilir.
 
 
Kod:
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: fffff8a0094ffa68, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: 0000000025b2c860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff96000154058, 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.Sec
Value: 2

Key : Analysis.Elapsed.Sec
Value: 32

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


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 7601.19045.amd64fre.win7sp1_gdr.151019-1254

SYSTEM_MANUFACTURER: LENOVO

SYSTEM_PRODUCT_NAME: 20079

SYSTEM_SKU: HuronRiver_CRB

SYSTEM_VERSION: Lenovo G570

BIOS_VENDOR: LENOVO

BIOS_VERSION: 40CN03WW(V2.02)

BIOS_DATE: 03/31/2011

BASEBOARD_MANUFACTURER: LENOVO

BASEBOARD_PRODUCT: Base Board Product Name

BASEBOARD_VERSION: Base Board Version

DUMP_TYPE: 2

BUGCHECK_P1: fffff8a0094ffa68

BUGCHECK_P2: ffffffffc000009d

BUGCHECK_P3: 25b2c860

BUGCHECK_P4: fffff96000154058

ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000009d

CPU_COUNT: 4

CPU_MHZ: 8f6

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 2a

CPU_STEPPING: 7

CPU_MICROCODE: 6,2a,7,0 (F,M,S,R) SIG: 15'00000000 (cache) 15'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-I8FA0KP

ANALYSIS_SESSION_TIME: 08-06-2019 00:23:34.0492

ANALYSIS_VERSION: 10.0.18914.1001 amd64fre

TRAP_FRAME:  fffff88003c4f740 -- (.trap 0xfffff88003c4f740)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=fffff900c0600b90 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000154058 rsp=fffff88003c4f8d0 rbp=000000000000fd14
r8=fffff900c0600b90 r9=fffff900c2100cd0 r10=0000000017cf0000
r11=0000000000000900 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
win32k!ProcessHungWindow+0x98:
fffff960`00154058 488b6c2438 mov rbp,qword ptr [rsp+38h] ss:0018:fffff880`03c4f908=000000000000fd14
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002ae8632 to fffff80002a75c40

STACK_TEXT:
fffff880`03c4f428 fffff800`02ae8632 : 00000000`0000007a fffff8a0`094ffa68 ffffffff`c000009d 00000000`25b2c860 : nt!KeBugCheckEx
fffff880`03c4f430 fffff800`02a9d23f : fffffa80`0754b650 fffff880`03c4f5a0 fffff880`04f8fc00 fffffa80`0754b650 : nt! ?? ::FNODOBFM::`string'+0x353ea
fffff880`03c4f510 fffff800`02a83ac9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`010b5fea : nt!MiIssueHardFault+0x28b
fffff880`03c4f5e0 fffff800`02a73d6e : 00000000`00000008 fffff960`00154058 00610003`00610000 00000000`00000000 : nt!MmAccessFault+0x1399
fffff880`03c4f740 fffff960`00154058 : 00000000`00000000 00000000`0000fd14 00000000`0000000a fffff900`c0634100 : nt!KiPageFault+0x16e
fffff880`03c4f8d0 fffff960`001860e3 : fffff900`c0634100 00000000`0000fd14 00000000`0000000a fffff900`c01cf3d8 : win32k!ProcessHungWindow+0x98
fffff880`03c4f900 fffff960`000d623d : fffff900`c01cf330 fffff900`c00c7000 00000000`00000004 fffff800`02a7f39b : win32k!xxxHungAppDemon+0xb3
fffff880`03c4f960 fffff960`000d6cb7 : 00000000`00000000 fffff960`00305ed0 00000000`00000004 00000000`00000001 : win32k!TimersProc+0xf1
fffff880`03c4f9b0 fffff960`00065318 : fffffa80`0000007b 00000000`0000000f fffff880`00000001 ffffffff`80000250 : win32k!RawInputThread+0x9ab
fffff880`03c4fa80 fffff960`000e789a : fffffa80`00000002 fffff880`03c3be00 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
fffff880`03c4fab0 fffff800`02a74ed3 : fffffa80`063399a0 00000000`00000004 000007ff`fffd3000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`03c4fae0 000007fe`fd1f1eea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00e7f978 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fd1f1eea


THREAD_SHA1_HASH_MOD_FUNC: 9721f6637eccc99a51120ddc52d02d9f0cf8cd8d

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 837809e536391278d066075ca10335293d1facfc

THREAD_SHA1_HASH_MOD: 1d008e22c78a65a72c8fd21a18c090605bc91615

FOLLOWUP_IP:
win32k!ProcessHungWindow+98
fffff960`00154058 488b6c2438 mov rbp,qword ptr [rsp+38h]

FAULT_INSTR_CODE: 246c8b48

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: win32k!ProcessHungWindow+98

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 56422d98

IMAGE_VERSION: 6.1.7601.19061

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: X64_0x7a_c000009d_win32k!ProcessHungWindow+98

BUCKET_ID: X64_0x7a_c000009d_win32k!ProcessHungWindow+98

PRIMARY_PROBLEM_CLASS: X64_0x7a_c000009d_win32k!ProcessHungWindow+98

TARGET_TIME: 2015-12-30T11:07:42.000Z

OSBUILD: 7601

OSSERVICEPACK: 1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2015-10-20 02:48:44

BUILDDATESTAMP_STR: 151019-1254

BUILDLAB_STR: win7sp1_gdr

BUILDOSVER_STR: 6.1.7601.19045.amd64fre.win7sp1_gdr.151019-1254

ANALYSIS_SESSION_ELAPSED_TIME: 7e5d

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x7a_c000009d_win32k!processhungwindow+98

FAILURE_ID_HASH: {0869cd8a-5962-494a-3865-adca02d464bf}

Followup:     MachineOwner
BIOS güncelle ve Win 10 1903'e temiz kurulum ile geç.
Güncel GPU sürücülerini kullan.
 
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…