Auteur Sujet: blue screen  (Lu 18325 fois)

0 Membres et 1 Invité sur ce sujet

Hors ligne couloulou2108

  • Membres
  • Members
  • Messages: 21
blue screen
« le: janvier 27, 2014, 15:10:56 »
Bonjour,

Ma demande concerne mon pc asus sous vista, qui ces derniers temps s'éteint intempestivement, et avant de s'éteindre m'affiche ce fameux écran bleu.
J'ai déjà fait un malware et un adwcleaner et effacé les fichiers suspects.
Mais rien n'y fait.
Pourriez-vous éclairer ma lanterne de vos connaissances?
Je vous serai très reconnaissante!!
Merci pour votre aide.

Em

Hors ligne hyunkel30

  • Ancien du Staff
  • Mega Power Members
  • ****
  • Messages: 21887
  • Le monde est devenu fou ...
Re : blue screen
« Réponse #1 le: janvier 27, 2014, 19:59:18 »
 :AAC Bonjour couloulou2108,

On va déjà regarder à quoi est lié l'écran bleu, car cela ne signifie pas obligatoirement une infection :

Télécharge Whocrashed (de Daniel Ternhell) sur ton bureau.

  • Double-clique sur whocrashedSetup.exe pour lancer l'installation.
    (utilisateur de Windows Vista\7\8 : clique droit sur whocrashedSetup.exe et sélectionne "exécuter en tant qu'administrateur")

  • Suis le processus d'installation puis lance le programme.
  • Clique sur "Analyze" en haut.

  • Descend l'ascenseur et copie-moi le contenu de l'encart "Crash Dump Analysis" dans ta prochaine réponse.
    (Note : s'il y de nombreux rapport, seulement les deux derniers)

  • Ferme le programme.

Hors ligne couloulou2108

  • Membres
  • Members
  • Messages: 21
Re : blue screen
« Réponse #2 le: janvier 28, 2014, 17:37:53 »
Bonsoir,

Merci de votre réponse rapide, voici le copier coller de l'analyse:

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 25/01/2014 11:20:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012514-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Sat 25/01/2014 11:20:10 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x2971)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: ntkrpamp.exe .
Google query: ntkrpamp.exe DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 24/01/2014 18:14:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012414-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5AD54)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Wed 22/01/2014 19:04:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012214-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5AD54)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Wed 22/01/2014 17:52:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012214-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5AD54)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Tue 21/01/2014 19:20:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012114-02.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0xA5C06)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF8EEA5C06, 0xFFFFFFFF8C86DAC8, 0xFFFFFFFF8C86D7C4)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: ATI Technologies Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Tue 21/01/2014 16:58:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012114-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5AD54)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Sun 19/01/2014 11:32:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011914-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5AD54)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Sat 18/01/2014 19:39:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011814-03.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5AD54)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Sat 18/01/2014 18:06:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011814-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5AD54)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.




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

11 crash dumps have been found and analyzed. Only 10 are included in this report. 3 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:

atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)
ntkrpamp.exe
avgntflt.sys

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.





Hors ligne hyunkel30

  • Ancien du Staff
  • Mega Power Members
  • ****
  • Messages: 21887
  • Le monde est devenu fou ...
Re : blue screen
« Réponse #3 le: janvier 28, 2014, 19:35:56 »
Re,

Ok, ça crash dur effectivement  ;D

Bon, la plupart ne sont pas déterminant, impossible de savoir ce qui est en cause.
Pour le reste, deux choses ressortent, le pilote de ta carte graphique, et le pilote de ton antivirus.

Avant d'aller plus loin, je vais faire un second diagnostic s'il te plait :

Télécharge Farbar Recovery Scan Tool (de Farbar) sur ton Bureau.

Attention: Tu dois lancer la version compatible avec ton système : 32 ou  64bits.

Sous IE9 ou IE10, le filtre SmartScreen déclenche une alerte. Cliquer sur Actions puis sur Exécuter quand même

  • Double-clique sur l'outil pour le lancer. Quand l'outil se lance, clique sur Yes pour accepter le disclamer.
  • Clique sur le bouton  Scan.
  • L'outil va créer un rapport nommé FRST.txt, enregistré dans le même dossier que l'outil.
  • A son premier lancement, l'outil va aussi créer un fichier nommé Addition.txt).
Poste les deux rapports générés.


Hors ligne couloulou2108

  • Membres
  • Members
  • Messages: 21
Re : blue screen
« Réponse #4 le: janvier 29, 2014, 14:21:09 »

Hors ligne hyunkel30

  • Ancien du Staff
  • Mega Power Members
  • ****
  • Messages: 21887
  • Le monde est devenu fou ...
Re : blue screen
« Réponse #5 le: janvier 29, 2014, 19:07:45 »
Re,

Y'aura du ménage à faire ensuite, y'a des adwares sur ce pc.

Pour les bluescreen, cela sembla avoir démarré après l'installation de ce pilote :
hamachi_2-2-0-109_fr_14515.msi

C'était un pilote pour quoi ? Webcam ?
C’est lié à LogMeIn peut-être (bureau à distance)

Cela te parait plausible avec le début des plantages ?

Hors ligne couloulou2108

  • Membres
  • Members
  • Messages: 21
Re : blue screen
« Réponse #6 le: janvier 29, 2014, 20:33:08 »
Oui c'est lié à logmein et hamachi sont lié, ça me sert pour mon réseau minecraft. Et oui, ça a commencé à buger à partir de son installation. Dois-je le supprimer?
Merci

Hors ligne hyunkel30

  • Ancien du Staff
  • Mega Power Members
  • ****
  • Messages: 21887
  • Le monde est devenu fou ...
Re : blue screen
« Réponse #7 le: janvier 29, 2014, 21:59:12 »
Re,

Au choix, désinstaller ou restaurer ton système à un point de restauration avant l'installation (mais je crois qu'il ne remontent pas assez loin d'après ce que je vois sur les rapports ... )

On verra déjà si cela stabilise le système ou pas.

 :AAN

Hors ligne couloulou2108

  • Membres
  • Members
  • Messages: 21
Re : blue screen
« Réponse #8 le: janvier 31, 2014, 20:08:25 »
j'ai désinstallé Log Me in hamachi que dois je faire maintenant ?  :III

Hors ligne couloulou2108

  • Membres
  • Members
  • Messages: 21
Re : blue screen
« Réponse #9 le: janvier 31, 2014, 20:12:37 »
apparemment le "blue screen" ne venait que de là j'ai réussi a éteindre mon ordinateur normalement sans que cet écran bleu s'affiche mais ai-je encore quelque chose a faire ?  :BAN

Hors ligne hyunkel30

  • Ancien du Staff
  • Mega Power Members
  • ****
  • Messages: 21887
  • Le monde est devenu fou ...
Re : blue screen
« Réponse #10 le: janvier 31, 2014, 22:16:39 »
Re,

Bonne nouvelle ;)

On va juste faire un peu de ménage avant de conclure, tu as quelques adwares (logiciels publicitaires)


1) Désinstalle les programmes suivants dans ta liste des programmes (si présents) :

Note : Si tu rencontres une erreur passe au suivant et poursuis la procédure

- CCleaner Packages (adware : logiciel publicitaire)
- Shopping Helper Smartbar (idem)




/!\ Crée un point de restauration manuel avant d'appliquer le correctif - Tutoriel en images /!\

  • Ouvre le Bloc-notes (Démarrer => Tous les programmes => Accessoires => Bloc-notes)
  • Copie/colle la totalité du contenu de la zone Code ci-dessous dans le Bloc-notes

