magellan
Modérâleur
Staff
J'en viens à me dire que la CM a a un souci :/ ce qui pue le retour SAV. Franchement si la machine est neuve... retour SAV sans pitié.
jacktara
Modérateur
Staff
+1
Si SAV encore valable et recherche de solution sur plus de une semaine. Retour immédiat.
Si SAV encore valable et recherche de solution sur plus de une semaine. Retour immédiat.
power971
Habitué
Bonjour à Tous !
Vous pensez vraiment qu'il n'y a pas d'autre solution que le retour SAV ? Ca va être très difficile pour moi...
Sinon, mon dernier rapport :
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 21/06/2016 22:30:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062116-5921-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80336AFEC1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Tue 21/06/2016 22:30:24 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80336AFEC1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Tue 21/06/2016 19:03:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062116-5968-01.dmp
This was probably caused by the following module: intcdaud.sys (IntcDAud+0xD37A)
Bugcheck code: 0x139 (0x3, 0xFFFFD001D1AD1510, 0xFFFFD001D1AD1468, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\intcdaud.sys
product: Intel(R) Display Audio
company: Intel(R) Corporation
description: Intel(R) Display Audio Driver
Bug check description: The kernel has detected the corruption of a critical data structure.
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: intcdaud.sys (Intel(R) Display Audio Driver, Intel(R) Corporation).
Google query: Intel(R) Corporation KERNEL_SECURITY_CHECK_FAILURE
On Mon 20/06/2016 22:43:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062016-6281-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF802A4B0AC1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Mon 20/06/2016 22:00:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062016-6031-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x5A277)
Bugcheck code: 0x139 (0x3, 0xFFFFD0006551C590, 0xFFFFD0006551C4E8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
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: qcamain1.sys .
Google query: qcamain1.sys KERNEL_SECURITY_CHECK_FAILURE
On Sat 18/06/2016 18:36:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061816-5843-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00026C91EB0, 0xFFFFD00026C91E08, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
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 18/06/2016 02:01:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061716-6125-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFD0011249C780, 0xFFFFD0011249C6D8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 17/06/2016 22:44:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061716-6375-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF800F2098C1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Tue 14/06/2016 13:55:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061416-5984-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x5A277)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF800F0108C1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
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: qcamain1.sys .
Google query: qcamain1.sys IRQL_NOT_LESS_OR_EQUAL
On Tue 14/06/2016 04:11:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061416-6015-01.dmp
This was probably caused by the following module: intcdaud.sys (IntcDAud+0xD37A)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF802F5CF3C1F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\intcdaud.sys
product: Intel(R) Display Audio
company: Intel(R) Corporation
description: Intel(R) Display Audio Driver
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.
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: intcdaud.sys (Intel(R) Display Audio Driver, Intel(R) Corporation).
Google query: Intel(R) Corporation IRQL_NOT_LESS_OR_EQUAL
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
13 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:
intcdaud.sys (Intel(R) Display Audio Driver, Intel(R) Corporation)
qcamain1.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.
Vous pensez vraiment qu'il n'y a pas d'autre solution que le retour SAV ? Ca va être très difficile pour moi...
Sinon, mon dernier rapport :
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 21/06/2016 22:30:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062116-5921-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80336AFEC1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Tue 21/06/2016 22:30:24 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80336AFEC1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Tue 21/06/2016 19:03:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062116-5968-01.dmp
This was probably caused by the following module: intcdaud.sys (IntcDAud+0xD37A)
Bugcheck code: 0x139 (0x3, 0xFFFFD001D1AD1510, 0xFFFFD001D1AD1468, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\intcdaud.sys
product: Intel(R) Display Audio
company: Intel(R) Corporation
description: Intel(R) Display Audio Driver
Bug check description: The kernel has detected the corruption of a critical data structure.
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: intcdaud.sys (Intel(R) Display Audio Driver, Intel(R) Corporation).
Google query: Intel(R) Corporation KERNEL_SECURITY_CHECK_FAILURE
On Mon 20/06/2016 22:43:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062016-6281-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF802A4B0AC1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Mon 20/06/2016 22:00:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062016-6031-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x5A277)
Bugcheck code: 0x139 (0x3, 0xFFFFD0006551C590, 0xFFFFD0006551C4E8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
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: qcamain1.sys .
Google query: qcamain1.sys KERNEL_SECURITY_CHECK_FAILURE
On Sat 18/06/2016 18:36:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061816-5843-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00026C91EB0, 0xFFFFD00026C91E08, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
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 18/06/2016 02:01:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061716-6125-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFD0011249C780, 0xFFFFD0011249C6D8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 17/06/2016 22:44:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061716-6375-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF800F2098C1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Tue 14/06/2016 13:55:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061416-5984-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x5A277)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF800F0108C1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
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: qcamain1.sys .
Google query: qcamain1.sys IRQL_NOT_LESS_OR_EQUAL
On Tue 14/06/2016 04:11:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061416-6015-01.dmp
This was probably caused by the following module: intcdaud.sys (IntcDAud+0xD37A)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF802F5CF3C1F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\intcdaud.sys
product: Intel(R) Display Audio
company: Intel(R) Corporation
description: Intel(R) Display Audio Driver
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.
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: intcdaud.sys (Intel(R) Display Audio Driver, Intel(R) Corporation).
Google query: Intel(R) Corporation IRQL_NOT_LESS_OR_EQUAL
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
13 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:
intcdaud.sys (Intel(R) Display Audio Driver, Intel(R) Corporation)
qcamain1.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.
_Othy_
Helper
salut
tes crash varient
"qcamain1.sys" (Qualcomm Atheros, le pilote carte réseau sans fil)
une autre fois c'est a cause de "intcdaud.sys" (intel audio)
avais tu mis à jour TOUS tes drivers comme demandé précédemment ??
https://sdi-tool.org/
tes crash varient
"qcamain1.sys" (Qualcomm Atheros, le pilote carte réseau sans fil)
une autre fois c'est a cause de "intcdaud.sys" (intel audio)
avais tu mis à jour TOUS tes drivers comme demandé précédemment ??
https://sdi-tool.org/
Eldarium
Modo d'Inde Rond
Staff
Meilleure réponse
Tu as essayé de réinitialiser ta machine et de remettre les pilotes propres et à jour ? Car si c'est toujours pas bon, c'est soit que les pilotes prévus pour cette machines ont été développés avec les pieds soit qu'un ou plusieurs composants sont foireux.
Eldarium
Modo d'Inde Rond
Staff
Peut-être une configuration d'usine un peu mal faite, sait-on jamais avec les master des grandes marques de PC... Le principal c'est que ça tourne comme il faut. 
magellan
Modérâleur
Staff
Eldarium :
Peut-être une configuration d'usine un peu mal faite, sait-on jamais avec les master des grandes marques de PC... Le principal c'est que ça tourne comme il faut.
+1 malheureusement. Bien des masters ne sont pas aussi affinés que nécessaire, et souvent lorsqu'un OS est relativement "vert" (W10...) on peut avoir des pilotes buggés ou incomplets.
Dernières actus
-
Une nouvelle PSP sans exclus serait sans intérêt pour Sony
17/05/2024 15:59
-
Assassin’s Creed Shadows moins cher : où précommander le jeu au meilleur prix ?
17/05/2024 14:57
-
Meilleure TV 4K 55 pouces : quel modèle choisir en 2024 ?
17/05/2024 14:44
-
Meilleure liseuse électronique : quel modèle choisir en 2024 ?
17/05/2024 13:32
-
ROG Ally X : Asus dope sa console portable, en attendant une vraie Gen2
17/05/2024 13:23
-
Ghost of Tsushima mélange FSR3 et DLSS, ne jetez pas encore votre vieille GeForce !
17/05/2024 10:45
Derniers messages publiés
Statistiques globales
- Discussions
- 730 167
- Membres
- 1 586 465
- Dernier membre
- Gordon_99
Partager cette page