Windows 8 Windows 8.1 Constantly Crashing

R

rob999

New Member
Hi everyone, I’ve been having bad issues with my Windows 8.1 desktop I built about a decade ago.

It used to run flawlessly until about a year ago. It started to randomly crash / restart itself with no triggers that I can correlate to causing the crashes.

I’ve reset the computer to factory defaults maybe a dozen times now and it used to work fine for a couple weeks after each reset then would start to intermittently crash. Next best solution was to just keep the power disconnected from the power supply over night and it would work fine for a few days until it starts to crash again.

I always installed and updated all drivers after each reset.

I thought after resetting it that the automatic updates that Windows would install was the issue but when I turned off automatic updates, it just made it worse.

Half the time it crashes, it will reset itself or show a blue screen withYour PC ran into a problem and needs to restart." Below are the error codes below that it tells me to look into.

CACHE_MANAGER
MEMORY_MANAGEMENT
UNEXPECTED_KERNEL_MODE_TRAP
KERNEL_SECURITY_CHECK_FAILURE
KMODE_EXCEPTION_NOT_HANDLED

Files sent to Microsoft after a crash:
C:\Windows\Minidump\031122-12250-01.dmp
C:\Users\RobPC\AppData\Local\Temp\WER\38125-0.sysdata.xml
C:\Windows\MEMORY.DMP

Link to current Windows Error Reporting:

This is all very frustrating since I run my business from this computer and it’s making it difficult to work. I’d like to avoid having to buy/build a new computer. I’m fine with replacing a part or two if necessary. I just don’t know enough about computers to figure this out myself. Any ideas would be greatly appreciated!

If you need anymore information, let me know and I will respond to your comment and add to the post.

Thanks in advance!
 
Providing you haven't did a reset since the last blue screen, do the following.

Download BlueScreenView
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

This will give me a list of your bluescreens. After that I may have you upload those files in your next reply so I can debug them using a debugger.

From what I can see so far its possible its bad memory or a hardware failure of some sort.

Providing we can get this sorted out, you know you can get upgrade to windows 10 for free right? Also, can you tell me the specs of your pc as far as motherboard, cpu, ram and other hardware?
 
Ok! Thanks so much for the help so far!

I didn't realize I can get Windows 10 for free. I'll definitely give it a try and see if it clears it up. I'll try that after we debug the info below.

My hardware components are:

CPU: AMD FX(tm)-8350 Eight-Core Processor Black Edition
GPU: AMD Radeon Powercolor TurboDuo HD7790
Motherboard: Gigabyte Ultra Durable 78LMT-USB3
RAM: Ballistix by Crucial 2x8bg Sport DDR3-1333
Power: EVGA 550w
Network Adapter: Realtek 8812BU Wireless LAN 802.11ac USB NIC / Realtek PCIe GBE Family Controller

