salut tous le monde.
alors voila quand je démarre mon pc, après le truc de la carte mère quand on peux allé dans le bios, il me fait un blue screen en me disant erreur et c'est jamais la même.
tous les drivers sont a jours.
j'ai fait une analyse whocrashe pour ceux qui veulent je la met après.
et j'ai l'impression que ça me fait l'erreur que quand le pc est froid par exemple si la je l'l’éteint et que je le rallume aussitôt aucune erreur par contre si je le redémarre dans une heure, erreur
je suis obligé de redémarré mon ordi 3-4 fois pour ne plus avoir d'erreur
parfois il reboot tous seul parfois il plante au niveau de la carte mère.
merci a ceux qui pourront m'aider.

whocrashed

crash dump analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 07/01/2014 17:32:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010714-8985-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80204E28F30, 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 Tue 07/01/2014 17:32:32 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: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80204E28F30, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 Mon 06/01/2014 21:05:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010614-6832-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x19 (0xD, 0xFFFFF90100702B80, 0xFF, 0x40EB2126F23D8304)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 06/01/2014 21:03:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010614-7004-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFF80235AB4C14, 0x8, 0xFFFFF80235AB4C14, 0x2)
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 Mon 06/01/2014 18:26:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010614-7113-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80205A70B58, 0x0, 0x3FF4)
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 Mon 06/01/2014 18:24:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010614-6817-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5409F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800484C309F, 0xFFFFF88002F091C8, 0xFFFFF88002F08A00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 05/01/2014 14:12:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010514-7300-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1A (0x41284, 0xE3F7684001, 0x2F21, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 05/01/2014 14:07:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010514-7347-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xFC (0xFFFFFA8007ED44B0, 0x80000002174009E3, 0xFFFFFA800906EDD0, 0x4)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 04/01/2014 11:04:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010414-8283-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4AB36F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8008E0B136F, 0xFFFFF88003119568, 0xFFFFF88003118DA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 31/12/2013 11:25:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123113-7004-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x40C90)
Bugcheck code: 0x24 (0xB50019060B, 0xFFFFF8800C656868, 0xFFFFF8800C6560A0, 0xFFFFF8800156CCC3)
Error: NTFS_FILE_SYSTEM
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 indicates a problem occurred in the NTFS file system.
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

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

personne ne peux m'aider ?