bonsoir,
 
ayant acheté une msi h81 p33 je l'installe tout va bien (je dois quand même formater a cause du Legacy UEFI) je choisi la méthode "conserver mes fichiers" tout fonctionne bien quand soudain  
 
1er code erreur: "MEMORY_MANAGEMENT"  
je reboot, je suis 1heure sur le pc tout va bien a part quelques fois des "aie aie aie" sur chrome  
puis  
2eme code erreur: "MEMORY_MANAGEMENT"
je reboot je fouille un peu sur le net, je teste mes barrettes etc
ensuite encore a peu près 50minutes
3eme code erreur: "KMODE_EXCEPTION_NOT_HANDLED"
 
je copie colle ici le résultat "WhoCrashed"
 
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\WINDOWS\Minidump
 
Crash dumps are enabled on your computer.
 
On Fri 26/05/2017 23:06:03 your computer crashed
crash dump file: C:\WINDOWS\Minidump\052617-29015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14EC00)  
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801DEFDB767, 0x0, 0xFFFFFFFFFFFFFFFF)
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 Fri 26/05/2017 23:06:03 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, 0xFFFFF801DEFDB767, 0x0, 0xFFFFFFFFFFFFFFFF)
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 Fri 26/05/2017 22:13:12 your computer crashed
crash dump file: C:\WINDOWS\Minidump\052617-26421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14EC00)  
Bugcheck code: 0x1A (0x41793, 0xFFFF8C8100ADFFF8, 0x150, 0x14F)
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. This problem might also be caused because of overheating (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 26/05/2017 21:12:09 your computer crashed
crash dump file: C:\WINDOWS\Minidump\052617-34687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14EC00)  
Bugcheck code: 0x1A (0x41792, 0xFFFFBABFFDB67768, 0x2000000000000, 0x0)
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. This problem might also be caused because of overheating (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.  
 
j'ai donc essayé de faire le vérificateur de driver windows en tapant verifier dans exécuter et là j'avais eu d'autre écran bleu je ne me souviens plus trop mais ça parlait de "tcpip.sys" et "ntsf.sys" aussi
et un autre aussi "INACCESSIBLE_BOOT_DEVICE"
bref je sature je comprends pas grand chose, un formatage complet ou flash du bios pourrait-il changer quelque chose? mes pilotes sont a jour selon "driverscloud"
cordialement,  
gt  
 
PC:
I5 4460
MSI H81 P33
16gb ram 2x8
AMD R7 260x
w10 64bits
alim hexa fsp 500w

salut,
as-tu un périphérique (souris, dd externe, dongle souris..., etc..) branché sur port USB 3 (port bleu), si oui essaye de le changer pour un port USB 2.0 (noir)

Salut.  Euh non les deux sont en noir 2.0.
Mais je pense que le problème est résolu grâce à un reformatage complet.  C'était un conflit de driver je pense.  Le truc marrant c'est qu'au début mon i5 m'annoncait 2 coeurs.  et depuis le reset Windows j'ai bien les 4 coeurs.  aucun bsod depuis hier tard le soir jusqu'à aujourd'hui.  je viens de reboot pour toutes les majs.  Ras  
Merci quand même erickred

pas de bp,  
je pensais au port USB 3 (ou leur driver) , car le KMODE Error qui est indiqué correspondait à ça.
enfin bref ravi pour toi que ça fonctionne.

 
bah franchement je pense que tu as raison c'était un bordel avec l'usb/drivers , parce que mon ancienne carte mère (sata 2.0, usb 2.0 only / ddr2 ) etc
je pense que c'était dû a ça!