Plusieurs BSOD différents depuis une semaine !
AzReah
Messages postés
32
Date d'inscription
Statut
Membre
Dernière intervention
-
Miura564 Messages postés 13404 Date d'inscription Statut Membre Dernière intervention -
Miura564 Messages postés 13404 Date d'inscription Statut Membre Dernière intervention -
Bonjour ,
Cela fait maintenant plus d'une semaine que je me tape des bluescreens de toutes sortes : PFN_LIST_CORRUPT , IRQL_NOT_LESS_OR_EQUAL ou encore BAD_POOL_CALLER ...
Je ne sais vraiment pas quoi faire et j'ai déjà lu mille et un forum sans aucune réponse pouvant m'aider , ....
Aidez moi svp !
AzReah
Cela fait maintenant plus d'une semaine que je me tape des bluescreens de toutes sortes : PFN_LIST_CORRUPT , IRQL_NOT_LESS_OR_EQUAL ou encore BAD_POOL_CALLER ...
Je ne sais vraiment pas quoi faire et j'ai déjà lu mille et un forum sans aucune réponse pouvant m'aider , ....
Aidez moi svp !
AzReah
A voir également:
- Plusieurs BSOD différents depuis une semaine !
- Bsod - Guide
- Ce fichier contient l'historique des livres empruntés à la bibliothèque. combien de titres différents contient-il ? ✓ - Forum Excel
- Sandra a décidé de mieux contrôler son image et sa présence sur différents réseaux sociaux. qu’est-il possible de faire sur ces réseaux ? - Forum Facebook
- Bibliothèque ✓ - Forum Windows 10
- Comment avoir deux écrans différents - Guide
23 réponses
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 17/09/2014 18:18:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091714-46394-01.dmp
This was probably caused by the following module: iastora.sys (iaStorA+0x8C01)
Bugcheck code: 0xA (0x9B966E2, 0x2, 0x1, 0xFFFFF800030AF447)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\iastora.sys
product: Intel Rapid Storage Technology driver
company: Intel Corporation
description: Intel Rapid Storage Technology driver - x64
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.
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: iastora.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation).
Google query: Intel Corporation IRQL_NOT_LESS_OR_EQUAL
On Wed 17/09/2014 18:18:35 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbaudio.sys (usbaudio+0x3698)
Bugcheck code: 0xA (0x9B966E2, 0x2, 0x1, 0xFFFFF800030AF447)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbaudio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Audio Class Driver
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 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.
Google query: Microsoft Corporation IRQL_NOT_LESS_OR_EQUAL
On Sat 13/09/2014 15:17:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091314-39296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4E (0x7, 0x13A195, 0x1, 0x0)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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 Sat 13/09/2014 12:38:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091314-39546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4E (0x7, 0x13A18F, 0x1, 0x0)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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 Fri 12/09/2014 18:19:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091214-46176-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 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 Fri 12/09/2014 16:35:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091214-40965-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x40D0005, 0xFFFFFA800B950980)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 12/09/2014 16:02:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091214-36551-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x839B3)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001C839B3, 0xFFFFF8800C0188A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Fri 12/09/2014 15:49:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091214-45692-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800BD66118, 0xFFFFF8800BD65970, 0xFFFFF80003489899)
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
--------------------------------------------------------------------------------
8 crash dumps have been found and analyzed. 2 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:
iastora.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation)
usbaudio.sys (USB Audio Class Driver, Microsoft Corporation)
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.
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 17/09/2014 18:18:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091714-46394-01.dmp
This was probably caused by the following module: iastora.sys (iaStorA+0x8C01)
Bugcheck code: 0xA (0x9B966E2, 0x2, 0x1, 0xFFFFF800030AF447)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\iastora.sys
product: Intel Rapid Storage Technology driver
company: Intel Corporation
description: Intel Rapid Storage Technology driver - x64
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.
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: iastora.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation).
Google query: Intel Corporation IRQL_NOT_LESS_OR_EQUAL
On Wed 17/09/2014 18:18:35 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbaudio.sys (usbaudio+0x3698)
Bugcheck code: 0xA (0x9B966E2, 0x2, 0x1, 0xFFFFF800030AF447)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbaudio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Audio Class Driver
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 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.
Google query: Microsoft Corporation IRQL_NOT_LESS_OR_EQUAL
On Sat 13/09/2014 15:17:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091314-39296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4E (0x7, 0x13A195, 0x1, 0x0)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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 Sat 13/09/2014 12:38:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091314-39546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4E (0x7, 0x13A18F, 0x1, 0x0)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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 Fri 12/09/2014 18:19:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091214-46176-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 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 Fri 12/09/2014 16:35:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091214-40965-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x40D0005, 0xFFFFFA800B950980)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 12/09/2014 16:02:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091214-36551-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x839B3)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001C839B3, 0xFFFFF8800C0188A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Fri 12/09/2014 15:49:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091214-45692-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800BD66118, 0xFFFFF8800BD65970, 0xFFFFF80003489899)
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
--------------------------------------------------------------------------------
8 crash dumps have been found and analyzed. 2 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:
iastora.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation)
usbaudio.sys (USB Audio Class Driver, Microsoft Corporation)
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.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Ton disque dur est peut être défaillant , ou autre ?
A tu fait un chkdsk ?
Avec Exécuter ou avec l'invite de commande, tape chkdsk /f
Aussi , fais un sfc /scannow
A moins que tu ait un problème de virus , crois tu ?
A tu fait un chkdsk ?
Avec Exécuter ou avec l'invite de commande, tape chkdsk /f
Aussi , fais un sfc /scannow
A moins que tu ait un problème de virus , crois tu ?
Non je n'ai pas fais de chkdsk ni de scannow , mon disque dur externe est quasi plein depuis a peu près le commencement des Bluescreens et je ne pense pas avoir de virus , car le dernier téléchargement que j'ai fais , c'était Minimum sur steam et c'est d'ailleurs juste après le téléchargement + le lancement que mon pc a commencé a crash
Ce n'est pas un DD externe presque plein qui peut causer ça a mon avis.
Des BSOD, c'est bien dur a diagnostiquer.
Autre chose, vérifier la température du CPU et autres avec Real Temp et SpeedFan.
Des BSOD, c'est bien dur a diagnostiquer.
Autre chose, vérifier la température du CPU et autres avec Real Temp et SpeedFan.
J'ai déjà fait avec GPU TWEAK que j'ai reçu avec ma carte graphique et la température est correcte ( ce n'est pas a cause de la surchauffe )
Oui , il cherche a restaures les données des secteurs défectueux.
Il y a aussi memtest86 a essayer pour tester ta RAM
Il y a aussi memtest86 a essayer pour tester ta RAM
Après le sfc /scannow , ils me disent : "La protection des ressources Windows a trouvé des fichiers endommagés et a pu les réparer. Des détails sont fournis dans le journal CBS.Logwindir\Logs\CBS\CBS.log. Par exemple C:\Windows\Logs\CBS\CBS.log"
Et après le chkdsk /f /r ils me disent que : " le type de système de fichiers est NTFS
impossible de verrouiller le lecteur en cours .
CHKDSK ne peut pas s'exécuter parce que le volume est utilisé par un autre processus . Et après ils disent que ce volume sera vérifié au prochain redémarrage donc je reviens .
Et après le chkdsk /f /r ils me disent que : " le type de système de fichiers est NTFS
impossible de verrouiller le lecteur en cours .
CHKDSK ne peut pas s'exécuter parce que le volume est utilisé par un autre processus . Et après ils disent que ce volume sera vérifié au prochain redémarrage donc je reviens .
Bonjour,
tout d'abord le plus simple, IRQL_NOT_LESS_OR_EQUAL, indique en général un problème de mémoire. Vérifie physiquement que tes barrettes mémoires ne soient pas defectueuses. Teste-les une par une puis en les croisant, en redémarrant entre chaque essais, tu devrais trouver rapidement laquelle est HS
Pour le crash, PFN_LIST_CORRUPT, la plupart du temps ce qui est mentionné, la mémoire, la température. Il faudrait voir si tous les pilotes sont à jour, faire une analyse du matériel. En mode console de réparation faire sfc/scannow, un chkdsk/f.
pour le message KMODE_EXCEPTION_NOT_HANDLED, il semble que ce soit un bug connu de Microsoft, pour Windows 8.1 et 8.1RT il faut installer la mise à jour kb2887595
tout d'abord le plus simple, IRQL_NOT_LESS_OR_EQUAL, indique en général un problème de mémoire. Vérifie physiquement que tes barrettes mémoires ne soient pas defectueuses. Teste-les une par une puis en les croisant, en redémarrant entre chaque essais, tu devrais trouver rapidement laquelle est HS
Pour le crash, PFN_LIST_CORRUPT, la plupart du temps ce qui est mentionné, la mémoire, la température. Il faudrait voir si tous les pilotes sont à jour, faire une analyse du matériel. En mode console de réparation faire sfc/scannow, un chkdsk/f.
pour le message KMODE_EXCEPTION_NOT_HANDLED, il semble que ce soit un bug connu de Microsoft, pour Windows 8.1 et 8.1RT il faut installer la mise à jour kb2887595
Pour IRQL_NOT _ ... Je dois encore faire un memtest
Pour le pfn_list_corrupt je ne pense pas que ce soit la surchauffe car il tourne a des températures normales
Et pour KMODE , ce n'est pas la maj car j'ai seven
Pour le pfn_list_corrupt je ne pense pas que ce soit la surchauffe car il tourne a des températures normales
Et pour KMODE , ce n'est pas la maj car j'ai seven
Ah ben on avance (très) doucement.... aides nous à t'aider.... tu peux déjà commencer par nous donner le détail de ta configuration ça permettra de cibler les recherches et d'éviter de chercher tous azimuts... Au fait, c'est un fixe ou un portable ?
memtest ne te diras pas grand chose, c'est physiquement qu'il va falloir tester tes barrettes
memtest ne te diras pas grand chose, c'est physiquement qu'il va falloir tester tes barrettes