Windows 2008 BSOD and reboot

Home Forums Server Operating Systems Windows Server 2008 / 2008 R2 Windows 2008 BSOD and reboot

Viewing 1 post (of 1 total)
  • Author
    Posts
  • Avatar
    nhbilly
    Member
    #145733

    I have a mini-dump of the problem but still can’t figure it out.
    This system has been running fine since June and all of a sudden this happens.

    Thanks in advance.

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

    Loading Dump File [C:Documents and SettingsusersDesktopMini110909-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:WINDOWSSymbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
    Product: Server, suite: Enterprise TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff80001815000 PsLoadedModuleList = 0xfffff800019d9dd0
    Debug session time: Mon Nov 9 21:02:34.824 2009 (GMT-6)
    System Uptime: 2 days 0:16:19.390
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    ………………………………………………………
    …………………………………………………….
    Loading User Symbols
    Loading unloaded module list
    …….
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck FC, {fffff8800644cb30, ee300000b9acd963, fffffa6004d8dae0, 2}

    Probably caused by : ntoskrnl.exe ( nt!IopLockMountedDeviceForRemove+17 )

    Followup: MachineOwner


    Here is the other part:

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
    An attempt was made to execute non-executable memory. The guilty driver
    is on the stack trace (and is typically the current instruction pointer).
    When possible, the guilty driver’s name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    Arguments:
    Arg1: fffff8800644cb30, Virtual address for the attempted execute.
    Arg2: ee300000b9acd963, PTE contents.
    Arg3: fffffa6004d8dae0, (reserved)
    Arg4: 0000000000000002, (reserved)

    Debugging Details:


    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

    BUGCHECK_STR: 0xFC

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8000186f450

    STACK_TEXT:
    fffffa6004d8d9f8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!IopLockMountedDeviceForRemove+0x17

    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!IopLockMountedDeviceForRemove+17
    fffff800`0186f450 48894c2408 mov qword ptr [rsp+8],rcx

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!IopLockMountedDeviceForRemove+17

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntoskrnl.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 49e0237f

    FAILURE_BUCKET_ID: X64_0xFC_nt!IopLockMountedDeviceForRemove+17

    BUCKET_ID: X64_0xFC_nt!IopLockMountedDeviceForRemove+17

    Followup: MachineOwner


Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.