BSOD ntkrnlmp.exe ??? HELP!

Page 1 of 2 12 LastLast

  1. Posts : 10
    Windows 7
       #1

    BSOD ntkrnlmp.exe ??? HELP!


    Hello all, first time poster. I tried using the search method but didn't find any solutions to my problem. I was a long time Vista user with no BSOD issues, since buying the HP DV4-2040US (Win7 64) in October my machine has crashed almost two dozen times, no exaggeration. Each time WinDbg shows the same culprit, ntkrnlmp.exe. From what I understand this is a major OS component and could actually be pointing towards other issues. Here's my latest mini dump (I'm new to this):


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


    Loading Dump File [C:\Windows\Minidump\112809-18376-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*f:\localsymbols*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`02e54000 PsLoadedModuleList = 0xfffff800`03091e50
    Debug session time: Sat Nov 28 16:27:44.880 2009 (GMT-5)
    System Uptime: 0 days 0:08:15.955
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1E, {ffffffffc0000005, fffff80002e388fe, 1, 90000000}

    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+460da )

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

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

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002e388fe, The address that the exception occurred at
    Arg3: 0000000000000001, Parameter 0 of the exception
    Arg4: 0000000090000000, Parameter 1 of the exception

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


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

    FAULTING_IP:
    hal!HalpHardwareLockFlags <PERF> (hal+0x2d8fe)+0
    fffff800`02e388fe 0100 add dword ptr [rax],eax

    EXCEPTION_PARAMETER1: 0000000000000001

    EXCEPTION_PARAMETER2: 0000000090000000

    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fc0e0
    0000000090000000

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x1E

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    TRAP_FRAME: fffff8800371bac0 -- (.trap 0xfffff8800371bac0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000090000000 rbx=0000000000000000 rcx=fffff80002e2fb50
    rdx=fffffa8004aba2b8 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002e388fe rsp=fffff8800371bc58 rbp=0000000000000000
    r8=0000000000000000 r9=000000001f0a8b3d r10=0000000000005107
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up di ng nz na po nc
    hal!HalpHardwareLockFlags <PERF> (hal+0x2d8fe):
    fffff800`02e388fe 0100 add dword ptr [rax],eax ds:8002:00000000`90000000=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80002f05a17 to fffff80002ec5f00

    STACK_TEXT:
    fffff880`0371b238 fffff800`02f05a17 : 00000000`0000001e ffffffff`c0000005 fffff800`02e388fe 00000000`00000001 : nt!KeBugCheckEx
    fffff880`0371b240 fffff800`02ec5542 : fffff880`0371ba18 00000000`00000000 fffff880`0371bac0 fffff880`009e8180 : nt! ?? ::FNODOBFM::`string'+0x460da
    fffff880`0371b8e0 fffff800`02ec40ba : 00000000`00000001 00000000`00000000 fffffa80`0445a100 fffffa80`0445a050 : nt!KiExceptionDispatch+0xc2
    fffff880`0371bac0 fffff800`02e388fe : fffff800`02f115ac fffffa80`04aae670 fffff880`0436b7f2 00000000`00000010 : nt!KiPageFault+0x23a
    fffff880`0371bc58 fffff800`02f115ac : fffffa80`04aae670 fffff880`0436b7f2 00000000`00000010 00000000`00000246 : hal!HalpHardwareLockFlags <PERF> (hal+0x2d8fe)
    fffff880`0371bc60 fffffa80`04aae670 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x1c
    00000000`00000246 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`04aae670


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+460da
    fffff800`02f05a17 cc int 3

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+460da

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

    FAILURE_BUCKET_ID: X64_0x1E_nt!_??_::FNODOBFM::_string_+460da

    BUCKET_ID: X64_0x1E_nt!_??_::FNODOBFM::_string_+460da

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

    I called HP, they want me to do a system restore (this seems to be the cure of everything) or send my PC in for service (I've only had this thing 6 weeks). I was hoping someone here could lend a helping hand. Sorry for the really long post. I'm really lost and completely frustrated with Windows 7.
      My Computer


  2. Posts : 93
    Win 7 Ultimate x64
       #2

    Here's a start: 0xc0000005 - Microsoft Search

    More: ntkrnlmp.exe - Microsoft Search

    This could be a virus, download and run AdAware and SpyBot.
      My Computer


  3. Posts : 10
    Windows 7
    Thread Starter
       #3

    Virus, really? I'll run spybot S&D and AVG. I'll report back if the software finds anything.
      My Computer


  4. Posts : 10
    Windows 7
    Thread Starter
       #4

    No threats were found, Sbybot found some "doubleclick" spyware but virus scan came back clean. Any other ideas?
      My Computer


  5. Posts : 93
    Win 7 Ultimate x64
       #5

    Well, when I read thru the potential issues, vid drivers occurred often. Correct and latest vid drivers installed? Need BIOS update to handle Win 7? Latest mobo drivers?
      My Computer


  6. Posts : 10
    Windows 7
    Thread Starter
       #6

    When I called HP they had me update the Bios and I've downloaded all the latest drivers. This is mind boggling. Am I missing something in the minidump above, is there something in the "stack" that you can see as a possible culprit? Thanks again for the help.
      My Computer


  7. Posts : 5,747
    7600.20510 x86
       #7

    Hi. Please follow this link and also completely uninstall AVG. It is the worst app on the net causing bsod, by far.

    https://www.sevenforums.com/crash-loc...d-problem.html
      My Computer


  8. Posts : 10
    Windows 7
    Thread Starter
       #8

    I followed those rules with the exception of the zip copy. I thought it would be easier if I just posted it instead.

    BTW, I've now uninstalled AVG.

    Mini dump now attached via zip.
      My Computer


  9. Posts : 93
    Win 7 Ultimate x64
       #9

    Do you have the Win 7 install disk? You can you do a Repair from the Recovery Console on that disk. A Repair just reloads the Win 7 DLLs usually leaving your other installed apps alone, but it makes no guarantees.
      My Computer


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

    lrstevens421 said:
    I followed those rules with the exception of the zip copy. I thought it would be easier if I just posted it instead.

    BTW, I've now uninstalled AVG.

    Mini dump now attached via zip.
    Hi and welcome. waht we really need is the original DMP file not the text output. we cant munge the text file

    Sorry

    Kenn J+
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
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 19:05.
Find Us