Bluescreen ohne Fehlermeldung bei Win XP - Minidump Infos unklar

Hallo Zusammen,

ich habe einen Win XP PC der in letzter Zeit (heute allein 5 mal) immer häufiger mit einem Bluescreen abstürzt.

Auf dem Screen selbst steht kein Hinweis, auch in der Ereignisanzeige nicht und aus dem Mini Dump werde ich nicht schlau. Kann jemand von euch mir einen Hinweis geben?

Vielen Dank schon mal,
Freddy


Inhalt des Dumps:

• *
• Bugcheck Analysis *
• *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 0, b29dbc08, 0}

Probably caused by : hardware

Followup: MachineOwner
*** Possible invalid call from 805805cc ( nt!IopXxxControlFile+0x374 )
*** Expected target 804ef0a0 ( nt!IoAllocateIrp+0x0 )

1: kd> !analyze -v

• *
• Bugcheck Analysis *
• *

*******************************************************************************

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: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: b29dbc08, Trap Frame
Arg4: 00000000

Debugging Details:


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

FAULTING_IP:
+0
00000000 ?? ???

TRAP_FRAME: b29dbc08 -- (.trap ffffffffb29dbc08)
ErrCode = 00000010
eax=00000004 ebx=b4df1030 ecx=b4df18b3 edx=00012017 esi=89aeb498 edi=89aa0c68
eip=00000000 esp=b29dbc7c ebp=b29dbd00 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000000 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 6

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 805805d1 to 00000000

STACK_TEXT:
b29dbc78 805805d1 00000004 00000001 b29dbd64 0x0
b29dbd00 80579298 00000300 00000328 00000000 nt!IopXxxControlFile+0x379
b29dbd34 8054167c 00000300 00000328 00000000 nt!NtDeviceIoControlFile+0x2a
b29dbd34 7c91e514 00000300 00000328 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0186cf04 00000000 00000000 00000000 00000000 0x7c91e514


POSSIBLE_INVALID_CONTROL_TRANSFER: from 805805cc to 804ef0a0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .trap ffffffffb29dbc08 ; kb

BUCKET_ID: CPU_CALL_ERROR

Followup: MachineOwner
*** Possible invalid call from 805805cc ( nt!IopXxxControlFile+0x374 )
*** Expected target 804ef0a0 ( nt!IoAllocateIrp+0x0 )