none
BSOD - Error code 1000008e, parameter1 c0000005, parameter2 f723cce2, parameter3 b8e67524, parameter4 00000000

    Question

  • Hello Experts ,

     We are continuosly getting above BSOD , on one of our Windows server 2003 . This server is getting randomly rebooted exactly at 1:35 AM in the morning. I have checked anyof the servcies or scheduled task for this time.  I did not find anything. I have checked the event logs as well at this time , Did not find anything there as well.,

    This is the VM , we are hosting the payroll on this system.

    I just want to know what is the problem here? I did check for McAfee antivirus, and it seems to be ok on this ,

    Dont know how to proceed to tackle this and not sure why this is getting rebooted at 1:35 AM Randomely?

    There are Memory Dumb and Minidumb files on the server. But unfortunately I am getting only below Bug Details in them ,

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


    Loading Dump File [C:\temp\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is 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+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlpa.exe -
    Windows Server 2003 Kernel Version 3790 (Service Pack 2) UP Free x86 compatible
    Product: Server, suite: TerminalServer SingleUserTS
    Built by: 3790.srv03_sp2_gdr.120503-0334
    Machine Name:
    Kernel base = 0x80800000 PsLoadedModuleList = 0x8089ffa8
    Debug session time: Sun Nov  4 01:31:07.857 2012 (UTC + 5:30)
    System Uptime: 2 days 23:57:49.546
    *********************************************************************
    * 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+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlpa.exe -
    Loading Kernel Symbols
    ...............................................................
    .................................................
    Loading User Symbols

    Loading unloaded module list
    ...
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 8E, {c0000005, f723cce2, b8e67524, 0}

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

    *** ERROR: Module load completed but symbols could not be loaded for fltMgr.sys
    *** ERROR: Module load completed but symbols could not be loaded for vsepflt.sys
    *** ERROR: Module load completed but symbols could not be loaded for volsnap.sys
    *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for mfehidk.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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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 : vsepflt.sys ( vsepflt+f744 )


    Any help is much appriciated.

    Thanks,

    _Prashant_


    MCSA|MCITP SA|Microsoft Exchange 2003 Blog - http://prashant1987.wordpress.com Disclaimer: This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Tuesday, November 06, 2012 6:52 AM

Answers

All replies

  • Hello Prashant, 

    With your data I am unable to figure out the exact Root cause for BSOD.

    Anyway we have a good link and which have all the info about various Bug check codes.So I suggest you check below link, hope it will help you in troubleshooting somehow.

    Bug Check 0x1000008E:http://msdn.microsoft.com/en-us/library/windows/hardware/ff557203(v=vs.85).aspx

    Thank you for understanding. Please share us dump file thorough sky drive, If possible?


    Regards, Ravikumar P

    Tuesday, November 06, 2012 8:21 AM
  • I Anaylsed the Dump file and found below information

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2003 Kernel Version 3790 (Service Pack 2) UP Free x86 compatible
    Product: Server, suite: TerminalServer SingleUserTS
    Built by: 3790.srv03_sp2_gdr.120503-0334
    Machine Name:
    Kernel base = 0x80800000 PsLoadedModuleList = 0x8089ffa8
    Debug session time: Sun Nov  4 01:31:07.857 2012 (UTC + 5:30)
    System Uptime: 2 days 23:57:49.546
    Loading Kernel Symbols
    ...............................................................
    .................................................
    Loading User Symbols
    Loading unloaded module list
    ...
    Unable to load image vsepflt.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for vsepflt.sys
    *** ERROR: Module load completed but symbols could not be loaded for vsepflt.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, f723cce2, b8e67524, 0}

    Unable to load image mfehidk.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for mfehidk.sys
    *** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
    Probably caused by : vsepflt.sys ( vsepflt+f744 )

    Now If see the caused by this is showing the VMWare driver (Probalby Network Driver) , Anyone knows about how to resolve this ?

    Do I need to update this ? If yes then How?

    Thanks,

    _Prashant_


    MCSA|MCITP SA|Microsoft Exchange 2003 Blog - http://prashant1987.wordpress.com Disclaimer: This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Wednesday, November 07, 2012 6:00 AM
  • Hi Prashant ,

    I found that they have suggested for update pf VM tools in your Vm.

    you can try that and revert back.


    Windows Server System Administrator

    Thursday, January 03, 2013 1:47 PM