Windows 8 and 8.1 Forums


Random BSOD since I changed CPU.

  1. #1


    Posts : 4
    Windows 8.1

    Random BSOD since I changed CPU.


    All of this started since i changed my CPU for a i7 3770k, had i5 3570.
    The total reinstallation of windows didn't change a thing.
    it seems like it is caused by ntoskrnl.exe
    I just don't know what to do at this point.
    Last edited by kyrom; 26 Apr 2015 at 08:21.

      My System SpecsSystem Spec

  2. #2


    Posts : 356
    Windows 8.1 Enterprise


    Hello,
    I see you complained about waiting too long in Have you been waiting for a response?
    I'm sorry you had to wait that much time. here is what your dumps have to say:

    Dump 1:

    This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

    Code:
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    
    Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: ffffd001adb00180, The PRCB address of the hung processor.
    Arg4: 0000000000000006, 0.
    
    
    Debugging Details:
    ------------------
    
    
    
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    PROCESS_NAME:  SndVol.exe
    
    
    CURRENT_IRQL:  d
    
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    
    STACK_TEXT:  
    ffffd001`b180dc88 fffff800`e0b743e1 : 00000000`00000101 00000000`00000018 00000000`00000000 ffffd001`adb00180 : nt!KeBugCheckEx
    ffffd001`b180dc90 fffff800`e0a549b7 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x12531
    ffffd001`b180dd20 fffff800`e119d67f : 00000000`00000002 ffffd001`b26941c0 ffffe001`3e8003b0 00000000`00000002 : nt!KeClockInterruptNotify+0x787
    ffffd001`b180df40 fffff800`e0ae6eb3 : ffffe001`3e800300 fffff800`e0b01af3 ffffd001`00000000 00000000`00000000 : hal!HalpTimerClockInterrupt+0x4f
    ffffd001`b180df70 fffff800`e0b52e2a : ffffe001`3e800300 ffffd001`b26941c0 00000000`00000000 ffffd001`ad992180 : nt!KiCallInterruptServiceRoutine+0xa3
    ffffd001`b180dfb0 fffff800`e0b5320f : 00000000`00000000 00000000`76853b9d ffffd001`b26941c0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    ffffd001`b2693ec0 fffff800`e0a420b7 : 00000000`00000000 00000000`00000080 00000000`80000005 ffffd001`00000001 : nt!KiInterruptDispatchLBControl+0x11f
    ffffd001`b2694050 fffff800`e0a41242 : 00000000`00000000 00000000`00000001 00000000`000902f8 00000000`00000002 : nt!MiFlushTbList+0x2e7
    ffffd001`b2694190 fffff800`e0a5857a : 00000000`00000002 ffffd001`b2694369 00000000`00000002 00000000`00000002 : nt!MiFlushTbAsNeeded+0xe6
    ffffd001`b26942d0 fffff800`e0a59c2f : 00000000`00000000 ffffd001`b26947b0 00000000`00000001 fffff901`400a3450 : nt!MiAllocatePagedPoolPages+0x17a
    ffffd001`b26943d0 fffff800`e0a58fe0 : 00000000`00000029 00000000`00000021 00000000`00001260 fffff960`000d21fc : nt!MiAllocatePoolPages+0xc3
    ffffd001`b2694420 fffff800`e0ca54d3 : 00000000`00000001 00000000`00000029 ffffe001`00000021 fffff960`003ba53a : nt!ExpAllocateBigPool+0xd0
    ffffd001`b2694510 fffff960`003b88d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0xa83
    ffffd001`b26945e0 fffff960`003b9036 : 00000000`00000000 00000000`00000001 00000000`00000001 fffff800`e0a6ce16 : win32k!NSInstrumentation::CLeakTrackingAllocator::AllocateCommon<<lambda_16c8fa6c1365df5cd1a45d38bb6ccfe2>,<lambda_278f24766fae20cbf0c48ddfc336e8e8> >+0x2f
    ffffd001`b26946b0 fffff960`000be295 : 00000000`00000000 fffff960`00000021 00000000`00000010 00000000`35306847 : win32k!NSInstrumentation::CLeakTrackingAllocator::Allocate+0x46
    ffffd001`b2694700 fffff960`000ba0ac : ffffd001`b26948d8 00000000`05000000 00000000`0000000a fffff800`e0a78722 : win32k!PALLOCMEM2+0x21
    ffffd001`b2694730 fffff960`000c40cb : 00000000`00000000 ffffd001`b26948d8 ffffd001`b2694821 fffff800`e0a6ce16 : win32k!AllocateObject+0xdc
    ffffd001`b2694770 fffff960`000c605b : 00000000`00000006 ffffd001`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x30b
    ffffd001`b2694870 fffff960`000d070f : ffffffff`e0011091 ffffd001`00000000 00000000`00000000 00000000`00000001 : win32k!GreCreateDIBitmapReal+0x2d3
    ffffd001`b26949c0 fffff800`e0b5d1b3 : ffffffff`e0011091 ffffd001`00000020 00000000`00000020 fffff901`00000002 : win32k!NtGdiCreateDIBitmapInternal+0x193
    ffffd001`b2694a90 00007fff`d95c6eba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000001`9c27e2c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`d95c6eba
    
    
    
    
    STACK_COMMAND:  kb
    
    
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: Unknown_Module
    
    
    IMAGE_NAME:  Unknown_Image
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    
    IMAGE_VERSION:  
    
    
    FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    
    
    BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:clock_watchdog_timeout_8_proc_analysis_inconclusive
    
    
    FAILURE_ID_HASH:  {f60c102e-9b2c-017b-9309-e4af1999e360}
    
    
    Followup: MachineOwner
    ---------
    Dump 2:

    Code:
    7: 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: ffffd0019ffc9f60
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    
    
    Debugging Details:
    ------------------
    
    
    
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    
    BUGCHECK_STR:  0x9C_GenuineIntel
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  f
    
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    
    LAST_CONTROL_TRANSFER:  from fffff801ef1d6745 to fffff801eeb5b9a0
    
    
    STACK_TEXT:  
    ffffd001`9ffc9f28 fffff801`ef1d6745 : 00000000`0000009c 00000000`00000000 ffffd001`9ffc9f60 00000000`00000000 : nt!KeBugCheckEx
    ffffd001`9ffc9f30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMcaReportError+0xf5
    
    
    
    
    STACK_COMMAND:  kb
    
    
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: Unknown_Module
    
    
    IMAGE_NAME:  Unknown_Image
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    
    IMAGE_VERSION:  
    
    
    FAILURE_BUCKET_ID:  0x9C_GenuineIntel_ANALYSIS_INCONCLUSIVE
    
    
    BUCKET_ID:  0x9C_GenuineIntel_ANALYSIS_INCONCLUSIVE
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0x9c_genuineintel_analysis_inconclusive
    
    
    FAILURE_ID_HASH:  {93f0a47b-3480-59a5-3cbc-3e11a1e4684d}
    
    
    Followup: MachineOwner
    ---------
    Dump 3:

    Code:
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe0013c07a028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000fe200000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000051166, Low order 32-bits of the MCi_STATUS value.
    
    
    Debugging Details:
    ------------------
    
    
    
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  f
    
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    
    STACK_TEXT:  
    fffff801`4f537a38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: GenuineIntel
    
    
    IMAGE_NAME:  GenuineIntel
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    
    IMAGE_VERSION:  
    
    
    FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
    
    
    BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_cache
    
    
    FAILURE_ID_HASH:  {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}
    
    
    Followup: MachineOwner
    ---------
    Dump 4:

    Code:
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    
    Arguments:
    Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
        the operating system. The only supported way to extend a kernel
        mode stack is by using KeExpandKernelStackAndCallout.
    Arg2: 000000000000000f
    Arg3: ffffd0019893a3c0
    Arg4: 0000000000000000
    
    
    Debugging Details:
    ------------------
    
    
    
    
    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump
    
    
    BUGCHECK_STR:  0xc4_91
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  f
    
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    
    LAST_CONTROL_TRANSFER:  from fffff80259ee8552 to fffff80259f6cca0
    
    
    STACK_TEXT:  
    ffffd001`98936e28 fffff802`59ee8552 : 00000000`000000c4 00000000`00000091 00000000`0000000f ffffd001`9893a3c0 : nt!KeBugCheckEx
    ffffd001`98936e30 fffff802`59ee4f61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpGetStackLimits+0xee
    ffffd001`98936e70 fffff802`59ee945e : ffffd001`98937d68 ffffd001`98937a70 ffffd001`98937d68 00000000`00000009 : nt!RtlDispatchException+0x61
    ffffd001`98937540 fffff802`59f788c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x646
    ffffd001`98937c30 fffff802`59f76dfe : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
    ffffd001`98937e10 fffff802`5a5cc182 : fffff802`5a5bde22 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0xfe
    ffffd001`98937fa8 fffff802`5a5bde22 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpWheaNativeReadMsr+0x2
    ffffd001`98937fb0 fffff802`5a5e799f : ffffe001`e1caf8d0 00000000`00000006 00000000`00000000 00000000`00000000 : hal!HalpMcaReadErrorPresence+0x4e
    ffffd001`98937ff0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0x73
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    nt!RtlpGetStackLimits+ee
    fffff802`59ee8552 cc              int     3
    
    
    SYMBOL_STACK_INDEX:  1
    
    
    SYMBOL_NAME:  nt!RtlpGetStackLimits+ee
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: nt
    
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  550f41a6
    
    
    IMAGE_VERSION:  6.3.9600.17736
    
    
    BUCKET_ID_FUNC_OFFSET:  ee
    
    
    FAILURE_BUCKET_ID:  0xc4_91_nt!RtlpGetStackLimits
    
    
    BUCKET_ID:  0xc4_91_nt!RtlpGetStackLimits
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0xc4_91_nt!rtlpgetstacklimits
    
    
    FAILURE_ID_HASH:  {14b7ae3a-41ea-e821-67a6-b967ab0ba5e5}
    
    
    Followup: MachineOwner
    ---------
    Dump 5:

    Code:
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    
    
    Arguments:
    Arg1: 0000000000000083, MmMapIoSpace called to map, but the caller hasn't locked down the MDL pages.
    Arg2: 00000000000f0000, Starting physical address to map.
    Arg3: 00000000000fffff, Number of bytes to map.
    Arg4: 00000000000001ad, The first page frame number that isn't locked down.
    
    
    Debugging Details:
    ------------------
    
    
    
    
    BUGCHECK_STR:  0xc4_83
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    
    PROCESS_NAME:  MaConfigAgent.
    
    
    CURRENT_IRQL:  0
    
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    
    LAST_CONTROL_TRANSFER:  from fffff800d79116b0 to fffff800d73dcca0
    
    
    STACK_TEXT:  
    ffffd000`238cd698 fffff800`d79116b0 : 00000000`000000c4 00000000`00000083 00000000`000f0000 00000000`000fffff : nt!KeBugCheckEx
    ffffd000`238cd6a0 fffff800`d79069ff : ffffd000`00000001 ffffd000`238cd730 fffff800`00000001 fffff800`d76b177f : nt!VerifierBugCheckIfAppropriate+0x3c
    ffffd000`238cd6e0 fffff800`d7922db7 : 00000000`000f0000 00000000`000fffff ffffe001`60b90060 ffffe001`5b600000 : nt!MmCheckMapIoSpace+0xa3
    ffffd000`238cd720 fffff800`3c811a02 : 00000000`000f0000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VerifierMmMapIoSpace+0x43
    ffffd000`238cd760 00000000`000f0000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffcf81`1a434fb8 : ma_config_amd64+0x1a02
    ffffd000`238cd768 00000000`00000000 : 00000000`00000000 00000000`00000000 ffffcf81`1a434fb8 00000000`00000000 : 0xf0000
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    ma_config_amd64+1a02
    fffff800`3c811a02 ??              ???
    
    
    SYMBOL_STACK_INDEX:  4
    
    
    SYMBOL_NAME:  ma_config_amd64+1a02
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: ma_config_amd64
    
    
    IMAGE_NAME:  ma-config_amd64.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5267dc99
    
    
    FAILURE_BUCKET_ID:  0xc4_83_VRF_ma_config_amd64+1a02
    
    
    BUCKET_ID:  0xc4_83_VRF_ma_config_amd64+1a02
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0xc4_83_vrf_ma_config_amd64+1a02
    
    
    FAILURE_ID_HASH:  {11b36b9a-321c-20c9-cbe6-67f4c533b8ea}
    
    
    Followup: MachineOwner
    ---------
    Dump 6:

    Code:
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    
    Arguments:
    Arg1: 0000000000000083, MmMapIoSpace called to map, but the caller hasn't locked down the MDL pages.
    Arg2: 00000000000f0000, Starting physical address to map.
    Arg3: 00000000000fffff, Number of bytes to map.
    Arg4: 00000000000001ab, The first page frame number that isn't locked down.
    
    
    Debugging Details:
    ------------------
    
    
    
    
    BUGCHECK_STR:  0xc4_83
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    
    PROCESS_NAME:  MaConfigAgent.
    
    
    CURRENT_IRQL:  0
    
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    
    LAST_CONTROL_TRANSFER:  from fffff800cf6fa6b0 to fffff800cf1c5ca0
    
    
    STACK_TEXT:  
    ffffd000`23eec698 fffff800`cf6fa6b0 : 00000000`000000c4 00000000`00000083 00000000`000f0000 00000000`000fffff : nt!KeBugCheckEx
    ffffd000`23eec6a0 fffff800`cf6ef9ff : ffffd000`00000001 ffffd000`23eec730 fffff800`00000001 fffff800`cf49a77f : nt!VerifierBugCheckIfAppropriate+0x3c
    ffffd000`23eec6e0 fffff800`cf70bdb7 : 00000000`000f0000 00000000`000fffff ffffe001`0b2e6150 ffffe001`0b400000 : nt!MmCheckMapIoSpace+0xa3
    ffffd000`23eec720 fffff800`8e9c6a02 : 00000000`000f0000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VerifierMmMapIoSpace+0x43
    ffffd000`23eec760 00000000`000f0000 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffcf81`6c410fb8 : ma_config_amd64+0x1a02
    ffffd000`23eec768 00000000`00000000 : 00000000`00000000 00000000`00000000 ffffcf81`6c410fb8 00000000`00000000 : 0xf0000
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    ma_config_amd64+1a02
    fffff800`8e9c6a02 ??              ???
    
    
    SYMBOL_STACK_INDEX:  4
    
    
    SYMBOL_NAME:  ma_config_amd64+1a02
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: ma_config_amd64
    
    
    IMAGE_NAME:  ma-config_amd64.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5267dc99
    
    
    FAILURE_BUCKET_ID:  0xc4_83_VRF_ma_config_amd64+1a02
    
    
    BUCKET_ID:  0xc4_83_VRF_ma_config_amd64+1a02
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0xc4_83_vrf_ma_config_amd64+1a02
    
    
    FAILURE_ID_HASH:  {11b36b9a-321c-20c9-cbe6-67f4c533b8ea}
    
    
    Followup: MachineOwner
    ---------
    Dump 1, 2 and 3
    are about "fatal Machine Check", "fatal hardware error" and "processor hang", these are all refering to Intel processor.


    Dump 4, 5 and 6
    are telling us that Driver verifier detected violation.
    In either case faulty driver mentioned is "ma-config_amd64.sys" which is a driver/hardware detection tool from
    Easily explore your PC, so I assume you were trying to fix your PC with this tool.

    I'm unable to read your event log and other files to check details because they are all in French
    Anyway I would recommend you to remove that tool from your PC and instead use driver verifier:
    Where can I download Driver Verifier?

    Dump 4 is telling us that "A driver switched stacks using a method that is not supported by the operating system"

    Obviously it is something about processor and possibly even driver, also please note that some MSI mother board models have an update for Intel i7 processor, mostly these updates are from year 2015, but your BIOS version is from 2013 thus possibly missing critical update.


    Unfortunately I was not able to find your exact mother board version, because I stuck at socket 1155 and then it asked for other information which I do not know.

    What I would recommend is to ensure you have latest drivers for your hardware, updating BIOS should be taken with care, and if you're unable to figure out how to find proper BIOS update on MSI Support then it's better not to do anything because doing it wrong could bring even more trouble.
    Having proper chip set driver installed can also make a big difference.

    There is an Intel® Processor Diagnostic Tool (64-bit) which you can use to perform a test and hopefully tell you what could be wrong with your processor.

    If you have any additional questions feel free to ask
      My System SpecsSystem Spec

  3. #3


    Posts : 4
    Windows 8.1


    First of all, thanks for answering me !
    I've deleted the ma-config driver . but the computer crashed again.
    I've done everything that you mention and my proc is fine !
    I think you spotted the problem here, you said that all msi mobo had bios update in 2015, and mine is 2013.
    But the thing is, the last update on the msi website is 2013.
    So i don't know...
    My MOBO : MSI Z77A-G43 GAMING
    (sorry for my froggy english)
      My System SpecsSystem Spec

  4. #4


    Posts : 356
    Windows 8.1 Enterprise


    Hi, thank you for reply.
    You said you PC crashed again so I assume you have more dump files which could potentially provide additional info.
    Also can you please give a link for MSI mother board update because here is what I get ( accepted offer by website after input ):

    Attachment 60984


    Attachment 60982
      My System SpecsSystem Spec

  5. #5


    Posts : 4
    Windows 8.1


    I've done everything you told me to do before i poste here , that's what I meant
    My PC crashed again after removing ma-config. But it was just a big freeze not a blue screen.
    Link : MSI Global - The best gaming gears maker in the world
      My System SpecsSystem Spec

  6. #6


    Posts : 356
    Windows 8.1 Enterprise


    Quote Originally Posted by kyrom View Post
    I've done everything you told me to do before i poste here , that's what I meant
    My PC crashed again after removing ma-config. But it was just a big freeze not a blue screen.
    Link : MSI Global - The best gaming gears maker in the world
    Hello,

    You said you completely removed ma-config tool therefore we can ignore dumps 3,4 and 6.
    I also have to believe you that you downloaded original drivers for all your devices as you told already so we can skip that part then, for now

    Remaining dumps are usually considered serious hardware errors, and in this case it could be either processor or mother board, hence the 0x101 and WHEA_UNCORRECTABLE_ERROR.
    It's wort'h performing another stress tests like prime95 which hopefully will reproduce BSOD and this could potentially tell us something more.

    Download here:
    GIMPS - Free Prime95 software downloads - PrimeNet

    Close all programs you might have open, unpack the zip file and run the executable.
    here is how will you run the test:

    Attachment 60994

    On next screen set "torture" setup like in following image and hit "OK"

    Attachment 60995

    After test is done post results.
      My System SpecsSystem Spec

  7. #7


    Posts : 356
    Windows 8.1 Enterprise


    I would also recommend to disable Level 2 cache of your processor in your BIOS, and then try to reproduce BSOD by performing stress test on processor, because this is most likely the cause.

    Code:
    0: kd> !errrec ffffe0013c07a028
    ===============================================================================
    Common Platform Error Record @ ffffe0013c07a028
    -------------------------------------------------------------------------------
    Record Id     : 01d0789acb7584cc
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 4/17/2015 16:05:32 (UTC)
    Flags         : 0x00000000
    
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe0013c07a0a8
    Section       @ ffffe0013c07a180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Cache error
    Operation     : Generic
    Flags         : 0x00
    Level         : 2
    CPU Version   : 0x00000000000306a9
    Processor ID  : 0x0000000000000000
    
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe0013c07a0f0
    Section       @ ffffe0013c07a240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : a9 06 03 00 00 08 10 00 - bf e3 9a 7f ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    
    Proc. Info 0  @ ffffe0013c07a240
    
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe0013c07a138
    Section       @ ffffe0013c07a2c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    
    Error         : DCACHEL2_PREFETCH_ERR (Proc 0 Bank 5)
      Status      : 0xfe20000000051166
      Address     : 0x00000000001e0200
      Misc.       : 0x000000324303c086
    
    
    0: kd> !cpuinfo
    CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features
     0  6,58,9 GenuineIntel 3500 0000001b00000000                   3d193fff
                          Cached Update Signature 0000001b00000000
                         Initial Update Signature 0000001b00000000
    Last edited by Addictive Gamer; 30 Apr 2015 at 00:53.
      My System SpecsSystem Spec

