Hi again rshaffer61
You're never going to guess what....
Things had been going great, no BSOD since last we "spoke" but tonight I was on Facebook collecting multiply things off the wall when "Hello BSOD, I've missed you"
I ran WhoCrashed & this was the verdict.
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 15/07/2011 11:49:18 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071511-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD8F1A)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805AFF1A, 0xFFFFFFFFB5356BC4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 4/05/2011 1:26:02 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini050411-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xE2505)
Bugcheck code: 0x10000050 (0xFFFFFFFF93913160, 0x0, 0xFFFFFFFF805B9505, 0x0)
Error: CUSTOM_ERROR
file path: C:\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 Mon 2/05/2011 6:06:46 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini050211-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x1F33B)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFF0, 0x2, 0x0, 0xFFFFFFFF804E2284)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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 CUSTOM_ERROR
On Fri 29/04/2011 6:52:37 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini042911-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x20A8C)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8053B9FF, 0xFFFFFFFFB48D1B0C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Mon 25/04/2011 9:40:33 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini042611-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF8AC5)
Bugcheck code: 0x10000050 (0xFFFFFFFF9AD4D8F8, 0x0, 0xFFFFFFFF805CFAC5, 0x0)
Error: CUSTOM_ERROR
file path: C:\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 Wed 20/04/2011 12:03:56 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini042011-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x12769)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805BC23D, 0xFFFFFFFFB3826C60, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sun 17/04/2011 12:35:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041711-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x27AF)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF832F1CB0, 0xFFFFFFFF832F1CD8, 0xA050027)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a pool header is corrupt.
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.
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 Fri 15/04/2011 8:54:35 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041511-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x118E1)
Bugcheck code: 0x10000050 (0xFFFFFFFFF000EEF3, 0x8, 0xFFFFFFFFF000EEF3, 0x2)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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 CUSTOM_ERROR
On Tue 12/04/2011 8:05:31 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041211-02.dmp
This was probably caused by the following module: ipnat.sys (ipnat+0xF34E)
Bugcheck code: 0x1000000A (0xFFFFFFFF9AC28430, 0x2, 0x1, 0xFFFFFFFF805469D0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\ipnat.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IP Network Address Translator
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 Tue 12/04/2011 7:58:01 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041211-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x2339)
Bugcheck code: 0x100000D1 (0x4, 0x2, 0x1, 0xFFFFFFFFB9E1E339)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 7/04/2011 11:47:05 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040711-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x1D7C2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8053BA38, 0xFFFFFFFFB3CA9974, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Tue 5/04/2011 7:08:54 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040511-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x118E1)
Bugcheck code: 0x10000050 (0xFFFFFFFF9ADB4F18, 0x0, 0xFFFFFFFF805BC23D, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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 CUSTOM_ERROR
On Mon 6/09/2010 10:33:34 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini090610-01.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x29A3E3)
Bugcheck code: 0x10000050 (0xFFFFFFFFB0195000, 0x1, 0xFFFFFFFFBF2AC3E3, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 174.82
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 174.82
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.dll (NVIDIA Compatible Windows 2000 Display driver, Version 174.82 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation CUSTOM_ERROR
On Tue 27/07/2010 9:32:11 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini072710-01.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x29A3E3)
Bugcheck code: 0x10000050 (0xFFFFFFFFB2C45000, 0x1, 0xFFFFFFFFBF2AC3E3, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 174.82
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 174.82
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.dll (NVIDIA Compatible Windows 2000 Display driver, Version 174.82 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation CUSTOM_ERROR
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
14 crash dumps have been found and analyzed. 8 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
aswsp.sys (avast! self protection module, AVAST Software)
nv4_disp.dll (NVIDIA Compatible Windows 2000 Display driver, Version 174.82 , NVIDIA Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Maybe I just shouldn't try to collect multiple windows of things off the Facebook wall. Things had been going so well (but I hadn't really been collecting multiples of things off the Facebook wall though since the last time I had this problem)
Where would we like to start this time?
Jodie