Hallo,

mit dem Tool kann ich nicht so recht was anfangen. Die Analyse konnte ich noch machen, aber das Collection Tool versteh ich nicht, da ich nicht weiß welchen Prozess ich auswählen muss.

Gibt es für Laien noch eine andere Alternative die Ursache für diese Bluescreens herauszufinden und zu beheben?

Grüße
Tuuli

du kannst auch das probieren

Bitte lade dir die neuste Version von WhoCrashed auf deinen Computer: WhoCrashed Download

• Installiere es
• Starte es als Administrator
• Klicke oben links auf den Button "Analyze"
• Scrolle herunter, die Bereiche Crash Dump Analysis und Conclusion bitte ins Forum kopieren

Bitte poste dein Ergebnis zwischen Code-Tags
Wenn ein Log zu lange ist, teile ihn bitte auf mehrere Antworten.

Code-Tags?

Drücke einfach die # in Antwortfenster und füge den Log dazwischen ein

Hier die Analyse:

System Information (local)
--------------------------------------------------------------------------------

Computer name: RM-DESKTOP-PC
Windows version: Windows Vista Service Pack 2, 6.0, build: 6002
Windows dir: C:\Windows
Hardware: MS-7366, MEDIONPC
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU E2200 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2145992704 bytes total




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 22.08.2015 13:22:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini082215-02.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A05F) 
Bugcheck code: 0x24 (0x1904AA, 0xFFFFFFFF8101375C, 0xFFFFFFFF81013458, 0xFFFFFFFF824DC797)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NT-Dateisystemtreiber
Bug check description: This indicates a problem occurred in the NTFS file system. 
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 Sat 22.08.2015 13:22:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A05F) 
Bugcheck code: 0x24 (0x1904AA, 0xFFFFFFFF8101375C, 0xFFFFFFFF81013458, 0xFFFFFFFF824DC797)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NT-Dateisystemtreiber
Bug check description: This indicates a problem occurred in the NTFS file system. 
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 Sat 22.08.2015 13:22:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini082215-01.dmp
This was probably caused by the following module: Unknown () 
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error. 
Google query: CUSTOM_ERROR



On Fri 21.08.2015 13:26:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini082115-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DEFD) 
Bugcheck code: 0xA (0x0, 0xFF, 0x1, 0xFFFFFFFF824C088B)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Wed 19.08.2015 19:31:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini081915-04.dmp
This was probably caused by the following module: win32k.sys (win32k+0x5949D) 
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8262F54D, 0xFFFFFFFF93650C29, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
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 that cannot be identified at this time. 



On Wed 19.08.2015 19:31:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini081915-03.dmp
This was probably caused by the following module: Unknown () 
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error. 
Google query: CUSTOM_ERROR



On Wed 19.08.2015 12:39:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini081915-02.dmp
This was probably caused by the following module: volsnap.sys (volsnap+0x152C) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFFFFF8852352C, 0xFFFFFFFF8A5FC594, 0xFFFFFFFF8A5FC290)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\volsnap.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Volumeschattenkopie-Treiber
Bug check description: This indicates that a system thread 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 that cannot be identified at this time. 



On Wed 19.08.2015 11:35:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini081915-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x25487) 
Bugcheck code: 0x50 (0xFFFFFFFF835DEB08, 0x0, 0xFFFFFFFF82687EDA, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\aswsnx.sys
product: Avast Antivirus 
company: AVAST Software
description: avast! Virtualization Driver
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software). 
Google query: AVAST Software PAGE_FAULT_IN_NONPAGED_AREA



On Mon 17.08.2015 09:23:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini081715-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xB7234) 
Bugcheck code: 0x4E (0x7, 0x14730, 0x179A8, 0x0)
Error: PFN_LIST_CORRUPT
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 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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Mon 17.08.2015 07:16:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini081715-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DEFD) 
Bugcheck code: 0xA (0x2, 0x1B, 0x0, 0xFFFFFFFF824EA073)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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
--------------------------------------------------------------------------------

11 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has 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)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.