start
Task: {1B0231E9-EA33-489B-998D-F47209A83ADD} - System32\Tasks\wp_update => C:\Users\zac77\AppData\Roaming\~tolzwjg.exe
HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\Hamachi2Svc => ""="Service"
HKLM\...\Run: [LogMeIn Hamachi Ui] - C:\Program Files\LogMeIn Hamachi\hamachi-2-ui.exe [3806544 2013-11-29] (LogMeIn Inc.)
HKLM\...\Run: [tuto4pc_fr_68] - "C:\Program Files\tuto4pc_fr_68\tuto4pc_fr_68.exe"
HKLM\...\Run: [LogMeIn GUI] - "C:\Program Files\LogMeIn\x86\LogMeInSystray.exe"
HKCU\...\Run: [Software updater] - "C:\Users\zac77\AppData\Roaming\FreeSoftwareUpdater\updater.exe" -h http://neoupdater.com/
Startup: C:\Users\zac77\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\MyPC Backup.lnk
ShortcutTarget: MyPC Backup.lnk -> C:\Program Files\MyPC Backup\MyPC Backup.exe (No File)
SearchScopes: HKCU - URL http://http://www.golsearch.com//?q={searchTerms}&babsrc=SP_ss_Btisdt6&mntrId=901B0015AFAE86CF&affID=119357&tt=200813_246&tsp=4982
BHO: No Name - {602ADB0E-4AFF-4217-8AA1-95DAC4DFA408} - No File
Toolbar: HKLM - No Name - {7FEBEFE3-6B19-4349-98D2-FFB09D4B49CA} - No File
FF Extension: Plus-HD-4.9 - C:\Users\zac77\AppData\Roaming\Mozilla\Firefox\Profiles\011dwexj.default\Extensions\d019febe-eb2b-4057-a3f2-7def88f2c9cd@1cced8ec-0ffe-43ea-b4b2-fbce5de8e9a4.com [2014-01-27]
FF HKCU\...\Firefox\Extensions: [lwoofer@lyricswoofer.co] - C:\Program Files\LyricsWoofer\128.xpi
CHR Extension: (Plus-HD-4.9) - C:\Users\zac77\AppData\Local\Google\Chrome\User Data\Default\Extensions\jjflmfkjppbmejlfbhlpgjnomdoefkfa [2014-01-07]
CHR HKLM\...\Chrome\Extension: [kbjlipmgfoamgjaogmbihaffnpkpjajp] - C:\Program Files\Nosibay\Bubble Dock\extensions\GCSurfMatch.crx [2013-08-23]
R2 Hamachi2Svc; C:\Program Files\LogMeIn Hamachi\hamachi-2.exe [1664336 2013-11-29] (LogMeIn Inc.)
R2 LMIGuardianSvc; C:\Program Files\LogMeIn Hamachi\LMIGuardianSvc.exe [375056 2013-10-11] (LogMeIn, Inc.)
R3 hamachi; C:\Windows\System32\DRIVERS\hamachi.sys [26176 2009-03-18] (LogMeIn, Inc.)
C:\Program Files\Nosibay
C:\Program Files\LyricsWoofer
C:\Program Files\MyPC Backup
C:\Users\zac77\AppData\Roaming\FreeSoftwareUpdater
C:\Program Files\tuto4pc_fr_68
C:\Program Files\LogMeIn Hamachi
C:\Users\zac77\AppData\Roaming\~tolzwjg.exe
end
  • Enregistre le fichier sur ton Bureau (au même endroit que FRST) sous le nom fixlist.txt
  • Ferme toutes les applications, y compris ton navigateur
  • Double-clique sur FRST.exe
    /!\ Sous Vista, Windows 7 et 8, il faut lancer le fichier par clic-droit -> Exécuter en tant qu'administrateur
  • Sur le menu principal, clique une seule fois sur Fix et patiente le temps de la correction

  • L'outil va créer un rapport de correction Fixlog.txt. Poste ce rapport dans ta réponse.
/!\ Ce script a été établi pour cet utilisateur, il ne doit, en aucun cas, être appliqué sur un autre système, au risque de provoquer de graves dysfonctionnement et endommager Windows /!\



Télécharge AdwCleaner (de Xplode) sur ton Bureau.


  • Double-clique sur adwcleaner0.exe pour lancer le programme.
    (Utilisateur de Vista/Windows 7, clique-droit sur le fichier adwcleaner0.exe -> Exécuter en tant qu'administrateur)
  • Dans la fenêtre principal, choisis l'option Recherche.
  • A la fin, un rapport apparaitra (sinon, il est situé ici C:\AdwCleaner[Rx].txt). Poste-le dans ta prochaine réponse.



Hors ligne couloulou2108

  • Membres
  • Members
  • Messages: 21
Re : blue screen
« Réponse #11 le: février 01, 2014, 17:10:28 »
je n'ai pas encore fait les rapports mais je jouais 1 h après je décide de mettre mon ordinateur en veille et là écran tout noir mais mon ordinateur n'est toujours pas en veille je décide donc de l'éteindre avec le bouton qui sert a allumer l'ordinateur, je le rallume et là windows a détecté d'un arrêt non planifié, nom de l'événement: blue screen  :'(  HELP

Hors ligne couloulou2108

  • Membres
  • Members
  • Messages: 21
Re : blue screen
« Réponse #12 le: février 01, 2014, 17:13:30 »
est-ce que les rapports servent à enlever ce qui reste de blue screen ou est-ce juste pour vérifier si il ne reste rien ?

Hors ligne hyunkel30

  • Ancien du Staff
  • Mega Power Members
  • ****
  • Messages: 21887
  • Le monde est devenu fou ...
Re : blue screen
« Réponse #13 le: février 01, 2014, 18:24:54 »
Re,

La procédures doit être faite, car elle va en même temps supprimer les restes de LoginMe et des adwares. ;)

Pour l'arrêt inopiné, refais ceci ensuite :