Blue screen list (I'll add more as it continues to crash):
==================================================
Dump File : 031122-12250-01.dmp
Crash Time : 3/11/2022 3:28:28 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000001`00000065
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`01a196a1
Caused By Driver : USBXHCI.SYS
Caused By Address : USBXHCI.SYS+196a1
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+1500a0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\031122-12250-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 329,216
Dump File Time : 3/11/2022 3:29:13 PM
==================================================

==================================================
Dump File : 031122-26625-01.dmp
Crash Time : 3/11/2022 12:49:48 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : ffffe000`02d3c4e8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+663e
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5b57d1
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\031122-26625-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 262,144
Dump File Time : 3/11/2022 12:49:55 PM
==================================================
 
rob999 said:
I didn't realize I can get Windows 10 for free
Click to expand...
Any windows 7 or 8.1 machine can still get windows 10 for free. Just go here and download the tool and choose to upgrade this pc.


From the 2 you posted, the first one was caused by your usb driver. The second one is a general hardware failure of some sort. Please navigate to C:\WINDOWS\Minidump\031122-26625-01.dmp and copy that file to your desktop(usually you can't zip the original file in that folder) and then zip it up and attach it to your next reply. I'll then debug that file to see if it will explain what hardware is causing the issue.

Unfortunately that motherboard only has 1 bios update since the original version. Are you by chance using a SATA SSD? Are you running bios F1 or F2?
 
Ok I just added the minidump file.

My storage is a Toshiba PH3300U-1I72 3TB SATA 6.0Gb/s 3.5" Internal Hard Drive

I'm barely passed novice level in regards to computers, so forgive me but I'm not exactly sure what you mean by running bios F1 or F2? I tried looking it up and just got results for what "F" button to open the bios upon startup. Is that what you mean?
 

Attachments

So here's your dump analysis:

Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Travis\Downloads\031122-26625-01\031122-26625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 9600.16384.amd64fre.winblue_rtm.130821-1623
Machine Name:
Kernel base = 0xfffff801`8e087000 PsLoadedModuleList = 0xfffff801`8e34e9b0
Debug session time: Fri Mar 11 12:49:48.317 2022 (UTC - 5:00)
System Uptime: 0 days 0:00:09.021
Loading Kernel Symbols
.......................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
7: kd> !analyze -v
*******************************************************************************
* *
* 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. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe00002d3c4e8, 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

Key : Analysis.CPU.mSec
Value: 2639

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 5521

Key : Analysis.Init.CPU.mSec
Value: 1953

Key : Analysis.Init.Elapsed.mSec
Value: 13881

Key : Analysis.Memory.CommitPeak.Mb
Value: 73

Key : WER.OS.Branch
Value: winblue_rtm

Key : WER.OS.Timestamp
Value: 2013-08-21T16:23:00Z

Key : WER.OS.Version
Value: 8.1.9600.16384


BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe00002d3c4e8

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffd000`20f3e500 fffff801`8e3fb2e8 : ffffe000`00656180 ffffe000`02d3c4c0 fffff801`8e35dd00 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x81
ffffd000`20f3ea30 fffff801`8e24290c : ffffe000`02d3c4c0 ffffd000`20f3eb50 fffff801`8e35dd20 ffffe000`00656040 : nt!WheapCreateTriageDumpFromPreviousSession+0x44
ffffd000`20f3ea60 fffff801`8e243729 : fffff801`8e35dd20 ffffd000`20f3eb50 fffff801`8e35dd20 ffffd000`20f3eb50 : nt!WheapProcessWorkQueueItem+0x48
ffffd000`20f3eaa0 fffff801`8e0c33cd : 00000000`00000002 fffff801`8e243704 ffffe000`02d8e668 ffffe000`0252ed70 : nt!WheapWorkQueueWorkerRoutine+0x25
ffffd000`20f3ead0 fffff801`8e16e664 : 00000000`00000000 ffffe000`00656040 ffffe000`00656040 ffffe000`002f7900 : nt!ExpWorkerThread+0x2b5
ffffd000`20f3eb80 fffff801`8e1dd6c6 : ffffd000`20768180 ffffe000`00656040 ffffd000`20774200 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`20f3ebe0 00000000`00000000 : ffffd000`20f3f000 ffffd000`20f38000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

OS_VERSION: 8.1.9600.16384

BUILDLAB_STR: winblue_rtm

OSPLATFORM_TYPE: x64

OSNAME: Windows 8.1

FAILURE_ID_HASH: {035dcc87-485b-74b3-1c1b-ee50cb0c2865}

Followup: MachineOwner
---------
Click to expand...
I'm thinking you have bad RAM. Are you overclocked at all?
 
voyagerfan99 said:
So here's your dump analysis:


I'm thinking you have bad RAM. Are you overclocked at all?
Click to expand...
Voyager, ok thanks. It's not overclocked according to my task manager

johnb35 said:
Any windows 7 or 8.1 machine can still get windows 10 for free. Just go here and download the tool and choose to upgrade this pc.


From the 2 you posted, the first one was caused by your usb driver. The second one is a general hardware failure of some sort. Please navigate to C:\WINDOWS\Minidump\031122-26625-01.dmp and copy that file to your desktop(usually you can't zip the original file in that folder) and then zip it up and attach it to your next reply. I'll then debug that file to see if it will explain what hardware is causing the issue.

Unfortunately that motherboard only has 1 bios update since the original version. Are you by chance using a SATA SSD? Are you running bios F1 or F2?
Click to expand...
John, it crashed again. I added the info and dump file for it below.
==================================================
Dump File : 031222-11562-01.dmp
Crash Time : 3/12/2022 7:44:00 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00000411
Parameter 2 : fffff6e0`0000ef50
Parameter 3 : 85400001`0000e900
Parameter 4 : ffffc000`0019ae79
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+68f9c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+1500a0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\031222-11562-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 281,248
Dump File Time : 3/12/2022 7:44:47 AM
==================================================
 

Attachments

Looks like you may have bad memory, you've had 2 blue screens with the same thing now. Bad memory could cause all these other errors you are getting as well.

You can either follow this guide to use windows memory checker or configure a usb/cd to run Memtest86 on your ram.

winaero.com

How to diagnose memory using Memory Diagnostics Tool in Windows 8

Describes how to check your PC's RAM using Memory Diagnostics Tool in Windows 8
winaero.com

www.memtest86.com

MemTest86 - Download now!

Download your free copy of MemTest86 here for USB.
www.memtest86.com
 
Those do sound RAM related, you might be able to pull one of the sticks out and see if you still exhibit the same behavior (or if so, swap them). I'd run a few RAM diagnostics like the ones listed above, if you receive any errors it's usually time to replace the RAM.
 
Thank you. Unfortunately, I did get two new sticks of RAM and it's continuing to crash. Haven't gotten BSOD yet, just resets and freezes.

I attached the newest minidump file.

Any ideas on the next likely suspect? Thanks so much!
 

Attachments

Did you run those memory tests first before buying new ram? I'll check the dump out when I get home in a few hours.
 
@voyagerfan99

Can you run that dump file as well? For some reason the readout is saying something is wrong with my symbols but never had a problem before. Just wondering if its the actual file with an issue.

Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\John\Desktop\bluescreens\031822-12875-01\031822-12875-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 9600.16384.amd64fre.winblue_rtm.130821-1623
Machine Name:
Kernel base = 0xfffff800`f4071000 PsLoadedModuleList = 0xfffff800`f43389b0
Debug session time: Fri Mar 18 08:53:00.474 2022 (UTC - 5:00)
System Uptime: 0 days 0:00:06.177
Loading Kernel Symbols
.......................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
2: kd> !analyze -v
*******************************************************************************
* *
* 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. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe00002daa038, 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:
------------------

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1155

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2622

Key : Analysis.Init.CPU.mSec
Value: 1858

Key : Analysis.Init.Elapsed.mSec
Value: 25593

Key : Analysis.Memory.CommitPeak.Mb
Value: 68

Key : WER.OS.Branch
Value: winblue_rtm

Key : WER.OS.Timestamp
Value: 2013-08-21T16:23:00Z

Key : WER.OS.Version
Value: 8.1.9600.16384


BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe00002daa038

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffd000`21187500 fffff800`f43e52e8 : ffffe000`011cf9c0 ffffe000`02daa010 fffff800`f4347d00 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x81
ffffd000`21187a30 fffff800`f422c90c : ffffe000`02daa010 ffffd000`21187b50 fffff800`f4347d20 ffffe000`011cf880 : nt!WheapCreateTriageDumpFromPreviousSession+0x44
ffffd000`21187a60 fffff800`f422d729 : fffff800`f4347d20 ffffd000`21187b50 fffff800`f4347d20 ffffd000`21187b50 : nt!WheapProcessWorkQueueItem+0x48
ffffd000`21187aa0 fffff800`f40ad3cd : fffff800`f454b260 fffff800`f422d704 ffffc000`0032ad30 ffffe000`011cf880 : nt!WheapWorkQueueWorkerRoutine+0x25
ffffd000`21187ad0 fffff800`f4158664 : ffffd000`20774200 ffffe000`011cf880 ffffe000`011cf880 ffffe000`002ec800 : nt!ExpWorkerThread+0x2b5
ffffd000`21187b80 fffff800`f41c76c6 : ffffd000`20768180 ffffe000`011cf880 ffffd000`20774200 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`21187be0 00000000`00000000 : ffffd000`21188000 ffffd000`21181000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD__UNKNOWN_IMAGE_AuthenticAMD.sys

OS_VERSION: 8.1.9600.16384

BUILDLAB_STR: winblue_rtm

OSPLATFORM_TYPE: x64

OSNAME: Windows 8.1

FAILURE_ID_HASH: {040e52e7-d090-063d-114e-a7764087f128}

Followup: MachineOwner
Click to expand...
---------
 
Unfortunately your hardware is 10years old so it might be anything. Bad motherboard, bad CPU (less common), bad PSU etc. The fact that disconnecting the power supply overnight gives you some respite, might indicate that the power supply is becoming unstable. You might be better taking it to a workshop where they can swap out with known good parts.
 
Last edited:
johnb35 said:
@voyagerfan99

Can you run that dump file as well? For some reason the readout is saying something is wrong with my symbols but never had a problem before. Just wondering if its the actual file with an issue.


---------
Click to expand...
Change your symbol path to pull from the internet for a fresh download.

.sympath srv*https://msdl.microsoft.com/download/symbols


Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Travis\Downloads\031822-12875-01\031822-12875-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 9600.16384.amd64fre.winblue_rtm.130821-1623
Machine Name:
Kernel base = 0xfffff800`f4071000 PsLoadedModuleList = 0xfffff800`f43389b0
Debug session time: Fri Mar 18 09:53:00.474 2022 (UTC - 4:00)
System Uptime: 0 days 0:00:06.177
Loading Kernel Symbols
.......................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
2: kd> !analyze -v
*******************************************************************************
* *
* 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. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe00002daa038, 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

Key : Analysis.CPU.mSec
Value: 2656

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2604

Key : Analysis.Init.CPU.mSec
Value: 2406

Key : Analysis.Init.Elapsed.mSec
Value: 12323

Key : Analysis.Memory.CommitPeak.Mb
Value: 73

Key : WER.OS.Branch
Value: winblue_rtm

Key : WER.OS.Timestamp
Value: 2013-08-21T16:23:00Z

Key : WER.OS.Version
Value: 8.1.9600.16384


BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe00002daa038

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffd000`21187500 fffff800`f43e52e8 : ffffe000`011cf9c0 ffffe000`02daa010 fffff800`f4347d00 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x81
ffffd000`21187a30 fffff800`f422c90c : ffffe000`02daa010 ffffd000`21187b50 fffff800`f4347d20 ffffe000`011cf880 : nt!WheapCreateTriageDumpFromPreviousSession+0x44
ffffd000`21187a60 fffff800`f422d729 : fffff800`f4347d20 ffffd000`21187b50 fffff800`f4347d20 ffffd000`21187b50 : nt!WheapProcessWorkQueueItem+0x48
ffffd000`21187aa0 fffff800`f40ad3cd : fffff800`f454b260 fffff800`f422d704 ffffc000`0032ad30 ffffe000`011cf880 : nt!WheapWorkQueueWorkerRoutine+0x25
ffffd000`21187ad0 fffff800`f4158664 : ffffd000`20774200 ffffe000`011cf880 ffffe000`011cf880 ffffe000`002ec800 : nt!ExpWorkerThread+0x2b5
ffffd000`21187b80 fffff800`f41c76c6 : ffffd000`20768180 ffffe000`011cf880 ffffd000`20774200 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`21187be0 00000000`00000000 : ffffd000`21188000 ffffd000`21181000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_PROCESSOR_CACHE_IMAGE_AuthenticAMD.sys

OS_VERSION: 8.1.9600.16384

BUILDLAB_STR: winblue_rtm

OSPLATFORM_TYPE: x64

OSNAME: Windows 8.1

FAILURE_ID_HASH: {d6c4d869-cd29-1e48-0267-5766712959d2}

Followup: MachineOwner
---------
Click to expand...
I think now that you replaced the RAM you need to wipe and reinstall Windows.
 
johnb35 said:
Did you run those memory tests first before buying new ram? I'll check the dump out when I get home in a few hours.
Click to expand...
Here's the results from the memory diagnostics test:

Log Name: Microsoft-Windows-MemoryDiagnostics-Results/Debug
Source: Microsoft-Windows-MemoryDiagnostics-Results
Date: 3/18/2022 8:17:30 PM
Event ID: 2001
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: Rob
Description:
Windows Memory Diagnostic results
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-MemoryDiagnostics-Results" Guid="{5F92BC59-248F-4111-86A9-E393E12C6139}" />
<EventID>2001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2022-03-19T00:17:30.119622200Z" />
<EventRecordID>1</EventRecordID>
<Correlation />
<Execution ProcessID="2276" ThreadID="2268" />
<Channel>Microsoft-Windows-MemoryDiagnostics-Results/Debug</Channel>
<Computer>Rob</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<Results xmlns="http://manifests.microsoft.com/win/2005/08/windows/Reliability/Postboot/Events">
<MemDiagRawData>ED3F0000000000000200000003000000050000000A000000E80100000C0000000200000000000000D4E73F003E050000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C80000000000000040773457B700000001000000C800000000000000C8000000000000000C00000038000000E6070300120014000800310000000700D4E73F003E05000001000020000001000600010000000000020001001000010000000000040001001400010000000000060001001900010000000000010001003200010000000000030001007F00010000000000000001000600020000000000020001001000020000000000040001001400020000000000060001001900020000000000010001003100020000000000030001008000020000000000</MemDiagRawData>
</Results>
</UserData>
</Event>
 
DavidG said:
Unfortunately your hardware is 10years old so it might be anything. Bad motherboard, bad CPU (less common), bad PSU etc. The fact that disconnecting the power supply overnight gives you some respite, might indicate that the power supply is becoming unstable. You might be better taking it to a workshop where they can swap out with know good parts.
Click to expand...
I replaced my PSU last year after my old one started making extremely loud buzzing noises 24/7. I can't recall exactly if the crashes started before or after replacing it, but certainly around the time of replacing it. Now I'm curious if this is the cause
 
rob999 said:
Here's the results from the memory diagnostics test:

Log Name: Microsoft-Windows-MemoryDiagnostics-Results/Debug
Source: Microsoft-Windows-MemoryDiagnostics-Results
Date: 3/18/2022 8:17:30 PM
Event ID: 2001
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: Rob
Description:
Windows Memory Diagnostic results
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-MemoryDiagnostics-Results" Guid="{5F92BC59-248F-4111-86A9-E393E12C6139}" />
<EventID>2001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2022-03-19T00:17:30.119622200Z" />
<EventRecordID>1</EventRecordID>
<Correlation />
<Execution ProcessID="2276" ThreadID="2268" />
<Channel>Microsoft-Windows-MemoryDiagnostics-Results/Debug</Channel>
<Computer>Rob</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<Results xmlns="http://manifests.microsoft.com/win/2005/08/windows/Reliability/Postboot/Events">
<MemDiagRawData>ED3F0000000000000200000003000000050000000A000000E80100000C0000000200000000000000D4E73F003E050000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C80000000000000040773457B700000001000000C800000000000000C8000000000000000C00000038000000E6070300120014000800310000000700D4E73F003E05000001000020000001000600010000000000020001001000010000000000040001001400010000000000060001001900010000000000010001003200010000000000030001007F00010000000000000001000600020000000000020001001000020000000000040001001400020000000000060001001900020000000000010001003100020000000000030001008000020000000000</MemDiagRawData>
</Results>
</UserData>
</Event>
Click to expand...
Unfortunately, that doesn't tell me anything. Doesn't say passed or failed or whatever.
 
Thank you all for the help. I did replace the ram and that was not the issue. Went to a computer repair store and had it there for 3 weeks. They claimed the tried replacing everything except for the motherboard and CPU and said that the motherboard is the issue claiming it's not telling the CPU fan to work, but the CPU fan is working... they quoted me $600 to replace the motherboard. I looked into replacing the motherboard on my own but decided to try to get a new PSU first before doing that since when I replaced the original PSU last summer, I believe that's when the crashing started to happen.

Low and behold, it does not crash with this new PSU. Not entirely sure why but I've had good luck so far. Hasn't crashed at all with extensive use the passed week and a half. Fingers crossed it will continue to do so

Thank!
 
Last edited:
You must log in or register to reply here.
Back
Top