Bonjour,
Voila je vous explique mon probleme,
J'ai installé un jeu hier soir a 18h et des bananes ce que a priori je n'aurais jamais du faire puisqu'il a fait crash mon pc.
Reboot-->Accueil Packard Bell-->Démarrage de Windows-->Bienvenue-->Et la sa plante a chaque démarrage.
UN ÉCRAN BLEU
Descriptif des info donné par cet erreur (Les grandes lignes):
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Technical information:
***STOP:0x00000000000000SE,(0x0000000000000002,0x00000000000001,0xfffff(880010490f6)
*** Storport.sys -Adress fffff880010490f6 base at fffff8800104800,Datestamp 4a5baces
Collecting data for crashdump...
Initializing disk for crash dump...
Begining demo of physical memory...
Dumping physical memory to disk:xx%
Voila des info sur mon pc:
Packard Bell modèle imediaS1300
Processeur AMD Athlon(tm)II 170u processor 2.01GHz
RAM 4Go
Carte graphique: ENGTX460 Direct cu GDDR5 1GB
Carte réseau: NVIDIA Nforce 10/100Mbps Ethernet
Démarrage du pc je tape donc F8
Les actions déjà exécutée:
1 Réparation du système:
Réparation du démarrage >> Il n'a trouvé aucun problème
Restauration du système >> J'ai essayer 4 restauration ca n'a rien changée
Récupération de l'image système >> Aucune image disponible
Diagnostic de mémoire Windows >> Il n'a trouvé aucun problème
Invité de commande >> CHKDSK n'a rien trouvé
Recovery management >> Si je pouvais éviter celui la ca m'arrangerais
2 Mode sans échec avec ou sans prise en charge réseau:
Marche 2 fois sur 3. Les fois ou sa bloque le chargement s'arrête a Windows\System32\Drivers\Classpnp.sys
3 Démarrer Windows normalement
J'accède a mon bureau 1 fois sur 10 mais hélas une fois dessus je ne peux rien faire.
C'est comme si le système ne répondais pas ou plus
4 Dernière configuration valable connue
Je l'ai lancée ca n'a une fois de plus rien changé
5 Mode débogage
Bloque au démarrage de Windows
6 CCleaner
J'ai tout nettoyer.Aucun changement
7 Avira (anti-virus)
J'ai effectué un scan complet ca ma affiché 4 avertissement (des .exe qui sont sur) et 2 résultat positif que j'ai immédiatement supprimé(ce n'était pas des fichier système)
Conclusion beaucoup d'action pour peu de réussite.
J'ai chercher un peu sur le net avec ma psp , et oui mon seul moyen de liaison avec internet a présent celui d'ailleurs avec lequel je vous écrit , et j'ai trouvé quelque info sur le storport.sys j'ai a priori réglé ce problème (je ne sais pas comment) puisque il ne s'affiche plus sur mon écran bleu.
Maintenant il m'affiche l'erreur suivante:
***STOP: 0x0000000a (0xfffffa88047e59c0, 0x0000000000000002, 0x0000000000000000, 0xfffff800030023da)
Voila 1 dump qui pourrait peut être vous aidée
http://www.megaupload.com/?d=SUO829UC
N'hésiter pas a poser vos question mais répondez moi vite mon pc étant mon outil de travail et mon outil de divertissements je suis bloquée et j'ai bien peur que si je reboot mon pc je ne pourrais pas revenir ici.
SVP aider moi je galère.
Ecran bleu WINRE ne change rien
-
nolin
- Messages : 4
- Enregistré le : dim. 6 mars 2011 18:31
- Etes vous un robot ? : Non
- Localisation : fougere 49150
Re: Ecran bleu WINRE ne change rien
je c'est pas si pas peux venir de ca mais en mode sans échec avec prise en charge réseau mon pc plante quand je veux activer le service audio et pour info le problème storport.sys est revenu
Re: Ecran bleu WINRE ne change rien
Bonjour,
Le fichier déposé sur MegaUpload est indisponible.
Merci de joindre ton fichier dump dans un .zip directement dans ta réponse.
Insérer une image ou un fichier en pièce jointe
@+
Le fichier déposé sur MegaUpload est indisponible.
Merci de joindre ton fichier dump dans un .zip directement dans ta réponse.
Insérer une image ou un fichier en pièce jointe
@+
En cas de problème constaté sur un sujet, alertez un modérateur. N'intervenez pas vous-même. Merci
-
nolin
- Messages : 4
- Enregistré le : dim. 6 mars 2011 18:31
- Etes vous un robot ? : Non
- Localisation : fougere 49150
Re: Ecran bleu WINRE ne change rien
j'ai installé whocrashed sa sera plus rapide de montrer ce qu'il me dit:
System Information (local)
--------------------------------------------------------------------------------
computer name: 103DUBLED
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) II 170u Processor AMD586, level: 16
1 logical processors, active mask: 1
RAM: 4294303744 total
VM: 2147352576, free: 2007392256
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 06/03/2011 19:25:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030611-22027-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFA8805BC7110, 0x2, 0x0, 0xFFFFF800035E03DA)
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 which cannot be identified at this time.
On Sun 06/03/2011 19:25:08 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalMakeBeep+0x1112)
Bugcheck code: 0xA (0xFFFFFA8805BC7110, 0x2, 0x0, 0xFFFFF800035E03DA)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 which cannot be identified at this time.
On Sun 06/03/2011 17:58:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030611-20701-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xD1 (0x68, 0x2, 0x0, 0xFFFFF880010AC0ED)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 06/03/2011 16:34:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030611-19515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFA88047E59C0, 0x2, 0x0, 0xFFFFF800030023DA)
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 which cannot be identified at this time.
On Sun 06/03/2011 16:22:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030611-39343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFA8805904938, 0x2, 0x0, 0xFFFFF800035E83DA)
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 which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
5 crash dumps have been found and analyzed.
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.
System Information (local)
--------------------------------------------------------------------------------
computer name: 103DUBLED
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) II 170u Processor AMD586, level: 16
1 logical processors, active mask: 1
RAM: 4294303744 total
VM: 2147352576, free: 2007392256
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 06/03/2011 19:25:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030611-22027-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFA8805BC7110, 0x2, 0x0, 0xFFFFF800035E03DA)
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 which cannot be identified at this time.
On Sun 06/03/2011 19:25:08 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalMakeBeep+0x1112)
Bugcheck code: 0xA (0xFFFFFA8805BC7110, 0x2, 0x0, 0xFFFFF800035E03DA)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 which cannot be identified at this time.
On Sun 06/03/2011 17:58:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030611-20701-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xD1 (0x68, 0x2, 0x0, 0xFFFFF880010AC0ED)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 06/03/2011 16:34:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030611-19515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFA88047E59C0, 0x2, 0x0, 0xFFFFF800030023DA)
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 which cannot be identified at this time.
On Sun 06/03/2011 16:22:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030611-39343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFA8805904938, 0x2, 0x0, 0xFFFFF800035E83DA)
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 which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
5 crash dumps have been found and analyzed.
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.
-
nolin
- Messages : 4
- Enregistré le : dim. 6 mars 2011 18:31
- Etes vous un robot ? : Non
- Localisation : fougere 49150
Re: Ecran bleu WINRE ne change rien
Bon étant donné que je ne pouvais pas attendre vos réponse j'ai formater le pc et la
ECRAN BLEU
Mort de rire c'est quoi cette anaque
Du coup ne pouvant plus rien faire puisque windows n'etait plus présent je vais installé ubuntu
Si vous avez des info sur ubuntu ou bien me dire comment remettre windows xp vista ou 7 sa me ferais plaisir
Je ne mais pas résolu pour le moment j'attend d'avoir vérifier que tous fonctionne bien
ECRAN BLEU
Mort de rire c'est quoi cette anaque
Du coup ne pouvant plus rien faire puisque windows n'etait plus présent je vais installé ubuntu
Si vous avez des info sur ubuntu ou bien me dire comment remettre windows xp vista ou 7 sa me ferais plaisir
Je ne mais pas résolu pour le moment j'attend d'avoir vérifier que tous fonctionne bien