Relance WhoCrashed :

  • Lance le programme depuis ton bureau ou le menu "Tous les programmes".
  • Clique sur "Analyze" en haut.

  • Descend l'ascenseur et copie-moi le contenu de l'encart "Crash Dump Analysis" dans ta prochaine réponse.
    (Note : s'il y de nombreux rapport, seulement les deux derniers)

  • Ferme le programme.

Hors ligne couloulou2108

  • Membres
  • Members
  • Messages: 21
Re : blue screen
« Réponse #14 le: février 03, 2014, 14:47:40 »
Bonjour,
Voici les rapports! Merci

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 01/02/2014 16:04:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020114-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DECD)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Sat 01/02/2014 16:04:36 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x2855)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: ntkrpamp.exe .
Google query: ntkrpamp.exe DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sat 01/02/2014 16:00:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020114-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DECD)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Sat 25/01/2014 11:20:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012514-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Fri 24/01/2014 18:14:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012414-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5AD54)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Wed 22/01/2014 19:04:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012214-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5AD54)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Wed 22/01/2014 17:52:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012214-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5AD54)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Tue 21/01/2014 19:20:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012114-02.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0xA5C06)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF8EEA5C06, 0xFFFFFFFF8C86DAC8, 0xFFFFFFFF8C86D7C4)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: ATI Technologies Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Tue 21/01/2014 16:58:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini012114-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5AD54)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Sun 19/01/2014 11:32:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011914-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x5AD54)
Bugcheck code: 0xD1 (0xFFFFFFFFCFF30023, 0xFF, 0x8, 0xFFFFFFFFCFF30023)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.

Hors ligne hyunkel30

  • Ancien du Staff
  • Mega Power Members
  • ****
  • Messages: 21887
  • Le monde est devenu fou ...
Re : blue screen
« Réponse #15 le: février 03, 2014, 19:46:50 »
Re,

Toujours le même module qui revient, mais qui est un fichier de base de Windows, sans indication de quel driver le fait planter.

On va quand même tester de mettre à jour le pilote de carte graphique

Tu connais ton modèle de carte graphique ?
Ou à défaut le modèle exact de ton pc ?

Hors ligne couloulou2108

  • Membres
  • Members
  • Messages: 21
Re : blue screen
« Réponse #16 le: février 04, 2014, 11:05:14 »
Bonjour,
Alors ma carte graphique est ATI Mobility Radeon HD 3470 version  8.451.0.0et elle semble fonctionnée par contre le rapport d'erreurs de la carte annonce 21857 évènements dont 130 dans les 7 derniers jours. Et mon Pc est un ASUS F5 entertainement System.

Merci pour votre aide.
Bonne journée.
 8)

Hors ligne hyunkel30

  • Ancien du Staff
  • Mega Power Members
  • ****
  • Messages: 21887
  • Le monde est devenu fou ...
Re : blue screen
« Réponse #17 le: février 04, 2014, 16:29:41 »
Re,

Ok, à télécharger et installer :
http://www2.ati.com/drivers/legacy/13-9-legacy_vista_win7_32_dd_ccc_whql.exe

Inutile d'installer autre chose que le pilote si tu en as la possibilité ;)

Redémarre ensuite le pc, puis regarde si le bluescreen réapparait ou pas.

 :AAN

Hors ligne couloulou2108

  • Membres
  • Members
  • Messages: 21
Re : blue screen
« Réponse #18 le: février 09, 2014, 11:13:13 »
j'ai téléchargé le pilote et apparemment blue screen n'est plus la mais a la place de blue screen il fait exactement la même chose mais c'est un écran noir  :hun:

Hors ligne hyunkel30

  • Ancien du Staff
  • Mega Power Members
  • ****
  • Messages: 21887
  • Le monde est devenu fou ...
Re : blue screen
« Réponse #19 le: février 09, 2014, 12:33:23 »
Re,

Alors le souci est peut-être bien matériel ...
C'est la carte graphique d'origine, tu ne l'as pas changée depuis que tu as le PC ?

Hors ligne couloulou2108

  • Membres
  • Members
  • Messages: 21
Re : blue screen
« Réponse #20 le: février 09, 2014, 12:44:47 »
je n'ai pas acheté moi même le pc je l'ai acheté a quelqu' un qui l'avait déjà utilisé mais cela fait 2 ans que je l'ai et je n'ai eu aucun problème 

Hors ligne couloulou2108

  • Membres
  • Members
  • Messages: 21
Re : blue screen
« Réponse #21 le: février 09, 2014, 12:49:43 »
pour info j'ai téléchargé la carte graphique ATI Mobility Radeon HD 3400 series

Hors ligne hyunkel30

  • Ancien du Staff
  • Mega Power Members
  • ****
  • Messages: 21887
  • Le monde est devenu fou ...
Re : blue screen
« Réponse #22 le: février 09, 2014, 15:02:45 »
Re,

de mon côté je ne peux plus faire grand chose ...
Soit c'est un souci matériel, et il faudrait vérifier la carte graphique, soit c'est un souci lié au système et il faudrait réinstaller, ce qui signifie tout remettre à zéro à partir d'un DVD vista ou de sauvegarde/recovery que tu aurais eu avec le pc ...
Car il ne semble pas comporter de partition réservée pour cela, ce qui est étrange par ailleurs ...

C'est un pc "monté" ou bien un pc de marque (ASUS par exemple) ?

Tags: