Plusieurs BSOD différents depuis une semaine !

Question

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

fabul · Answer

Salut,

Essaie Whocrashed

Ça en dira peut être d'avantage.

AzReah · Answer

J'ai déjà fait un Whocrashed , tu veux que je te mette le détail ?

fabul · Answer

Tant qu'a y être.

AzReah · Answer

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
toskrnl.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
toskrnl.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
toskrnl.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
toskrnl.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	cpip.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
tfs.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.

fabul · Answer

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 ?

AzReah · Answer

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

fabul · Answer

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.

AzReah · Answer

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 )

fabul · Answer

Alors, vas y pour

chkdsk /f ou chkdsk /f /r (c'est plus long)

Et sfc /scannow

AzReah · Answer

plus long mais plus complet ?

fabul · Answer

Oui , il cherche a restaures les données des secteurs défectueux.

Il y a aussi memtest86 a essayer pour tester ta RAM

AzReah · Answer

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 .

AzReah · Answer

Par contre je n'arrive pas a utilisé memtest tu pourras m'aider ?

fabul · Answer

Tu devra te débrouiller un peu car je ne le connais pas vraiment plus que toi memtest86

AzReah · Answer

Ok

AzReah · Answer

Voilà , j'ai fais le chkdsk , le scannow , je dois encore faire le memtest86

Miura564 · Answer

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

AzReah · Answer

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

AzReah · Answer

Ok je les testerai plus tard et j'ai un fixe

AzReah · Answer

Je te donne ma config dans 1 instant

AzReah · Answer

Voilà :
Système d'exploitation
	
Windows 7 Edition Familiale Premium ?(X64)? Service Pack 1
Date d'installation: 06/03/2013
	

Processeur
	
Intel Core i5 2300 Cadencé à 2.80 GHz
Nombre de coeurs: 4 physique(s), 4 logique(s)
Socket: Socket 1155 LGA
	

Carte mère
	
MEDIONPC MS-7707 1.1
Numéro de série (carte mère): To be filled by O.E.M.
SKU Number: To be filled by O.E.M.
Version du bios: E7707MLN.10E
Date: 01/04/2011
	

Chipset
	
Pont nord : Intel Sandy Bridge
Identifiant de révision: 09
Pont sud : Intel P67
Identifiant de révision: B3
	

Mémoire
	
4 Go de mémoire totale de type DDR3
Timings mémoire: 9.0 clocks-9 clocks-9 clocks-24 clocks-1 TT
Barrette Micron Technology de 2 Go
Fréquence maximale: 667 MHz
Bande passante: PC3-10700
Barrette Micron Technology de 2 Go
Fréquence maximale: 667 MHz
Bande passante: PC3-10700
	

Carte Graphique
	
NVIDIA GeForce GTX 770
Version DirectX installée: 11.0
	

Disque dur
	
Disque dur ST32000542AS de 1.82 To SATA II
Firmware: CC34
Version du SATA: SATA Rev 2.6
Numéro de série: 5XW2DZFR
Température HDD: 38 °C
Temps de fonctionnement: 5868 heures
Disque dur Generic CF Card Reader USB Device
Disque dur Generic SD MS Reader USB Device
Disque dur Generic SMC xD Reader USB Device
	

Lecteurs optiques
	
TSSTcorp CDDVDW SH-S223C
Version du firmware: ME02
	

Réseau
	
Microsoft Virtual WiFi Miniport Adapter
Type d'adaptateur: IEEE 802.11 wireless
Realtek RTL8191SU Wireless LAN 802.11n USB 2.0 Network Adapter
Type d'adaptateur: IEEE 802.11 wireless
Intel(R) 82579V Gigabit Network Connection
Type d'adaptateur: ethernet
Hamachi Network Interface
Type d'adaptateur: ethernet
Software Loopback Interface 1
Type d'adaptateur: Loopback
	

Cartes multimedia
	
Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller
NVIDIA Corporation GK104 HDMI Audio Controller
	

Clavier
	
Logitech HID-compliant Unifying keyboard
Logitech, Inc. Unifying Receiver (USB Receiver)
	

Souris
	
Logitech, Inc. Unifying Receiver (USB Receiver)
Logitech HID-compliant Unifying Mouse
	

Ecran(s)
	
LCDTV16
Fabricant: Targa
Resolution maximum: 1920 x 1080
Taille de l'écran: 72.3" (160 cm x 90 cm)
Date de fabrication: 07/01/2008
Ratio d'aspect: 16:9
Type d'entrée vidéo: 0.7V/0.3V (1Vp-p) Analog Signal
	

Périphérique USB
	
Logitech, Inc. Unifying Receiver (USB Receiver)
Version USB supportée: 2.0
Razer USA, Ltd Razer Kraken 7.1
Version USB supportée: 2.0
Alcor Micro Corp. Multimedia Card Reader (USB Card Reader)
Version USB supportée: 2.0
IMC Networks Mediao 802.11n WLAN [Realtek RTL8191SU] (RTL8191S WLAN Adapter )
Version USB supportée: 2.0

AzReah · Answer

Je vais partir je serai de retour dans +- 1h30 en tout cas merci pour ton aide ;)

Miura564 · Answer

pas de soucis on va continuer à chercher mais moi aussi je dois m'absenter, de retour vers 14h

Plusieurs BSOD différents depuis une semaine ! - Page 2

Discussions similaires

Newsletters