bsod - Locale ID: 2057, BCCode: 124

Toggle sidebar Toggle sidebar
P

Perrier9248

Reputable
Apr 9, 2015
5
0
4,510
I have been getting a bsod nearly everyday for the last 6 months and would like to find a fix as it is beginning to happen more frequently.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800891D7A8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\040915-31465-01.dmp
C:\Users\Me\AppData\Local\Temp\WER-67314-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
 
Sort by date Sort by votes
P

Perrier9248

Reputable
Apr 9, 2015
5
0
4,510
Hi, thanks for the quick answer.
I have downloaded and run WhoCrashed and got the following results -

On Thu 09/04/2015 19:20:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040915-22386-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4AF21C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80088243D8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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).
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.

Is it ntoskrnl.exe causing me to blue screen or a hardware issue?
thanks.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
ntoskrnl.exe is just the main portion of windows that device drivers talk to. Any bugcheck that point to the kernel will be caused by problems in the hardware or the driver for the hardware. You are unlikely to be hitting a new bug in ntoskrnl.exe.


-----------------
bugcheck 0x124 with parameter 1=0 is called by the CPU to shutdown the system because of a error detected inside of the CPU. Most often a error detected by the memory controller inside the CPU.

for the most part, it will not be caused by any driver unless it is a overclocking driver that is tweaking on hardware settings (voltages, clock rates)

to fix this you generally want to remove any overclocking software, reset your BIOS to defaults or update the BIOS if you can get a update.

you will be looking for something that will cause voltage fluctuations to the CPU or overheating.

if you just added a GPU, often if they pull more power than the PSU is rated for, it will causes the CPU power to drop too low and you will get memory problems or the CPU will reset.

The memory dump file is useful because you can look at the BIOS clock rates, the BIOS version dates, confirm your BIOS supports your CPU version, check or overclocking software, check how long the system was up.
(if the system uptime is less than 10 seconds, it means something different than if the system uptime is over 15 mins.)
also, you can use the memory .dmp file and the !errrec command to dump the reason the CPU shutdown the system.

anyway, put the .dmp file on a server and post a link and I will take a quick look.
 
Upvote 0 Downvote
P

Perrier9248

Reputable
Apr 9, 2015
5
0
4,510
Link to .dmp file - http://www.filedropper.com/040915-31465-01
system specs -
motherboard - gigabyte 78lmt ultra durable usb 3.0
graphics card - sapphire radeon r9 290 (added at christmas, but was getting bsod before)
Ram - 8gb
CPU - AMD fx6100 3.30 GHz
HDD - 1TB
OS - windows 7 home premium service pack 1 64bit
everything except from the graphics card is almost 3 years old.
thanks.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
your system was booted for 16 seconds
your system was shutdown by the CPU because of internal problem
with processor 0 trying to read from cache memory bank 4 and not getting a response
(CPU internal bus error)

most likely the system rebooted because of a power fluctuation to the CPU and you have a PSU that did not prevent the booting process via the power_ok signal so the CPU rebooted while the power was not stable.

I would be checking the power connections from the PSU to the graphics card and make sure they are properly connected and providing power.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
well then your power to your CPU dropped too low and you have to find out why.
if you were running a game or browser and you were using your system for more than 16 seconds. I would make sure i have no overclocking software installed. if that is the case, I would see about underclocking the GPU or trying a different power supply.

basically if the GPU does not get enough power it will attempt to pull too much power from the motherboard pci/e slot and the cpu voltage will drop too low and the CPU will reset. The power supply/motherboard are susposed to prevent the sytstem from powering back on until the power is ok but some skip the cost of adding the logic circuits.

oh, if you have your system on a cheap power strip you might want to connect directly to the wall. people have isolated this type of problem to power inputs to the power supply. (power strips, or plugged in to the same circuit where a motor get turned on. one guy had his machine reboot when his roommate fixed dinner. the motor of the fridge would turn on after he opened it up and it was on the same house circuit that was overloaded. Well, i thought it was funny)



 
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