Kmode_exception_not_not_handled


  1. Posts : 14
    Windows 7 64bit
       #1

    Kmode_exception_not_not_handled


    This forum has been a great resource this week! I think I am almost fixed, but...
    once more to the well.

    The system had been running well tonight with no crashes until now. It had been in sleep mode (like me) and suddenly rebooted 3 times with an error.

    NTFS_FILE_SYSTEM
    KMODE_EXCEPTION_NOT_HANDLED
    IRQL_NOT_LESS_OR_EQUAL

    Could someone decipher these dump files please?
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    JerryS said:
    This forum has been a great resource this week! I think I am almost fixed, but...
    once more to the well.

    The system had been running well tonight with no crashes until now. It had been in sleep mode (like me) and suddenly rebooted 3 times with an error.

    NTFS_FILE_SYSTEM
    KMODE_EXCEPTION_NOT_HANDLED
    IRQL_NOT_LESS_OR_EQUAL

    Could someone decipher these dump files please?
    Hi and welcome

    I took a quick look at 2 of the three the dmp's. they were caused by memory corruption.

    I would
    download memtestx86 and run in for several hours (preferably overnight).
    run system file check
    type cmd in search>right click and run as admin>sfc /scannow
    let us know the results
    also if you are overclocking stop
    if you have a raid update its driver.



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


    Loading Dump File [C:\Users\K\Desktop\112509-22791-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*d:\symbols*Symbol information
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e45e50
    Debug session time: Wed Nov 25 02:12:17.335 2009 (GMT-5)
    System Uptime: 0 days 2:43:23.207
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {fffffa0003aeb518, 2, 1, fffff80002d2aabf}

    Probably caused by : memory_corruption
    ( nt!MiIdentifyPfn+26f )

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

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

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffffa0003aeb518, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002d2aabf, address which referenced memory

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


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb00e0
    fffffa0003aeb518

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!MiIdentifyPfn+26f
    fffff800`02d2aabf f0410fba6e481f lock bts dword ptr [r14+48h],1Fh

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: svchost.exe

    TRAP_FRAME: fffff880049714f0 -- (.trap 0xfffff880049714f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=0e00000000000020
    rdx=000000000007fde4 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002d2aabf rsp=fffff88004971680 rbp=fffffa8003aeb668
    r8=0000000000094548 r9=0000000000000001 r10=0000000000000042
    r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na pe nc
    nt!MiIdentifyPfn+0x26f:
    fffff800`02d2aabf f0410fba6e481f lock bts dword ptr [r14+48h],1Fh ds:00000000`00000048=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80002c79469 to fffff80002c79f00

    STACK_TEXT:
    fffff880`049713a8 fffff800`02c79469 : 00000000`0000000a fffffa00`03aeb518 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`049713b0 fffff800`02c780e0 : 00000000`42506650 02000000`0008156f 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`049714f0 fffff800`02d2aabf : 00000000`00000000 02000000`00053b02 00000000`000018c0 fffff800`02f3ec8f : nt!KiPageFault+0x260
    fffff880`04971680 fffff800`02d2b76b : 00000000`00000000 00000000`00000004 fffffa80`08748ce8 fffffa80`08748000 : nt!MiIdentifyPfn+0x26f
    fffff880`04971720 fffff800`0308b0f5 : fffffa80`08748000 fffff880`04971ca0 fffff880`049717f8 00000000`00000000 : nt!MmQueryPfnList+0xbb
    fffff880`04971760 fffff800`02fcff78 : 00000000`00000006 00000000`00000000 fffffa80`08748000 fffff800`02c08001 : nt!PfpPfnPrioRequest+0x115
    fffff880`049717b0 fffff800`02f74cb3 : 00000000`00000000 fffff800`02c08000 00000000`00000000 fffff880`04971801 : nt! ?? ::NNGAKEGL::`string'+0x4853d
    fffff880`04971840 fffff800`02f75e49 : 00000000`017fb9e8 fffff880`011a36e4 00000000`017fba40 00000000`0817f1e0 : nt!ExpQuerySystemInformation+0x11c2
    fffff880`04971be0 fffff800`02c79153 : 00000000`0200db50 00000000`0200db01 fffff880`04971ca0 fffffa80`039b5d80 : nt!NtQuerySystemInformation+0x4d
    fffff880`04971c20 00000000`778e021a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`017fb918 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778e021a


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiIdentifyPfn+26f
    fffff800`02d2aabf f0410fba6e481f lock bts dword ptr [r14+48h],1Fh

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: nt!MiIdentifyPfn+26f

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+26f

    BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+26f

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

    Hope this helps point you in the right direction

    Ken J++
      My Computer


  3. Posts : 14
    Windows 7 64bit
    Thread Starter
       #3

    Thanks ZigZag,

    Early results so far...sfc /scannow came back clean...memtest86+ indicated a memory problem. A little digging on this and a few other forums led to adjust my MCH voltage up a touch. I had already adjusted memory timing and vDimm voltage per manufacture specs. SO far tonight no crashes. Even the event viewer has slowed down recording events. I will re-run memtest tonight to see if it is truly fixed.

    I will post results tomorrow.

    This had been a great forum! You guys rock!
      My Computer


  4. Posts : 14
    Windows 7 64bit
    Thread Starter
       #4

    Memtest came back with multiple errors. I suspect the memory was damaged when it was installed in a bad MB I had purchased. The MB has been replaced. I will get the memory replaced now as well. System actually running very stable. I had 1 BSOD last night that was attributed to Wdf01000.sys. Fisrt one in almost 24 hrs.

    It's closer...
      My Computer


  5. Posts : 14
    Windows 7 64bit
    Thread Starter
       #5

    System appears to be stable. I exchanged the RAM for new (actually added another 4GB for a total of 8) and tuned vDimm and MCH voltage. No BSOD for 3 days. The event logger has actually slowed down as well. Have played COD MW2 for hours. I did get a couple of video related errors/freezes and updated to the newest NVIDIA drivers.

    For reference - vDimm set to 2.08 and MCH set to 1.24.

    Great forum, great help! Thanks!
      My Computer


 

Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:20.
Find Us