Windows freezes after migration

  1. Posts : 31
    windows 10 pro 64 bit

    Windows freezes after migration

    Until now, I wasn't generally getting BSODs, just freezes, but I got one today.

    The story is that I did a bare metal restore of an OS from a Ryzen 5900x to a broadwell 5775c.
    The version is 10.020348 build 20348.
    I installed all the drivers from the MOBO mfg. It's an ASUS Rack z97-a.
    I installed new video drivers.
    I installed Intel chipset drivers.

    It works! But it's been freezing 1 to 2x a day. Usually it does not give a BSOD, but this time it did.

    It said STOPCODE MACHINE_CHECK_EXCEPTION. Guess I'll go look that up.

    And this error was in the log:
    Faulting application name: Explorer.EXE, version: 10.0.20348.1487, time stamp: 0x1c1c7563
    Faulting module name:, version: 10.0.20348.1311, time stamp: 0xa501f5f9
    Exception code: 0xc0000005
    Fault offset: 0x00000000001803be
    Faulting process id: 0xaec
    Faulting application start time: 0x01d9665498b8daa7
    Faulting application path: C:\Windows\Explorer.EXE
    Faulting module path: C:\Windows\SYSTEM32\
    Report Id: 4fd394d4-1482-4592-8851-42f5af23604e
    Faulting package full name:
    Faulting package-relative application ID:

    Most times it freezes, I find this in the log:
    FIX: Application Specific Permission Settings do not Grant Local Activation permission for COM Server Application (Solved) - - Windows Tips & How-tos


    EDIT: I tried uploading the zip created by your logger, but it fails. Any idea why that might happen. It just says 'upload failed'.

    Okay, looks like it is 2.08 MB, which is over the 2 MB limit. I will delete an old crash dump file from the zip and try again. Also, I note that there seems to be no way to close the manage attachment window without selecting a file.

      My Computer

  2. Posts : 402
    Windows 10 and Windows 11

    Was this just a CPU change on an existing system or are you saying that you restored a Windows system from one PC to a different PC?

    If the latter then I'm not surprised you're having issues. You cannot use a Windows system from one PC on a different PC. At install time Windows configures itself for the hardware platform it's on, this of course will be all wrong if you migrate it to a different PC. In addition, all the drivers for the old PC will still be present, even if you install new drivers for the new hardware, and these can (and do) cause all sorts of errors and BSODs.
      My Computer

  3. Posts : 31
    windows 10 pro 64 bit
    Thread Starter

    Well, I've built all my own PCs for many years, and I've migrated OSs between different machines sucessfully many times before, using VEEAM, which has a lot of driver checks built into the process. So it's certainly possible.

    But I will admit, this was an extreme case, moving from AMD to Intel. I've never done that before, it's always been Intel to Intel.

    That said, I keep digging up info on issues, and making changes, and the number of freezes is way way down, so that's made it hard to just give up
      My Computer

  4. Posts : 402
    Windows 10 and Windows 11

    I would never ever advise anyone to attempt to migrate a Windows system from one PC to another, it just makes no sense. Just because you can do something, doesn't mean you should - which is why I don't jump off 10-story buildings - even though I can.
      My Computer

  5. Posts : 31
    windows 10 pro 64 bit
    Thread Starter

    Thanks for the advice.
      My Computer

  6. Posts : 890
    10 Pro/11 Pro Dual Boot

    woodslanding said:
    Thanks for the advice.
    its more than just advice, its the correct answer. Backing up a system to restore to another is only supported (by microsoft) when hardware is identical.

    all of your dumps are the same, a machine check exception calling out your intel processor.

    if you wish to continue troubleshooting, do a clean install to see if the issue persists.

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

    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
    SAL returned an error for SAL_GET_STATEINFO while processing MCA.
    SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
    4 - MCA_FATAL
    FW reported a fatal MCA.
    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.
    SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
    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 (If Param 1 is < 0x80000000)
    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
    AMD64 Processors (If Param 1 is > 0x80000000)
    1 - Failure Type
    0x80000001: Spurious MCE
    2 - Address of MCA_EXCEPTION structure
    0x80000002: Rendezvous failure
    2 - Address of MCA_EXCEPTION structure
    Arg1: 0000000080000002
    Arg2: ffffe500f6718b10
    Arg3: 0000000000000000
    Arg4: 0000000000000000

    Debugging Details:


    Key : Analysis.CPU.mSec
    Value: 1702

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 36987

    Key : Analysis.Init.CPU.mSec
    Value: 156

    Key : Analysis.Init.Elapsed.mSec
    Value: 115016

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 79

    Key : WER.OS.Branch
    Value: fe_release

    Key : WER.OS.Timestamp
    Value: 2021-05-07T15:00:00Z

    Key : WER.OS.Version
    Value: 10.0.20348.1


    BUGCHECK_P1: 80000002

    BUGCHECK_P2: ffffe500f6718b10

    BUGCHECK_P3: 0

    BUGCHECK_P4: 0

    BLACKBOXNTFS: 1 (!blackboxntfs)

    BLACKBOXPNP: 1 (!blackboxpnp)



    PROCESS_NAME: System

    BAD_STACK_POINTER: ffffe500f6718ad8

    ffffe500`f6718ad8 fffff804`4b0f89a9 : 00000000`0000009c 00000000`80000002 ffffe500`f6718b10 00000000`00000000 : nt!KeBugCheckEx
    ffffe500`f6718ae0 fffff804`4b0f8e6b : 00000000`00000008 ffffe500`f6718e50 00000000`00000000 00000000`00000008 : nt!HalpMcaReportError+0x149
    ffffe500`f6718c40 fffff804`4b0f80d6 : 00000000`00000000 00000000`80000002 ffffe500`f6718ed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xab
    ffffe500`f6718c70 fffff804`4b0fa9fb : ffffd503`06ceb510 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x62
    ffffe500`f6718ca0 fffff804`4b1566b9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x3b
    ffffe500`f6718cd0 fffff804`4b025abe : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
    ffffe500`f6718d00 fffff804`4b0256e8 : 00000000`00000010 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7e
    ffffe500`f6718e40 fffff804`5a3d30a2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2a8
    ffffc00e`0805f538 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!C1Halt+0x2

    SYMBOL_NAME: intelppm!C1Halt+2

    MODULE_NAME: intelppm

    IMAGE_NAME: intelppm.sys

    IMAGE_VERSION: 10.0.20348.1450

    STACK_COMMAND: .thread ; .cxr ; kb



    OS_VERSION: 10.0.20348.1

    BUILDLAB_STR: fe_release


    OSNAME: Windows 10

    FAILURE_ID_HASH: {9595eaaf-5ed9-9646-4b21-9cdedcc50e68}

    Followup: MachineOwner
      My Computers


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 11:10.
Find Us

Windows 10 Forums