On Fri 4/22/2011 8:55:45 PM GMT your computer crashed
crash dump file: J:\WINDOWS\Minidump\Mini042211-08.dmp
This was probably caused by the following module: nv4_disp.sys (nv4_disp+0x17B592)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFFB82677F4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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: nv4_disp.sys .
Google query: nv4_disp.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 4/22/2011 8:17:48 PM GMT your computer crashed
crash dump file: J:\WINDOWS\Minidump\Mini042211-07.dmp
This was probably caused by the following module: nv4_disp.sys (nv4_disp+0x2446BE)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFB83B0925, 0xFFFFFFFFA2C44880, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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: nv4_disp.sys .
Google query: nv4_disp.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 4/22/2011 8:17:18 PM GMT your computer crashed
crash dump file: J:\WINDOWS\Minidump\Mini042211-09.dmp
This was probably caused by the following module: nv4_disp.sys (nv4_disp+0x11439C)
Bugcheck code: 0xEA (0xFFFFFFFF88F61978, 0xFFFFFFFF8A1BF538, 0xFFFFFFFF8A234930, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: nv4_disp.sys .
Google query: nv4_disp.sys THREAD_STUCK_IN_DEVICE_DRIVER
On Fri 4/22/2011 7:46:38 PM GMT your computer crashed
crash dump file: J:\WINDOWS\Minidump\Mini042211-05.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2BCD6)
Bugcheck code: 0x1000000A (0x0, 0x1C, 0x1, 0xFFFFFFFF80502CD6)
Error: CUSTOM_ERROR
file path: J:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 4/22/2011 5:01:30 PM GMT your computer crashed
crash dump file: J:\WINDOWS\Minidump\Mini042211-04.dmp
This was probably caused by the following module: rtkhdaud.sys (RtkHDAud+0x65A5D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFFA8D62A5D, 0xFFFFFFFFB84C7C6C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: J:\WINDOWS\system32\drivers\rtkhdaud.sys
product: Realtek(r) High Definition Audio Function Driver (HRTF data Copyright 1994 by MIT Media Lab)
company: Realtek Semiconductor Corp.
description: Realtek(r) High Definition Audio Function 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: rtkhdaud.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.).
Google query: rtkhdaud.sys Realtek Semiconductor Corp. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 4/22/2011 4:49:35 PM GMT your computer crashed
crash dump file: J:\WINDOWS\Minidump\Mini042211-03.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x9B82)
Bugcheck code: 0x4E (0x99, 0x2C445, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: J:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software PFN_LIST_CORRUPT
On Fri 4/22/2011 4:14:12 PM GMT your computer crashed
crash dump file: J:\WINDOWS\Minidump\Mini042211-02.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF8992D019)
Bugcheck code: 0x100000D1 (0x0, 0x2, 0x1, 0xFFFFFFFF8992D019)
Error: CUSTOM_ERROR
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: Unknown .
Google query: Unknown CUSTOM_ERROR
On Fri 4/22/2011 5:43:09 AM GMT your computer crashed
crash dump file: J:\WINDOWS\Minidump\Mini042211-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x171D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF80171D, 0xFFFFFFFFB16B2A30, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: J:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 4/21/2011 12:07:42 PM GMT your computer crashed
crash dump file: J:\WINDOWS\Minidump\Mini042111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x25D64)
Bugcheck code: 0x1000000A (0x490028, 0x1C, 0x1, 0xFFFFFFFF804FCD64)
Error: CUSTOM_ERROR
file path: J:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 4/21/2011 12:48:33 AM GMT your computer crashed
crash dump file: J:\WINDOWS\Minidump\Mini042011-02.dmp
This was probably caused by the following module: nv4_disp.sys (nv4_disp+0x11439E)
Bugcheck code: 0xEA (0xFFFFFFFF88E5E3A8, 0xFFFFFFFF897D6CE8, 0xFFFFFFFF8A3B80C8, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: nv4_disp.sys .
Google query: nv4_disp.sys THREAD_STUCK_IN_DEVICE_DRIVER
On Wed 4/20/2011 11:32:12 PM GMT your computer crashed
crash dump file: J:\WINDOWS\Minidump\Mini042011-01.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0xA34)
Bugcheck code: 0x24 (0x1902FE, 0xFFFFFFFFA4E0E534, 0xFFFFFFFFA4E0E230, 0xFFFFFFFF806E794F)
Error: NTFS_FILE_SYSTEM
file path: J:\WINDOWS\system32\drivers\aswmon2.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Filter Driver for Windows XP
Bug check description: This indicates a problem occurred in the NTFS file system.
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: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
Google query: aswmon2.sys AVAST Software NTFS_FILE_SYSTEM
On Wed 4/20/2011 3:21:05 AM GMT your computer crashed
crash dump file: J:\WINDOWS\Minidump\Mini041911-01.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0xA34)
Bugcheck code: 0x1000000A (0x841, 0x2, 0x1, 0xFFFFFFFF806E7A2A)
Error: CUSTOM_ERROR
file path: J:\WINDOWS\system32\drivers\aswmon2.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Filter Driver for Windows XP
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: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
Google query: aswmon2.sys AVAST Software CUSTOM_ERROR
The following dump files were found but could not be read. These files may be corrupt:
J:\WINDOWS\Minidump\Mini042211-06.dmp