Hey guys, first post and the noob is already looking for help!
I've started having random reboots in XP SP2, that seem to occur more frequently as the day goes on. Just added a XFX card to a ECS motherboard, using the newest drivers for the card. Then updated the drivers for the mobo, and checked to make sure I've got the latest bios installed.
I've got me latest minidump report in .txt, would it be to forward of me to post it here?
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: 80000004, The exception code that was not handled
Arg2: 804db9ff, The address that the exception occurred at
Arg3: f6e089ec, Trap Frame
Arg4: 00000000
Thanks!
I've started having random reboots in XP SP2, that seem to occur more frequently as the day goes on. Just added a XFX card to a ECS motherboard, using the newest drivers for the card. Then updated the drivers for the mobo, and checked to make sure I've got the latest bios installed.
I've got me latest minidump report in .txt, would it be to forward of me to post it here?
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: 80000004, The exception code that was not handled
Arg2: 804db9ff, The address that the exception occurred at
Arg3: f6e089ec, Trap Frame
Arg4: 00000000
Thanks!
