none
reboot serveur suite ecran bleu RRS feed

  • Question

  • Bonjour,

    j'ai un serveur 2016 qui reboot la nuit avec des message dans les journaux d'evenement:

    Journal : Systeme

    Source : BugCheck

    Evenement: 1001

    Niveau : Erreur

    l'ordinateur a redémarré après une vérification d'erreur. La vérification d'erreur était : 0x00000000a

    (0x00000000000002, 0x0000000000000000,0xfffff80382d10c73). un vidage à été enregistré dans c:\Windows\MEMORY.DMP ID de rapport : cc034d18-751d-4577-b21b-7ff256a6ab02

    cela reboot seulement la nuit, je soupçonne que cela vienne d'un logiciel de sauvegarde AOMEI Backupper server pourtant je recois bien les mail du logiciel qui me dise que les sauvegarde on été réalise avec succès

    merci pour votre aide

    cordialement

    vendredi 10 avril 2020 13:37

Réponses

Toutes les réponses

  • Bonjour Cedric,

    J'utilise whoCrashed pour trouver les coupables qui font planter les systèmes.

    https://www.malekal.com/tutoriel-whocrashed/


    "Marquer comme réponse" les réponses qui ont résolu votre problème



    vendredi 10 avril 2020 13:55
  • salut,

    soit tu nous poses ton fichier .DMP soit tu regardes les options de AOMEI, ça me le faisait une fois, j'avais coché vérifier l’intégralité et redémarrer peut être.

    vendredi 10 avril 2020 14:10
  • Bonjour,

    merci de votre aide à tous

    j'ai utilisé whoCrashed

    n Fri 10/04/2020 00:00:28 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\041020-30000-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x15D590)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801F6B066DF, 0xFFFF82810F6A1740, 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 10/04/2020 00:00:28 your computer crashed or a problem was reported
    crash dump file: C:\Windows\MEMORY.DMP
    This was probably caused by the following module: amwrtdrv.sys (amwrtdrv+0x1845)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801F6B066DF, 0xFFFF82810F6A1740, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\amwrtdrv.sys
    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.
    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: amwrtdrv.sys .
    Google query: amwrtdrv.sys SYSTEM_SERVICE_EXCEPTION



    On Wed 08/04/2020 00:00:28 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\040820-26625-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x15D590)
    Bugcheck code: 0xA (0x138, 0x2, 0x0, 0xFFFFF802FD112C73)
    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 is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    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 07/04/2020 01:00:53 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\040720-25671-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x15D590)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80069AF26DF, 0xFFFF85803CC91740, 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 05/04/2020 03:47:31 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\040520-26843-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x15D590)
    Bugcheck code: 0x18 (0x0, 0xFFFFE70CA4C76050, 0x2, 0xFFFFFFFFFFFFFFFF)
    Error: REFERENCE_BY_POINTER
    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 reference count of an object is illegal for the current state of the object.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    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 04/04/2020 00:00:28 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\040420-26062-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x15D590)
    Bugcheck code: 0xA (0x138, 0x2, 0x0, 0xFFFFF80012B0FC73)
    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 is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    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 03/04/2020 00:00:29 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\040320-27000-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x15D590)
    Bugcheck code: 0xA (0x138, 0x2, 0x0, 0xFFFFF801F1919C73)
    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 is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 02/04/2020 01:00:37 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\040220-29250-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x15D590)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803A7F096EB, 0xFFFFE501DFB8B8F0, 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 31/03/2020 01:00:35 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\033120-27937-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x15D590)
    Bugcheck code: 0xA (0x138, 0x2, 0x0, 0xFFFFF8022D595C73)
    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 is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 26/03/2020 00:00:28 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\032620-26593-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x15D590)
    Bugcheck code: 0xA (0x138, 0x2, 0x0, 0xFFFFF8004EB87C73)
    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 is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    vendredi 10 avril 2020 15:10
  • Bonjour,

    Vous pouvez utilisez la procédure suivante :

    -Test hardware avec tools constructeurs

    + Maj bios

    + Maj pilotes

    + Dism

    + Sfc

    + Chkdsk


    "Marquer comme réponse" les réponses qui ont résolu votre problème




    vendredi 10 avril 2020 17:06
  • Oui, ca ressemble à un problème matériel, test la ram avec memtest, et si c'est une vm regardes s'il y a assez de ressources (espace disque, processeur et ram).

    Parfois l'outil pètes avec la mémoire dynamique.

    vendredi 10 avril 2020 17:16