Aller au contenu
Site Communauté

Devii974

Membres
 Afficher le profil  Afficher son activité

  • Nbre de contenus

    18

  • Inscription

  • Dernière visite

 Type de contenu 

Messages posté(e)s par Devii974

    Bsod MACHINE_CHECK_EXCEPTION

    dans Windows

    Posté(e)

    - System
       
    - Provider
          [ Name] Windows Error Reporting
       
    - EventID 1001
          [ Qualifiers] 0
       
      Level 4
       
      Task 0
       
      Keywords 0x80000000000000
       
    - TimeCreated
          [ SystemTime] 2018-07-05T16:50:13.271340300Z
       
      EventRecordID 21752
       
      Channel Application
       
      Computer pcelina
       
      Security
    - EventData
          0x9C_GenuineIntel
          0
          BlueScreen
          Non disponible
          0737d9bc-ac18-43b1-87a3-855ea1b89d83
          9c
          0
          ffffce006a14bc80
          0
          0
          10_0_17134
          0_0
          768_1
           
           
          \\?\C:\WINDOWS\Minidump\070518-23343-01.dmp \\?\C:\WINDOWS\TEMP\WER-206671-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER65EF.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER65F0.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER660E.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER661F.tmp.txt
          C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9c_63587bc1dddbe8aa7b676680511ddbb732f561d_00000000_cab_05d7a067
           
          0
          9ebbfbb2-4e43-47b3-94c5-2ae78a096dc6
          268435456
           
          0

    Bsod MACHINE_CHECK_EXCEPTION

    dans Windows

    Posté(e)

    Bonjour, voilà après plusieurs jour sans bsod je me retrouve en machine check exception.

    Je joue au mmo et lorsque les bsod arrive bizarrement mon jeu est en marche.

    J'ai remarqué que il me déco souvent du server ou je suis. 

    - System
       
    - Provider
          [ Name] Windows Error Reporting
       
    - EventID 1001
          [ Qualifiers] 0
       
      Level 4
       
      Task 0
       
      Keywords 0x80000000000000
       
    - TimeCreated
          [ SystemTime] 2018-07-05T16:50:13.271340300Z
       
      EventRecordID 21752
       
      Channel Application
       
      Computer pcelina
       
      Security
    - EventData
          0x9C_GenuineIntel
          0
          BlueScreen
          Non disponible
          0737d9bc-ac18-43b1-87a3-855ea1b89d83
          9c
          0
          ffffce006a14bc80
          0
          0
          10_0_17134
          0_0
          768_1
           
           
          \\?\C:\WINDOWS\Minidump\070518-23343-01.dmp \\?\C:\WINDOWS\TEMP\WER-206671-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER65EF.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER65F0.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER660E.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER661F.tmp.txt
          C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9c_63587bc1dddbe8aa7b676680511ddbb732f561d_00000000_cab_05d7a067
           
          0
          9ebbfbb2-4e43-47b3-94c5-2ae78a096dc6
          268435456
           
          0

    Bsod MACHINE_CHECK_EXCEPTION

    dans Windows

    Posté(e)

    C'est un Windows 8.1 évoluer en 10, le 8.1 je l'ai acheter et le 10 quand Windows a fait son évolution gratuite.

    Ok je vais essayer de réparer pour voir ce qu'il se passe. 

    Je sais pas si sa avoir quelque chose mais j'ai des pages bleus depuis que j'ai installer un jeu sa n'a peut être rien avoir mais bon une piste reste une piste.

    En tout cas merci d'avoir répondu aussi vite.

     

     

    • J'aime 1

    Bsod MACHINE_CHECK_EXCEPTION

    dans Windows

    Posté(e) · Modifié par Le PoissonClown
    Aide : mise en forme plus lisible.

    Bonjour, j'ai un soucis avec des Bsod  MACHINE_CHECK_EXCEPTION

    J'ai comme config:

    • Carte mère asus maximus VIII hero
    • Processeur intel I5 6600K
    • Carte graphique 1050TI Gigabite G1 Gamin 4gb
    • Alim corsair TX550M
    • Barette ram Ballistix ddr4 4x4gb 3000udimm
    • Et une carte son Asus xonar dgx

    Whocrashed me dit:

    Révélation

    Windows version: Windows 10 , 10.0, build: 17134
    Windows dir: C:\WINDOWS
    Hardware: ASUSTeK COMPUTER INC., MAXIMUS VIII RANGER
    CPU: GenuineIntel Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz Intel586, level: 6
    4 logical processors, active mask: 15
    RAM: 17091174400 bytes total


     

    Crash Dump Analysis


    Crash dumps are enabled on your computer.

    Crash dump directories:
    C:\WINDOWS
    C:\WINDOWS\Minidump

    On Sun 24/06/2018 17:48:04 your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\062418-22609-01.dmp
    This was probably caused by the following module: hal.dll (hal+0x40D05)
    Bugcheck code: 0x9C (0x0, 0xFFFFE6002394BC80, 0x0, 0x0)
    Error: MACHINE_CHECK_EXCEPTION
    file path: C:\WINDOWS\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hardware Abstraction Layer DLL
    Bug check description: This bug check indicates that a fatal machine check exception has occurred.
    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 24/06/2018 17:48:04 your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\MEMORY.DMP
    This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0x18B5)
    Bugcheck code: 0x9C (0x0, 0xFFFFE6002394BC80, 0x0, 0x0)
    Error: MACHINE_CHECK_EXCEPTION
    file path: C:\WINDOWS\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hardware Abstraction Layer DLL
    Bug check description: This bug check indicates that a fatal machine check exception has occurred.
    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 24/06/2018 16:57:37 your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\062418-25640-01.dmp
    This was probably caused by the following module: hal.dll (hal+0x40D05)
    Bugcheck code: 0x9C (0x0, 0xFFFFF8002EDEBB80, 0x0, 0x0)
    Error: MACHINE_CHECK_EXCEPTION
    file path: C:\WINDOWS\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hardware Abstraction Layer DLL
    Bug check description: This bug check indicates that a fatal machine check exception has occurred.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



     

    Conclusion


    3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


    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.

    Ainsi que Windbg:

    Révélation

    Microsoft (R) Windows Debugger Version 10.0.15063.468 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

    Symbol search path is: srv*
    Executable search path is: 
    Windows 10 Kernel Version 17134 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 17134.1.amd64fre.rs4_release.180410-1804
    Machine Name:
    Kernel base = 0xfffff800`484a2000 PsLoadedModuleList = 0xfffff800`4885c1f0
    Debug session time: Sun Jun 24 17:48:04.937 2018 (UTC + 2:00)
    System Uptime: 0 days 0:36:25.624
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................................
    Loading User Symbols

    Loading unloaded module list
    ...........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9C, {0, ffffe6002394bc80, 0, 0}

    Probably caused by : intelppm.sys ( intelppm!MWaitIdle+23 )

    Followup:     MachineOwner
    ---------

    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    MACHINE_CHECK_EXCEPTION (9c)
    A fatal Machine Check Exception has occurred.
    KeBugCheckEx parameters;
        x86 Processors
            If the processor has ONLY MCE feature available (For example Intel
            Pentium), the parameters are:
            1 - Low  32 bits of P5_MC_TYPE MSR
            2 - Address of MCA_EXCEPTION structure
            3 - High 32 bits of P5_MC_ADDR MSR
            4 - Low  32 bits of P5_MC_ADDR MSR
            If the processor also has MCA feature available (For example Intel
            Pentium Pro), the parameters are:
            1 - Bank number
            2 - Address of MCA_EXCEPTION structure
            3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
            4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
        IA64 Processors
            1 - Bugcheck Type
                1 - MCA_ASSERT
                2 - MCA_GET_STATEINFO
                    SAL returned an error for SAL_GET_STATEINFO while processing MCA.
                3 - MCA_CLEAR_STATEINFO
                    SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
                4 - MCA_FATAL
                    FW reported a fatal MCA.
                5 - MCA_NONFATAL
                    SAL reported a recoverable MCA and we don't support currently
                    support recovery or SAL generated an MCA and then couldn't
                    produce an error record.
                0xB - INIT_ASSERT
                0xC - INIT_GET_STATEINFO
                      SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
                0xD - INIT_CLEAR_STATEINFO
                      SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
                0xE - INIT_FATAL
                      Not used.
            2 - Address of log
            3 - Size of log
            4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
        AMD64 Processors
            1 - Bank number
            2 - Address of MCA_EXCEPTION structure
            3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
            4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    Arguments:
    Arg1: 0000000000000000
    Arg2: ffffe6002394bc80
    Arg3: 0000000000000000
    Arg4: 0000000000000000

    Debugging Details:
    ------------------


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 401

    BUILD_VERSION_STRING:  17134.1.amd64fre.rs4_release.180410-1804

    SYSTEM_MANUFACTURER:  System manufacturer

    SYSTEM_PRODUCT_NAME:  System Product Name

    SYSTEM_SKU:  SKU

    SYSTEM_VERSION:  System Version

    BIOS_VENDOR:  American Megatrends Inc.

    BIOS_VERSION:  1902

    BIOS_DATE:  06/24/2016

    BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

    BASEBOARD_PRODUCT:  MAXIMUS VIII RANGER

    BASEBOARD_VERSION:  Rev 1.xx

    DUMP_TYPE:  1

    BUGCHECK_P1: 0

    BUGCHECK_P2: ffffe6002394bc80

    BUGCHECK_P3: 0

    BUGCHECK_P4: 0

    BUGCHECK_STR:  0x9C_GenuineIntel

    CPU_COUNT: 4

    CPU_MHZ: db0

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 5e

    CPU_STEPPING: 3

    CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: BE'00000000 (cache) BE'00000000 (init)

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  f

    ANALYSIS_SESSION_HOST:  PCELINA

    ANALYSIS_SESSION_TIME:  06-24-2018 18:14:37.0222

    ANALYSIS_VERSION: 10.0.15063.468 amd64fre

    BAD_STACK_POINTER:  ffffe6002394bc48

    LAST_CONTROL_TRANSFER:  from fffff80048456d05 to fffff8004863a330

    STACK_TEXT:  
    ffffe600`2394bc48 fffff800`48456d05 : 00000000`0000009c 00000000`00000000 ffffe600`2394bc80 00000000`00000000 : nt!KeBugCheckEx
    ffffe600`2394bc50 fffff800`4845714f : 00000000`00000004 ffffe600`2394bf50 00000000`00000000 00000000`00000004 : hal!HalpMcaReportError+0xf5
    ffffe600`2394bda0 fffff800`48457390 : ffff8382`060e28b0 ffffe600`2394bfd0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x12b
    ffffe600`2394bdd0 fffff800`4864883b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    ffffe600`2394be00 fffff800`486484ff : 00000000`00000000 fffff800`4864847e 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
    ffffe600`2394bf40 fffff803`b2bc13f3 : fffff803`b2bc13b4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x1bf
    ffffba81`8c64f5e8 fffff803`b2bc13b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`0000003a : intelppm!MWaitIdle+0x23
    ffffba81`8c64f5f0 fffff800`48540fbf : 00000000`00000000 00000000`0000007d ffffe600`23945ec8 00000001`bdcf67d2 : intelppm!AcpiCStateIdleExecute+0x24
    ffffba81`8c64f620 fffff800`4853ff35 : 00000000`00000003 00000000`00000002 00000000`00000000 00000000`00000008 : nt!PpmIdleExecuteTransition+0xeff
    ffffba81`8c64fa00 fffff800`4863da5c : 00000000`00000000 ffffe600`23940180 ffffe600`23950100 ffff8382`0eaf2700 : nt!PoIdle+0x345
    ffffba81`8c64fb60 00000000`00000000 : ffffba81`8c650000 ffffba81`8c649000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


    STACK_COMMAND:  kb

    THREAD_SHA1_HASH_MOD_FUNC:  73c987e2e48d368e307edaa2f88b043119b02c66

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  fd7dc44eef7b5e04b2707f0ed15e7e97ee1448ad

    THREAD_SHA1_HASH_MOD:  b803b7c11c52d0ad6df719f6be71385e898408f8

    FOLLOWUP_IP: 
    intelppm!MWaitIdle+23
    fffff803`b2bc13f3 4585c9          test    r9d,r9d

    FAULT_INSTR_CODE:  75c98545

    SYMBOL_STACK_INDEX:  6

    SYMBOL_NAME:  intelppm!MWaitIdle+23

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: intelppm

    IMAGE_NAME:  intelppm.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    BUCKET_ID_FUNC_OFFSET:  23

    FAILURE_BUCKET_ID:  0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle

    BUCKET_ID:  0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle

    PRIMARY_PROBLEM_CLASS:  0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle

    TARGET_TIME:  2018-06-24T15:48:04.000Z

    OSBUILD:  17134

    OSSERVICEPACK:  0

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK:  784

    PRODUCT_TYPE:  1

    OSPLATFORM_TYPE:  x64

    OSNAME:  Windows 10

    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

    OS_LOCALE:  

    USER_LCID:  0

    OSBUILD_TIMESTAMP:  2018-06-08 11:00:00

    BUILDDATESTAMP_STR:  180410-1804

    BUILDLAB_STR:  rs4_release

    BUILDOSVER_STR:  10.0.17134.1.amd64fre.rs4_release.180410-1804

    ANALYSIS_SESSION_ELAPSED_TIME:  3b1

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:0x9c_genuineintel_stackptr_error_intelppm!mwaitidle

    FAILURE_ID_HASH:  {d82f1232-e6fd-ac41-d01e-ddeec73b684b}

    Followup:     MachineOwner

     

    Je suis sous Windows 10 et il faut que je mette a jour Windows 8 je suis un peu perdu.

    Si quelqu'un peut m'aider merci d'avance.

×
×
  • Créer...