Merci de vous connecter ou de vous inscrire.

Auteur Sujet: BSOD En sortie de veille?  (Lu 2066 fois)

0 Membres et 1 Invité sur ce sujet

gmaster971

  • Newbie
  • *
  • :
  • Hors ligne Hors ligne
  • Messages: 1
BSOD En sortie de veille?
« le: juin 22, 2016, 08:33:21 pm »

Bonjour à tous. Je suis confronté à un problème assez épineux sur mon PC portable tout neuf (MSI GS60 6QC), et j'espère que vous pourrez m'aider.
Comme le dit le titre, l'ordinateur fait des BSOD en sortie de veille. Il ne le fait pas à tous les coups, mais au moins dans 60% des cas. Et comme vous le savez, en cas de travail en court, c'est assez ennuyeux.
Vous pouvez trouver ci-dessous le rapport d'erreur WhoCrashed de ces BSOD,ainsi que la config de l'ordi. N'étant pas familier avec ce domaine, je ne sais comment interpréter les résultats de ce rapport.
PS: J'ai acheté l'ordinateur sans OS, pourrait-il y avoir un lien?

--------------------------------------------------------------------------------
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.
IP archivée

johnt31

  • Expert
  • ****
  • :
  • Hors ligne Hors ligne
  • Messages: 15 480
Re : BSOD En sortie de veille?
« Réponse #1 le: juin 23, 2016, 08:48:26 am »

Slt

installe bleuscreenviewer  fais moi un screen de la première fenetre que je vois

qui cause le souci
IP archivée
Overcloking Master pourquoi as tu fermé tes portes :(

E4400 2Ghz@ 3.3Ghz air cooling



Skype => johnt3100

john9871j

  • Newbie
  • *
  • :
  • Hors ligne Hors ligne
  • Messages: 2
Re : BSOD En sortie de veille?
« Réponse #2 le: septembre 23, 2016, 11:37:59 am »

Je rencontre Kernel Security Check problème de défaillance dans mon pc
IP archivée

john9871j

  • Newbie
  • *
  • :
  • Hors ligne Hors ligne
  • Messages: 2
Re : BSOD En sortie de veille?
« Réponse #3 le: septembre 27, 2016, 10:31:59 am »

It take me 3 days to fix this issue
And I was finally found the Fix.
here is the link
if anybody wanna look

http://www.deskdecode.com/kernel-security-check-failure-0x00000139/
IP archivée