Windows Server SystemPost your Windows Server System question here. Besides Windows Server 2003, Windows Server System also includes other Microsoft Server software (such as BizTalk Server, Exchange Server, ISA Server & others).
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
Windows 2003 Server Ent. Ed. repeatedly crashing for 5-10 hours every 20 days or so
We have an HP Proliant DL580 G2 as a DB server (Windows 2003 Enterprise Edition upgraded from Windows 2000 Ent. Ed., SLQ 2000). The server has mirrored memory (4GB) and has SAN connectivity for backend data storage utilizing dual HBA cards. We have seen an issue on three separate occasions where the server will give the BSOD and reboot constantly for 10 hours or so. Sometimes it stays up for 2 minutes sometimes for 48, but never longer than that. After about 10 hours the problem just goes away.
The issue seems to occur every 20 days or so, and seems to happen between 5pm and 8am. That may just be a coincidence. I have pulled both network cards and HBA cards (which are all of the PCI-connected boards on the box) and the issue seems to stick around. I have also consolidated the memory on a single memory riser board (thus negating the mirrored memory aspect of the server). None of these changes stopped the BSOD.
Below is the most recent dump file. Any insight on what may be going on would be helpful!
Opened log file 'c:\debuglog.txt'
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Temp\DB46_Dmp_Files\Mini032905-22.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINNT;C:\WINNT\system32;C:\WINNT\system32\drivers
Windows Server 2003 Kernel Version 3790 MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 3790.srv03_gdr.040410-1234
Kernel base = 0x804de000 PsLoadedModuleList = 0x8057b6a8
Debug session time: Tue Mar 29 06:09:13.065 2005 (GMT-6)
System Uptime: 0 days 0:01:20.812
Loading Kernel Symbols
........................................................................... ....................................
Loading unloaded module list
..
Loading User Symbols
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck A, {98c, ff, 0, 804e61d0}
Probably caused by : ntkrnlmp.exe ( nt!KiIdleLoop+10 )
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000098c, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804e61d0, address which referenced memory
Thats an unusual set of behavior. I'll have to wait until tomorrow when i can unassemble that wait loop to see what its trying to read thats not there...
I'll let you know tomorrow probably. There is a chance that this one will have to go to microsoft support to be debugged, depending on how my unassemble goes.
![BenMcDonald[MS]'s Avatar](http://www.WindowsBBS.com/avatars/benmcdonald-ms-.gif?dateline=1103157319)
