[SOLVED] Can someone help me figure out why my computer keeps crashing?

Toggle sidebar Toggle sidebar
M

MrCanadian

Dec 21, 2019
3
0
10
Hello everyone,

My computer regularly crashes, most often after several hours of usage, but sometimes a few minutes after loading windows, and even while booting up windows. When it crashes, it will often crash again immediately after, then be find for hours until the next series of crashes.

I've run tests on the RAM and the hard drive, and I've updated all the drivers (to the best of my knowledge). I can't figure out the problem and would really appreciate a direction to go in. I'll include the data from my mini dump file below in case that helps. Thanks for taking the time to read this.

***
  • *
  • Bugcheck Analysis *
  • *
***

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe50c0563b8c8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.17763.914 (WinBuild.160101.0800)

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe50c0563b8c8

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR: 0x124_AuthenticAMD

CPU_COUNT: 6

CPU_MHZ: dbc

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-EV2QEE2

ANALYSIS_SESSION_TIME: 12-21-2019 15:45:47.0573

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

STACK_TEXT:
ffff8e0d4b3175a0 fffff80712a1bff9 : ffffe50c058b4040 ffffe50c0563b8a0 fffff807128a35c0 ffff8e0d00000000 : nt!WheapCreateLiveTriageDump+0x7b
ffff8e0d4b317ad0 fffff807127bae78 : ffffe50c0563b8a0 fffff807124d3191 0000000000000000 0000000000000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
ffff8e0d4b317b00 fffff807127bbb8b : fffff807128a3560 fffff807128a35c0 ffffe50c058671a8 ffffe50c03a50840 : nt!WheapProcessWorkQueueItem+0x48
ffff8e0d4b317b40 fffff807125891fa : ffffe50c03a80ac0 ffffe50c058b4040 fffff807158b9500 ffffe50c00000000 : nt!WheapWorkQueueWorkerRoutine+0x2b
ffff8e0d4b317b70 fffff807124f69c5 : ffffe50c058b4040 ffffe50c03a86200 ffffe50c058b4040 00000224a4bb3dfe : nt!ExpWorkerThread+0x16a
ffff8e0d4b317c10 fffff8071265bdfc : ffffbe81f1698180 ffffe50c058b4040 fffff807124f6970 0000000000000006 : nt!PspSystemThreadStartup+0x55
ffff8e0d4b317c60 0000000000000000 : ffff8e0d4b318000 ffff8e0d4b312000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x1c


THREAD_SHA1_HASH_MOD_FUNC: 26acd050bd9f055d0a04825d57b9e0e6be9c1a07

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2d7687bc4d9a24dd51c507635bc4ce8aa00fde94

THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6

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: 2019-12-21T20:14:31.000Z

OSBUILD: 17763

OSSERVICEPACK: 914

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: unknown_date

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.17763.914

ANALYSIS_SESSION_ELAPSED_TIME: 9a8

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_authenticamd_processor_cache

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

Followup: MachineOwner
 
Solution
Dcopymope
MrCanadian said:
All updates are square.

I run Windows Defender / Firewall and Malware Bytes.

The CPU overheating is a possibility, but is there a way for me to test that? Is there any good software I can use to monitor its condition, and what precisely should I be looking for (prior to a crash)?

Appreciated, thanks.
Click to expand...

Well there are a number of ways it can be done, but I use a program called 'Remote System Monitor' linked below. You have to install it on your cell phone as well for it to work, but you first install it on your PC. It securely monitors pretty much everything about your system. Don't let the alerts from your anti-virus program startle you. Its just a false positive.

Link: Remote System Monitor
Sort by date Sort by votes
Dcopymope

Dcopymope

Prominent
BANNED
Aug 13, 2018
471
27
695
MrCanadian said:
Hello everyone,

My computer regularly crashes, most often after several hours of usage, but sometimes a few minutes after loading windows, and even while booting up windows. When it crashes, it will often crash again immediately after, then be find for hours until the next series of crashes.

I've run tests on the RAM and the hard drive, and I've updated all the drivers (to the best of my knowledge). I can't figure out the problem and would really appreciate a direction to go in. I'll include the data from my mini dump file below in case that helps. Thanks for taking the time to read this.

