Hi Guys,
I have not posted for a while as all has been good with my world of computers, but now I ahve to ask for your help again,
When i switch on my desktop all is well for a while, then the system just shuts down and reboots, then I get the message your system has just recovered from a serious error.
then when I log with micrososoft it tells me to check for updates or restore to earlier, I do this but I still have the problem. I do not get a blue screen.
Hope its something simple?
Thanks in advance
: 1000008e BCP1 : C0000005 BCP2 : BF46E2A0 BCP3 : A6574A58
BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 256_1
This was the error code to be sent to microsoft.
I would just like to add the pc can run for hours without a crash then it can crash 3 or 4 times quickly
There are a couple of tools I suggest would be good to run, they may offer a deeper insight into this, first off I would get and run WhoCrashed, click Analyse at the top left, then scroll down to see the results, it will read any crash dumps found and give info on them, it also offers links to art9cles that may shed more light on the issue that helps find a solution.
Next get and run SpeedFan, see what the system temps are reported as, this is just to check it's not a heat issue, it's so quick and easy it doesn't hurt just to check, no point doing masses of other things to just find this may of been the cause all along, so if you report back the readings it will help.
Now although I saw nothing to support your hard drive concern, it is one of the few things we can scan to check it thoroughly, there are a couple of tools, but it's always best to use the drive makers own utility if available, so you need to know the make of hard drive, then go to that site and get the diagnostic software most provide, there are however a few makers that do not have such a utility, in such cases use HDDScan or HD Tune (free version not pro), run the extended tests if you want to be sure about your drive, but depending on the size of the drive and power of the system (speed etc) it may take hours to complete, but for smaller drives it will obviously be faster than larger ones, this should tell you if your fear of a drive fault is correct or not.
Lets see if any of this can shed more light, but at the same time try to think if you had recently added new hardware, or updated a driver, it wont hurt to check in the device manager to see if any conflicts are showing, but once you have tried these things report back and we can see if there is some specific answer to sort this issue for you.
Hi 8210GUY
please find the report from who crashed, I will continue with the rest of the instructions.
tuxedo
System Information (local)
——————————————————————————–
computer name: OWNER-44C5E63C2
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel® Pentium® D CPU 2.80GHz Intel586, level: 15
2 logical processors, active mask: 3
RAM: 1875914752 total
VM: 2147352576, free: 2033258496
——————————————————————————–
Crash Dump Analysis
——————————————————————————–
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sat 07/04/2012 17:32:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040712-03.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x15556)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8055196D, 0xFFFFFFFFA80B86EC, 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 Sat 07/04/2012 17:31:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040712-02.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0x7409)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8055196D, 0xFFFFFFFFA6D4C818, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\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 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: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
Google query: aswmon2.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sat 07/04/2012 17:22:10 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040712-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2A15)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8055196D, 0xFFFFFFFFA5F4FAA0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\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 Fri 06/04/2012 16:57:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040612-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C64F)
Bugcheck code: 0x1000000A (0x28, 0x2, 0x0, 0xFFFFFFFF804F364F)
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 Fri 06/04/2012 16:57:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040612-03.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2AB4)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805515A1, 0xFFFFFFFFA7131444, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\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 Fri 06/04/2012 14:30:47 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040612-02.dmp
This was probably caused by the following module: aswfsblk.sys (aswFsBlk+0x1771)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805515A1, 0xFFFFFFFFA5E83860, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\aswfsblk.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Access Blocking 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: aswfsblk.sys (avast! File System Access Blocking Driver, AVAST Software).
Google query: aswfsblk.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 06/04/2012 14:15:15 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040612-01.dmp
This was probably caused by the following module: igxpdx32.dll (igxpdx32+0x1D72A0)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF46E2A0, 0xFFFFFFFFA6574A58, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\igxpdx32.dll
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: DirectDraw® Driver for Intel® Graphics Technology
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: igxpdx32.dll (DirectDraw® Driver for Intel® Graphics Technology, Intel Corporation).
Google query: igxpdx32.dll Intel Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Thu 05/04/2012 11:09:06 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040512-06.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0x7409)
Bugcheck code: 0xC2 (0x7, 0xCD4, 0x5010800, 0xFFFFFFFFE4AB4008)
Error: BAD_POOL_CALLER
file path: C:\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 that the current thread is making a bad pool request.
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: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
Google query: aswmon2.sys AVAST Software BAD_POOL_CALLER
On Thu 05/04/2012 10:51:48 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040512-05.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2A15)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8055196D, 0xFFFFFFFFA6C2C820, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\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 05/04/2012 08:18:10 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040512-04.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0x7362)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF80551AE2, 0xFFFFFFFFA7735814, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\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 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: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
Google query: aswmon2.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Thu 05/04/2012 08:16:39 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040512-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A5A1)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805515A1, 0xFFFFFFFFF76C6974, 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 Thu 05/04/2012 07:41:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040512-02.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x15607)
Bugcheck code: 0x10000050 (0xFFFFFFFFA203800C, 0x0, 0xFFFFFFFF80593191, 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 Thu 05/04/2012 07:40:27 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xC607D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8059D07D, 0xFFFFFFFFA7A2AB60, 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 04/04/2012 13:20:09 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040412-02.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0x7409)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8055196D, 0xFFFFFFFFA6EF9818, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\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 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: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
Google query: aswmon2.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Wed 04/04/2012 09:03:20 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040412-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x15556)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805515A1, 0xFFFFFFFFA71B9700, 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
——————————————————————————–
Conclusion
——————————————————————————–
44 crash dumps have been found and analyzed. Only 15 are included in this report. 5 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)
aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software)
aswsnx.sys (avast! Virtualization Driver, AVAST Software)
igxpdx32.dll (DirectDraw® Driver for Intel® Graphics Technology, Intel Corporation)
aswfsblk.sys (avast! File System Access Blocking Driver, AVAST Software)
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.
Well there is pretty conclusive reports to suggest Avast is the main issue, my best guess in their latest update it added something new, and it won’t play nice with your system, the immediate solution is to uninstall Avast, but this means you would have no anti-virus, so you would be best advised to download a different anti-virus to use instead of Avast, the alternate is to stop Avast from running and wait for them to release another update to correct this, assuming you’re not a one off case of this issue, but this is obviously not without its risks, so changing anti-virus is probably the fastest wisest solution for this, if you did not get on with another anti-virus you could revert back to Avast in a month, and hope it has resolved the issue by then, and repeat if the issue remains.
Avast is my choice every time as an anti-virus, but good alternate options are Bitdefender, and Microsoft Security Essentials has been getting great reviews, everyone has their favourite, and there are other choices around, but personally these would be my first alternate choices to Avast, others will have their own preference.
The other clear issue is related to your video driver, so go to the makers site and download and install the latest drivers for your card, hopefully this will stop further problems.
Hope this helps a bit, it's annoying when an update causes so much trouble, but thankfully it's not that often, so try these suggestions and see how you go, then if need be we can look again if there is still a problem.
Thanks for the help and advice again, I will uninstall and find another anti-virus and try to find the video card makers for the updates,
Thanks to you and all the other people who help us out on WTT.
tuxedo
tuxedo
Thanks so much every thing is great again in my world of computers, once again WTT are the best.
