Écran bleu (BSOD) qcamain1.sys Alienware 17R2 W10

Ordinateurs portables - Matériel

Ordinateurs portables - Matériel
Rejoignez les discussions sur les ordinateurs portables DELL.

Écran bleu (BSOD) qcamain1.sys Alienware 17R2 W10

Cette question n'a pas de réponse

Bonjour,


Intel Core i7-4710HQ CPU @ 2.50GHz 16Go RAM

Intel HD Graphics 4600 Windows 8.1 64 bits Famille à l'achat, j'ai effectué une mise à jour vers Windows 10 64 bits Famille.


Depuis 2 mois j'ai des crashs à répétition tous les jours, ils varient de 1 à plus de 10.

J'ai tenté beaucoup de solutions :

- à commencer par la mise à jour de tous les drivers de mon ordinateur via le site de Dell, puis via d'autres sites et logiciels.

- j'ai effectué des scans antivirus avec différents logiciels.

- j'ai exécuté les diagnostics déjà présents sur l'ordinateur.

- j'ai essayé les diverses solutions proposées sur les différents forums et vidéos YouTube pour ce problème.

- j'ai effectué une remise à zéro de Windows en supprimant tout, puis une réparation via USB boot média création tool Windows 10.


Le problème ne survient pas en mode avion.

Merci d'avance, Mickael.


Crash Dump Analysis


Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Thu 16/11/2017 12:21:10 your computer crashed
crash dump file: C:\WINDOWS\Minidump\111617-36468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80124086370)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (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 16/11/2017 12:21:10 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x1182A8)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80124086370)
Error: DPC_WATCHDOG_VIOLATION
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
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 DPC_WATCHDOG_VIOLATION



On Thu 16/11/2017 12:20:19 your computer crashed
crash dump file: C:\WINDOWS\Minidump\111617-31890-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 Thu 16/11/2017 12:16:45 your computer crashed
crash dump file: C:\WINDOWS\Minidump\111617-36562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8022B693370)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (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 16/11/2017 11:24:52 your computer crashed
crash dump file: C:\WINDOWS\Minidump\111617-36500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8002C279370, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (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.




Conclusion


5 crash dumps have been found and 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:

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.

Toutes les réponses
  • Bonjour Mica0703,

    Merci de nous avoir contact.

    Je vous invite à installer la dernière version du Bios, et d’essayer aussi avec la version générique du pilote Wifi ou une version précédente.

    Je reste disponible si besoin.

    Passez une excellente fin de journée, cordialement.

    Mohamed

  • Bonjour,

    Le Bios est à jour, j'ai essayé tous les pilotes un à un pour la Wifi rien n'y fait pas même le standard.

    J'ai aussi réinitialisé les paramètres du Bios, pas de résultat positif.

    Cordialement, Mickael.

  • Bonjour Mica0703,

    Je vous invite à me communiquer le service Tag de votre système en message privé.

    Je viens de vous envoyer une demande d'ajout à la liste des amis.

    Bien cordialement.

    Mohamed