***
  • *
  • Bugcheck Analysis *
  • *
***

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe50c0563b8c8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.17763.914 (WinBuild.160101.0800)

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe50c0563b8c8

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR: 0x124_AuthenticAMD

CPU_COUNT: 6

CPU_MHZ: dbc

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-EV2QEE2

ANALYSIS_SESSION_TIME: 12-21-2019 15:45:47.0573

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

STACK_TEXT:
ffff8e0d4b3175a0 fffff80712a1bff9 : ffffe50c058b4040 ffffe50c0563b8a0 fffff807128a35c0 ffff8e0d00000000 : nt!WheapCreateLiveTriageDump+0x7b
ffff8e0d4b317ad0 fffff807127bae78 : ffffe50c0563b8a0 fffff807124d3191 0000000000000000 0000000000000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
ffff8e0d4b317b00 fffff807127bbb8b : fffff807128a3560 fffff807128a35c0 ffffe50c058671a8 ffffe50c03a50840 : nt!WheapProcessWorkQueueItem+0x48
ffff8e0d4b317b40 fffff807125891fa : ffffe50c03a80ac0 ffffe50c058b4040 fffff807158b9500 ffffe50c00000000 : nt!WheapWorkQueueWorkerRoutine+0x2b
ffff8e0d4b317b70 fffff807124f69c5 : ffffe50c058b4040 ffffe50c03a86200 ffffe50c058b4040 00000224a4bb3dfe : nt!ExpWorkerThread+0x16a
ffff8e0d4b317c10 fffff8071265bdfc : ffffbe81f1698180 ffffe50c058b4040 fffff807124f6970 0000000000000006 : nt!PspSystemThreadStartup+0x55
ffff8e0d4b317c60 0000000000000000 : ffff8e0d4b318000 ffff8e0d4b312000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x1c


THREAD_SHA1_HASH_MOD_FUNC: 26acd050bd9f055d0a04825d57b9e0e6be9c1a07

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2d7687bc4d9a24dd51c507635bc4ce8aa00fde94

THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6

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: 2019-12-21T20:14:31.000Z

OSBUILD: 17763

OSSERVICEPACK: 914

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: unknown_date

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.17763.914

ANALYSIS_SESSION_ELAPSED_TIME: 9a8

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_authenticamd_processor_cache

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

Followup: MachineOwner
Click to expand...

The module name titled 'AuthenticAMD' (bold text) indicates that something went wrong with your CPU. Is your BIOS up to date? How many anti-virus programs do you have installed? is your CPU overheating?
 
Upvote 0 Downvote
M

MrCanadian

Dec 21, 2019
3
0
10
Dcopymope said:
The module name titled 'AuthenticAMD' (bold text) indicates that something went wrong with your CPU. Is your BIOS up to date? How many anti-virus programs do you have installed? is your CPU overheating?
Click to expand...
Dcopymope said:
The module name titled 'AuthenticAMD' (bold text) indicates that something went wrong with your CPU. Is your BIOS up to date? How many anti-virus programs do you have installed? is your CPU overheating?
Click to expand...

All updates are square.

I run Windows Defender / Firewall and Malware Bytes.

The CPU overheating is a possibility, but is there a way for me to test that? Is there any good software I can use to monitor its condition, and what precisely should I be looking for (prior to a crash)?

Appreciated, thanks.
 
Upvote 0 Downvote
Dcopymope

Dcopymope

Prominent
BANNED
Aug 13, 2018
471
27
695
MrCanadian said:
All updates are square.

I run Windows Defender / Firewall and Malware Bytes.

The CPU overheating is a possibility, but is there a way for me to test that? Is there any good software I can use to monitor its condition, and what precisely should I be looking for (prior to a crash)?

Appreciated, thanks.
Click to expand...

Well there are a number of ways it can be done, but I use a program called 'Remote System Monitor' linked below. You have to install it on your cell phone as well for it to work, but you first install it on your PC. It securely monitors pretty much everything about your system. Don't let the alerts from your anti-virus program startle you. Its just a false positive.

Link: Remote System Monitor
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom