Announcement

Collapse
No announcement yet.

W2k Server BlueScreen, ntoskrnlmp.exe

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • W2k Server BlueScreen, ntoskrnlmp.exe

    Goodday!

    I have a serious problem with a Windows 2000 Server, SP4. (HP/COMPAQ)

    All of a sudden, i cannot login anymore in the console, or via RDP without the machine giving me a Blue screen, and dumping Memory.dmp/minidmp. Without any update, installation of driver, of other change made.

    Spent some time, trying to disasble services, booting safe mode (w/wo networking), (even last-known good), changing memory, or other cards, cleaning processor, but nothing seems to help login on anymore. The server seems to be working, Exchange, Progress Db server, and fileserver functions al work fine.

    Minidmp saying probable couse is ntoskrnl.exe, which is quite general ofcourse, the memory.dmp file is saying: probably caused by : ntkrnlmp.exe ( nt!IoWMISuggestInstanceName+1b27f )

    Unfortuntately i cant seem tot get ALL the symbol files right, but most of them are loaded now, giving me this -v analyse.

    Does anyone have any clue of where to go from here, i actualy dont know it anymore...

    Thanx in advance,

    Robert

    Code:
    MODULE_NAME: nt
    
    FAULTING_MODULE: 80400000 nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  3ee650b3
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.
    
    FAULTING_IP: 
    nt!IoWMISuggestInstanceName+1b27f
    805214ed 8b04f8          mov     eax,dword ptr [eax+edi*8]
    
    EXCEPTION_PARAMETER1:  00000000
    
    EXCEPTION_PARAMETER2:  00000ff8
    
    READ_ADDRESS: unable to get nt!MmPoolCodeEnd
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPagedPoolEnd
    unable to get nt!MmNonPagedPoolEnd
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSpecialPoolStart
    unable to get nt!MmPagedPoolStart
    unable to get nt!MmNonPagedPoolExpansionStart
    unable to get nt!MmPoolCodeStart
     00000ff8 
    
    DEFAULT_BUCKET_ID:  WRONG_SYMBOLS
    
    BUGCHECK_STR:  0x1E
    
    LAST_CONTROL_TRANSFER:  from 80467215 to 8042f2fc
    
    STACK_TEXT:  
    bfd5f924 80467215 bfd5f940 00000000 bfd5f994 nt!KeTerminateThread+0xd0e
    bfd5fa0c 8051fab3 e1013e88 ffffffff e1013e88 nt!Kei386EoiHelper+0x47d
    bfd5fa24 80522c7e e1013e88 002a8350 e129f614 nt!IoWMISuggestInstanceName+0x19845
    bfd5fa68 8052287f e1013e88 00286610 e129f614 nt!IoWMISuggestInstanceName+0x1ca10
    bfd5fab4 805226cc e15fc000 00000400 00000002 nt!IoWMISuggestInstanceName+0x1c611
    bfd5fb60 804d89e6 0000070c bfd5fc10 000a001f nt!IoWMISuggestInstanceName+0x1c45e
    bfd5fc64 80415139 bfd5fd64 e1013e88 80512c01 nt!NtDuplicateObject+0x1264
    bfd5fd44 80466389 00000708 00000007 00000000 nt!ExReleaseResourceLite+0xbb
    bfd5fd68 00000000 00000000 00000000 00000000 nt!KiReleaseSpinLock+0xba9
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nt!IoWMISuggestInstanceName+1b27f
    805214ed 8b04f8          mov     eax,dword ptr [eax+edi*8]
    
    SYMBOL_NAME:  nt!IoWMISuggestInstanceName+1b27f
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    BUCKET_ID:  WRONG_SYMBOLS
    
    Followup: MachineOwner
    ---------
    Last edited by salorob; 17th January 2008, 11:13. Reason: mentioning updates/drivers/etc..

  • #2
    Re: W2k Server BlueScreen, ntoskrnlmp.exe

    I would be tempted to map a drive to the server's C: drive from a remote location and delete your profile folder... that's usually the first (and most effective) step for problems while logging in.


    Tom
    For my own and your protection, I do not provide support by private message under any circumstances. All such messages will be deleted and ignored.

    Anything you say will be misquoted and used against you

    Comment


    • #3
      Re: W2k Server BlueScreen, ntoskrnlmp.exe

      Yes indeed.. but i`ve already tried that too already... but it did not work.

      ...

      Comment

      Working...
      X