bleu screen

Discussions gérénales sur Microsoft Windows 7, des différentes versions.

bleu screen

Messagepar Arivin » Ven 15 Juin 2018 20:31

Bonjour/Bonsoir
voici les details du probleme(fait avec Whocrashed)

System Information (local)
--------------------------------------------------------------------------------

Computer name: USER-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: HP ProBook 4540s, Hewlett-Packard, 17F6
CPU: GenuineIntel Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4170944512 bytes total




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

Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Fri 15/06/2018 19:53:59 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: netr28x.sys (netr28x+0x4BA8D)
Bugcheck code: 0xA (0xFFFFF8A000E34634, 0x2, 0x1, 0xFFFFF80002F51D31)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netr28x.sys
product: MediaTek 802.11n Wireless Adapters
company: MediaTek Inc.
description: MediaTek 802.11 Wireless Adapter Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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: netr28x.sys (MediaTek 802.11 Wireless Adapter Driver, MediaTek Inc.).
Google query: netr28x.sys MediaTek Inc. IRQL_NOT_LESS_OR_EQUAL



On Mon 28/05/2018 22:18:15 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052818-20264-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0xA (0xFFFFF8A000D8E9D4, 0x2, 0x0, 0xFFFFF80002F5216C)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 27/05/2018 01:25:13 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052718-22276-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0xA (0xFFFFF8A001503850, 0x2, 0x0, 0xFFFFF80002F9D414)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 25/05/2018 20:55:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052518-19905-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0xA (0xFFFFF8A0049A16A8, 0x2, 0x1, 0xFFFFF80002F03A78)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 25/05/2018 20:42:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052518-20935-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0xA (0xFFFFF8A0052FB8E0, 0x2, 0x0, 0xFFFFF80002FA05C9)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 24/05/2018 23:16:12 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052418-21559-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0xA (0xFFFFF8A004B739D4, 0x2, 0x0, 0xFFFFF80002F5A16C)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 23/05/2018 18:51:20 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052318-19546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0x5 (0xFFFFFA8003C65480, 0xFFFFFA8003F1AB10, 0x0, 0x1)
Error: INVALID_PROCESS_ATTACH_ATTEMPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).
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 Wed 23/05/2018 17:56:35 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052318-22573-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0xA (0xFFFFF8A000AD5D50, 0x2, 0x1, 0xFFFFF80002EFAA3D)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 22/05/2018 16:26:10 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052218-19765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0xA (0xFFFFF8A004BE6D34, 0x2, 0x0, 0xFFFFF80002F9616C)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 22/05/2018 04:18:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052218-20092-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0x5 (0xFFFFFA8003C65480, 0xFFFFFA8004263B10, 0x0, 0x1)
Error: INVALID_PROCESS_ATTACH_ATTEMPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).
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
--------------------------------------------------------------------------------

On your computer a total of 51 crash dumps have been found. Only 10 have been 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:

netr28x.sys (MediaTek 802.11 Wireless Adapter Driver, MediaTek Inc.)

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.
Arivin
 
Messages: 1
Inscription: Ven 15 Juin 2018 20:26

Re: bleu screen

Messagepar PatriciaG » Ven 15 Juin 2018 23:39

Bonjour,

Quels sont la marque et le modèle précis du PC ?

Quel est ton antivirus ?

1- Vérifie ton disque dur.
Clique sur le bouton Démarrer > Saisis cmd dans la zone de recherche > Fais un clic droit sur le programme nommé cmd.exe > Clique sur Exécuter en tant qu’administrateur.
> Puis saisis la commande administrateur suivante : chkdsk /f + Entrée.
Le système va te demander de confirmer l'exécution de la commande après redémarrage du pc > Valide.

2- Mets à jour tes pilotes.
Effectue une détection automatique des pilotes sur TousLesDrivers.com, onglet MES DRIVERS
http://www.touslesdrivers.com/
Fais les mises à jour requises.

Un des plantages est causé par le pilote de ta carte Wi-fi, donc réinstalle ce pilote, même s'il n'est pas donné obsolète par TLD.
Si TLD ne donne pas de lien de téléchargement pour ce pilote, réinstalle le pilote Wi-Fi depuis le site du fabricant de la carte ou depuis le site du constructeur de ton pc.

Après ces mises à jour, redémarre le PC après ces maj, puis effectue une nouvelle détection sur TLD et poste-moi le lien (pas les copies d’écran) du nouveau rapport de détection.

3- Contrôle ta RAM.
Exécute l'outil Windows de diagnostic des problèmes de mémoire du PC
http://www.pcastuces.com/pratique/windo ... /page1.htm

Après exécution de tous ces points, pense à me faire un retour détaillé.

Bonne réparation. :coucou:
Avatar de l’utilisateur
PatriciaG
 
Messages: 2936
Inscription: Jeu 11 Nov 2010 17:11
Localisation: Port-sur-Saône / Haute-Saône / France


Retourner vers Discussions Générales

Qui est en ligne

Utilisateurs parcourant ce forum: Aucun utilisateur enregistré et 1 invité

Livre photo