Écran bleu svp aide

PaulCarreau69 -  
 Paulcarreau69 -
Bonjour,
J'ai reçue il y a quelques heure mon pc , un vibox , sans Os installé
J'ai dans l'idée de brancher ma clef usb wifi
J'insert le Cd d'installation pour la clef et lorsque que je la branche cela m'affiche un écran bleu avec des écritures , je suis sous windows 7 installer manuellement
Merci de vos réponses rapides je l'espère!

4 réponses

  1. Tharkey
     
    Bonjour,
    Ton pc démarre-t-il et arrive-t-il jusqu'au bureau ?
    0
    1. PaulCarreau69
       
      Merci de ta réponse , et bien oui il fonctionne très bien , j'ai installer tous les drivers , et c'est que lorsque je branche la petite clef que le PC prend un écran bleu..
      0
    2. PaulCarreau69
       
      Merci de ta réponse , et bien oui il fonctionne très bien , j'ai installer tous les drivers , et c'est que lorsque je branche la petite clef que le PC prend un écran bleu..
      0
    3. PaulCarreau69
       
      Oui tout fonctionne très bien .. Besoin d'aide c'est bisarre..
      0
  2. Tharkey Messages postés 183 Statut Membre 14
     
    Télécharge WhoCrashed
    Ensuite tu l'ouvres en cliquant dessus avec le bouton droit de ta souris puis tu choisis Exécuter en tant qu'administrateur
    Puis une fois WhoCrashed ouvert tu cliques sur Analyze copie tout le rapport qui se trouve dans l'onglet Report, poste le rapport sur https://www.cjoint.com/ dont voici un tutoriel : https://www.commentcamarche.net/faq/29493-utiliser-cjoint-pour-heberger-des-fichiers puis met le lien généré par Cjoint dans ta réponse.
    0
    1. paulCarreau69
       
      Je ne peux rien telecharger étant donné que je n'ai pas internet.. Je peux le télécharger sur une clé usb pour le mettre sur le pc qui bug?
      0
    2. Tharkey Messages postés 183 Statut Membre 14
       
      Oui fait ça ! Si tu trouve la procédure cijoint trop complexe fait un simple copier coller du rapport whocrashed dans ta réponse !
      0
    3. paulCarreau69
       
      J'essaye de faire ça au plus vite dans l'après midi au plus vite , merci
      0
    4. Tharkey Messages postés 183 Statut Membre 14
       
      Entendu.
      0
    5. PaulCarreau69 > Tharkey Messages postés 183 Statut Membre
       
      La réponse !
      System Information (local)
      --------------------------------------------------------------------------------

      computer name: PAUL-PC
      windows version: Windows 7 , 6.1, build: 7600
      windows dir: C:\Windows
      Hardware: Gigabyte Technology Co., Ltd., F2A55M-HD2
      CPU: AuthenticAMD AMD A6-6400K APU with Radeon(tm) HD Graphics AMD586, level: 21
      2 logical processors, active mask: 3
      RAM: 2380070912 total
      VM: 2147352576, free: 1964691456




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

      Crash dump directory: C:\Windows\Minidump

      Crash dumps are enabled on your computer.

      On Sun 09/03/2014 14:40:37 GMT your computer crashed
      crash dump file: C:\Windows\Minidump\030914-13868-01.dmp
      This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
      Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
      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 09/03/2014 14:40:37 GMT your computer crashed
      crash dump file: C:\Windows\memory.dmp
      This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x29B3)
      Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
      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 Sun 09/03/2014 14:39:23 GMT your computer crashed
      crash dump file: C:\Windows\Minidump\030914-15210-01.dmp
      This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
      Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
      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 09/03/2014 11:36:51 GMT your computer crashed
      crash dump file: C:\Windows\Minidump\030914-15256-01.dmp
      This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
      Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
      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 09/03/2014 11:09:41 GMT your computer crashed
      crash dump file: C:\Windows\Minidump\030914-16411-01.dmp
      This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
      Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
      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 09/03/2014 10:58:26 GMT your computer crashed
      crash dump file: C:\Windows\Minidump\030914-19094-01.dmp
      This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
      Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
      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 09/03/2014 10:21:27 GMT your computer crashed
      crash dump file: C:\Windows\Minidump\030914-14976-01.dmp
      This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
      Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
      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 09/03/2014 10:14:21 GMT your computer crashed
      crash dump file: C:\Windows\Minidump\030914-15615-01.dmp
      This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
      Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
      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 09/03/2014 10:09:52 GMT your computer crashed
      crash dump file: C:\Windows\Minidump\030914-20264-01.dmp
      This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
      Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
      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
      --------------------------------------------------------------------------------

      9 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:

      ntkrpamp.exe

      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.
      0
  3. Tharkey Messages postés 183 Statut Membre 14
     
    Dsl j'avais du m'absenter un moment.
    Pour commencer, tu vas juste brancher cette clef wifi sur ton autre pc pour voir si il se passe la même chose mais tu ne vas PAS installer les pilotes du cd.
    0
    1. PaulCarreau69
       
      Désole , je suis juste un peu dégouté de ne pouvoir utiliser mon pc au plus vite ^^ je ferai sa demain ou lundi , merci de rester actif , bonne fin de week end
      0
    2. paulCarreau69
       
      Bonjour , alors oui la clef marche sur le pc portable de mon père !
      0
  4. Tharkey Messages postés 183 Statut Membre 14
     
    Bien c'est une bonne chose.
    Pour commencer, désinstalle-la clé wifi de ton vibox.
    0
    1. Paulcarreau69
       
      Excuse moi vraiment pour ces réponses tardives , aurais tu fb ou quelque chose pour parler plus rapidement sans être indiscret? Pour le pc , c'est fait fait , plu aucune trace de cette dernière
      0
    2. Paulcarreau69
       
      Elle est bien desinstallée que dois je faire a présent??
      0