Announcement

Collapse
No announcement yet.

Windows 2008 BSOD and reboot

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

  • Windows 2008 BSOD and reboot

    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 Settings\users\Desktop\Mini110909-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\WINDOWS\Symbols
    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 = 0xfffff800`01815000 PsLoadedModuleList = 0xfffff800`019d9dd0
    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:
    fffffa60`04d8d9f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 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
    ---------

  • #2
    Re: Windows 2008 BSOD and reboot

    Everyone stumped?

    Comment


    • #3
      Re: Windows 2008 BSOD and reboot

      Sounds a lot like NX (no execute).

      Pehaps a recently installed drive ?

      You could try setting the NX bios option to off so you might be able to boot.
      This option however can have variable names.

      Just a hunch though. I would appreciate it if you could state what you have tried yourself already.
      Please give points where appropriate

      <I dont create ready scripts for you, but I'm willing to point you in the right direction>

      Comment


      • #4
        Re: Windows 2008 BSOD and reboot

        Originally posted by Silver23 View Post
        Sounds a lot like NX (no execute).

        Pehaps a recently installed drive ?

        You could try setting the NX bios option to off so you might be able to boot.
        This option however can have variable names.

        Just a hunch though. I would appreciate it if you could state what you have tried yourself already.

        I thought it was my RAID card driver but that wasn't the case since it reboot during the day again. Latest drivers.

        I thought it was the Exchange 2007 CPS that was causing the problem. Turned it off and it still reboot/BSOD.

        This system was running solid for months. Latest thing I did so far is some ran Windows Updates for security and software patches. I've notice that the info store sucks up all the ram so I created a task schedule that restart the services everyday to free up the ram, system has 16GB of ram.

        Comment


        • #5
          Re: Windows 2008 BSOD and reboot

          Is the problem resolved now ?

          You should try to provide more information, you never mentioned your system would still boot...
          That's considered important information.
          Please give points where appropriate

          <I dont create ready scripts for you, but I'm willing to point you in the right direction>

          Comment


          • #6
            Re: Windows 2008 BSOD and reboot

            Its definately a driver issue and it should tell you what the offending driver is when it blue screened.

            LEt us know what the blue screen said.

            Comment


            • #7
              Re: Windows 2008 BSOD and reboot

              Ran Windows Update had the latest and greatest installed so far no BSOD.

              Comment

              Working...
              X