BSOD

[maunir]

I have debug'ed the dmp file, but need help analyzing it. Can someone point me to the right direction or tell me what's wrong with it. I'm using win xp. Intel P4 2.4 Ghz

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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.
An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates
that an unaligned data reference was encountered. The trap frame will
supply additional information.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: bf850a89, The address that the exception occurred at
Arg3: f72b8f34, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
win32k!PFEMEMOBJ::bInit+11c
bf850a89 0f85b8af0b00 jne win32k!PFEMEMOBJ::bInit+0x11e (bf90ba47)

TRAP_FRAME: f72b8f34 -- (.trap fffffffff72b8f34)
ErrCode = 00000000
eax=e17edac8 ebx=e17f4b98 ecx=e17f8530 edx=e17f86c3 esi=f72b9044 edi=e17f7348
eip=bf850a89 esp=f72b8fa8 ebp=f72b9004 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!PFEMEMOBJ::bInit+0x11c:
bf850a89 0f85b8af0b00 jne win32k!PFEMEMOBJ::bInit+0x11e (bf90ba47) [br=0]
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from bf84e36e to bf850a89

STACK_TEXT:
f72b9004 bf84e36e e17f4b98 00000001 00000000 win32k!PFEMEMOBJ::bInit+0x11c
f72b9048 bf81b62d 00000001 00000000 00000000 win32k!PFFMEMOBJ::bAddEntry+0x6a
f72b9088 bf823557 f72b91b0 00000001 00000000 win32k!PFFMEMOBJ::bLoadFontFileTable+0x7b
f72b90ec bf823832 f72b91b0 00000020 00000001 win32k!PUBLIC_PFTOBJ::bLoadFonts+0x27e
f72b9134 bf823780 f72b91b0 00000020 00000001 win32k!GreAddFontResourceWInternal+0xa9
f72b9274 8052d571 00078a58 00000020 00000001 win32k!NtGdiAddFontResourceW+0x132
f72b9274 7ffe0304 00078a58 00000020 00000001 nt!KiSystemService+0xc4
00c0fea8 7e097c5f 7e097b6b 00078a58 00000020 SharedUserData!SystemCallStub+0x4
00c0fee4 77d512c0 00c0ff8c 00000001 00000000 GDI32!NtGdiAddFontResourceW+0xc
00c0ff0c 77fb4da6 00c0ff1c 00000088 00000088 USER32!__ClientAddFontResourceW+0x3b
00c0ff3c 806133a7 00000000 003f78f8 e17eb6b0 ntdll!KiUserCallbackDispatcher+0x13
f72b9554 8057d4c1 f72b95e0 f72b95e4 00000000 nt!KiCallUserMode+0x4
f72b95b0 bf813d2e 0000004b f72b9664 00000088 nt!KeUserModeCallback+0x87
f72b987c bf813c7c f72b9890 00000001 00000000 win32k!xxxClientAddFontResourceW+0xc9
f72b9898 bf813db9 f72b9ac0 00000001 00000000 win32k!xxxAddFontResourceW+0x21
f72b9d28 bf813de4 00000001 0000002f 00c0ffb4 win32k!bEnumerateRegistryFonts+0x10a
f72b9d44 bf875da9 00000000 f72b9d64 00c0ffb4 win32k!xxxLW_LoadFonts+0x71
f72b9d54 8052d571 00000000 0000002f 51451425 win32k!NtUserCallOneParam+0x20
f72b9d54 7ffe0304 00000000 0000002f 51451425 nt!KiSystemService+0xc4
00c0ff0c 77fb4da6 00c0ff1c 00000088 00000088 SharedUserData!SystemCallStub+0x4
00c0ff3c 806133a7 00000000 003f78f8 e17eb6b0 ntdll!KiUserCallbackDispatcher+0x13
00c0ffec 00000000 0102a421 00000000 00000000 nt!CmpQueryKeyValueData+0x301


FAILED_INSTRUCTION_ADDRESS:
win32k!PFEMEMOBJ::bInit+11c
bf850a89 0f85b8af0b00 jne win32k!PFEMEMOBJ::bInit+0x11e (bf90ba47)

FOLLOWUP_IP:
win32k!PFEMEMOBJ::bInit+11c
bf850a89 0f85b8af0b00 jne win32k!PFEMEMOBJ::bInit+0x11e (bf90ba47)

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!PFEMEMOBJ::bInit+11c

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3f73195d

STACK_COMMAND: .trap fffffffff72b8f34 ; kb

BUCKET_ID: 0x8E_BAD_IP_win32k!PFEMEMOBJ::bInit+11c

Followup: MachineOwner

 

[linney]

What is the history behind this fault?

Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

http://msdn.microsoft.com/library/d..._12795dee-19a9-4461-a135-bbb882b81455.xml.asp

Random "0x0000008E" Error Message on a Blue Screen in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;827663&FR=1&PA=1&SD=HSCH

A "STOP: 0x0000008E" error message occurs when you change the hardware acceleration setting

http://support.microsoft.com/default.aspx?scid=kb;en-us;330187&FR=1&PA=1&SD=HSCH

 

[Prydonian]

Maunir;

Is your system fully patched? This particular Bugcheck was addressed in SP2.... Also, have you recently added new hardware or changed/updated/reloaded any drivers or applications?

If so, remove the hardware/drivers and use the system restore point from just before the hardware was added.

Mike, The IT Guy.




Life is too short to drink warm beer....