Windows 10 Computer crashes during gaming

mlow25

New Member
My computer keeps restarting while playing video games, but not while browsing Chrome or other applications. I've been monitoring temperatures while running Heaven Benchmark at high settings, and the CPU doesn't get hotter than low 70's, and the GPU doesn't get higher than mid 60's. I've updated my bios and drivers, and I've tried 2 different PSUs.

The most recent crash gave me this in the event viewer:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff81831d753028, 0x00000000bc000800, 0x0000000001010135).
 

ussnorway

Windows Forum Team
Staff member
Premium Supporter
Bugcheck translate as hardware so a losse cable, faultly disc, overclocking etc... it normally isn't just a driver issue unless the software is for some other type of device
 

mlow25

New Member
Bugcheck translate as hardware so a losse cable, faultly disc, overclocking etc... it normally isn't just a driver issue unless the software is for some other type of device
Since my computer only restarts while playing video games (Valorant, Hitman, etc), would it be possible for the issue to be a CPU issue as well? I've never overclocked, and I don't see any loose cables.
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff81831d753028, 0x00000000bc000800, 0x0000000001010135)
Bugcheck 124 can relate to overheating issues especially when gaming. Monitior your temps using something like HWiNFO64 and if need be clear out any dust.
 

Druker

Honorable Member
My computer keeps restarting while playing video games, but not while browsing Chrome or other applications. I've been monitoring temperatures while running Heaven Benchmark at high settings, and the CPU doesn't get hotter than low 70's, and the GPU doesn't get higher than mid 60's. I've updated my bios and drivers, and I've tried 2 different PSUs.

The most recent crash gave me this in the event viewer:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff81831d753028, 0x00000000bc000800, 0x0000000001010135).

Have you noticed any plumes of green smoke ascending out through the exhaust ports on your laptop? I ask that because the next door neighbor who lives about 300 miles from here reported this although I'm not sure what he was doing to have the cpu get that hot.
 

mlow25

New Member
Have you noticed any plumes of green smoke ascending out through the exhaust ports on your laptop? I ask that because the next door neighbor who lives about 300 miles from here reported this although I'm not sure what he was doing to have the cpu get that hot.
No smoke from my desktop
 

mlow25

New Member
If you can post the actual dump file that would be great.
My computer restarted again today, and I have the dump file, but unsure how to send it here. I copied and pasted all the text it showed me. I don't believe im overheating because neither GPU or CPU temps go over low 70's under load.

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


Loading Dump File [C:\Windows\Minidump\080922-10984-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 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff807`79000000 PsLoadedModuleList = 0xfffff807`79c2a330
Debug session time: Tue Aug 9 13:45:46.071 2022 (UTC - 7:00)
System Uptime: 0 days 5:49:03.659
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`793f88b0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffc980`c659c940=????????????????
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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff81831d753028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000bc000800, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000001010135, 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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2234

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3967

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x124

Key : Bugcheck.Code.Register
Value: 0x124

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1


FILE_IN_CAB: 080922-10984-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff81831d753028

BUGCHECK_P3: bc000800

BUGCHECK_P4: 1010135

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VALORANT-Win64

STACK_TEXT:
ffffc980`c659c938 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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

kemical

Windows Forum Admin
Staff member
Premium Supporter
Thanks but really need the actual dump file, can you post to a file sharing site and post the link?

Try running these scans in meantime:

Open an admin command prompt or windows terminal, type:

sfc /scannow

press enter

After the above scan has finished type:

dism /online /cleanup-image /restorehealth

press enter.
 

mlow25

New Member
Thanks but really need the actual dump file, can you post to a file sharing site and post the link?

Try running these scans in meantime:

Open an admin command prompt or windows terminal, type:

sfc /scannow

press enter

After the above scan has finished type:

dism /online /cleanup-image /restorehealth

press enter.
I ran both of the scans to nothing new, and I uploaded one of my dumps to onedrive.

My computer also has crashed once more since then, and I got these 2 errors in the event viewer this time.

1.
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Bus/Interconnect Error
Processor APIC ID: 10

The details view of this entry contains further information.

2. The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffcd074b628028, 0x00000000bc800800, 0x00000000060c0859). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: bfb409c6-ead3-4bcd-a525-85d3182e3cef.

Here is the dump file for this second crash: 081222-10343-01.dmp
 
Last edited:

Jhonny0

New Member
If you're getting crashes during high-end gaming, you have several options. Games running on your system are more demanding than ever before, and the requirements are high. Most newer games require 1GB of RAM and a dual-core CPU. You've got to have a decent graphics card, too, but that's not all. When it comes to gaming, your computer is only as good as the PSU (power supply unit) that supplies it with power. If you're running a 1GB system, a 400W PSU is just not going to cut it. The computer is not just a processor, and it's hard to get a cheap PSU that will power your system and not overheat. and also check out my blog Apksvilla
 

mlow25

New Member
If you're getting crashes during high-end gaming, you have several options. Games running on your system are more demanding than ever before, and the requirements are high. Most newer games require 1GB of RAM and a dual-core CPU. You've got to have a decent graphics card, too, but that's not all. When it comes to gaming, your computer is only as good as the PSU (power supply unit) that supplies it with power. If you're running a 1GB system, a 400W PSU is just not going to cut it. The computer is not just a processor, and it's hard to get a cheap PSU that will power your system and not overheat. and also check out my blog Apksvilla
Its not only high end games that crash, which is the strange part. I've played lots of Cities: Skylines without issues, but csgo causes restarts every once and a while, and I would assume Cities Skylines is more demanding than cs
 
Top