Your minidump crashes with exactly the same problem getnd5b.sys.
Debugging Details:
------------------
WRITE_ADDRESS: 00000000
CURRENT_IRQL: 2
FAULTING_IP:
+ffffffff85b30373
85b30373 0001 add [ecx],al
CUSTOMER_CRASH_COUNT: 5
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from f7314c1c to 85b30373
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f79fbe84 f7314c1c 8605c438 8608cf30 00000000 0x85b30373
f79fbea8 f6297b69 8637e130 8608cf30 00000000 NDIS!ndisMSendCompleteX+0x8d
f79fbec8 f7314c1c 863f5cb8 0108cf30 00000000 psched!ClSendComplete+0x67
f79fbeec f77ff232 8636bad0 8608cf30 00000000 NDIS!ndisMSendCompleteX+0x8d
f79fbf24 f77ff302 f79fbfd0 00000000 8636bad0 getnd5b+0x3232
f79fbf54 f7420b94 860e6770 8651cc60 f79fbfcf getnd5b+0x3302
f79fbfd0 80540d5d 85e830c8 85e830b4 00000000 atapi!IdePortCompletionDpc+0x204
f79fbff4 80540a2a f6bb3a94 00000000 00000000 nt!KiRetireDpcList+0x46
f79fbff8 f6bb3a94 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
80540a2a 00000000 00000009 bb835675 00000128 0xf6bb3a94
FOLLOWUP_IP:
getnd5b+3232
f77ff232 ?? ???
SYMBOL_STACK_INDEX: 4
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: getnd5b+3232
MODULE_NAME: getnd5b
IMAGE_NAME: getnd5b.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 410f4542
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0xD1_W_getnd5b+3232
BUCKET_ID: 0xD1_W_getnd5b+3232
Followup: MachineOwner
May I suggest that you Google for getnd5b.sys, and see if you can find out why this driver keeps crashing.
Regards Howard
