Windows 7 Kernel Mode Exception Not Handled 1000008e Mavi Ekran Hatası

numanturle

Hectopat
Katılım
31 Ocak 2013
Mesajlar
56
Yer
Diyarbakır
Daha fazla  
Cinsiyet
Erkek
Merhaba arkadaşlar. Mavi ekran hatası alıyorum sürekli, yardımcı olur musunuz ? Dosyayı analiz ettiğimde:
Kod:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18700.x86fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0x82c0a000 PsLoadedModuleList = 0x82d4a310
Debug session time: Mon Feb  9 11:39:35.090 2015 (UTC - 5:00)
System Uptime: 0 days 0:09:37.668
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 9a180d20, The address that the exception occurred at
Arg3: a70cbb38, Trap Frame
Arg4: 00000000

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
win32k!RFONTOBJ::bMatchRealization+b
9a180d20 8b4648          mov     eax,dword ptr [esi+48h]

TRAP_FRAME:  a70cbb38 -- (.trap 0xffffffffa70cbb38)
ErrCode = 00000000
eax=41200000 ebx=a70cbc90 ecx=a70cbcdc edx=00008005 esi=41200000 edi=a70cbcdc
eip=9a180d20 esp=a70cbbac ebp=a70cbbb4 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
win32k!RFONTOBJ::bMatchRealization+0xb:
9a180d20 8b4648          mov     eax,dword ptr [esi+48h] ds:0023:41200048=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 9a189483 to 9a180d20

STACK_TEXT:
a70cbbb4 9a189483 a70cbc2c 10018000 00000000 win32k!RFONTOBJ::bMatchRealization+0xb
a70cbbf0 9a1a7752 a70cbc2c 10018000 00000000 win32k!RFONTOBJ::bFindRFONT+0x49
a70cbc98 9a1a79eb fdd12008 00000000 00000002 win32k!RFONTOBJ::bInit+0x285
a70cbcb0 9a13eb56 a70cbcc8 00000000 00000002 win32k!RFONTOBJ::vInit+0x16
a70cbcd4 9a13eca4 41200000 a70cbcf4 3d2286d0 win32k!GreGetRealizationInfo+0x2a
a70cbd24 82c3f8c6 0c0110a0 0025f47c 0025f494 win32k!NtGdiGetRealizationInfo+0x41
a70cbd24 77a070f4 0c0110a0 0025f47c 0025f494 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
0025f494 00000000 00000000 00000000 00000000 0x77a070f4


STACK_COMMAND:  kb

FOLLOWUP_IP:
win32k!RFONTOBJ::bMatchRealization+b
9a180d20 8b4648          mov     eax,dword ptr [esi+48h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!RFONTOBJ::bMatchRealization+b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  54372c31

FAILURE_BUCKET_ID:  0x8E_win32k!RFONTOBJ::bMatchRealization+b

BUCKET_ID:  0x8E_win32k!RFONTOBJ::bMatchRealization+b

Followup: MachineOwner

Minidump dosyası ;
Dosya
 
Son düzenleyen: Moderatör:
Uyarı! Bu konu 11 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Technopat Haberler

Geri
Yukarı