Bonjour , depuis quelques jours, windows ne cesse de crasher avec à chaque fois des erreurs différentes mais si la plupart sont récurrentes .
J'ai essayé de formater, sauf qu'il plante pendant la réparation ou formatage ... Du coup c'est compliqué
J'ai essayé de mettre à jour les pilotes mais rien à faire , ca reste la même.
En fait il marche très bien seulement en mode sans échec

Voici le rapport de whocrashed

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 16/05/2015 16:49:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051615-25375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0x7F (0x8, 0x0, 0xFFFFF803B067BFF0, 0xFFFFF803AED75F2A)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 Intel CPU generated a trap and the kernel failed to catch this trap.
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 16/05/2015 16:49:35 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: 0x7F (0x8, 0x0, 0xFFFFF803B067BFF0, 0xFFFFF803AED75F2A)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 16/05/2015 15:26:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051615-20156-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x57C2F) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001ECC2F, 0xFFFFD000CF72CEE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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. 



On Sat 16/05/2015 15:20:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051615-31015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0x7F (0x8, 0xFFFFF803EC291E70, 0xFFFFD001C34EC018, 0xFFFFF803EA9D8E01)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 Intel CPU generated a trap and the kernel failed to catch this trap.
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 16/05/2015 10:54:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051615-22609-01.dmp
This was probably caused by the following module: jraid.sys (jraid+0xD43B) 
Bugcheck code: 0x7F (0x8, 0xFFFFF8015A691E70, 0xFFFFF800E568FE38, 0xFFFFF801B055543B)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\jraid.sys
product: JMicron JMB36X RAID Driver
company: JMicron Technology Corp.
description: JMicron JMB36X RAID Driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: jraid.sys (JMicron JMB36X RAID Driver, JMicron Technology Corp.). 
Google query: JMicron Technology Corp. UNEXPECTED_KERNEL_MODE_TRAP



On Sat 16/05/2015 10:32:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051615-22500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0xA (0xFFFFFA82D35B9E40, 0x2, 0x1, 0xFFFFF803F7A7BB90)
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 Sat 16/05/2015 06:42:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051615-20359-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x5F38) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8015E189F38, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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 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. 



On Sat 16/05/2015 06:36:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051615-20312-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF8012C34E222) 
Bugcheck code: 0xD1 (0xFFFFC003256DA9B3, 0x2, 0x0, 0xFFFFF8012C34E222)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 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. 



On Fri 15/05/2015 18:53:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051515-20671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) 
Bugcheck code: 0xA (0xFFFFF80300CF1D20, 0x2, 0x1, 0xFFFFF803CAACECA1)
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 Fri 15/05/2015 18:47:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051515-30593-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x9401) 
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF800EC2F6D0B, 0xFFFFE001059A3080, 0x2C)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 341.44 
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 341.44 
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. 
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 341.44 , NVIDIA Corporation). 
Google query: NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED





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

51 crash dumps have been found and analyzed. Only 10 are included in this report. 3 third party drivers have 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: 

athwnx.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 341.44 , NVIDIA Corporation)
jraid.sys (JMicron JMB36X RAID Driver, JMicron Technology Corp.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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. 

En espérant que vous pourrez m'aider.

Aucune idée ?

Je ne suis pas specialiste du tout mais au bout d'un temps j'avais des blue screens et c'etait dut à une mise a jour du driver de ma cg (une amd) mais comme tu a une nvidia je ne sais pas si c'est pareil.
Bref j'ai totu desintaller completement et reinstaller la version que j'ai eu avec mon pc (en cd)

Sauf que je peux pas tout réinstaller , même avec le CD , car ça plante pendant l'opération