Welkom op ons forum!

Heb je een computerprobleem of een algemene vraag? Registreer een account op het forum, wij helpen je dan graag verder om het probleem vakkundig op te lossen.

Gebruikersavatar
martijnvkk
Lid
Berichten: 5
Lid geworden op: 01 nov 2012 20:48

De laatste tijd heb ik bijna wel elke keer als ik mijn computer opstart bleuscreen, bijvoorbeeld: BAD_POOL_HEADER of MEMOVRY_MANAGEMENT of DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dit zijn mijn PC specs:
http://speccy.piriform.com/results/7EDt ... UrNiRkYajT
Hopelijk kunnen jullie me helpen.

Groetjes Martijn
Gebruikersavatar
Abraham54
Collega Helper
Berichten: 2755
Lid geworden op: 15 feb 2010 21:00
Contacteer: Website

Heb je soms een driverupdateprogramma gebruikt?

WhoCrashed introductie

WhoCrashed beschrijving

Download de free home edition van WhoCrashed naar je bureaublad via klik hier Afbeelding en installeer het tool via klikken/dubbelklikken op "whocrashedSetup.exe"

Nadat 'WhoCrashed' is opgestart, klik je op de "Analyze" knop.

Selekteer nu de inhoud van het venster, kopieer dit en post het resultaat in je volgende post.
Domheid is ook een gave God's, maar men mag haar niet misbruiken.
Gebruikersavatar
martijnvkk
Lid
Berichten: 5
Lid geworden op: 01 nov 2012 20:48

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 28-11-2012 15:35:21 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: i8042prt.sys (i8042prt+0xC2AB)
Bugcheck code: 0xD1 (0xA4, 0x6, 0x0, 0xFFFFFFFF8B7712AB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\i8042prt.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: i8042-poortstuurprogramma
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.
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 that cannot be identified at this time.



On Wed 28-11-2012 15:29:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112812-01.dmp
This was probably caused by the following module: aswfsblk.sys (aswFsBlk+0x1B40)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF830D1E6A, 0xFFFFFFFFB0AB85F4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\aswfsblk.sys
product: avast! Antivirus
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: AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Fri 9-11-2012 16:57:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110912-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x2FA4)
Bugcheck code: 0xF5 (0x6E, 0xFFFFFFFF9FCE0718, 0xFFFFFFFF9FCE06E8, 0x0)
Error: FLTMGR_FILE_SYSTEM
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Microsoft Bestandssysteemfilterbeheer
Bug check description: This indicates that an unrecoverable failure occurred in the Filter Manager.
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 that cannot be identified at this time.



On Thu 8-11-2012 15:22:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110812-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF8300707E)
Bugcheck code: 0x1A (0x3451, 0xFFFFFFFFC050A640, 0xFFFFFFFF8AA05C68, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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.
Google query: MEMORY_MANAGEMENT



On Tue 6-11-2012 14:10:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110612-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x1862B)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF89A3D688, 0xFFFFFFFF89A3D7D4, 0xFFFFFFFF8326EB00)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: AVAST Software CRITICAL_OBJECT_TERMINATION



On Wed 31-10-2012 16:22:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini103112-01.dmp
This was probably caused by the following module: tslwwff.sys (TsLwWfF+0x20EA)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFFA2CC8306)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tslwwff.sys
product: CommView for WiFi
company: TamoSoft
description: WiFi Capture Driver
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: tslwwff.sys (WiFi Capture Driver, TamoSoft).
Google query: TamoSoft DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 30-10-2012 15:34:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini103012-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x298F8)
Bugcheck code: 0x18 (0xFFFFFFFFBAD0B0B0, 0xFFFFFFFF88129020, 0x2, 0xFFFFFFFF8A7E7758)
Error: REFERENCE_BY_POINTER
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
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: AVAST Software REFERENCE_BY_POINTER



On Sun 28-10-2012 15:13:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102812-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4AFA7)
Bugcheck code: 0x1 (0xFFFFFFFF8325CD65, 0x0, 0xFFFF, 0x0)
Error: APC_INDEX_MISMATCH
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 18-10-2012 15:25:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101812-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xB251F)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF830CC51F, 0xFFFFFFFFA3055C38, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Sat 13-10-2012 10:18:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101312-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF86060DB8, 0xFFFFFFFF86060E60, 0x8150008)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 12-10-2012 17:51:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101212-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x69FE)
Bugcheck code: 0xC2 (0xD, 0xFFFFFFFF897FAF00, 0x20206F49, 0xFFFFFFFF89F11698)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: AVAST Software BAD_POOL_CALLER



On Thu 11-10-2012 15:01:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101112-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x98339)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFFB, 0x0, 0xFFFFFFFF8320C5D1, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
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 that cannot be identified at this time.



On Sat 6-10-2012 8:17:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100612-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x2623)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x1, 0xFFFFFFFFBCB497A4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Tue 25-9-2012 14:37:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini092512-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xA0907)
Bugcheck code: 0x50 (0xFFFFFFFFD08E593E, 0x0, 0xFFFFFFFF8B8A2907, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
Bug check description: This indicates that invalid system memory has been referenced.
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 that cannot be identified at this time.



On Wed 19-9-2012 15:29:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini091912-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x25EFD)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF89CCB2E8, 0xFFFFFFFF89CCB3A0, 0x8170010)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
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.
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: AVAST Software BAD_POOL_HEADER
Gebruikersavatar
Abraham54
Collega Helper
Berichten: 2755
Lid geworden op: 15 feb 2010 21:00
Contacteer: Website

We gaan ervoor zorgen dat je nu eerst de allernieuwste versie Avast 7 in jouw Windows krijgt.
Daarvoor dient de oudere versie eerst verwijderd te worden.

Downloads:

a) Avast 7 Free Antivirus 2012: http://www.avast.com/nl-nl/index

b) avast Software Uninstall Utility: http://www.chip.de/downloads/avast-Soft ... 40395.html

Zijn beide downloads ontvangen, dan herstart jij naar Veilige modus.
Indien je niet weet hoe: http://users.telenet.be/marcvn/spyware/ ... modus.html

In Veilige modus gebruik je nu het avast Software Uninstall Utility om alles wat Avast in jouw windows heeft gezet te verwijderen en het register te ontdoen van de Avast instellingen.

Is dat gebeurd, dan herstart je weer naar je gewone bureaublad en installeer je Avast 7 Free Antivirus 2012:.
Domheid is ook een gave God's, maar men mag haar niet misbruiken.
Gebruikersavatar
martijnvkk
Lid
Berichten: 5
Lid geworden op: 01 nov 2012 20:48

Gedaan nu ik mijn computer opstartte kreeg ik deze:


On Thu 6-12-2012 16:45:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini120612-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x186E4)
Bugcheck code: 0x50 (0xFFFFFFFFD9ED181C, 0x1, 0xFFFFFFFF91AF26E4, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
Bug check description: This indicates that invalid system memory has been referenced.
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: AVAST Software PAGE_FAULT_IN_NONPAGED_AREA
Gebruikersavatar
Abraham54
Collega Helper
Berichten: 2755
Lid geworden op: 15 feb 2010 21:00
Contacteer: Website

Ik denk dat je het werkgeheugen in je PC eens moet kontroleren.

Kijk hier http://pcsupport.about.com/od/toolsofth ... rytest.htm voor zo'n testprogramma.

Laat maar weten wat de uitkomst is.
Domheid is ook een gave God's, maar men mag haar niet misbruiken.
Gebruikersavatar
martijnvkk
Lid
Berichten: 5
Lid geworden op: 01 nov 2012 20:48

Hey, nadat het probleem enige tijd weg was startte mijn computer niet goed op :( met weer hetzelfde probleem, ik snap niet.
Hier is een WhoCrashed logje:
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 25-1-2013 16:14:15 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF8313882A)
Bugcheck code: 0xC5 (0x0, 0x2, 0x1, 0xFFFFFFFF8313882A)
Error: DRIVER_CORRUPTED_EXPOOL
Bug check description: This indicates that the system attempted to access invalid 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. 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.
Google query: DRIVER_CORRUPTED_EXPOOL



On Sun 13-1-2013 15:05:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011313-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF)
Bugcheck code: 0x1A (0x3451, 0xFFFFFFFFC046BED8, 0xFFFFFFFF88F510E0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 12-12-2012 18:49:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121212-01.dmp
This was probably caused by the following module: aswtdi.sys (aswTdi+0x3315)
Bugcheck code: 0xD1 (0xFFFFFFFFE887DA86, 0x2, 0x0, 0xFFFFFFFF90E78315)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\aswtdi.sys
product: avast! Antivirus
company: AVAST Software
description: avast! TDI Filter Driver
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: aswtdi.sys (avast! TDI Filter Driver, AVAST Software).
Google query: AVAST Software DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Thu 6-12-2012 16:45:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini120612-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x186E4)
Bugcheck code: 0x50 (0xFFFFFFFFD9ED181C, 0x1, 0xFFFFFFFF91AF26E4, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
Bug check description: This indicates that invalid system memory has been referenced.
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: AVAST Software PAGE_FAULT_IN_NONPAGED_AREA



On Wed 28-11-2012 15:29:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112812-01.dmp
This was probably caused by the following module: aswfsblk.sys (aswFsBlk+0x1B40)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF830D1E6A, 0xFFFFFFFFB0AB85F4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\aswfsblk.sys
product: avast! Antivirus
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: AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Fri 9-11-2012 16:57:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110912-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x2FA4)
Bugcheck code: 0xF5 (0x6E, 0xFFFFFFFF9FCE0718, 0xFFFFFFFF9FCE06E8, 0x0)
Error: FLTMGR_FILE_SYSTEM
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Microsoft Bestandssysteemfilterbeheer
Bug check description: This indicates that an unrecoverable failure occurred in the Filter Manager.
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 that cannot be identified at this time.



On Thu 8-11-2012 15:22:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110812-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF8300707E)
Bugcheck code: 0x1A (0x3451, 0xFFFFFFFFC050A640, 0xFFFFFFFF8AA05C68, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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.
Google query: MEMORY_MANAGEMENT



On Tue 6-11-2012 14:10:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini110612-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x1862B)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF89A3D688, 0xFFFFFFFF89A3D7D4, 0xFFFFFFFF8326EB00)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: AVAST Software CRITICAL_OBJECT_TERMINATION



On Wed 31-10-2012 16:22:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini103112-01.dmp
This was probably caused by the following module: tslwwff.sys (TsLwWfF+0x20EA)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFFA2CC8306)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tslwwff.sys
product: CommView for WiFi
company: TamoSoft
description: WiFi Capture Driver
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: tslwwff.sys (WiFi Capture Driver, TamoSoft).
Google query: TamoSoft DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 30-10-2012 15:34:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini103012-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x298F8)
Bugcheck code: 0x18 (0xFFFFFFFFBAD0B0B0, 0xFFFFFFFF88129020, 0x2, 0xFFFFFFFF8A7E7758)
Error: REFERENCE_BY_POINTER
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
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: AVAST Software REFERENCE_BY_POINTER



On Sun 28-10-2012 15:13:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102812-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4AFA7)
Bugcheck code: 0x1 (0xFFFFFFFF8325CD65, 0x0, 0xFFFF, 0x0)
Error: APC_INDEX_MISMATCH
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 18-10-2012 15:25:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101812-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xB251F)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF830CC51F, 0xFFFFFFFFA3055C38, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Sat 13-10-2012 10:18:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101312-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF86060DB8, 0xFFFFFFFF86060E60, 0x8150008)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 12-10-2012 17:51:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101212-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x69FE)
Bugcheck code: 0xC2 (0xD, 0xFFFFFFFF897FAF00, 0x20206F49, 0xFFFFFFFF89F11698)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: AVAST Software BAD_POOL_CALLER



On Thu 11-10-2012 15:01:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101112-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x98339)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFFB, 0x0, 0xFFFFFFFF8320C5D1, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
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 that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

39 crash dumps have been found and analyzed. Only 15 are included in this report. 7 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)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 306.97 , NVIDIA Corporation)
aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software)
tslwwff.sys (WiFi Capture Driver, TamoSoft)
aswsnx.sys (avast! Virtualization Driver, AVAST Software)
aswfsblk.sys (avast! File System Access Blocking Driver, AVAST Software)
aswtdi.sys (avast! TDI Filter 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.
Gebruikersavatar
Abraham54
Collega Helper
Berichten: 2755
Lid geworden op: 15 feb 2010 21:00
Contacteer: Website

Heb jij de geheugentest inmiddels uitgevoerd?
Zo niet, dan toch maar eens gaan doen!

En doe ook het volgende:

ga naar Start en typ in de zoekregel cmd - bovenaan in het startmenu zie je nu de betreffende snelkoppeling.
Klik deze snelkoppeling met rechts aan en kies voor Als administrator uitvoeren.

In het zwarte venster typ je nu sfc /scannow gevolgd door indrukken van de Entertoets.
Denk wel aan de spatie na 'sfc'.
In het zwarte venster zie je vervolgens de voortgang van de scan.
SFC (SystemFileChecker) houdt in dat systeembestanden gecontroleerd worden op juist funktioneren, zo nodig volgt reparatie.
Let goed op de laatste meldingen in het venster: indien aangegeven wordt, dat herstel afhankelijk is van opnieuw opstarten, doe dit dan.

Is de scan klaar en hoeft er niet gerebooted te worden, typ je Exit gevolgd door indrukken van de Entertoets.
Laat wel weten wat het resultaat van de scan is.
Domheid is ook een gave God's, maar men mag haar niet misbruiken.
Gebruikersavatar
martijnvkk
Lid
Berichten: 5
Lid geworden op: 01 nov 2012 20:48

Abraham54 schreef:Heb jij de geheugentest inmiddels uitgevoerd?
Zo niet, dan toch maar eens gaan doen!

En doe ook het volgende:

ga naar Start en typ in de zoekregel cmd - bovenaan in het startmenu zie je nu de betreffende snelkoppeling.
Klik deze snelkoppeling met rechts aan en kies voor Als administrator uitvoeren.

In het zwarte venster typ je nu sfc /scannow gevolgd door indrukken van de Entertoets.
Denk wel aan de spatie na 'sfc'.
In het zwarte venster zie je vervolgens de voortgang van de scan.
SFC (SystemFileChecker) houdt in dat systeembestanden gecontroleerd worden op juist funktioneren, zo nodig volgt reparatie.
Let goed op de laatste meldingen in het venster: indien aangegeven wordt, dat herstel afhankelijk is van opnieuw opstarten, doe dit dan.

Is de scan klaar en hoeft er niet gerebooted te worden, typ je Exit gevolgd door indrukken van de Entertoets.
Laat wel weten wat het resultaat van de scan is.

De resultaten van de scan waren er bestanden die beschadigd waren maar ze konden niet allemaal hersteld worden, het logje staat bij BRS volgens mij kon ik niet openen. (toegang geweigerd)
Gebruikersavatar
Abraham54
Collega Helper
Berichten: 2755
Lid geworden op: 15 feb 2010 21:00
Contacteer: Website

Ik was er al bang voor dat die SFC-melding mogelijk zou komen.
De beste oplossing voor jou is daarom Windows opnieuw te installeren.
Domheid is ook een gave God's, maar men mag haar niet misbruiken.

Terug naar “Blauwe schermen en opstartproblemen”