Foutmelding en herstart windows

[RensvN]

Ik krijg de laatste tijd verschillende keren onderstaande melding:

De pc valt uit en start opnieuw op.

Kan iemand me vertellen hoe dit kan, wat dit is en wat ik moet doen.

Alvast bedankt!

Probleemhandtekening:

Gebeurtenisnaam van probleem: BlueScreen

Versie van besturingssysteem: 6.1.7601.2.1.0.256.1

Landinstelling-id: 1043

Aanvullende informatie over dit probleem:

BCCode: 50

BCP1: FFFFFFE8

BCP2: 00000000

BCP3: 8AC339CB

BCP4: 00000000

OS Version: 6_1_7601

Service Pack: 1_0

Product: 256_1

Bestanden die helpen bij het beschrijven van het probleem:

C:\Windows\Minidump\062212-30562-01.dmp

C:\Users\rens\AppData\Local\Temp\WER-59781-0.sysdata.xml

Lees de onlineprivacyverklaring:

Windows 7 Privacyverklaring - Microsoft Windows

Als de onlineprivacyverklaring niet beschikbaar is, lees dan onze offlineprivacyverklaring:

C:\Windows\system32\nl-NL\erofflps.txt

[Dasle]

Download Blue Screen View.

Start het programma op.

Je zal nu een overzicht krijgen van de laatste foutmeldingen en Minidumps (.dmp-bestand).

Dubbelklik op het .dmp-bestand dat overeenstemt met het tijdstip waarop je het laatste blauwe scherm kreeg.

Je zal nu een overzicht krijgen.

Geef in je volgende bericht de waarde van volgende onderdelen:

• bug check string
  
• bug check code
  
• caused by driver
  
• de 4 parameters
  

Als je meerdere .dmp bestanden hebt, geef dan bovenstaande informatie voor de laatste 5. Zet er in dit geval ook de datum en tijd van de crash bij.

[RensvN]

Ik heb het programma gedownload maar als ik het opstart krijg ik een melding van 0 crashes en dat terwijl ik vanochtend nog een bluescreen heb gehad.

Ik heb wel van een eerder foutmelding de berichtgeving gekopiërd.

Dit kunt u vinden in mijn volgende post.

---------- Post toegevoegd om 11:17 ---------- Vorige post was om 11:16 ----------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 22-6-2012 7:36:46 GMT your computer crashed

crash dump file: C:\Windows\Minidump\062212-30562-01.dmp

This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x26C3)

Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFE8, 0x0, 0xFFFFFFFF8AC339CB, 0x0)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\drivers\aswmonflt.sys

product: avast! Antivirus System

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: aswmonflt.sys AVAST Software PAGE_FAULT_IN_NONPAGED_AREA

On Fri 22-6-2012 7:36:46 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x26C3)

Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFE8, 0x0, 0xFFFFFFFF8AC339CB, 0x0)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\drivers\aswmonflt.sys

product: avast! Antivirus System

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: aswmonflt.sys AVAST Software PAGE_FAULT_IN_NONPAGED_AREA

On Fri 22-6-2012 6:05:40 GMT your computer crashed

crash dump file: C:\Windows\Minidump\062212-17484-01.dmp

This was probably caused by the following module: win32k.sys (win32k+0xC942A)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000046, 0xFFFFFFFF82AD5940, 0xFFFFFFFF955C68B8, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\win32k.sys

product: Besturingssysteem Microsoft® Windows®

company: Microsoft Corporation

description: Multi-User Win32-stuurprogramma

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 Mon 18-6-2012 6:22:09 GMT your computer crashed

crash dump file: C:\Windows\Minidump\061812-20562-01.dmp

This was probably caused by the following module: fltmgr.sys (fltmgr+0xA82F)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8AE3B82F, 0xFFFFFFFFA95DAAA0, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\drivers\fltmgr.sys

product: Besturingssysteem Microsoft® Windows®

company: Microsoft Corporation

description: Microsoft Bestandssysteemfilterbeheer

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 Sat 16-6-2012 14:34:44 GMT your computer crashed

crash dump file: C:\Windows\Minidump\061612-19687-01.dmp

This was probably caused by the following module: aswsnx.sys (aswSnx+0x8DC6)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8AE2C0D2, 0xFFFFFFFFA80B05E4, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\drivers\aswsnx.sys

product: avast! Antivirus System

company: AVAST Software

description: avast! Virtualization 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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).

Google query: aswsnx.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

On Sat 16-6-2012 14:32:57 GMT your computer crashed

crash dump file: C:\Windows\Minidump\061612-20906-01.dmp

This was probably caused by the following module: fltmgr.sys (fltmgr+0xA885)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8AA0A885, 0xFFFFFFFF9C22F750, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\drivers\fltmgr.sys

product: Besturingssysteem Microsoft® Windows®

company: Microsoft Corporation

description: Microsoft Bestandssysteemfilterbeheer

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 Sat 9-6-2012 7:50:05 GMT your computer crashed

crash dump file: C:\Windows\Minidump\060912-17406-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E3BF)

Bugcheck code: 0x1A (0x41287, 0x1C, 0x0, 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 which cannot be identified at this time.

Conclusion

--------------------------------------------------------------------------------

7 crash dumps have been found and analyzed. 2 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:

aswsnx.sys (avast! Virtualization Driver, AVAST Software)

aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, 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.

[Dasle]

Welke versie van Avast gebruik je de gratis versie of een betalende versie?

Voer eens een controle van je geheugen uit met MemTest86+, een handleiding en een downloadlocatie vind je hier.

Wat is het resultaat van deze test?