Windows 10: BSOD on a newly replaced MOBO

Discus and support BSOD on a newly replaced MOBO in Windows 10 Drivers and Hardware to solve the problem; Hello guys, I had this problem for a few months already and I ha my motherboard replaced to fix the problem. But only after a few days, the same BSOD... Discussion in 'Windows 10 Drivers and Hardware' started by Evan Justin del Castillo, Jun 7, 2020.

  1. EVAN JUSTIN DEL CASTILLO
    Evan Justin del Castillo Win User

    BSOD on a newly replaced MOBO


    Hello guys,


    I had this problem for a few months already and I ha my motherboard replaced to fix the problem. But only after a few days, the same BSOD happened with the same error. Maybe someone can help me with this. Here is the latest dumpfile of the last BSOD.




    Microsoft R Windows Debugger Version 10.0.19041.1 X86

    Copyright c Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Users\evanj\Desktop\060720-21031-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available



    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 18362 MP 12 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 18362.1.amd64fre.19h1_release.190318-1202

    Machine Name:

    Kernel base = 0xfffff802`0f000000 PsLoadedModuleList = 0xfffff802`0f448170

    Debug session time: Sun Jun 7 12:38:20.481 2020 UTC + 8:00

    System Uptime: 1 days 18:40:00.591

    Loading Kernel Symbols

    .



    Press ctrl-c cdb, kd, ntsd or ctrl-break windbg to abort symbol loads that take too long.

    Run !sym noisy before .reload to track down problems loading symbols.



    ..............................................................

    ................................................................

    ................................................................

    ................................................

    Loading User Symbols

    Loading unloaded module list

    ..............................................

    For analysis of this file, run !analyze -v

    2: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    DRIVER_POWER_STATE_FAILURE 9f

    A driver has failed to complete a power IRP within a specific time.

    Arguments:

    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time

    Arg2: ffff8a8866b4a060, Physical Device Object of the stack

    Arg3: fffffa07b163f7b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack

    Arg4: ffff8a886b7fa870, The blocked IRP



    Debugging Details:

    ------------------



    Implicit thread is now ffff8a88`63ce7540

    *** WARNING: Unable to verify timestamp for igdkmd64.sys

    *** WARNING: Unable to verify timestamp for win32k.sys



    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 11



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-J1RPL90



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 74



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 80



    Key : Analysis.System

    Value: CreateObject





    BUGCHECK_CODE: 9f



    BUGCHECK_P1: 3



    BUGCHECK_P2: ffff8a8866b4a060



    BUGCHECK_P3: fffffa07b163f7b0



    BUGCHECK_P4: ffff8a886b7fa870



    DRVPOWERSTATE_SUBCODE: 3



    FAULTING_THREAD: ffff8a8863ce7540



    IMAGE_NAME: pci.sys



    MODULE_NAME: pci



    FAULTING_MODULE: fffff802111e0000 pci



    BLACKBOXACPI: 1 !blackboxacpi





    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    PROCESS_NAME: System



    STACK_TEXT:

    fffffa07`b161dba0 fffff802`0f11507d : fffff802`0a832180 117ea606`fffffffe fffff802`ffffffff 00000000`00000001 : nt!KiSwapContext+0x76

    fffffa07`b161dce0 fffff802`0f113f04 : ffff8a88`63ce7540 fffff802`00000000 fffff802`00000000 ffff8a88`00000000 : nt!KiSwapThread+0xbfd

    fffffa07`b161dd80 fffff802`0f1136a5 : 00000000`00000000 ffffde09`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x144

    fffffa07`b161de20 fffff802`110f2a9a : fffffa07`b161df68 00000000`00000000 00000000`00000000 ffff8a88`67aa7900 : nt!KeWaitForSingleObject+0x255

    fffffa07`b161df00 fffff802`11101797 : fffffa07`00000000 ffff8a88`67aa7988 00000000`00000004 00000000`00000028 : ACPI!SyncEvalObject+0x29a

    fffffa07`b161dfb0 fffff802`1110135a : 00000000`00000000 ffffde09`614ab490 00000000`00000000 ffffde09`45905bb0 : ACPI!AMLIEvalNameSpaceObject+0xab

    fffffa07`b161e010 fffff802`110f1586 : ffff8a88`74eed460 fffff802`00000004 ffffde09`614ab490 ffff8a88`67aa7a00 : ACPI!ACPIIoctlEvalControlMethod+0xa6

    fffffa07`b161e0a0 fffff802`110f10d8 : ffff8a88`662ef980 00000000`00000007 ffff8a88`74eed5c0 fffff802`0f11e797 : ACPI!ACPIIrpDispatchDeviceControl+0x186

    fffffa07`b161e0e0 fffff802`0f10a929 : 00000000`00000007 00000000`c00000bb fffffa07`b161e2a0 00000000`00000000 : ACPI!ACPIDispatchIrp+0xc8

    fffffa07`b161e160 fffff802`25f4fb46 : 00000000`00000019 00000000`00000000 00000000`00000103 00000000`00000000 : nt!IofCallDriver+0x59

    fffffa07`b161e1a0 fffff802`25df3bfa : 00000000`00000000 ffff8a88`6caea030 00000000`00000000 00000000`00000000 : dxgkrnl!DpiFdoDispatchIoctl+0x6f6

    fffffa07`b161ecc0 fffff802`0f10a929 : ffffde09`597dc280 fffff802`00000014 00000000`00000000 fffffa07`b161ee98 : dxgkrnl!DpiDispatchIoctl+0xda

    fffffa07`b161ede0 fffff802`25df2292 : 00000000`00000000 ffff8a88`6caea180 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x59

    fffffa07`b161ee20 fffff802`2a74873e : ffffffff`fe363c00 00000000`ffffffff ffff8a88`6cba4000 fffff802`0000003c : dxgkrnl!DpEvalAcpiMethod+0x162

    fffffa07`b161eef0 ffffffff`fe363c00 : 00000000`ffffffff ffff8a88`6cba4000 fffff802`0000003c ffffde09`597dc280 : igdkmd64+0x5873e

    fffffa07`b161eef8 00000000`ffffffff : ffff8a88`6cba4000 fffff802`0000003c ffffde09`597dc280 00000000`00000014 : 0xffffffff`fe363c00

    fffffa07`b161ef00 ffff8a88`6cba4000 : fffff802`0000003c ffffde09`597dc280 00000000`00000014 00000000`20504d40 : 0xffffffff

    fffffa07`b161ef08 fffff802`0000003c : ffffde09`597dc280 00000000`00000014 00000000`20504d40 00000000`00000000 : 0xffff8a88`6cba4000

    fffffa07`b161ef10 ffffde09`597dc280 : 00000000`00000014 00000000`20504d40 00000000`00000000 00000000`ffffffff : 0xfffff802`0000003c

    fffffa07`b161ef18 00000000`00000014 : 00000000`20504d40 00000000`00000000 00000000`ffffffff 00000000`0000037d : 0xffffde09`597dc280

    fffffa07`b161ef20 00000000`20504d40 : 00000000`00000000 00000000`ffffffff 00000000`0000037d fffffa07`b161f030 : 0x14

    fffffa07`b161ef28 00000000`00000000 : 00000000`ffffffff 00000000`0000037d fffffa07`b161f030 fffff802`2a7489ad : 0x20504d40





    STACK_COMMAND: .thread 0xffff8a8863ce7540 ; kb



    IMAGE_VERSION: 10.0.18362.752



    SYMBOL_NAME: pci!PciBusInterface_GetBusData <PERF> pci+0x0+0



    BUCKET_ID_FUNC_OFFSET: 0



    FAILURE_BUCKET_ID: 0x9F_3_ACPI_pci!PciBusInterface_GetBusData__PERF__pci+0x0



    OS_VERSION: 10.0.18362.1



    BUILDLAB_STR: 19h1_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {3768e0cb-c0c4-138e-4d0b-a325e2d0952b}



    Followup: MachineOwner

    ---------

    :)
     
    Evan Justin del Castillo, Jun 7, 2020
    #1
  2. ROHN007
    Rohn007 Win User

    Need to Replace my Mobo...

    You will have to contact MS Support to get help activating after you replace the MOBO.

    There is one exception to the no transfer rule that others have cited. That is when you replace the MOBO under warranty with the same model MOBO. So, get confirmation from HP that this is an equivalent replacement before contacting MS.
     
    Rohn007, Jun 7, 2020
    #2
  3. NOLYNHARVEY
    NolynHarvey Win User
    Replaced MOBO, BSOD, Freezes and Crashes

    Hello all,

    Long story short, I replaced my motherboard last night and since then I've been having some BSOD, freezes and crashes. Narrowing it down, I think it may be driver related. But honestly, I have no clue.

    Here are my specs:

    CPU: Ryzen 7 2700x

    GPU: Nvidia 2070 Super

    RAM: G.Skill Ripjaws 32gb DDR4 3200

    MOBO: ROG STRIX B450-F

    STORAGE: 2 Samsung 960 EVO NVME 500gb.

    All of my components are three months old apart from my new MOBO.

    A little more information before moving on:

    - I did Memtest86 last week on my RAM, everything came back clear.

    - Got great CPU Temps even under stress (32C idle).

    - I updated the new MOBO BIOS to it's current version, same with the GPU Drivers and LAN drivers.

    - I conducted sfc /scannow it came back fine.

    - I conducted DISM.exe /Online /Cleanup-image /Scanhealth and it came up fine.

    - I conducted DISM.exe /Online /Cleanup-image /Restorehealth and my pc froze.

    - I've tried Driver Verifier as instructed here and have
    no idea if it's working or not, I've yet to get another BSOD since activating it.

    - Last night I conducted Memtest86 and woke up to it frozen with a black screen with the blue windows logo and three loading circles at the bottom. Ran Memtest86 again and got through a few passes with no errors, canceled it to keep troubleshooting.

    - Finally, System Restore of any type doesn't seem to work, it either fails or crashes.

    Here are the top errors I am getting:

    - Error 1 -
    DMP File

    - Error 2 -
    DMP File

    - Error 3- Couldn't find this DMP...

    - Error 4 -
    DMP File

    Update: While getting these photos in paint, I got another crash. Here's the error and DMP file.

    - Error 5 - Couldn't find this DMP either...

    Currently running Memtest86 again and closely monitoring it.

    Let me know if you need anything additional to help with this. I really appreciate you taking time to help me with this!
     
    NolynHarvey, Jun 7, 2020
    #3
  4. DEN
    den Win User

    BSOD on a newly replaced MOBO

    BSoDS on newly built PC

    Since it is my first time, i did not know that there is a vendors approved list. and it is not. is that the reason for my BSODS?
     
    den, Jun 7, 2020
    #4
Thema:

BSOD on a newly replaced MOBO

Loading...

  1. BSOD on a newly replaced MOBO - Similar Threads - BSOD newly replaced

  2. New MOBO and CPUBooting to windows then BSOD

    in Windows 10 Software and Apps
    New MOBO and CPUBooting to windows then BSOD: Need helpI have a new upgrade for my system with a new Asrock B550 and AMD Ryzen 5 5600G new PSUPut new MOBO in and Doesnt recognize it. If I clear the Bios it might boot up or just crash back to BIOS screen. If it does boot up to windows it crashes to the Bios screen to...

  3. Persistent Intermittent BSOD's on upgraded mobo

    in Windows 10 BSOD Crashes and Debugging
    Persistent Intermittent BSOD's on upgraded mobo: Hello all, I had a few BSOD issues when on my previous motherboard related to the game bar and the GameInputRedistributable crashing my desktop, and decided to start with a fresh install when moving to a new X570 mother board from my previous X470 build. All other...

  4. Replaced MOBO, BSOD, Freezes and Crashes

    in Windows 10 Drivers and Hardware
    Replaced MOBO, BSOD, Freezes and Crashes: Hello all, Long story short, I replaced my motherboard last night and since then I've been having some BSOD, freezes and crashes. Narrowing it down, I think it may be driver related. But honestly, I have no clue. Here are my specs: CPU: Ryzen 7 2700x GPU: Nvidia 2070 Super...

  5. Reactvation after MOBO and CPU replacement.

    in Windows 10 Updates and Activation
    Reactvation after MOBO and CPU replacement.: A few days ago I attempted to perform the cu update from 1903 xxxxx.418 to 1909 using the files and procedure from uudump. Downloading and creating the ISO all went well. Mounted the ISO on my SSD and initiated the upgrade. It was proceeding as it should. At some point my pc...

  6. FAN NOT WORKING AFTER MOBO REPLACEMENT

    in Windows 10 Drivers and Hardware
    FAN NOT WORKING AFTER MOBO REPLACEMENT: Hi guys, i have a lenovo ideapad 320E its specs are i5-7200U 8gb ddr4 2gb nvidia 940 mx ... It recently got short circuited and i had to get the motherboard replaced,fortunately for me it was covered under warranty but now when i use dxdiag tool it shows my model is...

  7. Windows 10 and a replacement mobo of the same make and model

    in Windows 10 Updates and Activation
    Windows 10 and a replacement mobo of the same make and model: Had to pull a one week old motherboard and return it and which is being replaced with another of the same make and model. The Windows 10 registration & MS approval is on the boot drive, but will I have a problem with Windows 10 because of the change? 113038

  8. Windows 10 deactivated after mobo replace.

    in Windows 10 Updates and Activation
    Windows 10 deactivated after mobo replace.: Hi I have a problem. I upgraded my Windows 8.1 (key from Dreamspark) to Windows 10 in april. After RTM release, everything was OK, but I replaced my old motherboard (because it was just cheap shit and it just broke) to Sabretooth 990FX 2.0. My Windows is now deactivated. I...

  9. BSODs, failing mobo?

    in Windows 10 BSOD Crashes and Debugging
    BSODs, failing mobo?: Hey, what's up all. Recently, over the span of 3 days, I've been experiencing multiple BSODs. First couple times the BSOD was caused by a driver, which I've removed. Despite this, I'm still getting random BSODs (I just had one 20-30 minutes ago), except this time the bug...

  10. Replacing mobo with an identical replacement: what do I need to know?

    in Windows 10 Installation and Upgrade
    Replacing mobo with an identical replacement: what do I need to know?: Hi All: I just bought an identical (new) Vostro 270 mobo to replace the bad one in my Inspiron 660. Besides having to reactivate Windows 10, what else do I need to know or have on hand before proceeding? - Will I need to download drivers in advance - or can I update...