On Fri 22-7-2011 16:27:37 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF83266744, 0xFFFFFFFF95DB3454, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .
Google query: ntkrpamp.exe KERNEL_MODE_EXCEPTION_NOT_HANDLED
On Sun 17-7-2011 9:27:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071711-36785-01.dmp
This was probably caused by the following module: avgidsshim.sys (AVGIDSShim+0xE53)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF99F55382, 0xFFFFFFFF9F50BC78, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\avgidsshim.sys
product: AVG IDS
company: AVG Technologies CZ, s.r.o.
description: IDS Application Activity Monitor Loader Driver.
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avgidsshim.sys (IDS Application Activity Monitor Loader Driver., AVG Technologies CZ, s.r.o. ).
Google query: avgidsshim.sys AVG Technologies CZ, s.r.o. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 15-7-2011 22:44:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071611-34569-01.dmp
This was probably caused by the following module: hal.sys (hal+0x4A2E)
Bugcheck code: 0xD1 (0xFFFFFFFF8B347394, 0x4, 0x8, 0xFFFFFFFF8B347394)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: hal.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL