Wednesday, October 10, 2012 2:32 AM
Here is a link to the dump files:
And here is information I got from a website about the dump file.
Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffffffdb, memory referenced. Arg2: 00000000, value 0 = read operation, 1 = write operation. Arg3: 80530160, If non-zero, the instruction address which referenced the bad memory address. Arg4: 00000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 READ_ADDRESS: GetUlongFromAddress: unable to read from 80543d08 ffffffdb FAULTING_IP: nt!KiTrap0E+d8 80530160 8453dc test byte ptr [ebx-24h],dl MM_INTERNAL_CODE: 0 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: wanmpsvc.exe MISALIGNED_IP: nt!KiTrap0E+d8 80530160 8453dc test byte ptr [ebx-24h],dl LAST_CONTROL_TRANSFER: from 77f56c81 to 80530160 STACK_TEXT: f33ddd64 77f56c81 00000000 00000000 00000000 nt!KiTrap0E+0xd8 WARNING: Frame IP not in any known module. Following frames may be wrong. 0012f994 00000000 00000000 00000000 00000000 0x77f56c81 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTrap0E+d8 80530160 8453dc test byte ptr [ebx-24h],dl SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiTrap0E+d8 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: hardware FAILURE_BUCKET_ID: IP_MISALIGNED BUCKET_ID: IP_MISALIGNED Followup: MachineOwner ---------
- Edited by flierfootball Wednesday, October 10, 2012 3:03 AM
Wednesday, October 10, 2012 5:55 AM
yes, it looks there's a problem with a driver (AOL's Wan miniport service).
I would recommend you updating network drivers from manufacturer's website.