Ecan bleu Windows 7 - Erreur: 0x0000003B (0x00000000c0000005,0xF Fermé

Question

Bonjour.
Depuis quelque temps, mon système plante sans raison apparente.
En effet, parfois c'est lorsque j'utilise l'un ou l'autre  ou plusieurs de mes logiciels, parfois lorsque je cherche sur le net, et parfois il plante seul, lorsque je ne suis pas là!. A mon retour je trouve l'écran bleu.

J'ai pris une photo de cet écran. Cela me permet de recopier le texte ci dessous. 
Mes connaissances de l'Anglais sont quasiment nulles !

Mon code d'erreur: 0x0000003B (0x00000000c0000005,0xFFFFF8000379B890,0xFFFFF8800755B130,Cx0000000000000000)

Le texte: 
---------------------------------------
if this is the first time you've seen this error screen,
restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed.
if this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware or sofware. Disable bios memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select safe mode.

Technical information:

***Stop: 0x0000003B (0x00000000c0000005,0xFFFFF8000379B890,0xFFFFF8800755B130,Cx0000000000000000)

Collecting data for crash dump ...
Initializing disk for crash dump ...
Beginning dump of physical memory.
Dumping physical memory to disk: 100
Physical memory dump complete.
Contact your admin or technical support group for further assistance.
-----------------------------------

J'ai recherché sur le net sans trouver ce cas.
J'ai recherché par le centre de maintenance, lequel m'informe qu'aucun problème n'est détecté.

Je suis preneur de toute aide sur le sujet.
Bien cordialement.
Jqs.

Utilisateur anonyme · Answer

Bonjour . Téléchargez Whocrashed ---> http://www.google.fr/... ce qui renseignera sur les raisons de ces plantages . Cordialement

Goupille1 · Answer

Bonsoir.
Merci pour votre réponse.
J'ai donc téléchargé et installé Whocrashed .
Malheureusement, il est en anglais et je n'ai pas compris grand chose.

J'ai collé le résultat de l'analyse ci-dessous.

Merci encore pour votre aide.
Bien cordialement.
J.U.



Welcome to WhoCrashed (HOME EDITION) v 5.01
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution. 

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice. 

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems. 

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available. 

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network. 

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: BUREAU
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: imedia S3800, Packard Bell, FIH57
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4151410688 total
VM: 2147352576, free: 1922035712




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 06/07/2014 07:28:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070614-50138-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003798890, 0xFFFFF88007DFF130, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
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 06/07/2014 07:28: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: 0x3B (0xC0000005, 0xFFFFF80003798890, 0xFFFFF88007DFF130, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
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 04/07/2014 19:28:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070414-56799-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000379B890, 0xFFFFF8800755B130, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
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 04/07/2014 13:19:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070414-44241-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000377086F, 0xFFFFF8800AF55140, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
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 04/07/2014 13:10:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070414-53336-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7E709) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000372186F, 0xFFFFF880093A3140, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
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 04/07/2014 09:02:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070414-47689-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000371586F, 0xFFFFF8800AFB2140, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
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 Thu 03/07/2014 11:28:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070314-51683-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000372486F, 0xFFFFF8800A26B140, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
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 01/07/2014 20:58:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070114-52166-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000371886F, 0xFFFFF88008838140, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
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 01/07/2014 17:13:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070114-50185-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000376586F, 0xFFFFF88007E70140, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
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 29/06/2014 07:27:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062914-49577-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000371A86F, 0xFFFFF8800A145140, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
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
--------------------------------------------------------------------------------

10 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 actually 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.

Utilisateur anonyme · Answer

Bonjour . Vous devriez envisager de faire un sfc /scannow ---> http://www.google.fr/... , cet outil réparera les erreurs système , durée 15/20min. , NE PAS interrompre le processus et à la fin de l'analyse un rapport sera affiché signifiant si il a put tout réparer ou non . Cordialement

Goupille1 · Answer

Bonjour.
J'ai appliqué "sfc/scannow" qui n'a trouvé aucune violation d'intégrité.

Y a t'il une autre vérification à faire ?

Merci.

J.U.

Utilisateur anonyme · Answer

C'est ce fichier qui est manquant ---> <racine windows>\system32
toskrnl.exe donc veuillez suivre cette procédure ---> http://www.google.fr/... . Cordialement

Utilisateur anonyme · Answer

C'est ce fichier qui est manquant ---> <racine windows>\system32
toskrnl.exe donc veuillez suivre cette procédure ---> http://www.google.fr/... . Cordialement

Goupille1 · Answer

Désolé, je n'ai pas de CD d'installation. C'est un PC acheté chez Leclerc et livré sans CD.

D'autre part, j'ai recherché le fichier "ntoskrnl.exe".
Ses propriétés me donnent:

Description : NT Kernel & System
Emplacement C:\Windows\System32
Taille : 5,29 Mo (5 550 016 octets)
Sur disque : 5,29 Mo (5 550 080 octets)
Crée le : ?mercredi ?14 ?mai ?2014, ??08:59:03
Modifié le : mardi ?4 ?mars ?2014, ??10:47:01
Dernier accès le : ?mercredi ?14 ?mai ?2014, ??08:59:03.

Cdlt.

Goupille1 · Answer

OK.
Merci pour vos réponses. Je vais voir. Je vous tiens au courant.
Bonne soirée.
J.U.