Le blue screen ne s'arrête jamais aIDEZ MOI

sdfsdfsdf -  
luppi Messages postés 1580 Date d'inscription   Statut Membre Dernière intervention   -
Bonjour,

Le bblue screen ne cesse de revenir encore et encore toute les minutes

Il était fréquent, mais depuis une semaine il est devenu quotidien et aujourd'hui il est arrivé 3 fois, et depuis 20 minutes presque toute les minutes mon ordi s'éteint

j'ai quelque chose d'extremement important à vérifier demain sur mon pc, qui me stress à mort, et je dois le vérifier

AIDEZ MOI SVP

17 réponses

  1. sdfsdfsdf
     
    Ne me demandez pas le code, il y en a un différent à CHAQUE FOIS
    0
  2. docsteph Messages postés 8467 Date d'inscription   Statut Membre Dernière intervention   1 192
     
    cela dépend de beaucoup de choses............;
    0
  3. luppi Messages postés 1580 Date d'inscription   Statut Membre Dernière intervention   110
     
    Tension non stable ? à tu bidouiller quelque chose dans le bios ?
    surchauffe ? Ton pc est correctement nettoyé ?
    HDD foutu ? il gratte ? il fait du bruit ? il met du temps à ouvrir un fichier ?
    0
  4. sdfsdfsdf
     
    Non, je n'ai toucher à rien, et il ne fait rien
    0
  5. Vous n’avez pas trouvé la réponse que vous recherchez ?

    Posez votre question
  6. sdfsdfsdf
     
    Je vous en supplie AIDEZ MOI j'ai quelque chose d'extrêmement important à vérifier sur mon pc demain et je n'ai PAS LES MOYENS de me payer une réparation et de perdre mon rodi
    0
  7. sdfsdfsdf
     
    Je crois que ca a un rapport avec ntoskrnl.exe
    0
  8. sdfsdfsdfll
     
    De grâce, aidez moi, si demain je ne peux pas vérifier ce que je vais vérifier cela risque d'avoir un impact sur le restant de MA VIE
    0
  9. sdfsdfsdfll
     
    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sun 15/01/2012 20:55:28 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011512-19484-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xA (0x248, 0x2, 0x1, 0xFFFFF80003078848)
    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 15/01/2012 20:55:28 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0xA (0x248, 0x2, 0x1, 0xFFFFF80003078848)
    Error: IRQL_NOT_LESS_OR_EQUAL
    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 15/01/2012 20:26:00 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011512-20935-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xC5 (0x95395, 0x2, 0x0, 0xFFFFF800031CBB05)
    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 Sun 15/01/2012 17:36:28 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011512-19765-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xD1 (0x667FEBF, 0x2, 0x0, 0xFFFFF880028D7941)
    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 Sat 14/01/2012 14:13:36 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011412-18969-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
    Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    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 program 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.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

    On Thu 12/01/2012 15:03:22 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011212-20779-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xD1 (0x800684F297, 0x2, 0x0, 0xFFFFF880028A1941)
    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 Wed 11/01/2012 21:52:09 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011112-20857-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
    Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    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 program 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.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

    On Tue 10/01/2012 17:42:04 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011012-25381-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xD1 (0x673A4AE, 0x2, 0x0, 0xFFFFF880028BB941)
    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.
    0
  10. sdfsdfsdfll
     
    Voici les écrits du logiciel who crashed

    et apparemment il n'a pas tout notifié vu que j'ai eu le blue screen beaucoup plus de fois que ca aujourd'hui
    0
  11. sdfsdfsdfll
     
    De toute façon je pense que d'ici très peu de temps je ne pourrai même plus en faire

    Ca fait plus d'an un que je parcour les forums et que je pose des questions, et peu de réponse

    si je paie pour cette ordi, j'aurai presque plus de quoi bouffer, et si mon ordi n'est plus là, je peux plus bosser à la maison, et mon patron de vire, après je finirai tout bonnement à la rue.
    0
    1. Utilisateur anonyme
       
      Même plus en faire
      Plus en faire quoi?
      Je t'apporte un solution essai la au moins.
      0
    2. sdfsdfsdfll
       
      Quel solution ?
      0
    3. sdfsdfsdfll
       
      j'avais pas vu ton lien désolé
      0
    4. sdfsdfsdfll
       
      Ce langage est un jargon pour moi et je ne crois pas avoir encore le cd de windows
      0
  12. docsteph Messages postés 8467 Date d'inscription   Statut Membre Dernière intervention   1 192
     
    soit un problème de ram défectueuse, l'alim ou bien un périphérique.

    cdlt
    0
  13. sdfsdfsdfll
     
    Le chinois ou ca, je vois pas la différence
    0
  14. docsteph Messages postés 8467 Date d'inscription   Statut Membre Dernière intervention   1 192
     
    donc cela dépasse tes compétences, amène le a un réparateur. c'est ta seule solution.
    0
  15. sdfsdfsdfll
     
    Si je fais ca je fini à la rue, c'est on ne peu plus simple.
    0
  16. luppi Messages postés 1580 Date d'inscription   Statut Membre Dernière intervention   110
     
    mode sans echec marche pas ?
    ou démarre sur un liveCD genre ubuntu ( linux ) et récupère les données importantes sur une clef USB ou disque Dur externe .
    0