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.
Can you tell from the dump what hardware device is causing the stop errors ?
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:\Documents and Settings\dewing\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows Server 2003 Kernel Version 3790 MP (4 procs) Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_rtm.030324-2048
Kernel base = 0x804de000 PsLoadedModuleList = 0x8057b6a8
Debug session time: Thu Mar 3 02:55:04.257 2005 (GMT-5)
System Uptime: 4 days 19:33:07.016
Loading Kernel Symbols
........................................................................... ...............................
Loading unloaded module list
.....
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffdf00c). Type ".hh dbgerr001" for details
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck D1, {e000, ff, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
*** Possible invalid call from 80747715 ( hal!HalpIpiHandler+0xad )
*** Expected target 807484dc ( hal!HalEndSystemInterrupt+0x0 )
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000e000, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory
I'm not sure if the KB article bigjoe references is applicable to this dump. That hotfix is for a D1, but its an RDBSS/MRXSMB fix, which are not on the stack for this crash.
This particular crash is pretty far hosed up, and not one of the ones i can do just by lookin at it. I can tell you that it was in the middle of processing an interrupt when something referenced a bad location, which threw a page fault and a bugcheck. The interrupt is 1D, the IPI interrupt, so this certainly looks like the same thing we were talking about in those other threads. You should see if your CPU model and stepping match what ben referenced.
It would be interesting to see another dump to see if it also has a reference to an HalpIpiHandler crash. If it does, you should try that hotfix.