[Système d'exploitation : Problème] Erreur fatale, écran bleu.

Voilà j'ai encore eu un bleu screen !!! j'ai prit un screen pour vous montrez en espérant avoir un coup de main      



voilà ..

J'ai looké vite fait sur internet et on me dit que sa serrait un disque dur défectueux ...  

je confirme c'est le disque dur qui est défectueux
suit cette procédure et dis moi si tu as la même chose
http://www.commentcamarche.net/forum/affich-25873483-kernel-data-inpage-error

si c'est le cas, c'est ton disque dur interne (le 1°) qu'il faut changer

oui je vais regardé

Mais le soucis c'est que il m'en a mit encore un différent a présent ...

Je pense que la nouvelle version de l’écran ne change pas le fondement du problème...

Croc a raison un blue screen c'est un périphérique Hardware qui déconne....le plus souvent c'est le DD.
Attendons de voir ce que va dire Croc...  

Dis-moi, tu peux faire des relevés de température?
Pour voir si t'as pas un composant qui chauffe trop et qui le mette en sécurité.

Normalement dans %appdata% , tu es censé avoir des fichiers de dump (extension .dmp ou .mdmp) qui détaillent le contenu de l'erreur/blue screen. Si tu les as, passe-les moi que je puisse les consulter. Bien entendu, uniquement ceux qui sont en rapport avec ton plantage.

Voilà la procédure que je te conseille, il s'agit de vérifier les différentes parties de ton matériel:

1. Retirer une barrette de RAM à la fois pour écarter tout problème de la RAM.
   
2. Si tu as un autre DD bootable, je te conseille de le mettre pour voir si le DD n'est pas défectueux.
   
3. Si tu as une alim de secours, change-la.
   

Je pige que dale , la j'ai juste envie de taper mon point dans la carte mère et de le lancer par la fenêtre !
De plus le truc arrête pas de ce couper tout seul même en mode sans échec ...
Au démarrage il me dit d'appuyer sur F11 pour un truc de revover ou je sais pas quoi ...
Si je ne le fais pas il me mais BootMPG absent ou un truc du style et je dois faire ctrl alt delete..

J'ai arrêté au sinon il va vraiment volé par la fenêtre.

En plus jamais personne sur ts ...

ce soir on sera la....te bile pas les pannes PC on en a tous notre compte....on va trouver c'est sur....

Merci de ton soutient Baraz !! sa fait toujours plaisir

--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.00
--------------------------------------------------------------------------------

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: SHARINGANHEIE
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: H87M-D3H, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8463093760 total
VM: 2147352576, free: 1999503360




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 3/01/2014 11:11:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010314-20950-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80093BD110, 0xFFFFFA80093BD3F0, 0xFFFFF800033BFE10)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 3/01/2014 11:11:17 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: 0xF4 (0x3, 0xFFFFFA80093BD110, 0xFFFFFA80093BD3F0, 0xFFFFF800033BFE10)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 3/01/2014 10:48:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010314-23556-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x50 (0xFFFFF8000000FBCF, 0x8, 0xFFFFF8000000FBCF, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 3/01/2014 00:04:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010314-16099-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8008094B30, 0xFFFFFA8008094E10, 0xFFFFF800033D0240)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 2/01/2014 23:09:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010314-15584-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x7A (0xFFFFF6FC5001D000, 0xFFFFFFFFC000000E, 0x159AB6880, 0xFFFFF8A003A00778)
Error: KERNEL_DATA_INPAGE_ERROR
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 the requested page of kernel data from the paging file could not be read into memory.
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 2/01/2014 22:06:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010214-24195-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xF1C7C)
Bugcheck code: 0x7A (0xFFFFF6FC400097B0, 0xFFFFFFFFC000000E, 0x1B7C89860, 0xFFFFF880012F6C7C)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider 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.