Résolu BSOD à répètition

  • Auteur de la discussion Eytspak
  • Date de début

Eytspak

Nouveau membre
Bonsoir,

Depuis un certains temps j'ai presque tous les jours un BSOD, j'ai installé who crashed: voici certains rapport malheureusement ils sont souvent différent sauf DRIVER IRQL NOT LESS OR EQUAL qui revient fréquemment
je suis complètement perdue et ne sais pas quoi faire :/

On Tue 10/05/2016 15:43:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\051016-5593-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x2, 0x2, 0x1, 0xFFFFF80157721F00)
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 Sun 08/05/2016 15:39:37 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050816-6250-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x8CBB0)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFF8B, 0x8, 0x1, 0xFFFFF8019E64CBB0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 26/04/2016 19:26:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042616-5703-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80257A7A29C)
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 25/04/2016 02:40:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042516-6046-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!HMAssignmentUnlock+0x4)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9611D680874, 0xFFFFD000C51C6CC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du noyau Base Win32k
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 Tue 19/04/2016 17:48:08 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041916-14531-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x6FF8)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801356E0A18, 0xFFFFD0015E953988, 0xFFFFD0015E9531A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\aswmonflt.sys
product: Avast Antivirus
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
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.
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: AVAST Software SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Sun 17/04/2016 18:46:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041716-20406-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x61941, 0x117120F0, 0x1D, 0xFFFFD0006BF99B00)
Error: MEMORY_MANAGEMENT
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 10/04/2016 14:07:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041016-14156-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xA, 0x2, 0x0, 0xFFFFF80088EF6A0E)
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 Sun 10/04/2016 04:24:55 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041016-17343-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip!TcpPeriodicTimeoutHandler+0x799)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF801B9686DB9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 Thu 07/04/2016 20:17:21 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040716-14875-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x2D0C3)
Bugcheck code: 0xD1 (0xFFFFD8045FD5A1C8, 0x2, 0x0, 0xFFFFF8017393793B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 01/04/2016 03:23:22 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040116-14250-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI!Isoch_Transfer_CompleteCancelable+0x1F0)
Bugcheck code: 0xD1 (0x855E4A70, 0x2, 0x0, 0xFFFFF800896B19CC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote XHCI USB
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.




pc monté par moi même je peux aussi dire que j'avais ce soucis de BSOD avec mon ancienne cg (gtx760) là c'est une r9 390

Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: MS-7821, MSI, Z87-G45 GAMING (MS-7821)
CPU: GenuineIntel Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17118740480 bytes total
 

job31

Admin tout frippé
Staff
Bonjour,

config (alim?)
Entre les deux CG tu as bien nettoyé les drivers graphiques ?
Drivers à jour ?
 

Haldriel

Helper
Bonjour,

Tu peux télécharger crystaldiskinfo (site officiel : ), le lancer et nous donner le résultat? Je serai curieux de l'état de santé de ton disque système...

Cordialement,
Haldriel
 

AccroPC2

Fou du PC
Staff
Hello,

Quand je vois des erreurs type *_IRQL_NOT_LESS_OR_EQUAL --> Memtest386.
Il y a une bonne chance qu'une barrette de ram soit défectueuse. ( A installer sur une clé USB, booter dessus et laisser 5 pass mini ).

Bye.
 

magellan

Modérâleur
Staff
+1 pour la Ram, cela peut aussi être un mauvais paramétrage issu d'un overclocking mal foutu (mais là j'en doute).
 

Eytspak

Nouveau membre
bonsoir

merci pour vos réponses
j'ai lancé crystaldiskinfo pour le ssd correct 98 % et le hdd correct,
j'ai bien supprimé les drivers nvidia mais comme dit dans mon post j'avais ce soucis de BSOD avant le changement de cg j'avais du démonté / remonté le pc car j'ai du changé de boitier pour la r9
je vais test memtest demain après le boulot
je n'ai rien oc sur mon pc
l'alim est une corsair gs 600
 

Haldriel

Helper


C'est une alimentation bas de gamme commercialisée a partir de 2010.... Lances un petit OCCT en mode "Power Supply", histoire de voir combien de temps ca tiens.

En étant méchant je placerai un petit pari en disant a la louche pas plus de 2 minutes
 

Eytspak

Nouveau membre
je ne comprends pas l'intérêt de sdi tool car il me propose d'installer des drivers pour pc portable et lorsque je coche "pour ce pc" je n'ai que un driver appeler "index"
 

Eytspak

Nouveau membre
mon alim est plus précisément la gs600 gaming édition 2013 donc non c'est du milieu de gamme pour le jeu
 

Haldriel

Helper


Ca mériterai quand même un petit test sous OCCT pour vérifier que tout va bien. Et Memtest si ca passe au niveau de l’alimentation, comme recommandé par AccroPC pour tester la RAM
 

_Othy_

Helper
salut,
c'est la premiere etape, sdi va d'abord indexer la liste de tes composants pour ce pc et pas telecharger tous les pilotes possible et imaginable
 

Eytspak

Nouveau membre
d'accord mais je ne comprends pas le fonctionnement je commence par quoi ?
je n'ai pas eu de BSOD depuis 4 jours maintenant depuis une MAJ de windows 10( coïncidence? ).
le memtest est négatif
 

_Othy_

Helper
Meilleure réponse
salut,

"seulement ceux pour ce pc" , du coup index est coché, tu fais OK
la ça va télécharger, tu attend bien sure. quand fini, tu aura la liste des drivers non à jour que tu pourra sélectionner et installer si tu le veux
 

magellan

Modérâleur
Staff
Un truc possible et particulièrement idiot. Pour peu que ton W10 n'était pas à jour côté pilotes, les BSOD n'auraient plus rien de suprenants, et un update aurait résolu les bugs potentiels... va savoir!
 

dandibot

Grand Maître
Hello, le mieux reste une mise à jour manuelle via le site du fabricant.
 

_Othy_

Helper
il m'est arrivé plusieurs fois que SDI trouve le pilote et pas drivercloud, du coup je reste sur celui là.
en plus, il n'y a pas d'install à faire et on peut recuperer tous les packs de drivers pour les mettre sur une clé afin de depanner un ami/client...

@dandibot, pas d'accord avec toi, bien souvent les fabricant de CM (par exemple) n'ont pas les pilotes à jour sur leur site, ce serait trops lourds pour eux de devoir certifié chaque nouvelle version.

EDIT: et une dernière chose, gratuit, pas de logiciel tierce installés, ni de pub ou autre cochonnerie !!
 
Vous devez vous inscrire ou vous connecter pour répondre ici.
Derniers messages publiés
Statistiques globales
Discussions
730 079
Messages
6 716 702
Membres
1 586 247
Dernier membre
MrAzgarIII
Partager cette page
Haut