Jump to content

Computer freezes after startup

BiggestLeo
 Share
Posted

Hello and thanks for reading my question. Just today I was playing the Witcher 3 when my computer completely froze-- the mouse and keyboard were unresponsive and nothing worked, so I cut the power and rebooted my computer. I was immediately greeted with a screen saying that the main bios was corrupted and that I had to restore it with my backup bios. I did this and was successfully able to enter the os, only to have my system freeze again, a few seconds later. I cut the power again and was again greeted with the corrupt bios screen. So after a few vicious cycles I decided to flash the newest bios onto the system via USB and clear the CMOS. This got rid of the corrupt bios screen on startup but my system still froze a few minutes after boot up. I have no idea what to do next and would greatly appreciate any advice. 

System
CPU-FX-6300
GPU-GTX 750TI
RAM- Corsair Vengeance 8GB DDR3 1600
MOBO-Gigabyte GA-970A-DS3P ATX AM3+ Motherboard
SSD-PNY CS1311 240GB 2.5" Solid State Drive

OS-64 bit Windows 10 Home Premium

Link to comment
https://linustechtips.com/topic/642943-computer-freezes-after-startup/
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Hi, i have the usb that installs windows 10 via iso

 

the issue occurs in bios, os, and safe mode though. I did get a BSOD in one of my attempts to startup the system

 

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


Loading Dump File [C:\Users\Leo\Desktop\081416-4921-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 10586 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.545.amd64fre.th2_release.160802-1857
Machine Name:
Kernel base = 0xfffff800`99e7a000 PsLoadedModuleList = 0xfffff800`9a157cf0
Debug session time: Sun Aug 14 18:53:30.317 2016 (UTC - 4:00)
System Uptime: 0 days 0:18:55.040
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe00150244028, b8800000, 20f0f}

Probably caused by : AuthenticAMD

Followup:     MachineOwner
---------

0: 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.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe00150244028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b8800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000020f0f, Low order 32-bits of the MCi_STATUS value.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.10586.545 (th2_release.160802-1857)

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

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

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

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

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  FD

BIOS_DATE:  02/26/2016

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  970A-DS3P

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

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe00150244028

BUGCHECK_P3: b8800000

BUGCHECK_P4: 20f0f

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:  nb3test.exe

CURRENT_IRQL:  f

ANALYSIS_SESSION_HOST:  DESKTOP-4HOAG0U

ANALYSIS_SESSION_TIME:  08-14-2016 21:47:00.0102

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

STACK_TEXT:  
fffff800`9ba4ea68 fffff800`99e3cf1f : 00000000`00000124 00000000`00000000 ffffe001`50244028 00000000`b8800000 : nt!KeBugCheckEx
fffff800`9ba4ea70 fffff800`9a08a8bc : ffffe001`50244028 ffffe001`50286cb0 ffffe001`50286cb0 ffffe001`50286cb0 : hal!HalBugCheckSystem+0xcf
fffff800`9ba4eab0 fffff800`99e3d40c : 00000000`00000728 00000000`00000000 fffff800`9ba4ee70 00000000`00000000 : nt!WheaReportHwError+0x258
fffff800`9ba4eb10 fffff800`99e3d764 : ffffe001`00000010 ffffe001`50286cb0 fffff800`9ba4ecb8 ffffe001`50286cb0 : hal!HalpMcaReportError+0x50
fffff800`9ba4ec60 fffff800`99e3d64e : ffffe001`502ca860 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe8
fffff800`9ba4ecb0 fffff800`99e3da19 : ffffe001`502ca860 fffff800`9ba4eef0 00000000`00000000 00001f80`00000f00 : hal!HalpMceHandler+0xda
fffff800`9ba4ecf0 fffff800`99fc647b : 00000000`00000000 00000000`0000002b 00000000`77bb6d3c ffffe001`546bd840 : hal!HalHandleMcheck+0x49
fffff800`9ba4ed20 fffff800`99fc6231 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff800`9ba4ee60 00000000`7740709d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
00000000`0060fe48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7740709d


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  5587b7eef3e5d1004cbe2a4ed5296100dcf38cda

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  2a486745d9a076c4f8eeb79914c2528efe771d13

THREAD_SHA1_HASH_MOD:  2199336a955b99afec8bfbbee3a384cfc1a11512

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS

PRIMARY_PROBLEM_CLASS:  0x124_AuthenticAMD_PROCESSOR_BUS

TARGET_TIME:  2016-08-14T22:53:30.000Z

OSBUILD:  10586

OSSERVICEPACK:  545

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-08-03 05:15:01

BUILDDATESTAMP_STR:  160802-1857

BUILDLAB_STR:  th2_release

BUILDOSVER_STR:  10.0.10586.545

ANALYSIS_SESSION_ELAPSED_TIME: 685

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus

FAILURE_ID_HASH:  {6db180b1-fe77-439b-a001-507159592435}

Followup:     MachineOwner
---------

0: 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.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe00150244028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b8800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000020f0f, Low order 32-bits of the MCi_STATUS value.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.10586.545 (th2_release.160802-1857)

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

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

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

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

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  FD

BIOS_DATE:  02/26/2016

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  970A-DS3P

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

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe00150244028

BUGCHECK_P3: b8800000

BUGCHECK_P4: 20f0f

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:  nb3test.exe

CURRENT_IRQL:  f

ANALYSIS_SESSION_HOST:  DESKTOP-4HOAG0U

ANALYSIS_SESSION_TIME:  08-14-2016 21:47:01.0772

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

