Ecran bleu à l'ouverture de la sessio

benzetor Messages postés 5 Statut Membre -  
Malekal_morte- Messages postés 178136 Date d'inscription   Statut Modérateur, Contributeur sécurité Dernière intervention   -
Bonjour,

Depuis hier je n'arrive plus à ouvrir ma session sur Windows 7 (session unique) la page se charge un bout de temps, puis cette écran bleu apparaît (image jointe) . Je ne suis pas très calé en informatique du coup j'aurai besoin d'aide.

Merci d'avance

5 réponses

  1.
    Malekal_morte- Messages postés 178136 Date d'inscription   Statut Modérateur, Contributeur sécurité Dernière intervention   24 711
     
    Salut,

    Utilise Whocrashed : Telecharger WhoCrashed
    => Tutoriel WhoCrashed
    Fais un copier/coller du contenu ici comme indiqué dans le tuto.

    puis :

    Suis le tutoriel FRST. ( prends le temps de lire attentivement - tout y est bien expliqué ).

    Télécharge et lance le scan FRST, 3 rapports FRST seront générés :
    • FRST.txt
    • Shortcut.txt
    • Additionnal.txt


    Envoie ces 3 rapports sur le site http://pjjoint.malekal.com/ et en retour donne les 3 liens pjjoint qui mènent aux rapports ici dans une nouvelle réponse afin que l'on puisse les consulter.

    Veuillez appuyer sur une touche pour continuer la désinfection...
    0
  2. benzetor Messages postés 5 Statut Membre
     
    Merci beaucoup pour votre réponse Malekal_morte- , mais je ne peux rien faire puisque je n'ai pas accès à ma session. Est ce possible de le faire en mode sans échec ?

    Pourriez-vous m'indiquer si mon image de l'écran bleu apparaît, je n'en suis pas sûr ?
    0
    1. Malekal_morte- Messages postés 178136 Date d'inscription   Statut Modérateur, Contributeur sécurité Dernière intervention   24 711
       
      tente en mode sans échec.
      Si tu as Avast!, désinstalle le.

      Tu peux utiliser le cleaner par clef USB : https://www.avast.com/fr-fr/uninstall-utility
      0
  3. benzetor Messages postés 5 Statut Membre
     
    Rapport WhoCrashed

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

    Computer name: KARTHIK-PC
    Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    Windows dir: C:\Windows
    Hardware: HP EliteBook 8570p, Hewlett-Packard, 17A7
    CPU: GenuineIntel Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz Intel586, level: 6
    4 logical processors, active mask: 15
    RAM: 3097022464 bytes total

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

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Mon 3/20/2017 4:13:15 PM your computer crashed
    crash dump file: C:\Windows\Minidump\032117-15054-01.dmp
    This was probably caused by the following module: tcpipreg.sys (tcpipreg+0x4287)
    Bugcheck code: 0xC4 (0x0, 0x0, 0x0, 0x0)
    Error: DRIVER_VERIFIER_DETECTED_VIOLATION
    file path: C:\Windows\system32\drivers\tcpipreg.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: TCP/IP Registry Compatibility Driver
    Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
    The driver requested a zero-byte pool allocation. 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 DRIVER_VERIFIER_DETECTED_VIOLATION

    On Mon 3/20/2017 4:13:15 PM your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: tcpipreg.sys (tcpipreg+0x4287)
    Bugcheck code: 0xC4 (0x0, 0x0, 0x0, 0x0)
    Error: DRIVER_VERIFIER_DETECTED_VIOLATION
    file path: C:\Windows\system32\drivers\tcpipreg.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: TCP/IP Registry Compatibility Driver
    Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
    The driver requested a zero-byte pool allocation. 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 DRIVER_VERIFIER_DETECTED_VIOLATION

    On Mon 3/20/2017 4:11:37 PM your computer crashed
    crash dump file: C:\Windows\Minidump\032017-18330-01.dmp
    This was probably caused by the following module: tcpipreg.sys (tcpipreg+0x4287)
    Bugcheck code: 0xC4 (0x0, 0x0, 0x0, 0x0)
    Error: DRIVER_VERIFIER_DETECTED_VIOLATION
    file path: C:\Windows\system32\drivers\tcpipreg.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: TCP/IP Registry Compatibility Driver
    Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
    The driver requested a zero-byte pool allocation. 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 DRIVER_VERIFIER_DETECTED_VIOLATION

    On Mon 3/20/2017 4:10:00 PM your computer crashed
    crash dump file: C:\Windows\Minidump\032017-16629-01.dmp
    This was probably caused by the following module: tcpipreg.sys (tcpipreg+0x4287)
    Bugcheck code: 0xC4 (0x0, 0x0, 0x0, 0x0)
    Error: DRIVER_VERIFIER_DETECTED_VIOLATION
    file path: C:\Windows\system32\drivers\tcpipreg.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: TCP/IP Registry Compatibility Driver
    Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
    The driver requested a zero-byte pool allocation. 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 DRIVER_VERIFIER_DETECTED_VIOLATION

    On Mon 3/20/2017 3:57:46 PM your computer crashed
    crash dump file: C:\Windows\Minidump\032017-14367-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0x4106F)
    Bugcheck code: 0xA (0x16, 0x2, 0x0, 0xFFFFFFFF82C8CAE8)
    Error: 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 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 that cannot be identified at this time.

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

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

    tcpipreg.sys (TCP/IP Registry Compatibility Driver, Microsoft Corporation)

    If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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.
    0

  5. Vous n’avez pas trouvé la réponse que vous recherchez ?

    Posez votre question
  6. Malekal_morte- Messages postés 178136 Date d'inscription   Statut Modérateur, Contributeur sécurité Dernière intervention   24 711
     
    Vas dans le Panneau de configuration
    et désinstalle tout ça :
    BingProvidedSearch
    tous les programmes Cisco
    Java
    SafeZone Stable

    ~~

    Passe un coup de SFC en suivant le tutoriel System File Check

    0
    2. benzetor Messages postés 5 Statut Membre
       
      Bonjour Malekal_morte- merci encore pour tout ce que vous faîtes pour moi.
      Je n'ai pas pu supprimer les programmes Cisco car ils ne sont pas présent dans mon panneau de config, dois-je supprimer le dossier Cisco dans Program Files ? Pour SafeZone Stable je ne le vois ni dans le panneau de config ni dans Program Files. Tout le reste a été supprimé et j'ai passé un coup de SFC.

      Pour le driver verifier, j'avais bien compris que c'est lui qui causait l'écran bleu à l'ouverture de session, sauf que je l'avais activé car j'avais un écran bleu du tupe "IRQL_NOT_LESS_OR_EQUAL" qui arrivait régulièrement. Sa désactivation m'a permis d'accéder à ma session (ce à quoi je t'en remercie infiniment) mais je ne sais pas encore si le premier problème est résolu à l'heure actuelle dois-je repasser un coup de WhoCrashed ?
      0
      1. Malekal_morte- Messages postés 178136 Date d'inscription   Statut Modérateur, Contributeur sécurité Dernière intervention   24 711 > benzetor Messages postés 5 Statut Membre
         
        Essaye ça :

        Touche Windows + R
        tape regedt32.exe
        et ok

        Déroule à gauche

        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces\<your-adapter-interface>

        Si tu as IPAdress
        qui est à null (ou vide).
        Supprime IPAdress et redémarre l'ordinateur.
        0

Discussions similaires

Carte bancaire dans machine à laver
Nicolas -
kusanagi79 -

5 réponses
Machine à laver CB
Imane -
fabul -

2 réponses