Solved BSODs happening every 2 to 3 days usually while idle or working (not while gaming)

philc43 said:

Hello @edgrace91

It would really help if you provided the full set of logfiles as requested in the BSOD Posting Instructions.

Click to expand...

philc43 said:

I've looked through the logs and can see that this was a new installation on 8th October. You then proceeded to load drivers and software for two days and it was then that the BSODs started.

Was the installation a clean install or did you keep files from a previous installation?

The two BSODs are different. The first one was a DPC Watchdog variety and this can only really be debugged if you provide the full memory dump which is called memory.dmp and can be found in the C:\Windows folder. Unfortunately this dump gets overwritten everytime you have a new BSOD so the dump I needed is no longer there. Next time you have a 0x133 bugcheck please copy the memory.dmp to your desktop, zip it and save to a One Drive or Dropbox shared folder and provide a link to it in your next post.

The second BSOD is a 0xd1 Driver IRQL type and there are no obvious causes that can be found from the analysis of the dump.

I suspect it may be driver related. It would have been interesting to have waited for longer intervals between loading drivers and software to see if you could identify when the problem started and then undo recent changes.

There is a process called a clean boot which lets you do something similar. Have a read of this tutorial and see if you understand what to do.

Perform a Clean Boot in Windows 11 to Troubleshoot Software Conflicts

This tutorial will show you how to perform a clean boot to start Windows 10 or Windows 11 using a minimal set of drivers and startup programs for troubleshooting application conflicts. Troubleshooting Windows can be a complex process due to the many different drivers, settings, and programs...

www.elevenforum.com

Click to expand...

philc43 said:

Thanks for this latest dump file. It confirms the micro code update process was running when the crash happened.

FAILURE_BUCKET_ID: IP_MISALIGNED_AuthenticAMD.sys

However, this is incorrectly identified as a .sys driver. The actual driver is the following:

Code:

0: kd> lmDvmmcupdate_AuthenticAMD
Browse full module list
start             end                 module name
fffff804`12dc0000 fffff804`12df5000   mcupdate_AuthenticAMD   (deferred)           
    Mapped memory image file: C:\WINDOWS\System32\mcupdate_AuthenticAMD.dll
    Image path: \SystemRoot\system32\mcupdate_AuthenticAMD.dll
    Image name: mcupdate_AuthenticAMD.dll
    Browse all global symbols  functions  data
    Image was built with /Brepro flag.
    Timestamp:        729AEFCF (This is a reproducible build file hash, not a timestamp)
    CheckSum:         0002D6A7
    ImageSize:        00035000
    File version:     10.0.22621.1
    Product version:  10.0.22621.1
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.A Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     mcupdate.dll
        OriginalFilename: mcupdate_AuthenticAMD.dll
        ProductVersion:   10.0.22621.1
        FileVersion:      10.0.22621.1 (WinBuild.160101.0800)
        FileDescription:  AMD Microcode Update Library
        LegalCopyright:   © Microsoft Corporation. All rights reserved.

I'm wondering if you have some problem with the AMD micro code for your processor. Please make sure the AMD chipset driver is updated from your motherboard support page. There was an update provided in September 2022.

Click to expand...

philc43 said:

Please send a link to a new log file and I can compare with the one you provided in post #3

Click to expand...

philc43 said:

The logs show that the drivers were not changed so you had already applied the latest versions. Keep your eye on the motherboard website to see if any new versions become available or contact them to see if they are aware of any issues around the micro-code updates.

If there is a hardware problem - we usually recommend leaving or using the system in safe-mode for 24 to 48 hours to see if it is stable. I know that this is not something you can easily do if it is a PC you depend upon for work but perhaps you can try overnight or over weekends when it is not being used.

Click to expand...

edgrace91 said:

Hi, Ive been experiencing a variation of Bsods over the last year.

I've already been through a lot of steps on this forum: Page 4 - Question - Multiple BSOD issues ?

I really need my PC to be stable becasue I want to be able to render animations using UE5 overnight and some of the time it fails because of bsod, it also is annoying in general and I don't want it to corrupt my pc.

here is a link to the latest minidump: 101122-6968-01.zip

hope someone can help. Cheers

Click to expand...

imanlien2020 said:

I just starting getting BSODs this week, I just installed TranslucentTB and it started happening, so uninstalled and no more BSODs for me.
Alot of software causes this to happen and can be very hard to track down which one. Ive not seen anyone getting a BSOD via using UE5 at all but..
Well here you go...guess lots of people do actually have this issue.
BSODs using UE5

Click to expand...