TechSpot

BSOD: npfs.sys

By Smarthy
Nov 27, 2008
  1. Microsoft (R) Windows Debugger Version 6.6.0007.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [\\10.70.0.16\c$\WINDOWS\Minidump\Mini112508-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
    Product: Server, suite: TerminalServer
    Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
    Debug session time: Tue Nov 25 00:05:06.317 2008 (GMT+1)
    System Uptime: 0 days 14:58:12.929
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    .....................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 4E, {9a, 8892, 6, 2}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *** WARNING: Unable to verify timestamp for Npfs.SYS
    *** ERROR: Module load completed but symbols could not be loaded for Npfs.SYS
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    Probably caused by : Npfs.SYS ( Npfs+4e07 )

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

    What to do?
     
  2. kimsland

    kimsland Ex-TechSpotter Posts: 14,524

    Please update all your drivers
     
  3. Smarthy

    Smarthy TS Rookie Topic Starter

    is there a way to see which driver is outdated? because as far as I know all the drivers are updated.
    Or is there any clue of whick driver is outdated?
     
  4. Smarthy

    Smarthy TS Rookie Topic Starter

    Ok I've looked futher into this.
    And found the possible problem and that the:
    Intel 82801EB LPC Interface controller 24D0

    Where can I find a good update driver for this product?
     
  5. kimsland

    kimsland Ex-TechSpotter Posts: 14,524

    Please put your System Specs information in your Profile

    If you have a brand name computer (like Dell; HP; or other) please place the Computer name & Model number in your Mobo field of your Profile
     
  6. Smarthy

    Smarthy TS Rookie Topic Starter

    The computer is part of a domain so everest won't work.

    I found this on a website:
    Hardware
    Type Description
    DVD/CD-ROM Drives DELL VCD SCSI CdRom Device
    PHILIPS DVD-ROM SDR089
    Disk Drives DELL VSF SCSI Disk Device
    PERC LD 0 PERCRAID SCSI Disk Device 33.86Gb
    Display Adapters RADEON 7000 SERIES 16Mb
    Floppy Disk Drives (Standard floppy disk drives) Floppy disk drive
    IDE ATA/ATAPI Controllers Intel(R) 82801EB Ultra ATA Storage Controllers
    Primary IDE Channel
    Secondary IDE Channel
    Keyboards USB Human Interface Device
    Mice and Other Pointing Devices USB Human Interface Device
    Monitors Plug and Play Monitor - (Standard monitor types)
    USB Controllers Intel(R) 82801EB USB Universal Host Controller - 24D2
    Intel(R) 82801EB USB Universal Host Controller - 24D4
    Intel(R) 82801EB USB Universal Host Controller - 24D7
    Intel(R) 82801EB USB2 Enhanced Host Controller - 24DD
     
  7. kimsland

    kimsland Ex-TechSpotter Posts: 14,524

  8. Smarthy

    Smarthy TS Rookie Topic Starter

    Your correct!
    It's a DELL poweredge 1850

    I haven't filled in my profile specs, because I have multiple computers :p

    Anyway, I've checked every single driver, used some programs for it. And every driver is up-to-date and signed by microsoft.
    I'm thinking more of a hardware failure lately.
    We've been monitoring this server very secure lately, and there is never a simulair situation for the server to crash, only thing that's allways the same is that people are loggin out at the moment the server crashes.
     
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...