none
Intel to AMD Processor BugCheck RRS feed

  • Question

  • Hi, i recently change my homelab environment from Intel to AMD processor, and i has been getting BugCheck. i would like to look for opinion before going ahead to format the environment.

    Microsoft (R) Windows Debugger Version 10.0.18869.1002 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [\\192.168.2.4\c$\Windows\MEMORY.DMP]
    Kernel Bitmap Dump File: Full address space is available
    
    Symbol search path is: srv*
    Executable search path is: 
    Windows 10 Kernel Version 17763 MP (12 procs) Free x64
    Product: Server, suite: TerminalServer DataCenter SingleUserTS
    Built by: 17763.1.amd64fre.rs5_release.180914-1434
    Machine Name:
    Kernel base = 0xfffff805`1140b000 PsLoadedModuleList = 0xfffff805`118265d0
    Debug session time: Thu May 30 03:17:44.121 2019 (UTC + 8:00)
    System Uptime: 0 days 1:52:08.855
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................................................
    Loading User Symbols
    
    Loading unloaded module list
    ......
    For analysis of this file, run !analyze -v
    nt!KeBugCheckEx:
    fffff805`115beef0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff805`136f6c70=00000000000001ca
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYNTHETIC_WATCHDOG_TIMEOUT (1ca)
    A system wide watchdog has expired. This indicates that the system
    is hung and not processing timer ticks.
    Arguments:
    Arg1: 000000001f2900e8, The time since the watchdog was last reset, in interrupt time.
    Arg2: 0000000fe4f55593, The current interrupt time.
    Arg3: 0000000fe4f863c1, The current QPC timestamp.
    Arg4: 0000000000000008, The index of the clock processor.
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
        Key  : Analysis.CPU.Sec
        Value: 2
    
        Key  : Analysis.Elapsed.Sec
        Value: 15
    
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 63
    
    
    PROCESSES_ANALYSIS: 1
    
    SERVICE_ANALYSIS: 1
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 402
    
    BUILD_VERSION_STRING:  17763.1.amd64fre.rs5_release.180914-1434
    
    SYSTEM_MANUFACTURER:  System manufacturer
    
    SYSTEM_PRODUCT_NAME:  System Product Name
    
    SYSTEM_SKU:  SKU
    
    SYSTEM_VERSION:  System Version
    
    BIOS_VENDOR:  American Megatrends Inc.
    
    BIOS_VERSION:  1002
    
    BIOS_DATE:  03/07/2019
    
    BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.
    
    BASEBOARD_PRODUCT:  TUF B450M-PLUS GAMING
    
    BASEBOARD_VERSION:  Rev X.0x
    
    DUMP_TYPE:  0
    
    BUGCHECK_P1: 1f2900e8
    
    BUGCHECK_P2: fe4f55593
    
    BUGCHECK_P3: fe4f863c1
    
    BUGCHECK_P4: 8
    
    CPU_COUNT: c
    
    CPU_MHZ: d42
    
    CPU_VENDOR:  AuthenticAMD
    
    CPU_FAMILY: 17
    
    CPU_MODEL: 8
    
    CPU_STEPPING: 2
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1CA
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  f
    
    ANALYSIS_SESSION_HOST:  \
    
    ANALYSIS_SESSION_TIME:  05-30-2019 09:12:37.0727
    
    ANALYSIS_VERSION: 10.0.18869.1002 amd64fre
    
    BAD_STACK_POINTER:  fffff805136f6c68
    
    LAST_CONTROL_TRANSFER:  from fffff80511eae810 to fffff805115beef0
    
    STACK_TEXT:  
    fffff805`136f6c68 fffff805`11eae810 : 00000000`000001ca 00000000`1f2900e8 0000000f`e4f55593 0000000f`e4f863c1 : nt!KeBugCheckEx
    fffff805`136f6c70 fffff805`11eb46b2 : 0000000f`e4f863c1 00000000`00000001 00000000`00000000 fffff805`116a6350 : hal!HalpWatchdogCheckPreResetNMI+0xd0
    fffff805`136f6cb0 fffff805`1169737b : 00000000`00000001 ffffd40e`635c9100 fffff805`0e505180 fffff805`116a63e0 : hal!HalpPreprocessNmi+0x12
    fffff805`136f6ce0 fffff805`115ca102 : 00000000`00000800 fffff805`136f6ef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0xcb
    fffff805`136f6d30 fffff805`115c9ec3 : 00000000`00000800 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
    fffff805`136f6e70 fffff805`116f083e : 00000000`00000000 0000151c`ed15bf94 00000000`00000000 ffffd40e`635c9100 : nt!KiNmiInterrupt+0x203
    fffff805`136e47a0 fffff805`114f1acb : fffff805`116f0860 00000000`00000000 ffffd40e`635c9010 00000000`000001ab : nt!PpmIdleGuestExecute+0x1e
    fffff805`136e47e0 fffff805`114f127f : 00000000`00000000 00000000`00000002 00000000`00000001 00000000`00000001 : nt!PpmIdleExecuteTransition+0x6bb
    fffff805`136e4b00 fffff805`115c28ec : 00000000`00000000 fffff805`0e505180 fffff805`1196b400 ffffd40e`6a4c8480 : nt!PoIdle+0x33f
    fffff805`136e4c60 00000000`00000000 : fffff805`136e5000 fffff805`136df000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  cb522721ccf98392c0a19a23914952c2ac4c66ec
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  92c3c39bc2f820fb511b9f80a53b6968264c5512
    
    THREAD_SHA1_HASH_MOD:  77e3653e8f322fbd447ccc02351d9fed3c4e96be
    
    FOLLOWUP_IP: 
    nt!KiProcessNMI+cb
    fffff805`1169737b 488b3dfe621900  mov     rdi,qword ptr [nt!KiNmiCallbackListHead (fffff805`1182d680)]
    
    FAULT_INSTR_CODE:  fe3d8b48
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!KiProcessNMI+cb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  7fd0bac2
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  cb
    
    FAILURE_BUCKET_ID:  0x1CA_STACKPTR_ERROR_nt!KiProcessNMI
    
    BUCKET_ID:  0x1CA_STACKPTR_ERROR_nt!KiProcessNMI
    
    PRIMARY_PROBLEM_CLASS:  0x1CA_STACKPTR_ERROR_nt!KiProcessNMI
    
    TARGET_TIME:  2019-05-29T19:17:44.000Z
    
    OSBUILD:  17763
    
    OSSERVICEPACK:  0
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  400
    
    PRODUCT_TYPE:  3
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    OSEDITION:  Windows 10 Server TerminalServer DataCenter SingleUserTS
    
    OS_LOCALE:  
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  2037-12-14 14:42:10
    
    BUILDDATESTAMP_STR:  180914-1434
    
    BUILDLAB_STR:  rs5_release
    
    BUILDOSVER_STR:  10.0.17763.1.amd64fre.rs5_release.180914-1434
    
    ANALYSIS_SESSION_ELAPSED_TIME:  3ac9
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x1ca_stackptr_error_nt!kiprocessnmi
    
    FAILURE_ID_HASH:  {09a889cd-f940-6da5-9668-0c0c98a7d643}
    
    Followup:     MachineOwner
    ---------
    
    

    Thursday, May 30, 2019 1:15 AM

All replies

  • How did you go about making the change from Intel to AMD?  Generally speaking, everything requires a new installation.  You cannot simply move a system disk from an Intel CPU to an AMD CPU - they use different hardware instructions. 

    tim

    Thursday, May 30, 2019 1:18 PM
  • Hi,

    I agree with Tim, if we don't perform a new installation, it will causes several issues: 

    boot mode/sata controller mode compatibility (system doesn't boot); driver compatibility (performance issues); loss of windows activation.

    Windows 10 installation media: 

    https://www.microsoft.com/en-us/software-download/windows10

    For your reference: 

    https://www.quora.com/Why-does-my-PC-gets-bsod-when-I-change-CPU

    Note: This is a third-party link and we do not have any guarantees on this website. This is just for your convenience. And Microsoft does not make any guarantees about the content.

    Best regards,

    Yilia 



    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Friday, May 31, 2019 2:20 AM
    Moderator
  • cool. i tried to remove as many legacy drivers before go ahead and swap processor. 

    seems like i should really re-setup everything, i will go ahead to do that this weekend and hope for the best. 

    Thank guys!

    Friday, May 31, 2019 2:37 AM
  • i had reformat everything and start from 0. seems like amd ryzen still causing hyper-v host to BSOD randomly. 
    Saturday, June 1, 2019 12:57 AM
  • AMD Ryzen is a desktop CPU.  I don't think it has been qualified to support Windows Server.  This does not necessarily mean that you won't be able to get Windows Server to run on a Ryzen CPU, but it does mean that it is up to you to find the combination that works to give you an unsupported environment.  You may have to try different device drivers that the defaults that are installed with a Windows Server installation.  You may need to find the right BIOS settings.

    You might have more luck finding an AMD Ryzen technical forum and ask the experts there if anyone has gotten the Ryzen to successfully run Windows Server.  The bottom line is that this is an issue that needs to be worked from the AMD side because the chip has not been certified by AMD or any of their OEMs to support Windows Server.


    tim


    Saturday, June 1, 2019 1:21 PM
  • Hi Tim, 

    You're probably right. now that i cleaned / uninstall all the drives, with AMD cleanup utility. running stock without any driver, seems to be much more stable.

    in short, Ryzen is indeed not so suitable for my homelab, especially with Windows Server 2019. 

    Sunday, June 2, 2019 8:12 AM
  • Hi,

    I am glad to hear that your issue was successfully resolved.

    If there is anything else we can do for you, please feel free to post in the forum.

    Best Regards,

    Yilia


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, June 4, 2019 6:55 AM
    Moderator