| |
| |||||||
Alles rund um Windows: Windows Vista Crash DumpWindows 7 Hilfe zu allen Windows-Betriebssystemen: Windows XP, Windows Vista, Windows 7, Windows 8(.1) und Windows 10 / Windows 11- als auch zu sämtlicher Windows-Software. Alles zu Windows 10 ist auch gerne willkommen. Bitte benenne etwaige Fehler oder Bluescreens unter Windows mit dem Wortlaut der Fehlermeldung und Fehlercode. Erste Schritte für Hilfe unter Windows. |
 |
16.08.2015, 16:19
| #1 |
 |  Problem: Windows Vista Crash Dump Hallo, beim Starten des PCs meiner Eltern kam ein blauer Bildschirm mit Text (siehe Bild im Anhang). Was ist das? Viele Grüße Tuuli |
|
19.08.2015, 14:14
| #3 |
| | Windows Vista Crash Dump Details 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 |
|
20.08.2015, 02:16
| #4 |
| /// Malwareteam   | Lösung: Windows Vista Crash Dump du kannst auch das probieren Bitte lade dir die neuste Version von WhoCrashed auf deinen Computer: WhoCrashed Download
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 
__________________ Mfg, Rafael ~ I'm storm. I'm calm. I'm fire. I'm ice. I'm burningice. ~  Unterstütze uns mit einer Spende ......... Lob, Kritik oder Wünsche ......... .......... Folge uns auf Facebook .......... |
|
22.08.2015, 14:31
| #5 |
| | Wie Windows Vista Crash Dump Hier die Analyse: Code:
ATTFilter 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.
|
|
22.08.2015, 17:53
| #6 |
| /// Malwareteam | Wo Windows Vista Crash Dump Lösung! Überprüfung der Festplatten
Überprüfung der Systemintegrität
Weiters deinstalliere einmal Avast und lass danach noch dieses Tool hier laufen: https://www.avast.com/uninstall-utility
__________________ --> Windows Vista Crash Dump |
|
22.08.2015, 18:55
| #7 |
| | Windows Vista Crash Dump Bei chkdsk kommt folgende Meldung: Der Typ des Dateisystems ist NTFS. Das aktuelle Laufwerk kann nicht gesperrt werden. CHKDSK kann nicht ausgeführt werden, weil das Volume von einem anderen Prozess verwendet wird. Soll dieses Volume überprüft werden, wenn das System das nächste Mal gestartet wird? (J/N) |
|
22.08.2015, 18:56
| #8 | |
| /// Malwareteam | Windows Vista Crash DumpZitat:
Einfach J drücken und neustarten
__________________ Mfg, Rafael ~ I'm storm. I'm calm. I'm fire. I'm ice. I'm burningice. ~ Unterstütze uns mit einer Spende ......... Lob, Kritik oder Wünsche ......... .......... Folge uns auf Facebook .......... |
|
22.08.2015, 21:18
| #9 |
| | Windows Vista Crash Dump Chkdsk läuft jetzt. Das dauert ne Weile. Melde mich morgen wieder. Nach sfc /scannow wurde eine CBS.log erstellt. Den Inhalt kann ich irgendwie nicht posten, dabei hängt sich Firefox ständig auf. Avast habe ich deinstalliert und habe jetzt vorerst mal Emsisoft die Testversion drauf gemacht. Ich habe da noch schnell den Schnell-Scan drüberlaufen lassen. Es gab zwei Funde, welche ich in die Quarantäne verschoben habe. Code:
ATTFilter Emsisoft Anti-Malware - Version 10.0
Quarantäne-Protokoll
Datum Quelle Vorgang Fund
22.08.2015 22:13:27 Value: HKEY_USERS\S-1-5-21-1429313419-2184147580-785989940-1001\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\POLICIES\SYSTEM -> DISABLEREGISTRYTOOLS Unter Quarantäne Setting.DisableRegistryTools (A)
22.08.2015 22:13:27 Value: HKEY_USERS\S-1-5-21-1429313419-2184147580-785989940-1001\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\POLICIES\SYSTEM -> DISABLETASKMGR Unter Quarantäne Setting.DisableTaskMgr (A)
|
|
22.08.2015, 21:35
| #10 |
| /// Malwareteam | Windows Vista Crash Dump [gelöst] also ist chkdsk schon durch? wurden fehler gefunden?
__________________ Mfg, Rafael ~ I'm storm. I'm calm. I'm fire. I'm ice. I'm burningice. ~ Unterstütze uns mit einer Spende ......... Lob, Kritik oder Wünsche ......... .......... Folge uns auf Facebook .......... |
|
23.08.2015, 10:02
| #11 | |
| | Windows Vista Crash Dump [gelöst] chkdsk hat nichts gefunden. Zitat:
Heute morgen hatte ich nun wieder insgesamt drei Abstürze "PAGE_FAULT_IN_NONPAGED_AREA" Einmal beim laufenden Betrieb. |
|
23.08.2015, 20:37
| #12 |
| /// Malwareteam | Windows Vista Crash Dump [gelöst] Hast du CMD als Administrator ausgeführt? Bitte führe noch einmal SFC aus, wie hier beschrieben. Wurde ein Fehler festgestellt der nicht behoben werden konnte? Wenn ja: Gehe in folgenden Pfad: C:\Windows\logs\cbs und suche die cbs.log Kopiere sie auf den Desktop. Führe jetzt folgendes im CMD aus: Code:
ATTFilter findstr /c:"[SR]" %userprofile%\Desktop\cbs.log >%userprofile%\Desktop\sfcdetails.txt
__________________ Mfg, Rafael ~ I'm storm. I'm calm. I'm fire. I'm ice. I'm burningice. ~ Unterstütze uns mit einer Spende ......... Lob, Kritik oder Wünsche ......... .......... Folge uns auf Facebook .......... |
|
24.08.2015, 16:35
| #13 |
| | Windows Vista Crash Dump [gelöst] Ja CMD habe ich als Administrator ausgeführt. Ich mache jetzt nochmal das sfc /scannow. Code:
ATTFilter 2015-08-24 17:10:42, Info CSI 00000018 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:10:42, Info CSI 00000019 [SR] Beginning Verify and Repair transaction
2015-08-24 17:11:06, Info CSI 0000001b [SR] Verify complete
2015-08-24 17:11:07, Info CSI 0000001c [SR] Verifying 100 (0x00000064) components
2015-08-24 17:11:07, Info CSI 0000001d [SR] Beginning Verify and Repair transaction
2015-08-24 17:11:27, Info CSI 0000001f [SR] Verify complete
2015-08-24 17:11:28, Info CSI 00000020 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:11:28, Info CSI 00000021 [SR] Beginning Verify and Repair transaction
2015-08-24 17:11:58, Info CSI 00000023 [SR] Verify complete
2015-08-24 17:11:59, Info CSI 00000024 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:11:59, Info CSI 00000025 [SR] Beginning Verify and Repair transaction
2015-08-24 17:12:04, Info CSI 00000029 [SR] Verify complete
2015-08-24 17:12:05, Info CSI 0000002a [SR] Verifying 100 (0x00000064) components
2015-08-24 17:12:05, Info CSI 0000002b [SR] Beginning Verify and Repair transaction
2015-08-24 17:12:10, Info CSI 00000031 [SR] Verify complete
2015-08-24 17:12:11, Info CSI 00000034 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:12:11, Info CSI 00000035 [SR] Beginning Verify and Repair transaction
2015-08-24 17:12:17, Info CSI 0000003b [SR] Verify complete
2015-08-24 17:12:18, Info CSI 0000003c [SR] Verifying 100 (0x00000064) components
2015-08-24 17:12:18, Info CSI 0000003d [SR] Beginning Verify and Repair transaction
2015-08-24 17:12:21, Info CSI 00000043 [SR] Verify complete
2015-08-24 17:12:22, Info CSI 00000044 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:12:22, Info CSI 00000045 [SR] Beginning Verify and Repair transaction
2015-08-24 17:12:26, Info CSI 0000004b [SR] Verify complete
2015-08-24 17:12:27, Info CSI 0000004e [SR] Verifying 100 (0x00000064) components
2015-08-24 17:12:27, Info CSI 0000004f [SR] Beginning Verify and Repair transaction
2015-08-24 17:12:30, Info CSI 00000053 [SR] Verify complete
2015-08-24 17:12:31, Info CSI 00000056 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:12:31, Info CSI 00000057 [SR] Beginning Verify and Repair transaction
2015-08-24 17:12:35, Info CSI 00000059 [SR] Verify complete
2015-08-24 17:12:36, Info CSI 0000005c [SR] Verifying 100 (0x00000064) components
2015-08-24 17:12:36, Info CSI 0000005d [SR] Beginning Verify and Repair transaction
2015-08-24 17:12:40, Info CSI 0000005f [SR] Verify complete
2015-08-24 17:12:41, Info CSI 00000062 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:12:41, Info CSI 00000063 [SR] Beginning Verify and Repair transaction
2015-08-24 17:12:44, Info CSI 00000067 [SR] Verify complete
2015-08-24 17:12:45, Info CSI 00000068 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:12:45, Info CSI 00000069 [SR] Beginning Verify and Repair transaction
2015-08-24 17:12:50, Info CSI 0000006b [SR] Verify complete
2015-08-24 17:12:52, Info CSI 0000006c [SR] Verifying 100 (0x00000064) components
2015-08-24 17:12:52, Info CSI 0000006d [SR] Beginning Verify and Repair transaction
2015-08-24 17:13:06, Info CSI 0000006f [SR] Verify complete
2015-08-24 17:13:07, Info CSI 00000070 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:13:07, Info CSI 00000071 [SR] Beginning Verify and Repair transaction
2015-08-24 17:13:12, Info CSI 00000073 [SR] Verify complete
2015-08-24 17:13:12, Info CSI 00000074 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:13:12, Info CSI 00000075 [SR] Beginning Verify and Repair transaction
2015-08-24 17:13:15, Info CSI 00000077 [SR] Verify complete
2015-08-24 17:13:17, Info CSI 00000078 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:13:17, Info CSI 00000079 [SR] Beginning Verify and Repair transaction
2015-08-24 17:13:20, Info CSI 0000007b [SR] Verify complete
2015-08-24 17:13:21, Info CSI 0000007c [SR] Verifying 100 (0x00000064) components
2015-08-24 17:13:21, Info CSI 0000007d [SR] Beginning Verify and Repair transaction
2015-08-24 17:13:24, Info CSI 0000007f [SR] Verify complete
2015-08-24 17:13:25, Info CSI 00000080 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:13:25, Info CSI 00000081 [SR] Beginning Verify and Repair transaction
2015-08-24 17:13:34, Info CSI 00000083 [SR] Verify complete
2015-08-24 17:13:35, Info CSI 00000084 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:13:35, Info CSI 00000085 [SR] Beginning Verify and Repair transaction
2015-08-24 17:13:38, Info CSI 00000087 [SR] Verify complete
2015-08-24 17:13:39, Info CSI 00000088 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:13:39, Info CSI 00000089 [SR] Beginning Verify and Repair transaction
2015-08-24 17:13:43, Info CSI 0000008b [SR] Verify complete
2015-08-24 17:13:43, Info CSI 0000008c [SR] Verifying 100 (0x00000064) components
2015-08-24 17:13:43, Info CSI 0000008d [SR] Beginning Verify and Repair transaction
2015-08-24 17:13:46, Info CSI 0000008f [SR] Verify complete
2015-08-24 17:13:47, Info CSI 00000090 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:13:47, Info CSI 00000091 [SR] Beginning Verify and Repair transaction
2015-08-24 17:13:53, Info CSI 00000093 [SR] Verify complete
2015-08-24 17:13:54, Info CSI 00000094 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:13:54, Info CSI 00000095 [SR] Beginning Verify and Repair transaction
2015-08-24 17:13:57, Info CSI 00000097 [SR] Verify complete
2015-08-24 17:13:58, Info CSI 00000098 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:13:58, Info CSI 00000099 [SR] Beginning Verify and Repair transaction
2015-08-24 17:14:02, Info CSI 0000009b [SR] Verify complete
2015-08-24 17:14:02, Info CSI 0000009c [SR] Verifying 100 (0x00000064) components
2015-08-24 17:14:02, Info CSI 0000009d [SR] Beginning Verify and Repair transaction
2015-08-24 17:14:06, Info CSI 0000009f [SR] Verify complete
2015-08-24 17:14:07, Info CSI 000000a0 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:14:07, Info CSI 000000a1 [SR] Beginning Verify and Repair transaction
2015-08-24 17:14:10, Info CSI 000000a3 [SR] Verify complete
2015-08-24 17:14:10, Info CSI 000000a4 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:14:10, Info CSI 000000a5 [SR] Beginning Verify and Repair transaction
2015-08-24 17:14:14, Info CSI 000000a7 [SR] Verify complete
2015-08-24 17:14:15, Info CSI 000000a8 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:14:15, Info CSI 000000a9 [SR] Beginning Verify and Repair transaction
2015-08-24 17:14:18, Info CSI 000000ab [SR] Verify complete
2015-08-24 17:14:19, Info CSI 000000ac [SR] Verifying 100 (0x00000064) components
2015-08-24 17:14:19, Info CSI 000000ad [SR] Beginning Verify and Repair transaction
2015-08-24 17:14:22, Info CSI 000000af [SR] Verify complete
2015-08-24 17:14:23, Info CSI 000000b0 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:14:23, Info CSI 000000b1 [SR] Beginning Verify and Repair transaction
2015-08-24 17:14:26, Info CSI 000000b3 [SR] Verify complete
2015-08-24 17:14:26, Info CSI 000000b4 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:14:26, Info CSI 000000b5 [SR] Beginning Verify and Repair transaction
2015-08-24 17:14:29, Info CSI 000000b7 [SR] Verify complete
2015-08-24 17:14:30, Info CSI 000000b8 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:14:30, Info CSI 000000b9 [SR] Beginning Verify and Repair transaction
2015-08-24 17:14:33, Info CSI 000000bb [SR] Verify complete
2015-08-24 17:14:34, Info CSI 000000bc [SR] Verifying 100 (0x00000064) components
2015-08-24 17:14:34, Info CSI 000000bd [SR] Beginning Verify and Repair transaction
2015-08-24 17:14:37, Info CSI 000000bf [SR] Verify complete
2015-08-24 17:14:37, Info CSI 000000c0 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:14:37, Info CSI 000000c1 [SR] Beginning Verify and Repair transaction
2015-08-24 17:14:40, Info CSI 000000c3 [SR] Verify complete
2015-08-24 17:14:41, Info CSI 000000c4 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:14:41, Info CSI 000000c5 [SR] Beginning Verify and Repair transaction
2015-08-24 17:14:44, Info CSI 000000c7 [SR] Verify complete
2015-08-24 17:14:45, Info CSI 000000c8 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:14:45, Info CSI 000000c9 [SR] Beginning Verify and Repair transaction
2015-08-24 17:14:48, Info CSI 000000cb [SR] Verify complete
2015-08-24 17:14:49, Info CSI 000000cc [SR] Verifying 100 (0x00000064) components
2015-08-24 17:14:49, Info CSI 000000cd [SR] Beginning Verify and Repair transaction
2015-08-24 17:14:53, Info CSI 000000cf [SR] Verify complete
2015-08-24 17:14:54, Info CSI 000000d0 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:14:54, Info CSI 000000d1 [SR] Beginning Verify and Repair transaction
2015-08-24 17:14:57, Info CSI 000000d3 [SR] Verify complete
2015-08-24 17:14:58, Info CSI 000000d4 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:14:58, Info CSI 000000d5 [SR] Beginning Verify and Repair transaction
2015-08-24 17:15:00, Info CSI 000000d7 [SR] Verify complete
2015-08-24 17:15:01, Info CSI 000000d8 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:15:01, Info CSI 000000d9 [SR] Beginning Verify and Repair transaction
2015-08-24 17:15:05, Info CSI 000000db [SR] Verify complete
2015-08-24 17:15:05, Info CSI 000000dc [SR] Verifying 100 (0x00000064) components
2015-08-24 17:15:05, Info CSI 000000dd [SR] Beginning Verify and Repair transaction
2015-08-24 17:15:10, Info CSI 000000df [SR] Verify complete
2015-08-24 17:15:11, Info CSI 000000e0 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:15:11, Info CSI 000000e1 [SR] Beginning Verify and Repair transaction
2015-08-24 17:15:14, Info CSI 000000e3 [SR] Verify complete
2015-08-24 17:15:14, Info CSI 000000e4 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:15:14, Info CSI 000000e5 [SR] Beginning Verify and Repair transaction
2015-08-24 17:15:17, Info CSI 000000e7 [SR] Verify complete
2015-08-24 17:15:18, Info CSI 000000e8 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:15:18, Info CSI 000000e9 [SR] Beginning Verify and Repair transaction
2015-08-24 17:15:21, Info CSI 000000eb [SR] Verify complete
2015-08-24 17:15:21, Info CSI 000000ec [SR] Verifying 100 (0x00000064) components
2015-08-24 17:15:21, Info CSI 000000ed [SR] Beginning Verify and Repair transaction
2015-08-24 17:15:25, Info CSI 000000ef [SR] Verify complete
2015-08-24 17:15:25, Info CSI 000000f0 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:15:25, Info CSI 000000f1 [SR] Beginning Verify and Repair transaction
2015-08-24 17:15:28, Info CSI 000000f3 [SR] Verify complete
2015-08-24 17:15:29, Info CSI 000000f4 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:15:29, Info CSI 000000f5 [SR] Beginning Verify and Repair transaction
2015-08-24 17:15:31, Info CSI 000000f7 [SR] Verify complete
2015-08-24 17:15:32, Info CSI 000000f8 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:15:32, Info CSI 000000f9 [SR] Beginning Verify and Repair transaction
2015-08-24 17:15:35, Info CSI 000000fb [SR] Verify complete
2015-08-24 17:15:36, Info CSI 000000fc [SR] Verifying 100 (0x00000064) components
2015-08-24 17:15:36, Info CSI 000000fd [SR] Beginning Verify and Repair transaction
2015-08-24 17:15:41, Info CSI 000000ff [SR] Verify complete
2015-08-24 17:15:42, Info CSI 00000100 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:15:42, Info CSI 00000101 [SR] Beginning Verify and Repair transaction
2015-08-24 17:15:44, Info CSI 00000103 [SR] Verify complete
2015-08-24 17:15:45, Info CSI 00000104 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:15:45, Info CSI 00000105 [SR] Beginning Verify and Repair transaction
2015-08-24 17:15:48, Info CSI 00000107 [SR] Verify complete
2015-08-24 17:15:48, Info CSI 00000108 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:15:48, Info CSI 00000109 [SR] Beginning Verify and Repair transaction
2015-08-24 17:15:51, Info CSI 0000010b [SR] Verify complete
2015-08-24 17:15:52, Info CSI 0000010c [SR] Verifying 100 (0x00000064) components
2015-08-24 17:15:52, Info CSI 0000010d [SR] Beginning Verify and Repair transaction
2015-08-24 17:15:55, Info CSI 0000010f [SR] Verify complete
2015-08-24 17:15:55, Info CSI 00000110 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:15:55, Info CSI 00000111 [SR] Beginning Verify and Repair transaction
2015-08-24 17:15:58, Info CSI 00000113 [SR] Verify complete
2015-08-24 17:15:59, Info CSI 00000114 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:15:59, Info CSI 00000115 [SR] Beginning Verify and Repair transaction
2015-08-24 17:16:03, Info CSI 00000117 [SR] Verify complete
2015-08-24 17:16:04, Info CSI 00000118 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:16:04, Info CSI 00000119 [SR] Beginning Verify and Repair transaction
2015-08-24 17:16:11, Info CSI 0000011b [SR] Verify complete
2015-08-24 17:16:11, Info CSI 0000011c [SR] Verifying 100 (0x00000064) components
2015-08-24 17:16:12, Info CSI 0000011d [SR] Beginning Verify and Repair transaction
2015-08-24 17:16:18, Info CSI 0000011f [SR] Verify complete
2015-08-24 17:16:19, Info CSI 00000120 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:16:19, Info CSI 00000121 [SR] Beginning Verify and Repair transaction
2015-08-24 17:16:25, Info CSI 00000123 [SR] Verify complete
2015-08-24 17:16:26, Info CSI 00000124 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:16:26, Info CSI 00000125 [SR] Beginning Verify and Repair transaction
2015-08-24 17:16:32, Info CSI 00000127 [SR] Verify complete
2015-08-24 17:16:33, Info CSI 00000128 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:16:33, Info CSI 00000129 [SR] Beginning Verify and Repair transaction
2015-08-24 17:16:40, Info CSI 0000012c [SR] Verify complete
2015-08-24 17:16:40, Info CSI 0000012d [SR] Verifying 100 (0x00000064) components
2015-08-24 17:16:40, Info CSI 0000012e [SR] Beginning Verify and Repair transaction
2015-08-24 17:16:47, Info CSI 00000131 [SR] Verify complete
2015-08-24 17:16:48, Info CSI 00000132 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:16:48, Info CSI 00000133 [SR] Beginning Verify and Repair transaction
2015-08-24 17:16:53, Info CSI 00000135 [SR] Verify complete
2015-08-24 17:16:54, Info CSI 00000136 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:16:54, Info CSI 00000137 [SR] Beginning Verify and Repair transaction
2015-08-24 17:17:01, Info CSI 00000139 [SR] Verify complete
2015-08-24 17:17:02, Info CSI 0000013a [SR] Verifying 100 (0x00000064) components
2015-08-24 17:17:02, Info CSI 0000013b [SR] Beginning Verify and Repair transaction
2015-08-24 17:17:11, Info CSI 00000145 [SR] Verify complete
2015-08-24 17:17:12, Info CSI 00000146 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:17:12, Info CSI 00000147 [SR] Beginning Verify and Repair transaction
2015-08-24 17:17:18, Info CSI 00000149 [SR] Verify complete
2015-08-24 17:17:19, Info CSI 0000014a [SR] Verifying 100 (0x00000064) components
2015-08-24 17:17:19, Info CSI 0000014b [SR] Beginning Verify and Repair transaction
2015-08-24 17:17:25, Info CSI 0000014d [SR] Verify complete
2015-08-24 17:17:26, Info CSI 0000014e [SR] Verifying 100 (0x00000064) components
2015-08-24 17:17:26, Info CSI 0000014f [SR] Beginning Verify and Repair transaction
2015-08-24 17:17:31, Info CSI 00000151 [SR] Verify complete
2015-08-24 17:17:32, Info CSI 00000152 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:17:32, Info CSI 00000153 [SR] Beginning Verify and Repair transaction
2015-08-24 17:17:40, Info CSI 00000155 [SR] Verify complete
2015-08-24 17:17:40, Info CSI 00000156 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:17:40, Info CSI 00000157 [SR] Beginning Verify and Repair transaction
2015-08-24 17:17:50, Info CSI 00000159 [SR] Verify complete
2015-08-24 17:17:50, Info CSI 0000015a [SR] Verifying 100 (0x00000064) components
2015-08-24 17:17:50, Info CSI 0000015b [SR] Beginning Verify and Repair transaction
2015-08-24 17:17:59, Info CSI 0000015d [SR] Verify complete
2015-08-24 17:18:00, Info CSI 0000015e [SR] Verifying 100 (0x00000064) components
2015-08-24 17:18:00, Info CSI 0000015f [SR] Beginning Verify and Repair transaction
2015-08-24 17:18:16, Info CSI 00000166 [SR] Verify complete
2015-08-24 17:18:17, Info CSI 00000167 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:18:17, Info CSI 00000168 [SR] Beginning Verify and Repair transaction
2015-08-24 17:18:33, Info CSI 0000016a [SR] Verify complete
2015-08-24 17:18:34, Info CSI 0000016b [SR] Verifying 100 (0x00000064) components
2015-08-24 17:18:34, Info CSI 0000016c [SR] Beginning Verify and Repair transaction
2015-08-24 17:18:59, Info CSI 0000016e [SR] Verify complete
2015-08-24 17:19:00, Info CSI 0000016f [SR] Verifying 100 (0x00000064) components
2015-08-24 17:19:00, Info CSI 00000170 [SR] Beginning Verify and Repair transaction
2015-08-24 17:19:11, Info CSI 00000172 [SR] Verify complete
2015-08-24 17:19:11, Info CSI 00000173 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:19:11, Info CSI 00000174 [SR] Beginning Verify and Repair transaction
2015-08-24 17:19:17, Info CSI 00000176 [SR] Verify complete
2015-08-24 17:19:18, Info CSI 00000177 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:19:18, Info CSI 00000178 [SR] Beginning Verify and Repair transaction
2015-08-24 17:19:21, Info CSI 0000017a [SR] Verify complete
2015-08-24 17:19:22, Info CSI 0000017b [SR] Verifying 100 (0x00000064) components
2015-08-24 17:19:22, Info CSI 0000017c [SR] Beginning Verify and Repair transaction
2015-08-24 17:19:25, Info CSI 0000017e [SR] Verify complete
2015-08-24 17:19:26, Info CSI 0000017f [SR] Verifying 100 (0x00000064) components
2015-08-24 17:19:26, Info CSI 00000180 [SR] Beginning Verify and Repair transaction
2015-08-24 17:19:30, Info CSI 00000182 [SR] Verify complete
2015-08-24 17:19:31, Info CSI 00000183 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:19:31, Info CSI 00000184 [SR] Beginning Verify and Repair transaction
2015-08-24 17:19:43, Info CSI 000001a2 [SR] Verify complete
2015-08-24 17:19:44, Info CSI 000001a3 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:19:44, Info CSI 000001a4 [SR] Beginning Verify and Repair transaction
2015-08-24 17:19:47, Info CSI 000001a6 [SR] Verify complete
2015-08-24 17:19:48, Info CSI 000001a7 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:19:48, Info CSI 000001a8 [SR] Beginning Verify and Repair transaction
2015-08-24 17:19:49, Info CSI 000001aa [SR] Verify complete
2015-08-24 17:19:50, Info CSI 000001ab [SR] Verifying 100 (0x00000064) components
2015-08-24 17:19:50, Info CSI 000001ac [SR] Beginning Verify and Repair transaction
2015-08-24 17:19:54, Info CSI 000001ae [SR] Verify complete
2015-08-24 17:19:55, Info CSI 000001af [SR] Verifying 100 (0x00000064) components
2015-08-24 17:19:55, Info CSI 000001b0 [SR] Beginning Verify and Repair transaction
2015-08-24 17:20:01, Info CSI 000001b2 [SR] Verify complete
2015-08-24 17:20:03, Info CSI 000001b3 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:20:03, Info CSI 000001b4 [SR] Beginning Verify and Repair transaction
2015-08-24 17:20:12, Info CSI 000001b6 [SR] Verify complete
2015-08-24 17:20:13, Info CSI 000001b7 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:20:13, Info CSI 000001b8 [SR] Beginning Verify and Repair transaction
2015-08-24 17:20:24, Info CSI 000001bb [SR] Verify complete
2015-08-24 17:20:25, Info CSI 000001bc [SR] Verifying 100 (0x00000064) components
2015-08-24 17:20:25, Info CSI 000001bd [SR] Beginning Verify and Repair transaction
2015-08-24 17:20:38, Info CSI 000001bf [SR] Verify complete
2015-08-24 17:20:38, Info CSI 000001c0 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:20:38, Info CSI 000001c1 [SR] Beginning Verify and Repair transaction
2015-08-24 17:20:43, Info CSI 000001c3 [SR] Verify complete
2015-08-24 17:20:44, Info CSI 000001c4 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:20:44, Info CSI 000001c5 [SR] Beginning Verify and Repair transaction
2015-08-24 17:20:53, Info CSI 000001c7 [SR] Verify complete
2015-08-24 17:20:53, Info CSI 000001c8 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:20:53, Info CSI 000001c9 [SR] Beginning Verify and Repair transaction
2015-08-24 17:20:59, Info CSI 000001cb [SR] Verify complete
2015-08-24 17:21:00, Info CSI 000001cc [SR] Verifying 100 (0x00000064) components
2015-08-24 17:21:00, Info CSI 000001cd [SR] Beginning Verify and Repair transaction
2015-08-24 17:21:06, Info CSI 000001cf [SR] Verify complete
2015-08-24 17:21:06, Info CSI 000001d0 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:21:06, Info CSI 000001d1 [SR] Beginning Verify and Repair transaction
2015-08-24 17:21:16, Info CSI 000001d3 [SR] Verify complete
2015-08-24 17:21:17, Info CSI 000001d4 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:21:17, Info CSI 000001d5 [SR] Beginning Verify and Repair transaction
2015-08-24 17:21:30, Info CSI 000001fa [SR] Verify complete
2015-08-24 17:21:31, Info CSI 000001fb [SR] Verifying 100 (0x00000064) components
2015-08-24 17:21:31, Info CSI 000001fc [SR] Beginning Verify and Repair transaction
2015-08-24 17:21:40, Info CSI 000001fe [SR] Verify complete
2015-08-24 17:21:41, Info CSI 000001ff [SR] Verifying 100 (0x00000064) components
2015-08-24 17:21:41, Info CSI 00000200 [SR] Beginning Verify and Repair transaction
2015-08-24 17:22:02, Info CSI 00000202 [SR] Verify complete
2015-08-24 17:22:02, Info CSI 00000203 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:22:02, Info CSI 00000204 [SR] Beginning Verify and Repair transaction
2015-08-24 17:22:11, Info CSI 00000206 [SR] Verify complete
2015-08-24 17:22:11, Info CSI 00000207 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:22:11, Info CSI 00000208 [SR] Beginning Verify and Repair transaction
2015-08-24 17:22:27, Info CSI 0000020a [SR] Verify complete
2015-08-24 17:22:28, Info CSI 0000020b [SR] Verifying 100 (0x00000064) components
2015-08-24 17:22:28, Info CSI 0000020c [SR] Beginning Verify and Repair transaction
2015-08-24 17:22:39, Info CSI 0000020e [SR] Verify complete
2015-08-24 17:22:39, Info CSI 0000020f [SR] Verifying 100 (0x00000064) components
2015-08-24 17:22:39, Info CSI 00000210 [SR] Beginning Verify and Repair transaction
2015-08-24 17:22:51, Info CSI 00000212 [SR] Verify complete
2015-08-24 17:22:52, Info CSI 00000213 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:22:52, Info CSI 00000214 [SR] Beginning Verify and Repair transaction
2015-08-24 17:22:59, Info CSI 00000216 [SR] Verify complete
2015-08-24 17:23:00, Info CSI 00000217 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:23:00, Info CSI 00000218 [SR] Beginning Verify and Repair transaction
2015-08-24 17:23:06, Info CSI 0000021a [SR] Verify complete
2015-08-24 17:23:06, Info CSI 0000021b [SR] Verifying 100 (0x00000064) components
2015-08-24 17:23:06, Info CSI 0000021c [SR] Beginning Verify and Repair transaction
2015-08-24 17:23:13, Info CSI 0000021f [SR] Verify complete
2015-08-24 17:23:14, Info CSI 00000220 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:23:14, Info CSI 00000221 [SR] Beginning Verify and Repair transaction
2015-08-24 17:23:19, Info CSI 00000223 [SR] Verify complete
2015-08-24 17:23:19, Info CSI 00000224 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:23:19, Info CSI 00000225 [SR] Beginning Verify and Repair transaction
2015-08-24 17:23:37, Info CSI 00000227 [SR] Verify complete
2015-08-24 17:23:38, Info CSI 00000228 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:23:38, Info CSI 00000229 [SR] Beginning Verify and Repair transaction
2015-08-24 17:23:47, Info CSI 0000022b [SR] Verify complete
2015-08-24 17:23:47, Info CSI 0000022c [SR] Verifying 100 (0x00000064) components
2015-08-24 17:23:47, Info CSI 0000022d [SR] Beginning Verify and Repair transaction
2015-08-24 17:23:54, Info CSI 0000022f [SR] Verify complete
2015-08-24 17:23:55, Info CSI 00000230 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:23:55, Info CSI 00000231 [SR] Beginning Verify and Repair transaction
2015-08-24 17:24:03, Info CSI 00000233 [SR] Verify complete
2015-08-24 17:24:04, Info CSI 00000234 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:24:04, Info CSI 00000235 [SR] Beginning Verify and Repair transaction
2015-08-24 17:24:11, Info CSI 00000237 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-08-24 17:24:13, Info CSI 00000239 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-08-24 17:24:13, Info CSI 0000023a [SR] This component was referenced by [l:158{79}]"Package_16_for_KB948465~31bf3856ad364e35~x86~~6.0.1.18005.948465-49_neutral_GDR"
2015-08-24 17:24:16, Info CSI 0000023c [SR] Verify complete
2015-08-24 17:24:17, Info CSI 0000023d [SR] Verifying 100 (0x00000064) components
2015-08-24 17:24:17, Info CSI 0000023e [SR] Beginning Verify and Repair transaction
2015-08-24 17:24:23, Info CSI 00000240 [SR] Verify complete
2015-08-24 17:24:24, Info CSI 00000241 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:24:24, Info CSI 00000242 [SR] Beginning Verify and Repair transaction
2015-08-24 17:24:33, Info CSI 00000244 [SR] Verify complete
2015-08-24 17:24:34, Info CSI 00000245 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:24:34, Info CSI 00000246 [SR] Beginning Verify and Repair transaction
2015-08-24 17:24:41, Info CSI 00000249 [SR] Verify complete
2015-08-24 17:24:41, Info CSI 0000024a [SR] Verifying 100 (0x00000064) components
2015-08-24 17:24:41, Info CSI 0000024b [SR] Beginning Verify and Repair transaction
2015-08-24 17:24:54, Info CSI 0000024d [SR] Verify complete
2015-08-24 17:24:55, Info CSI 0000024e [SR] Verifying 100 (0x00000064) components
2015-08-24 17:24:55, Info CSI 0000024f [SR] Beginning Verify and Repair transaction
2015-08-24 17:25:00, Info CSI 00000251 [SR] Verify complete
2015-08-24 17:25:01, Info CSI 00000252 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:25:01, Info CSI 00000253 [SR] Beginning Verify and Repair transaction
2015-08-24 17:25:07, Info CSI 00000255 [SR] Verify complete
2015-08-24 17:25:08, Info CSI 00000256 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:25:08, Info CSI 00000257 [SR] Beginning Verify and Repair transaction
2015-08-24 17:25:15, Info CSI 00000259 [SR] Verify complete
2015-08-24 17:25:15, Info CSI 0000025a [SR] Verifying 100 (0x00000064) components
2015-08-24 17:25:15, Info CSI 0000025b [SR] Beginning Verify and Repair transaction
2015-08-24 17:25:23, Info CSI 0000025e [SR] Verify complete
2015-08-24 17:25:24, Info CSI 0000025f [SR] Verifying 100 (0x00000064) components
2015-08-24 17:25:24, Info CSI 00000260 [SR] Beginning Verify and Repair transaction
2015-08-24 17:25:32, Info CSI 00000268 [SR] Verify complete
2015-08-24 17:25:33, Info CSI 00000269 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:25:33, Info CSI 0000026a [SR] Beginning Verify and Repair transaction
2015-08-24 17:25:42, Info CSI 0000026c [SR] Verify complete
2015-08-24 17:25:42, Info CSI 0000026d [SR] Verifying 100 (0x00000064) components
2015-08-24 17:25:42, Info CSI 0000026e [SR] Beginning Verify and Repair transaction
2015-08-24 17:25:53, Info CSI 00000270 [SR] Verify complete
2015-08-24 17:25:54, Info CSI 00000271 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:25:54, Info CSI 00000272 [SR] Beginning Verify and Repair transaction
2015-08-24 17:26:02, Info CSI 00000274 [SR] Verify complete
2015-08-24 17:26:03, Info CSI 00000275 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:26:03, Info CSI 00000276 [SR] Beginning Verify and Repair transaction
2015-08-24 17:26:05, Info CSI 00000278 [SR] Verify complete
2015-08-24 17:26:06, Info CSI 00000279 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:26:06, Info CSI 0000027a [SR] Beginning Verify and Repair transaction
2015-08-24 17:26:14, Info CSI 0000027c [SR] Verify complete
2015-08-24 17:26:14, Info CSI 0000027d [SR] Verifying 100 (0x00000064) components
2015-08-24 17:26:14, Info CSI 0000027e [SR] Beginning Verify and Repair transaction
2015-08-24 17:26:27, Info CSI 00000280 [SR] Verify complete
2015-08-24 17:26:28, Info CSI 00000281 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:26:28, Info CSI 00000282 [SR] Beginning Verify and Repair transaction
2015-08-24 17:26:37, Info CSI 00000284 [SR] Verify complete
2015-08-24 17:26:38, Info CSI 00000285 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:26:38, Info CSI 00000286 [SR] Beginning Verify and Repair transaction
2015-08-24 17:26:44, Info CSI 00000288 [SR] Verify complete
2015-08-24 17:26:45, Info CSI 00000289 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:26:45, Info CSI 0000028a [SR] Beginning Verify and Repair transaction
2015-08-24 17:27:03, Info CSI 0000028c [SR] Verify complete
2015-08-24 17:27:04, Info CSI 0000028d [SR] Verifying 100 (0x00000064) components
2015-08-24 17:27:04, Info CSI 0000028e [SR] Beginning Verify and Repair transaction
2015-08-24 17:27:10, Info CSI 00000290 [SR] Verify complete
2015-08-24 17:27:11, Info CSI 00000291 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:27:11, Info CSI 00000292 [SR] Beginning Verify and Repair transaction
2015-08-24 17:27:14, Info CSI 00000294 [SR] Verify complete
2015-08-24 17:27:15, Info CSI 00000295 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:27:15, Info CSI 00000296 [SR] Beginning Verify and Repair transaction
2015-08-24 17:27:21, Info CSI 00000298 [SR] Verify complete
2015-08-24 17:27:22, Info CSI 00000299 [SR] Verifying 100 (0x00000064) components
2015-08-24 17:27:22, Info CSI 0000029a [SR] Beginning Verify and Repair transaction
2015-08-24 17:27:32, Info CSI 000002a8 [SR] Verify complete
2015-08-24 17:27:33, Info CSI 000002a9 [SR] Verifying 60 (0x0000003c) components
2015-08-24 17:27:33, Info CSI 000002aa [SR] Beginning Verify and Repair transaction
2015-08-24 17:27:37, Info CSI 000002ac [SR] Verify complete
2015-08-24 17:27:37, Info CSI 000002ad [SR] Repairing 1 components
2015-08-24 17:27:37, Info CSI 000002ae [SR] Beginning Verify and Repair transaction
2015-08-24 17:27:37, Info CSI 000002b0 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-08-24 17:27:37, Info CSI 000002b2 [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-08-24 17:27:37, Info CSI 000002b3 [SR] This component was referenced by [l:158{79}]"Package_16_for_KB948465~31bf3856ad364e35~x86~~6.0.1.18005.948465-49_neutral_GDR"
2015-08-24 17:27:37, Info CSI 000002b5 [SR] Repair complete
2015-08-24 17:27:37, Info CSI 000002b6 [SR] Committing transaction
2015-08-24 17:27:37, Info CSI 000002ba [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
|
|
24.08.2015, 17:13
| #14 |
| /// Malwareteam | Windows Vista Crash Dump [gelöst] Okay die Fehler sollten nichts mit deinem Bluescreen zu tun haben. Hast du jetzt noch Probleme? Wenn ja, haben sie sich gebessert und mach bitte neue Logs mit WhoCrashed
__________________ Mfg, Rafael ~ I'm storm. I'm calm. I'm fire. I'm ice. I'm burningice. ~ Unterstütze uns mit einer Spende ......... Lob, Kritik oder Wünsche ......... .......... Folge uns auf Facebook .......... |
|
25.08.2015, 09:01
| #15 |
| | Windows Vista Crash Dump [gelöst] Heute Morgen hat er sich aufgehängt beim Booten, aber es kam kein Bluescreen. Danach kam die Frage ob Windows normal gestartet werden soll oder im abgesicherten Modus. Windows konnte normal gestartet werden und lief seitdem auch ohne Probleme. Ihr ein neues WhoCrashed Log: Code:
ATTFilter Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 23.08.2015 09:24:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini082315-03.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x240A5B)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82648A5B, 0xFFFFFFFF95403C38, 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 Sun 23.08.2015 09:24:55 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF82648A5B, 0xFFFFFFFF95403C38, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe KERNEL_MODE_EXCEPTION_NOT_HANDLED
On Sun 23.08.2015 08:52:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini082315-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x982C2)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFEC, 0x0, 0xFFFFFFFF8247483F, 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 Sun 23.08.2015 08:40:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini082315-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x265D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A0E65D, 0xFFFFFFFF8EE9F970, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Microsoft Dateisystem-Filter-Manager
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 Sat 22.08.2015 19:22:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini082215-03.dmp
This was probably caused by the following module: hal.dll (hal+0x9DC1)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF824595E0, 0xFFFFFFFF8926FB64, 0xFFFFFFFF8926F860)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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: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
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
15 crash dumps have been found and analyzed. Only 10 are included in this report. 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
ntkrpamp.exe
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.
|
|
| Themen zu Windows Vista Crash Dump |
| anhang, arten, bildschirm, blauer, blauer bildschirm, crash, crash dump, pcs, starte, starten, vista, windows, windows vista |
Linear-Darstellung
