DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: b7cb9b1e, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b7cb9b1e, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: b7cb9b1e
CURRENT_IRQL: 2
FAULTING_IP:
viahduaa+17b1e
b7cb9b1e ?? ???
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: BF2142.exe
LAST_CONTROL_TRANSFER: from b7cae077 to b7cb9b1e
FAILED_INSTRUCTION_ADDRESS:
viahduaa+17b1e
b7cb9b1e ?? ???
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f78a29e0 b7cae077 f78a2eb8 892cbab0 00001180 viahduaa+0x17b1e
f78a2f4c b7c85680 b9eedb80 b9eeca00 b9eedb80 viahduaa+0xc077
f78a2f74 b7c85945 f78a2f00 00001180 f78a2fa4 portcls!CPortPinWaveCyclic::Copy+0x60
f78a2fb4 b7c7f7bf 00045380 80702ae4 ffdff000 portcls!CPortPinWaveCyclic::RequestService+0x298
f78a2fcc 804dcd12 893fa8d0 893fa8c0 00000000 portcls!CServiceGroup::ServiceDpc+0x2a
f78a2ff4 804dc87d b6891a6c 00000000 00000000 nt!KiRetireDpcList+0x61
f78a2ff8 b6891a6c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
804dc87d 00000000 00000009 0081850f bb830000 0xb6891a6c
STACK_COMMAND: kb
FOLLOWUP_IP:
viahduaa+17b1e
b7cb9b1e ?? ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: viahduaa+17b1e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: viahduaa
IMAGE_NAME: viahduaa.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 475f8140
FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_viahduaa+17b1e
BUCKET_ID: 0xD1_CODE_AV_BAD_IP_viahduaa+17b1e
Followup: MachineOwner
---------
ok das war die erste dann hab ich den neusten viahduaa.sys treiber
ausprobiert
danach:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: b82d2b14, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b82d2b14, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: b82d2b14
CURRENT_IRQL: 2
FAULTING_IP:
viahduaa+19b14
b82d2b14 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from b82c68b3 to b82d2b14
FAILED_INSTRUCTION_ADDRESS:
viahduaa+19b14
b82d2b14 ?? ???
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
80556d8c b82c68b3 80557314 89e91508 000011a0 viahduaa+0x19b14
805573a8 b829c680 b7ff2180 b7ff0fe0 b7ff2180 viahduaa+0xd8b3
805573d0 b829c945 80557400 000011a0 80557400 portcls!CPortPinWaveCyclic::Copy+0x60
80557410 b82967bf 0004e180 80561f20 ffdff000 portcls!CPortPinWaveCyclic::RequestService+0x298
80557428 804dcd12 88eafcf0 88eafce0 00000000 portcls!CServiceGroup::ServiceDpc+0x2a
80557440 80561cc0 ffdffc50 00000000 80561cc0 nt!KiRetireDpcList+0x61
80557450 804dcbf7 00000000 0000000e 00000000 nt!KiIdleThread0
80557454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28
STACK_COMMAND: kb
FOLLOWUP_IP:
viahduaa+19b14
b82d2b14 ?? ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: viahduaa+19b14
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: viahduaa
IMAGE_NAME: viahduaa.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48337f4f
FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_viahduaa+19b14
BUCKET_ID: 0xD1_CODE_AV_BAD_IP_viahduaa+19b14
Followup: MachineOwner
---------
hoffe du verstehst was das ist danke
REPI
jblover
