Blue Screen incessant
HeroCop
-
HeroCop -
HeroCop -
Bonjour,
Je suis désespérément à la recherche d'une solution pour ces blue screen incessant, je n'arrive plus à travailler tranquillement.
Dès que je repositionne l'écran, que je bouge brusquement mon PC ou parfois comme ça sans raison, mon ordinateur répond avec un merveilleux Blue Screen. Je n'ai pas noté les codes d'erreur s'affichant dessus, si besoin je le noterai à la prochaine manifestation.
Fabricant : Acer
Modèle : Swift SF114-31
Processeur : Intel(R) Pentium(R) CPU N3710 @ 1.60GHz 1.60 GHz
RAM : 4Go
Type du système : 64bits, processeur x64
Je pensais qu'il s'agissait un problème d'espace sur le disque dur mais il me reste plus de 5go d'espace libre.
Merci d'avance pour votre aide!
Je suis désespérément à la recherche d'une solution pour ces blue screen incessant, je n'arrive plus à travailler tranquillement.
Dès que je repositionne l'écran, que je bouge brusquement mon PC ou parfois comme ça sans raison, mon ordinateur répond avec un merveilleux Blue Screen. Je n'ai pas noté les codes d'erreur s'affichant dessus, si besoin je le noterai à la prochaine manifestation.
Fabricant : Acer
Modèle : Swift SF114-31
Processeur : Intel(R) Pentium(R) CPU N3710 @ 1.60GHz 1.60 GHz
RAM : 4Go
Type du système : 64bits, processeur x64
Je pensais qu'il s'agissait un problème d'espace sur le disque dur mais il me reste plus de 5go d'espace libre.
Merci d'avance pour votre aide!
A voir également:
- Blue Screen incessant
- Blue screen - Guide
- Screen whatsapp - Accueil - Messagerie instantanée
- Blue griffon - Télécharger - HTML
- Apowersoft screen recorder - Télécharger - Capture d'écran
- Double screen pc - Guide
3 réponses
Bonjour HeroCop,
Il est mieux que tu mets les codes erreurs que tu as pour que nous puissions mieux t'aider.
Cordialement,
Il est mieux que tu mets les codes erreurs que tu as pour que nous puissions mieux t'aider.
Cordialement,
Bonjour,
J’ai eu un nouveau blue screen : le code est 0x000001d3
J’ai vu qu’il s’agissait peut etre d’un problème de pilote mais je n’ai aucune mise à jour de disponible.
J’ai eu un nouveau blue screen : le code est 0x000001d3
J’ai vu qu’il s’agissait peut etre d’un problème de pilote mais je n’ai aucune mise à jour de disponible.
Je n'ai aucun signal attention sur le gestionnaire, tout semble bien fonctionner et à jour.
EDIT :
Comme vu sur certains posts, j'ai utilisé le logiciel WhoCrashed, voici le rapport :
System Information (local)
--------------------------------------------------------------------------------
Computer name: LAPTOP-PRRRPMKB
Windows version: Windows 10 , 10.0, version 1703, build: 15063
Windows dir: C:\WINDOWS
Hardware: Swift SF114-31 , Acer, Oxford2
CPU: GenuineIntel Intel(R) Pentium(R) CPU N3710 @ 1.60GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 4202971136 bytes (3,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Wed 19/06/2019 16:06:49 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061919-12546-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Wed 19/06/2019 15:02:35 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061919-20343-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Fri 14/06/2019 20:34:52 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061419-17171-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Fri 14/06/2019 17:27:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061419-13281-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Thu 13/06/2019 16:33:17 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061319-11718-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Wed 12/06/2019 01:56:42 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061219-13562-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Wed 12/06/2019 01:35:42 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061219-12718-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Wed 12/06/2019 00:56:09 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061219-18796-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Sun 02/06/2019 16:42:59 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\060219-12906-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\061919-14671-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 13 crash dumps have been found. Only 10 have been analyzed. Only 9 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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.
EDIT :
Comme vu sur certains posts, j'ai utilisé le logiciel WhoCrashed, voici le rapport :
System Information (local)
--------------------------------------------------------------------------------
Computer name: LAPTOP-PRRRPMKB
Windows version: Windows 10 , 10.0, version 1703, build: 15063
Windows dir: C:\WINDOWS
Hardware: Swift SF114-31 , Acer, Oxford2
CPU: GenuineIntel Intel(R) Pentium(R) CPU N3710 @ 1.60GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 4202971136 bytes (3,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Wed 19/06/2019 16:06:49 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061919-12546-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Wed 19/06/2019 15:02:35 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061919-20343-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Fri 14/06/2019 20:34:52 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061419-17171-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Fri 14/06/2019 17:27:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061419-13281-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Thu 13/06/2019 16:33:17 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061319-11718-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Wed 12/06/2019 01:56:42 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061219-13562-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Wed 12/06/2019 01:35:42 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061219-12718-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Wed 12/06/2019 00:56:09 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061219-18796-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
On Sun 02/06/2019 16:42:59 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\060219-12906-01.dmp
This was probably caused by the following module: qcamain1.sys (Qcamain10x64+0x10F8A0)
Bugcheck code: 0x1D3 (0x3EB, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 CUSTOM_ERROR
The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\061919-14671-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 13 crash dumps have been found. Only 10 have been analyzed. Only 9 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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.
