Ecran bleu

Le matériel conseillé, compatibilité, problèmes, périphériques.

Ecran bleu

Messagepar arthurcorre_ » Lun 28 Aoû 2017 14:08

Bonjour,

Ci-joint vous trouverez le rapport d'erreurs de WhoCrashed. Les écrans bleus ne surviennent uniquement lorsque je joue.

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 27/08/2017 23:47:27 your computer crashed
crash dump file: C:\Windows\Minidump\082817-19047-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F950)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 02/07/2017 14:38:30 your computer crashed
crash dump file: C:\Windows\Minidump\070217-19749-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000307B90C)
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 Sun 02/07/2017 14:38:30 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: scmndisp.sys (scmndisp+0x16D1)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000307B90C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\scmndisp.sys
product: ® Neutral Wireless Solution
company: Windows (R) Codename Longhorn DDK provider
description: NDIS User mode I/O 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: scmndisp.sys (NDIS User mode I/O Driver, Windows (R) Codename Longhorn DDK provider).
Google query: Windows (R) Codename Longhorn DDK provider IRQL_NOT_LESS_OR_EQUAL



On Thu 29/06/2017 17:58:18 your computer crashed
crash dump file: C:\Windows\Minidump\062917-19749-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800030C790C)
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 Mon 19/06/2017 20:58:27 your computer crashed
crash dump file: C:\Windows\Minidump\061917-17409-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000309590C)
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
--------------------------------------------------------------------------------

11 crash dumps have been found and analyzed. Only 5 are included in this report. 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:

scmndisp.sys (NDIS User mode I/O Driver, Windows (R) Codename Longhorn DDK provider)

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.
arthurcorre_
 
Messages: 2
Inscription: Lun 28 Aoû 2017 14:06

Re: Ecran bleu

Messagepar mwonex » Lun 28 Aoû 2017 15:17

Bonjour,

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

Rechercher dans le gestionnaire et le site du jeu si tu as le pilote "adhoc"

It is suggested you look for an update for the following driver: scmndisp.sys (NDIS User mode I/O Driver, Windows (R) Codename Longhorn DDK provider).

conclusion:
try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers.

La solution est dans la recherche sur Google avec le nom de ces pilotes en associant les erreurs rapportées pour ces pilotes, ainsi que le nom, marque et type du PC.

lire:
https://community.netgear.com/t5/WiFi-Adapters/BSOD-issue-Win-8-1-64-bit-WNA3100/td-p/997817
Désinstaller/réinstaller le pilote en question (Netgear il semble).
@+
Windows 10 64 bits minitour Acer => mis à jour vers Windows 10.Version 1709 (version du système d'exploitation 16299.64)- Portable Asus Windows 10
Mais toujours intéressé par ce forum.
Avatar de l’utilisateur
mwonex
 
Messages: 3031
Inscription: Ven 11 Fév 2011 20:01
Localisation: R.P. France 92

Re: Ecran bleu

Messagepar arthurcorre_ » Lun 28 Aoû 2017 15:43

Bonjour,

Merci !
Je pense que c'est effectivement la raison de mes écrans bleus fréquents !
J'ai les mêmes symptômes que l'utilisateur a reporté sur le forum, ma clé reste allumée après l'extinction de mon PC, ce que je trouvais très anormal !
A voir si c'est réglé maintenant...
arthurcorre_
 
Messages: 2
Inscription: Lun 28 Aoû 2017 14:06

Re: Ecran bleu

Messagepar PatriciaG » Mar 29 Aoû 2017 01:18

Bonjour,

Si je comprends bien, tu as réinstallé ton pilote Wi-Fi Netgear comme indiqué par Mwonex.

J'espère que cela a résolu ton bug.
Dans le cas contraire, effectue une détection automatique des pilotes sur TousLesDrivers.com, onglet MES DRIVERS
http://www.touslesdrivers.com/
Fais les mises à jour requises, ensuite redémarre le pc, puis effectue une nouvelle détection sur TLD pour vérifier que les mises à jour sont bien prises en compte et que Windows n'a pas réinstallé un autre pilote au redémarrage.

Si tes pilote sont corrects et que les BSOD persistent, il faut explorer d'autre pistes, en particulier un problème de RAM.
En effet, une barrette défaillante peut provoquer de tels écrans bleus.

Teste ta mémoire RAM
- d'abord avec l'Outil Windows de diagnostic des problèmes de mémoire du PC
Tutoriel : http://www.pcastuces.com/pratique/windows/memoire_windows10/page1.htm
- ensuite avec Memtest86+, pour un test plus approfondi, si l'Outil Windows n'a détecté aucune anomalie
http://www.memtest.org/
Tutoriel : http://www.commentcamarche.net/faq/899-memtest-tester-ses-barrettes-de-ram

@+
Avatar de l’utilisateur
PatriciaG
 
Messages: 2740
Inscription: Jeu 11 Nov 2010 17:11
Localisation: Port-sur-Saône / Haute-Saône / France


Retourner vers Matériels

Qui est en ligne

Utilisateurs parcourant ce forum: Aucun utilisateur enregistré et 0 invités

Livre photo