Crash minidump + sysdata.xml sur CC Première Pro
Fermé
mikusdu88
Messages postés
2
Date d'inscription
mardi 2 octobre 2018
Statut
Membre
Dernière intervention
2 octobre 2018
-
2 oct. 2018 à 22:26
mikusdu88 Messages postés 2 Date d'inscription mardi 2 octobre 2018 Statut Membre Dernière intervention 2 octobre 2018 - 2 oct. 2018 à 22:58
mikusdu88 Messages postés 2 Date d'inscription mardi 2 octobre 2018 Statut Membre Dernière intervention 2 octobre 2018 - 2 oct. 2018 à 22:58
A voir également:
- Crash minidump + sysdata.xml sur CC Première Pro
- Premiere pro gratuit - Télécharger - Montage & Édition
- I14 pro max - Guide
- Cc cleaner - Télécharger - Nettoyage
- Clé d'activation windows 10 pro - Guide
- Cc mail - Guide
1 réponse
mikusdu88
Messages postés
2
Date d'inscription
mardi 2 octobre 2018
Statut
Membre
Dernière intervention
2 octobre 2018
2 oct. 2018 à 22:58
2 oct. 2018 à 22:58
Je continue la bataille, je fais des mises à jours sur mon système,
je profite pour vous donnez mes 12 mini-dumpings
System Information (local)
--------------------------------------------------------------------------------
Computer name: MKUS-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., 970 PRO GAMING/AURA
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 12776718336 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are disabled for your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Tue 02/10/2018 21:30:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100218-11934-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800B70E028, 0xB6000000, 0x100153)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is 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 Tue 02/10/2018 19:45:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100218-12214-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800B8AB028, 0xB6000000, 0x100153)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is 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 Tue 02/10/2018 19:44:17 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100218-12074-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880035DE180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 02/10/2018 19:07:57 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: hal.dll (hal!halreturntofirmware+0xb25)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003765180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
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 29/09/2018 14:07:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092918-12246-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003765180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
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 25/01/2018 14:35:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012518-72056-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA63A0)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: CRITICAL_SERVICE_FAILED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 23/01/2018 14:57:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012318-72072-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA63A0)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: CRITICAL_SERVICE_FAILED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
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 21/01/2018 11:37:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012118-72010-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA63A0)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: CRITICAL_SERVICE_FAILED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 16/01/2018 16:36:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011618-72072-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA63A0)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: CRITICAL_SERVICE_FAILED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
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 11/11/2017 20:19:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\$R3SV558.DMP
This was probably caused by the following module: aswsp.sys (aswSP+0x3E83F)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8005120028, 0xB6000000, 0x100153)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsp.sys .
Google query: aswsp.sys WHEA_UNCORRECTABLE_ERROR
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 12 crash dumps have been found. Only 10 have been analyzed. 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:
aswsp.sys
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.
je profite pour vous donnez mes 12 mini-dumpings
System Information (local)
--------------------------------------------------------------------------------
Computer name: MKUS-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., 970 PRO GAMING/AURA
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 12776718336 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are disabled for your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Tue 02/10/2018 21:30:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100218-11934-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800B70E028, 0xB6000000, 0x100153)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is 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 Tue 02/10/2018 19:45:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100218-12214-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800B8AB028, 0xB6000000, 0x100153)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is 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 Tue 02/10/2018 19:44:17 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100218-12074-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880035DE180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 02/10/2018 19:07:57 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: hal.dll (hal!halreturntofirmware+0xb25)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003765180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
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 29/09/2018 14:07:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092918-12246-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003765180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
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 25/01/2018 14:35:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012518-72056-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA63A0)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: CRITICAL_SERVICE_FAILED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 23/01/2018 14:57:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012318-72072-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA63A0)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: CRITICAL_SERVICE_FAILED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
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 21/01/2018 11:37:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012118-72010-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA63A0)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: CRITICAL_SERVICE_FAILED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 16/01/2018 16:36:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011618-72072-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA63A0)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: CRITICAL_SERVICE_FAILED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
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 11/11/2017 20:19:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\$R3SV558.DMP
This was probably caused by the following module: aswsp.sys (aswSP+0x3E83F)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8005120028, 0xB6000000, 0x100153)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsp.sys .
Google query: aswsp.sys WHEA_UNCORRECTABLE_ERROR
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 12 crash dumps have been found. Only 10 have been analyzed. 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:
aswsp.sys
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.
