CONNEXION
  • RetourJeux
    • Sorties
    • Hit Parade
    • Les + populaires
    • Les + attendus
    • Soluces
    • Tous les Jeux
    • Gaming
  • RetourActu Gaming
    • News
    • Astuces
    • Tests
    • Previews
    • Toute l'actu gaming
  • RetourBons plans
    • Bons plans
    • Bons plans Smartphone
    • Bons plans Hardware
    • Bons plans Image et Son
    • Bons plans Amazon
    • Bons plans Cdiscount
    • Bons plans Decathlon
    • Bons plans Fnac
    • Tous les Bons plans
  • RetourJVTech
    • Actus High-Tech
    • Intelligence Artificielle
    • Smartphones
    • Mobilité urbaine
    • Hardware
    • Image et son
    • Tutoriels
    • Tests produits High-Tech
    • Guides d'achat High-Tech
    • JVTech
  • RetourCulture
    • Actus Culture
    • Culture
  • RetourVidéos
    • A la une
    • Gaming Live
    • Vidéos Tests
    • Vidéos Previews
    • Gameplay
    • Trailers
    • Chroniques
    • Replay Web TV
    • Toutes les vidéos
  • RetourForums
    • Hardware PC
    • PS5
    • Switch 2
    • Xbox Series
    • Switch
    • Pokemon pocket
    • FC 25 Ultimate Team
    • League of Legends
    • Tous les Forums
  • PC
  • PS5
  • Xbox Series
  • Switch 2
  • PS4
  • One
  • Switch
  • iOS
  • Android
  • MMO
  • RPG
  • FPS
En ce moment Genshin Impact Valhalla Breath of the wild Animal Crossing GTA 5 Red dead 2
Liste des sujets

Ecran bleu

mrdrizt
mrdrizt
Niveau 2
10 juillet 2017 à 18:34:33

Bonjour

Suite à l'installation de mon nouveau processeur et de 4go de ram en plus, j'ai plusieurs fois des bsod. J'ai mis réinstaller windows, mis à jour mes pilotes, enlever la nouvelle barrette de ram mais rien ne change. J'ai fait une analyse whocrashed :

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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 10/07/2017 18:22:09 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071017-25437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0xA (0xFFFFF90B3A229000, 0xFF, 0xDF, 0xFFFFF802866FFA11)
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 Mon 10/07/2017 18:22:09 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: 0xA (0xFFFFF90B3A229000, 0xFF, 0xDF, 0xFFFFF802866FFA11)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Mon 10/07/2017 17:50:28 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071017-31828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0x1A (0x1233, 0x7D746, 0x0, 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.

On Mon 10/07/2017 11:31:56 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071017-27328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0x139 (0x3, 0xFFFFE500566DE720, 0xFFFFE500566DE678, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 10/07/2017 11:08:51 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071017-28890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0x139 (0x3, 0xFFFFBC80CABB6C70, 0xFFFFBC80CABB6BC8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

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

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

Ma config :
gtx 750
athlon x4 880k
8go de ram

Si une personne peut me répondre, ça serait sympa.

mrkrabs1258
mrkrabs1258
Niveau 10
10 juillet 2017 à 19:05:55

Bonjour à toi :)
J'ai fait quelque recherche vis à vis de ton problème et y'à pas mal d'info. Mais le plus simple, si l'anglais ne te dérange pas, c'est que tu te rende sur ce forum, que tu poste ton sujet là bas et que tu attendes l'aide des gens (qui semble plus que compétent) qui pourront t'aider.

https://www.tenforums.com/bsod-crashes-debugging/87712-bsod-ntoskrnl-exe-nt-0x16c3f0.html

mrdrizt
mrdrizt
Niveau 2
11 juillet 2017 à 11:51:32

Merci, je vais voir, je te tiens au courant.

Sous forums
  • Aide à l'achat Mac
  • Internet
  • Macintosh
  • Création de sites web
  • Création de Jeux
  • Linux
  • Programmation
  • Steam Deck
  • Hardware
La vidéo du moment