TechSpot

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)  BSOD

?

Is it a RAM issue ?

  1. YES

    0 vote(s)
    0.0%
  2. NO

    0 vote(s)
    0.0%
  3. DON'T KNOW

    100.0%
By avinashsuratkal
Jun 18, 2008
  1. Hi,

    I have assembled the new computer with below config

    AMD Phenom 2.2GHz
    2GB DDR2 RAM

    320GB Seagate IDE HDD
    DVD Writer IDE HDD

    I have Windows XP sp2 installed in my computer.
    Video card installed is 8400GS Super --- Nvidia Gforce 512 MB

    CPU heat shows 54 degree celcius, is that ok ?

    Both connected via same IDE cable (primary and secondary)

    Problem is it sometimes gives me a "blue screen of death" and reboots.

    I did a analysis of minidump and found following logs
    ++++++
    Opened log file 'c:\debuglog.txt'

    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini061708-03.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
    Windows XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Tue Jun 17 21:15:26.375 2008 (GMT+6)
    System Uptime: 0 days 0:24:47.385
    Loading Kernel Symbols
    ..........................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, bac8448f, b480a938, 0}

    Unable to load image sptd.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sptd.sys
    *** ERROR: Module load completed but symbols could not be loaded for sptd.sys
    Probably caused by : Npfs.SYS ( Npfs!NpFindPrefix+5 )

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

    2: kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * 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: bac8448f, The address that the exception occurred at
    Arg3: b480a938, Trap Frame
    Arg4: 00000000

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


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

    FAULTING_IP:
    Npfs!NpFindPrefix+5
    bac8448f 0fb6450c movzx eax,byte ptr [ebp+0Ch]

    TRAP_FRAME: b480a938 -- (.trap 0xffffffffb480a938)
    .trap 0xffffffffb480a938
    ErrCode = 00000002
    eax=b480a9dc ebx=88a94850 ecx=0000cc28 edx=00000043 esi=88903958 edi=889039c8
    eip=bac8448f esp=b480a9ac ebp=b480a9ac iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    Npfs!NpFindPrefix+0x5:
    bac8448f 0fb6450c movzx eax,byte ptr [ebp+0Ch] ss:0010:b480a9b8=01
    .trap
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 3

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: AiNap.exe

    LAST_CONTROL_TRANSFER: from bac8161e to bac8448f

    STACK_TEXT:
    b480a9ac bac8161e b480a9dc 00000001 b480a9cc Npfs!NpFindPrefix+0x5
    b480aa14 bac816ff 89b3fe78 88903958 889039c8 Npfs!NpCommonCreate+0x14e
    b480aa28 ba6e81f6 89b3fe78 88903958 88903968 Npfs!NpFsdCreate+0x17
    WARNING: Stack unwind information not available. Following frames may be wrong.
    b480aa58 804eeeb1 89bcc378 89b3fe78 88903958 sptd+0x141f6


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    Npfs!NpFindPrefix+5
    bac8448f 0fb6450c movzx eax,byte ptr [ebp+0Ch]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: Npfs!NpFindPrefix+5

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Npfs

    IMAGE_NAME: Npfs.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107b86

    FAILURE_BUCKET_ID: 0x8E_Npfs!NpFindPrefix+5

    BUCKET_ID: 0x8E_Npfs!NpFindPrefix+5

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

    eax=b480a9dc ebx=88a94850 ecx=0000cc28 edx=00000043 esi=88903958 edi=889039c8
    eip=bac8448f esp=b480a9ac ebp=b480a9ac iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    Npfs!NpFindPrefix+0x5:
    bac8448f 0fb6450c movzx eax,byte ptr [ebp+0Ch] ss:0010:b480a9b8=01
    ChildEBP RetAddr Args to Child
    b480a9ac bac8161e b480a9dc 00000001 b480a9cc Npfs!NpFindPrefix+0x5 (FPO: [Non-Fpo])
    (4315174A)
    Unloaded modules:
    b478d000 b47b8000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    baeff000 baf00000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b4938000 b4945000 DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b4948000 b4956000 swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    bac58000 bac5f000 Fdc.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt
    ++++++

    I also did memtest via memtest86 and attached is the output.

    Could someone please confirm me that it is RAM issue.

    - Avinash
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...