STOP rrrors

[Ayman Altounji]

I receive the following Stop error on my NT server randomly, does anyone know what it refers to.
STOP: 0x0000000A (0x00000034, 0x00000002, 0x00000001,
0x80003D3A)

[Ayman Altounji]

This doesn't help with your problem Tim, but we've recently had this problem as well. It was Attached to Event ID 4188 generated by Compaq System Management Driver.

[Ayman Altounji]

With this little information, all I can tell you is this.
It can be caused by a buggy device driver, a bios problem, a system service, a backup utility, a virus scanner.

You have received a trap messsage.
All that means is
0x00000034 was the memory referenced
2 was the IRQ referenced at the time of reference
1 - it was a write
0x80003D3A - address which referenced memory.

Other than that there is no way to know unless a dump is provided or a live-debug is done.

You can than execute stack traces to determine root cause.
Its not easy but its the only way.

mark-

[Ayman Altounji]

Don't forget the default recommendations to upgrade everything (drivers, bios,) before investing a lot of time taking the software apart. It may save time in the long run

[Ayman Altounji]

Estoy interesado en conocer la soluci?n a este problema, pues tengo un servidor Proliant 7000 que se ha reiniciado por si mismo y ha presentado este evento 4188:
BLUE SCREN TRAP (NT BugCheck Data = STOP: 0x00000050 (0xA1DBA4D4, 0x00000001, 0x00000000, 0x00000002))