Problème d'écrans bleus sur un pc portable gamer

[BSOD_ma_tuer]

Bonjour,

J'ai récemment fait l'acquisition d'un pc portable Lenovo Y50-70.

Le lendemain même de l'achat, tandis que je découvrais les fonctionnalités de windows 8.1 (installé d'office) : mon premier BSOD avec comme erreur IRQL_NOT_LESS_OR_EQUAL.
Quelques jours plus tard la même erreur se reproduit, puis de plus en plus fréquemment. Je cherche alors des solutions sur internet, parcours de nombreux forums... Je découvre les .dmp, le journal d'événements etc... J'essaie toutes sortes de procédures ; mises à jours, nettoyages avec Adwcleaner ou MalwaresBytes, vérification des drivers, diagnostic de mémoire (utilitaire windows) en espérant résoudre mon problème tout seul mais en vain.

Je finis par le réinitialiser, (choisissez cette option si vous prévoyez de recycler le pc) en me disant que j'ai peut-être installé un truc de travers ou autre.

Là encore la procédure semble impossible puisque plusieurs fois, à des étapes de complétion complètement aléatoires, le pc n'est pas d'accord et redémarre sur toujours la même erreur, IRQL_NOT_LESS_OR_EQUAL.

Dès que j'ai pu ré-accéder au menu de redémarrage avancé, j'ai choisi une simple "actualisation" plutôt, elle finit par se faire.

J'ai eu 1 ou 2 jours tranquille, puis le problème est revenu. J'effectue une nouvelle actualisation, mais les écrans bleus persistent.

J'ai également essayé memtest86 5.1, sur clé usb. Un premier test de 4 heures et des poussières (4 passes) : pas d'erreurs. Un second test sur tous les cpu en parallèle (10 passes) qui a pris environ 8 heures : pas d'erreurs.

Ma conclusion : je n'arriverai pas à résoudre mon problème seul.

Voici le seul rapport WhoCrashed qu'il me reste, un passage récent de Ccleaner les ayant tous effacés...


Crash Dump Analysis


Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 07/11/2014 15:07:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110714-16671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x93 (0x3BC, 0xFFFFC0015B603000, 0x0, 0x1)
Error: INVALID_KERNEL_HANDLE
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 an invalid or protected handle was passed to
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 07/11/2014 15:07:36 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: 0x93 (0x3BC, 0xFFFFC0015B603000, 0x0, 0x1)
Error: INVALID_KERNEL_HANDLE
Bug check description: This bug check indicates that an invalid or protected handle was passed to
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 07/11/2014 14:31:49 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110714-11250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0xA (0xFFFFFA800720AF48, 0x2, 0x1, 0xFFFFF8017009EA56)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Fri 07/11/2014 04:02:29 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110714-14140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0xA (0xFFFFFA95A5D68FC0, 0x2, 0x0, 0xFFFFF8022C08FBFC)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Fri 07/11/2014 03:55:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110714-13656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0xA (0xFFFFFAB99CCE7FF0, 0x2, 0x0, 0xFFFFF8018249CBFC)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Fri 07/11/2014 03:25:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110714-9578-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x20A34)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80150AB3A34, 0xFFFFD000C6D1CBB8, 0xFFFFD000C6D1C3C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 07/11/2014 01:44:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110714-9968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0xA (0xFFFFFA899CCE7FF0, 0x2, 0x0, 0xFFFFF8005C691BFC)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.




Conclusion


7 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


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.

Merci de votre attention.

[gh78]

Hello
rapporte le vite à ton magasin pour un échange, ce bsod apparait uniquement quand tu as un problème matériel lié à la ram ou une carte graphique Nvidia. Vu que tu viens de l'acquérir, il est sous garantie et ne peuvent pas te refuser l'échange. Une petite recherche sur google en direct s'il te ne croient pas leur feront comprendre que c'est la stricte vérité.