BSOD - Help would be greatly appreciated

Hi,

I keep running into random blue screens of death. I’ve been trying to figure out how to fix it.

I went online and did some research, was able to open my “memory dump”.

I still cannot understand what went wrong. Can anyone please tell me what to do.

Thank you.

Here’s the dump:

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.192 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: To be filled by O.E.M.

SYSTEM_PRODUCT_NAME: To be filled by O.E.M.

SYSTEM_SKU: SKU

SYSTEM_VERSION: To be filled by O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 2501

BIOS_DATE: 04/07/2014

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: M5A99FX PRO R2.0

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffde067810f028

BUGCHECK_P3: b0800000

BUGCHECK_P4: 40151

BUGCHECK_STR: 0x124_AuthenticAMD

CPU_COUNT: 8

CPU_MHZ: 10ee

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: javaw.exe

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: DESKTOP-64F8SMV

ANALYSIS_SESSION_TIME: 01-23-2018 18:34:39.0857

ANALYSIS_VERSION: 10.0.16299.15 x86fre

STACK_TEXT:
ffff85801e3d1c38 fffff8019e323f1f : 0000000000000124 0000000000000000 ffffde067810f028 00000000b0800000 : nt!KeBugCheckEx
ffff85801e3d1c40 fffff80529d6148a : ffffde067810f028 ffffde06774ed5c0 ffffde06774ed5c0 ffffde06774ed5c0 : hal!HalBugCheckSystem+0xcf
ffff85801e3d1c80 fffff8019dc98ab1 : ffffde067810f028 0000000000000000 ffffde06774ed5c0 ffffde06774ed5c0 : PSHED!PshedBugCheckSystem+0xa
ffff85801e3d1cb0 fffff8019e324460 : 0000000000000728 0000000000000004 ffff85801e3d2000 0000000000000000 : nt!WheaReportHwError+0x261
ffff85801e3d1d10 fffff8019e3247c0 : 0000000000000010 0000000000000004 ffff85801e3d1eb8 0000000000000004 : hal!HalpMcaReportError+0x50
ffff85801e3d1e60 fffff8019e3246ae : ffffde06774ece50 0000000000000001 ffff85801e3d2000 0000000000000000 : hal!HalpMceHandlerCore+0xe0
ffff85801e3d1eb0 fffff8019e324a89 : ffffde06774ece50 ffff85801e3d20f0 0000000000000000 0000000000000000 : hal!HalpMceHandler+0xda
ffff85801e3d1ef0 fffff8019db98a3b : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : hal!HalHandleMcheck+0x49
ffff85801e3d1f20 fffff8019db986bd : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KxMcheckAbort+0x7b
ffff85801e3d2060 0000000004a4071c : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x47d
0000000014a0f5f8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x4a4071c

THREAD_SHA1_HASH_MOD_FUNC: 88e882887fe56e19e033ccb065f96059ef746ee5

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 62092442456e2885276f77384982ec3d08c9223a

THREAD_SHA1_HASH_MOD: 4f95fe8af2e6cfcf04d63a4a4c0edcdd9add15b3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_CACHE

PRIMARY_PROBLEM_CLASS: 0x124_AuthenticAMD_PROCESSOR_CACHE

TARGET_TIME: 2018-01-23T23:05:47.000Z

OSBUILD: 16299

OSSERVICEPACK: 192

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-01-01 06:07:05

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.192

ANALYSIS_SESSION_ELAPSED_TIME: 19d6

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_authenticamd_processor_cache

FAILURE_ID_HASH: {b533751b-676e-7546-bcdc-24e6c40d0064}

Can you give me the minidump located in C:\Windows\Minidump\

I can look in them to figure what the issue is.

From the current look of what you posted, is java up-to-date?

1 Like

I agree with @Novasty that you should check that Java is up to date first, but that’s probably not the root cause. I use a little program from NirSoft called Blue Screen View. It will read the minidump info and give it to you in a much easier to read format, usually pointing to the driver that caused the crash.

https://www.nirsoft.net/utils/blue_screen_view.html

If you need help reading the output of the minidump, we’ll be happy to help you with that.

1 Like

BSV doesn’t provide enough information.
WinDBG + Sysnative will cover a lot more in a human readable format as well.

2 Likes

That works too. Whatever gets the info. :slight_smile:

1 Like

Here is my dump file:
https://drive.google.com/file/d/1cI1bRH-175_prSrHTSCt1qqqXr1t0Ils/view?usp=sharing

When did the BSoDs start happening?

Do you know how to uninstall Windows updates?

I do know how to uninstall windows updates.

I thought it was my ram but I tested my memory using memtest86 and everything passed.

I still need to know when it started happening otherwise I can’t recommend what I think I should recommend.

I’m not sure when it started. I’ve always had this problem. I believe I got my first one when I had to use wireless adapter issues.

I recently reset my pc completely and i’m still having the BSOD.

What kind of adapter do you have? Have you tried running the PC without the wireless adapter?

yes. It would fix the issue. I did purchase a new adapter recently and the problem continues. Not sure if the BSOD is for the same reason.
I used an ASUS AC56.
Now I’m using AC1200 from BrosTrend.

Are the drivers up to date?

Do you have the capacity and access to a PCI-e based wireless adapter?

Also how did you find such an obscure name?

also try and uninstall this update: https://support.microsoft.com/en-ca/help/4056892/windows-10-update-kb4056892

Drivers are up to date. PCI-e possibility, if problem consists.
I will try uninstalling that update, see if it fixes it.