BSOD:MS-9249 1U Server

Question

I'm experiencing random BSOD with this server.  I did not write down the last BSOD message, but I believe it was the IRQ_NOT_LESS_OR_EQUAL
It failed twice on me yesterday, but I couldn't get the info because when I switched the monitor over to the box through my KVM there was no video output.
When it fails it fails hard.  System does not reboot even though Win2K is setup to reboot.  No failed events are in the logs.
Ran memtest for 9 hours.  No problems reported.  Right now I'm running Prime95.
No BIOS update exists for this box according to MSI's LiveUpdate.
This is a server box so it has a minimal amount of additional software on it -- MySQL, Sygate Firewall, BlackIce Defender, IIS v5 are the major services running.
The only thing "odd" is that I share this USB mouse with another system (unplugging when needed) so I was wondering if maybe a USB driver issue.
Code: [Select]
 MSI: MS-9249 1U Rackmount Server
 BIOS: W9249MS V1.0 030204
   OS: Windows 2000 Workstation SP4
  CPU: Intel P4 2.8GHz  HT enabled
  RAM: 2x512 Crucial CT6472Z40B (Slots A0 & A2)
       DDR PC3200 CL=3 Unbuffered ECC DDR400 2.6V 64Meg x 72
       RAM BIOS Setting: 3 8 3 3
   HD: Hitachi SATA
  PCI: empty
VIDEO: On-board ATI Rage XL PCI
  PSU: MSI OEM
  DRAM Timing: By SPD
Latest LiveUpdate: 10/09/2004 (No BIOS update, updated Intel INF and LAN)
Memtest86: No errors.  Standard Test. 52 Passes. 9.3 hours
No BIOS settings to change RAM voltage

Answer 1

Well the pig BSOD'ed on me again today.
Code: [Select]
Use !analyze -v to get detailed debugging information.
BugCheck A, {bc6558, 2, 0, 80437d8c}
Probably caused by : memory_corruption ( nt!MiRemovePteTracker+72 )
Followup: MachineOwner
1: kd> !analyze -v
*                        Bugcheck Analysis                                    *
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: 00bc6558, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 80437d8c, address which referenced memory
Debugging Details:
READ_ADDRESS:  00bc6558 Paged pool
CURRENT_IRQL:  2
FAULTING_IP:
nt!MiRemovePteTracker+72
80437d8c 8a11             mov     dl,[ecx]
DEFAULT_BUCKET_ID:  DRIVER_FAULT
BUGCHECK_STR:  0xA
LAST_CONTROL_TRANSFER:  from 5345534a to 80469d1c
STACK_TEXT:  
ec423780 5345534a 4e4f4953 373d4449 39434541 nt!KiTrap13
WARNING: Frame IP not in any known module. Following frames may be wrong.
203b4333 00000000 00000000 00000000 00000000 0x5345534a
STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP:
nt!MiRemovePteTracker+72
80437d8c 8a11             mov     dl,[ecx]
FOLLOWUP_NAME:  MachineOwner
SYMBOL_NAME:  nt!MiRemovePteTracker+72
MODULE_NAME:  nt
DEBUG_FLR_IMAGE_TIMESTAMP:  40d1d19a
IMAGE_NAME:  memory_corruption
BUCKET_ID:  0xA_nt!MiRemovePteTracker+72
Followup: MachineOwner