Solved

Windows 2008R2 Unexpected Shutdowns

Posted on 2010-11-29
4
2,687 Views
Last Modified: 2012-05-10
I am having an issue with a brand new server that has started randomly rebooting 3 - 4 times per day.  In the event viewer the following message is given each time:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa800adba028, 0x00000000be000000, 0x000000000001009f). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111710-37986-01

Below is the contents of the memory.dmp file.

I have checked to make sure I have all the firmware and driver updates.  The server ran fine for about a week and the only changes that were made just prior to this (2 days before random reboots started) were the insertion of an LSI 2000 Series PCI-E Ultra320 SCSI controller and a Quantum LTO4 Tape drive and installation of MAS-90 Accounting Software version 4.4.  These reboots do not occur during the backup but typically during the day when the server is being used.



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


Loading Dump File [C:\Windows\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+                                    *
*********************************************************************
Unable to read KLDR_DATA_TABLE_ENTRY at 000001b9`d78b0000 - NTSTATUS 0xC0000147

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000`00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 7 Kernel Version 7600 (Service Pack 16.35656) MP (16 procs) Free x64
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0164f000 PsLoadedModuleList = 0xfffff800`0188ce50
Debug session time: Thu Nov 25 06:42:26.404 2010 (UTC - 5:00)
System Uptime: 0 days 13:42:12.750
*********************************************************************
* 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 read KLDR_DATA_TABLE_ENTRY at 000001b9`d78b0000 - NTSTATUS 0xC0000147

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000`00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
Unable to read KLDR_DATA_TABLE_ENTRY at 000001b9`d78b0000 - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete
GetContextState failed, 0xD0000141
CS descriptor lookup failed
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get program counter
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800ae34028, be000000, 1009f}

GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
Page 17c76a0 too large to be in the dump file.
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Page 17c76a0 too large to be in the dump file.
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
Unable to get current machine context, NTSTATUS 0xC0000141
GetContextState failed, 0xD0000141
GetContextState failed, 0xD0000141
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0
Comment
Question by:Cybertronnh
  • 2
4 Comments
 
LVL 3

Expert Comment

by:ggupta7
ID: 34233322
0
 
LVL 1

Expert Comment

by:HHTech1
ID: 34238686
It looks like you have an issue with the debugging tool and the symbols. No worries...

With new servers running memory intensive applications most of the time it is a faulty or corrupt driver, bad RAM memory, or a bad sector on a hard drive.

Easiest solution is to do the following 3 suggestions in order.
1. Run a memory test for the ram, or just replace all sticks. This needs to be done before the following steps.
2. Run 'sfc /scannow' from a command prompt. This will repair any drivers that may be corrupt or faulty within the windows directory.
3. Lastly run 'chkdsk c: /f/r'  from the command prompt. Run this on all partitions by replacing the 'c' with the other partions. This may take some time for each drive depending on the size, but a nessecary task to find and repair any bad sectors. You can safely answer yes to dismount the drive on all drives except the one where windows is installed. For this one you will have to schedule it to run the chkdsk on reboot, just follow the prompts after you execute the command on the windows partition.

0
 

Accepted Solution

by:
Cybertronnh earned 0 total points
ID: 34346073
The problem was the LSI SCSI card that I had inserted just prior to these shutdowns.  I replaced the card with an Adaptec PCI Express SCSI Ultra 320 card the server has run flawlessly since.
0
 

Author Closing Comment

by:Cybertronnh
ID: 34387561
This matter is resolved.
0

Featured Post

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Join & Write a Comment

this article is a guided solution for most of the common server issues in server hardware tasks we are facing in our routine job works. the topics in the following article covered are, 1) dell hardware raidlevel (Perc) 2) adding HDD 3) how t…
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now