Bluescreen

Lu-k -  
 Lu-k -
Bonjour,

Par deux fois un écran bleu m'est apparu. Je vous copie le rapport de Windows :

Signature du problème :
Nom d'événement de problème: BlueScreen
Version du système: 6.1.7601.2.1.0.768.3
Identificateur de paramètres régionaux: 1036

Informations supplémentaires sur le problème :
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF8000300D26C
BCP3: FFFFF8800AC9AA90
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Fichiers aidant à décrire le problème :
C:\Windows\Minidump\102412-27643-01.dmp
C:\Users\Lucas\AppData\Local\Temp\WER-64756-0.sysdata.xml

Je n'y connais vraiment rien en informatique ! Merci beaucoup de votre aide.

3 réponses

  1. Lu-k
     
    Merci beaucoup hisaeh de votre réponse et excusez la lenteur de la mienne.
    J'ai utilisé Whocrashed comme vous me l'avez conseillé. Voici le rapport d'analyse :

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sun 28/10/2012 12:48:39 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\102812-38111-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FB426C, 0xFFFFF8800A24BA90, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    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 28/10/2012 12:48:39 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: 0x3B (0xC0000005, 0xFFFFF80002FB426C, 0xFFFFF8800A24BA90, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    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 24/10/2012 06:52:20 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\102412-27643-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000300D26C, 0xFFFFF8800AC9AA90, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    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 19/10/2012 20:05:17 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\101912-28984-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FB726C, 0xFFFFF8800A2F7A90, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    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 10/04/2012 07:36:58 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\041012-28142-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD10)
    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 that cannot be identified at this time.

    On Fri 24/02/2012 10:14:23 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\022412-30420-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 that cannot be identified at this time.

    Que dois-je faire ?
    Merci d'avance de vos réponses.
    0
  2. Lu-k
     
    J'ajoute qu'après un sfc/verifyonly le programme de protection des ressources Windows n'a trouvé aucune violation d'intégrité.
    0