Identified cause of BSOD 124

Pages (2): 1 2 Next

Woody_JuX
Member

130

03-22-2023, 10:05 PM

I’ve identified the main culprits behind my annoying BSODs—primarily ntoskrnl.exe and hal.dll. I’ve attached some images so you can see what I found. Let me know if you need more details. Thanks ahead!

Woody_JuX

03-22-2023, 10:05 PM #1

_Geqr_
Senior Member

554

04-05-2023, 03:57 AM

Check if the operating system is damaged. Was a fresh installation performed?

_Geqr_

04-05-2023, 03:57 AM #2

Check if the operating system is damaged. Was a fresh installation performed?

cjtheman94
Junior Member

04-06-2023, 07:10 AM

I've installed Windows 7 three times on this disk recently... That's quite a few times already!

cjtheman94

04-06-2023, 07:10 AM #3

I've installed Windows 7 three times on this disk recently... That's quite a few times already!

soul_harveste
Member

223

04-06-2023, 01:20 PM

It seems like you're wondering if a memory issue might be causing this problem.

soul_harveste

04-06-2023, 01:20 PM #4

It seems like you're wondering if a memory issue might be causing this problem.

TxCommand
Member

169

04-06-2023, 03:22 PM

Unreal, this recollection is quite old—it was part of an earlier version and didn’t cause any issues.

TxCommand

04-06-2023, 03:22 PM #5

Unreal, this recollection is quite old—it was part of an earlier version and didn’t cause any issues.

Cokkie77
Senior Member

556

04-07-2023, 03:29 AM

Recall abilities may become less accurate as time passes... it's not always about immediate failure.

Cokkie77

04-07-2023, 03:29 AM #6

Recall abilities may become less accurate as time passes... it's not always about immediate failure.

WildCandy
Senior Member

675

04-13-2023, 10:08 PM

Did you test MemTest? Run it to confirm. My RAM performed flawlessly across multiple builds, but one stick stopped working suddenly and only realized the issue during a MemTest.

WildCandy

04-13-2023, 10:08 PM #7

Did you test MemTest? Run it to confirm. My RAM performed flawlessly across multiple builds, but one stick stopped working suddenly and only realized the issue during a MemTest.

SirrKarma
Junior Member

04-14-2023, 07:30 PM

I tested my system with MemTest and everything worked well.

SirrKarma

04-14-2023, 07:30 PM #8

I tested my system with MemTest and everything worked well.

Bayan9
Member

158

04-15-2023, 12:39 PM

I believe I've identified the cause! Looking at the times shown in the photos I shared, it usually occurs around the same time each morning. My PC is configured to wake up at 6:00 a.m. and enter sleep mode three hours after inactivity. I go to school without using it until I return home. If the PC remains asleep all day, then there should be no problems.

Bayan9

04-15-2023, 12:39 PM #9

jamdonut
Junior Member

04-15-2023, 01:57 PM

#10

Log Name: Origin: Microsoft-Windows-WHEA-Logger Date: 1/27/2017 6:18:42 AM Event ID: 18 Category: None Level: Error Keywords: User: LOCAL SERVICE Machine Check Exception Description: Fatal hardware issue Detailed Info: The record shows a critical processor error. Caused by component: Processor Core Error Source: Machine Check Exception Error Type: Cache Hierarchy Error Processor ID: 2 Additional data available in the full view. Event XML contains structured details including system version, event type, and technical parameters. Event Record ID: 16270

jamdonut

04-15-2023, 01:57 PM #10

Pages (2): 1 2 Next