STACK_TEXT:  
fffff800`9ba4ea68 fffff800`99e3cf1f : 00000000`00000124 00000000`00000000 ffffe001`50244028 00000000`b8800000 : nt!KeBugCheckEx
fffff800`9ba4ea70 fffff800`9a08a8bc : ffffe001`50244028 ffffe001`50286cb0 ffffe001`50286cb0 ffffe001`50286cb0 : hal!HalBugCheckSystem+0xcf
fffff800`9ba4eab0 fffff800`99e3d40c : 00000000`00000728 00000000`00000000 fffff800`9ba4ee70 00000000`00000000 : nt!WheaReportHwError+0x258
fffff800`9ba4eb10 fffff800`99e3d764 : ffffe001`00000010 ffffe001`50286cb0 fffff800`9ba4ecb8 ffffe001`50286cb0 : hal!HalpMcaReportError+0x50
fffff800`9ba4ec60 fffff800`99e3d64e : ffffe001`502ca860 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe8
fffff800`9ba4ecb0 fffff800`99e3da19 : ffffe001`502ca860 fffff800`9ba4eef0 00000000`00000000 00001f80`00000f00 : hal!HalpMceHandler+0xda
fffff800`9ba4ecf0 fffff800`99fc647b : 00000000`00000000 00000000`0000002b 00000000`77bb6d3c ffffe001`546bd840 : hal!HalHandleMcheck+0x49
fffff800`9ba4ed20 fffff800`99fc6231 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff800`9ba4ee60 00000000`7740709d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
00000000`0060fe48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7740709d


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  5587b7eef3e5d1004cbe2a4ed5296100dcf38cda

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  2a486745d9a076c4f8eeb79914c2528efe771d13

THREAD_SHA1_HASH_MOD:  2199336a955b99afec8bfbbee3a384cfc1a11512

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS

PRIMARY_PROBLEM_CLASS:  0x124_AuthenticAMD_PROCESSOR_BUS

TARGET_TIME:  2016-08-14T22:53:30.000Z

OSBUILD:  10586

OSSERVICEPACK:  545

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-08-03 05:15:01

BUILDDATESTAMP_STR:  160802-1857

BUILDLAB_STR:  th2_release

BUILDOSVER_STR:  10.0.10586.545

ANALYSIS_SESSION_ELAPSED_TIME: 68b

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus

FAILURE_ID_HASH:  {6db180b1-fe77-439b-a001-507159592435}

Followup:     MachineOwner
---------

0: 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.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe00150244028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b8800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000020f0f, Low order 32-bits of the MCi_STATUS value.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.10586.545 (th2_release.160802-1857)

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

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

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

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

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  FD

BIOS_DATE:  02/26/2016

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  970A-DS3P

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

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe00150244028

BUGCHECK_P3: b8800000

BUGCHECK_P4: 20f0f

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:  nb3test.exe

CURRENT_IRQL:  f

ANALYSIS_SESSION_HOST:  DESKTOP-4HOAG0U

ANALYSIS_SESSION_TIME:  08-14-2016 21:47:32.0390

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

STACK_TEXT:  
fffff800`9ba4ea68 fffff800`99e3cf1f : 00000000`00000124 00000000`00000000 ffffe001`50244028 00000000`b8800000 : nt!KeBugCheckEx
fffff800`9ba4ea70 fffff800`9a08a8bc : ffffe001`50244028 ffffe001`50286cb0 ffffe001`50286cb0 ffffe001`50286cb0 : hal!HalBugCheckSystem+0xcf
fffff800`9ba4eab0 fffff800`99e3d40c : 00000000`00000728 00000000`00000000 fffff800`9ba4ee70 00000000`00000000 : nt!WheaReportHwError+0x258
fffff800`9ba4eb10 fffff800`99e3d764 : ffffe001`00000010 ffffe001`50286cb0 fffff800`9ba4ecb8 ffffe001`50286cb0 : hal!HalpMcaReportError+0x50
fffff800`9ba4ec60 fffff800`99e3d64e : ffffe001`502ca860 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe8
fffff800`9ba4ecb0 fffff800`99e3da19 : ffffe001`502ca860 fffff800`9ba4eef0 00000000`00000000 00001f80`00000f00 : hal!HalpMceHandler+0xda
fffff800`9ba4ecf0 fffff800`99fc647b : 00000000`00000000 00000000`0000002b 00000000`77bb6d3c ffffe001`546bd840 : hal!HalHandleMcheck+0x49
fffff800`9ba4ed20 fffff800`99fc6231 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff800`9ba4ee60 00000000`7740709d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
00000000`0060fe48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7740709d


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  5587b7eef3e5d1004cbe2a4ed5296100dcf38cda

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  2a486745d9a076c4f8eeb79914c2528efe771d13

THREAD_SHA1_HASH_MOD:  2199336a955b99afec8bfbbee3a384cfc1a11512

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS

PRIMARY_PROBLEM_CLASS:  0x124_AuthenticAMD_PROCESSOR_BUS

TARGET_TIME:  2016-08-14T22:53:30.000Z

OSBUILD:  10586

OSSERVICEPACK:  545

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-08-03 05:15:01

BUILDDATESTAMP_STR:  160802-1857

BUILDLAB_STR:  th2_release

BUILDOSVER_STR:  10.0.10586.545

ANALYSIS_SESSION_ELAPSED_TIME: 659

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus

FAILURE_ID_HASH:  {6db180b1-fe77-439b-a001-507159592435}

Followup:     MachineOwner
---------

Link to post
Share on other sites
Posted

repair the os and see if that works

if not reinstall it, if not then your MB might have a damaged ROM chip or it's got a root kit and is trying to do something

****SORRY FOR MY ENGLISH IT'S REALLY TERRIBLE*****

Been married to my wife for 3 years now! Yay!

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×