Random BSOD since I changed CPU.
Related Threads
Random BSOD Errors / Restart after BSOD in BSOD Crashes and Debugging
Hallo, every couple of days I get a BSOD. Mainly while leaving the pc unused at night. For detailed informations see minidump-files below. Furthermore the PC doesn't autmoatically restart (even it is activated in system properties / advanced / startup and recovery). This is insofar very...
Random BSOD at random times in BSOD Crashes and Debugging
Hello, Im new here so bare with me :think: I built my custom pc a year ago now. Since day one iv been experiencing BSOD. At first it happened during or just after the first boot up of that day and was always Memory Management error. Soon after, i upgraded my ram from 4gb to 8 gb. After doing this...
I have been getting a ton of bsods I have re installed video drivers, updated and reinstalled windows 8. Did countless hardware test(Video ram, check memory, Cpu test) all passed temperatures stay around 25-35 c. Recently uninstalled all video drivers and re installed. The bsods sometimes go away...
BSOD When playing games random Bsod messages in BSOD Crashes and Debugging
Hey I have a problem with my pc I got a few weeks ago It keeps getting the bsod and turning on and off randomly at times I use it mostly to play games and watch youtube , twitch ext. also internet can sometimes crash pointing this out Bsod can happen when playing a game and when on the web...
BSOD at Random Times for Random Reasons in BSOD Crashes and Debugging
DCP Watchdog, Memory Management, Kernel Security Failure and several others at random times - especially during large file transfers between drives. I did a memory test and it stated there was an issue but I removed the culprit and the random BSOD continues. Thanks for your help
Hey guys, so I am in a bit of a pickle. I have an HP m6-k015dx laptop and it is giving me hell. I will get random BSOD's, usually at or a short while after login. They usually happen consecutively and then stop. I was able to enable driver verifier in order to see what was wrong. After it was...
Hi, i'm new to this forum and i hope you guy can help me :) So my laptop is relatively new, it's not even a month old. I guess i've been downloading a lot of stuff that caused this error. Now, i'm not a computer expert or any type of expert, so please bear with me :D Before i go on, here are...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook