Help Random Rebooting BSOD (124)

Toggle sidebar Toggle sidebar
F

FullAnarchy

Reputable
May 17, 2015
3
0
4,510
Hello and first off thanks for any help. I've been having this problem now for about 2 months. My computer no matter what I'm doing Netflix ,gaming ,idle anything it just randomly crashes.Though I just made this desktop 2 months ago with all new pieces. I've tried so many things. Fresh install,dust cleaning,updating windows which most recently slowed down my computer, updated bios, all drivers updated(Mostly), took everything out and put it back together. i have very many dumps to upload. Any Help is greatly appreciated :)

Specs-
Motherboard-GA-78LMT-USB3 (rev. 6.0)
Processor-AMD FX 6300 six-core processor 3.50 GHz
Graphics-PowerColor PCS+ AMD Radeon R9 290 4GB GDDR5
Memory(Ram)-G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3
Psu-Antec TruePower Classic series TP-750C 750W ATX12V
SSD-Intel 730 Series SSDSC2BP240G4R5 2.5" 240GB

Dumps-
Crash dump file: C:\Windows\Minidump\051615-25365-01.dmp
Date/time: 5/17/2015 3:50:12 AM GMT
Uptime: 00:00:10
Machine: FULLANARCHY-PC
Bug check name: WHEA_UNCORRECTABLE_ERROR
Bug check code: 0x124
Bug check parm 1: 0x0
Bug check parm 2: 0xFFFFFA80089648F8
Bug check parm 3: 0x0
Bug check parm 4: 0x0
Probably caused by: ntkrnlmp.exe
Driver description:
Driver product:
Driver company:
OS build: Built by: 7601.18839.amd64fre.win7sp1_gdr.150427-0707
Architecture: x64 (64 bit)
CPU count: 6
Page size: 4096

Bug check description:
This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

Comments:
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Kernal Stack-

nt!WheapCreateLiveTriageDump+0x6C
nt!WheapCreateTriageDumpFromPreviousSession+0x49
nt!WheapProcessWorkQueueItem+0x57
nt!WheapWorkQueueWorkerRoutine+0x25
nt!ExpWorkerThread+0x111
nt!PspSystemThreadStartup+0x5A
nt!KxStartSystemThread+0x16
 
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
if you have the windows debugger installed you can run the command
!errrec 0xFFFFFA80089648F8
and it will dump the reason the CPU shutdown the system.

also the debug session stats will have a System Uptime
in general for this type of error if it is a small uptime (less than 15 seconds) it mean your system rebooted because of a power fluctuation to the CPU and the power was not stable when the CPU restarted.

with a longer uptime, you are more likely looking at a overheating problem.
(in general) in that case you check the fan, stop any overclocking of the CPU and GPU, increase cooling, blow out dust, ...




 
Upvote 0 Downvote
F

FullAnarchy

Reputable
May 17, 2015
3
0
4,510
I already cleared dust and when I enter that command it says
===============================================================================
Common Platform Error Record @ fffffa80089648f8
-------------------------------------------------------------------------------
Signature : *** INVALID ***
Revision : 0.0
Record Id : 0000000000000000
Severity : Recoverable (0)
Length : 0
Creator : {00000002-0000-0000-90a7-e8d7fe070000}
Notify Type : {00000002-0000-0000-90a7-e8d7fe070000}
Flags : 0x00000000
but besides that I monitor temps. 32.9 max right now while playing diablo 3 so I doubt its heat any other ideas? :(
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
strange result. you can put the memory dump on a server and post a link and I can check it with my debugger and tools.
bugcheck 0x124 is a panic shutdown and sometimes it might stop the CPU before the files are written. When that happens you are lucky to get useful info.



 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom