Hallo, danke für die Antwort, hier die Auswertung:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 987250a3, The address that the exception occurred at
Arg3: 8fbf7b54, Exception Record Address
Arg4: 8fbf7730, Context Record Address
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:
stdriver32+30a3
987250a3 3b11 cmp edx,dword ptr [ecx]
EXCEPTION_RECORD: 8fbf7b54 -- (.exr 0xffffffff8fbf7b54)
ExceptionAddress: 987250a3 (stdriver32+0x000030a3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00005c80
Attempt to read from address 00005c80
CONTEXT: 8fbf7730 -- (.cxr 0xffffffff8fbf7730)
eax=a12f5c80 ebx=a12f0000 ecx=00005c80 edx=00000000 esi=87a29200 edi=00000000
eip=987250a3 esp=8fbf7c1c ebp=8fbf7c64 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
stdriver32+0x30a3:
987250a3 3b11 cmp edx,dword ptr [ecx] ds:0023:00005c80=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 00005c80
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d68718
Unable to read MiSystemVaType memory at 82d48160
00005c80
FOLLOWUP_IP:
stdriver32+30a3
987250a3 3b11 cmp edx,dword ptr [ecx]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 987254bd to 987250a3
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8fbf7c64 987254bd 87a29200 8fbf7ca0 987260ca stdriver32+0x30a3
8fbf7c70 987260ca 00000000 00000003 00000000 stdriver32+0x34bd
8fbf7ca0 987263a7 00000000 00000000 8783766c stdriver32+0x40ca
8fbf7d40 9872707a 8783766c 880e25b8 8fbf7d90 stdriver32+0x43a7
8fbf7d50 82e0e6d3 87837628 a0923ce0 00000000 stdriver32+0x507a
8fbf7d90 82cc00f9 9872704c 87837628 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: stdriver32+30a3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: stdriver32
IMAGE_NAME: stdriver32.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d059370
STACK_COMMAND: .cxr 0xffffffff8fbf7730 ; kb
FAILURE_BUCKET_ID: 0x7E_stdriver32+30a3
BUCKET_ID: 0x7E_stdriver32+30a3
Followup: MachineOwner
