1.Offres Promotionnelles - Livraison 728x90

Mon PC crashe, aidez moi !

Le matériel conseillé, compatibilité, problèmes, périphériques.

Mon PC crashe, aidez moi !

Messagede odanija » Dim 10 Juin 2012 13:36

Bonjour,

J'ai trouvé sur votre forum un post expliquant que, quand le PC crashe, il fallait charger WhoCrashed et que vous acceptiez de lire le rapport du logiciel et d'aider.

Alors, je me permets de vous poster le résultat ci-dessous.

Je vois que c'est un problème lié à : iastor.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation).
Mmais je ne sais pas trop comment m'y prendre pour résoudre.

MOn PC est un portable ASUS U46S.

Merci de vos conseils.

Odanija



Welcome to WhoCrashed (HOME EDITION) v 3.05
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.


To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.



--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: AUDREYPORTABLE
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8496291840 total
VM: 2147352576, free: 1954435072



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sat 09/06/2012 16:08:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060912-22276-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80011C0260, 0xFFFFFA80011C0280, 0x402560A)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 which cannot be identified at this time.


On Sat 09/06/2012 16:08:24 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: iastor.sys (iaStor+0x22066)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80011C0260, 0xFFFFFA80011C0280, 0x402560A)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\iastor.sys
product: Intel Rapid Storage Technology driver
company: Intel Corporation
description: Intel Rapid Storage Technology driver - x64
Bug check description: This indicates that a pool header is corrupt.
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.
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: iastor.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation).
Google query: iastor.sys Intel Corporation BAD_POOL_HEADER




On Fri 11/05/2012 14:23:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051112-24975-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0xC5 (0xA, 0x2, 0x1, 0xFFFFF800031B0617)
Error: DRIVER_CORRUPTED_EXPOOL
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 system attempted to access invalid 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. 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 which cannot be identified at this time.


On Fri 11/05/2012 14:16:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051112-24726-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0x19 (0x20, 0xFFFFFA800193ABC0, 0xFFFFFA800193AC10, 0x405AD98)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 which cannot be identified at this time.



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

4 crash dumps have been found and analyzed. A third party driver has 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:

iastor.sys (Intel Rapid Storage Technology driver - x64, Intel 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 actually 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.
odanija
 
Messages: 2
Inscription: Dim 10 Juin 2012 13:32

Re: Mon PC crashe, aidez moi !

Messagede nardino » Dim 10 Juin 2012 17:39

Bonjour,
Dans le BIOS, désactive le Raid et le mode AHCI pour tester.
@+
Image
En cas de problème constaté sur un sujet, contactez un modérateur par MP. N'intervenez pas vous-même. Merci
Avatar de l’utilisateur
nardino
 
Messages: 6342
Inscription: Dim 11 Jan 2009 16:03
Localisation: Reims

Re: Mon PC crashe, aidez moi !

Messagede odanija » Mer 13 Juin 2012 11:35

Bonjour,

"Désactiver le Bios et activer le Raid" : heu... je ne sais pas ce que ça veut dire.
Mais si vous pouvez me donner un pas à pas, je veux bien essayer.
odanija
 
Messages: 2
Inscription: Dim 10 Juin 2012 13:32

Re: Mon PC crashe, aidez moi !

Messagede nardino » Mer 13 Juin 2012 12:31

Bonjour,

Quand on ne sait pas, ce n'est pas un reproche, il faut au moins être attentif.
Je dis : dans le BIOS il faut désactiver le raid et le mode AHCI et tu interprètes par : désactiver le BIOS et activer le raid, même si tu ne sais pas à quoi cela correspond, tu vois bien que ce n'est pas la même chose.
Ceci étant dit, je vais e donner des instructions les plus claires possibles.
Pour accéder au BIOS, il faut tapoter quelques secondes sur la touche Suppr ou la touche F2 selon les marques des ordinateurs. Ceci dès que tu as appuyé sur la touche de démarrage du pc.

Je cite
Le Bios ( Basic Input Output System ) est un programme logé dans une mémoire non volatile (située sur la carte mère du PC) et chargé de la gestion des composants électroniques de l'ordinateur. Il effectue de nombreux tests à la mise sous tension du PC.
Il met en route et règle les périphériques et autres cartes d'extension en fonction de paramètres fixés par le constructeur, paramètres que vous pouvez toutefois modifier pour améliorer les performances de votre machine.

Il existe deux grandes familles de Bios : les Bios Award, conçus par Phoenix, et les Bios Ami, développés par American Megatrends. Le nom du Bios installé sur votre PC s'affiche brièvement à la mise sous tension.

Pour accéder aux paramètres du Bios, maintenez la touche Suppr de votre clavier enfoncée à l'allumage si vous avez un Bios Award, ou la touche F2 si vous avez un Bios Ami.

Il est possible que ces touches soient inactives sur votre ordinateur (sur des PC de marque Compaq, par exemple, c'est souvent la touche F10 qui donne accès au Bios). Dans ce cas, la touche à utiliser figure dans le mode d'emploi de votre ordinateur ou de sa carte mère.
Elle apparaît brièvement à l'écran juste après avoir allumé le PC.


Voici ce que tupeux voir dans un BIOS AMI : http://www.tutoriaux-excalibur.com/astu ... 1-ahci.png
A l'aide des flèches du clavier tu sélectionnes IDE et tu valides par la touche F10 puis tu acceptes les modifications.

Le pc va redémarrer, donne des nouvelles.
@+
Image
En cas de problème constaté sur un sujet, contactez un modérateur par MP. N'intervenez pas vous-même. Merci
Avatar de l’utilisateur
nardino
 
Messages: 6342
Inscription: Dim 11 Jan 2009 16:03
Localisation: Reims


Retourner vers Matériels

Qui est en ligne

Utilisateurs parcourant ce forum: Bing [Bot] et 0 invités

Livre photo