BSOD BCCode 124, Mini dump access, WinSDK issue

Toggle sidebar Toggle sidebar
R

RAZZCAZZ

Honorable
Dec 12, 2013
6
0
10,510
Specs:

CPU: Intel Core I7
Motherboard: ASUS Z87
Video Card: EVGA GeForce GTX 770
RAM: Corsair Vengeance 16GB
SSD: Samsung 840 Pro Series 128GB
HDD: Seagate Barracuda 1 TB
Windows 7 Premium 64bit

Built my first computer. I am a noob.
I received a BSOD, with a following BCCode 124 message. I would like to investigate the issue by looking at my minidump files. Windows cannot open the files, and the Minidump folder has a lock on it (which now has been removed by adding rights to the folder) yet access is denied when trying to view on notepad or through other minuscule means. It has been recommended to download the Windows SDK for Windows 7. I download from the windows xp link because the other links are Windows 8 and other junk links. After i download the Windows 7 SDK .exe and open it, I only select the Debug toolkit to use in reading my minidump files. When I try to install I receive an Error Install message.

If I can only access my minidump files and read what the possible issue is that is causing the BSOD then I would also like to post it here for more personal input. Thank you!
 
Sort by date Sort by votes
neieus

neieus

Distinguished
Dec 29, 2011
1,776
0
20,460
I believe you're on the right track by downloading the Windows SDK since that should contain the windows debugger to view crash dumps but there are also apps like whocrashed and others that can do the same thing. I personally use Windows debugger but even after you install it you have to configure the debugger to download the symbols.
 
Upvote 0 Downvote
R

RAZZCAZZ

Honorable
Dec 12, 2013
6
0
10,510



I wonder why I keep receiving an Error message when trying to install SDK.
Would you prefer that I try "whocrashed" instead?
 
Upvote 0 Downvote
R

RAZZCAZZ

Honorable
Dec 12, 2013
6
0
10,510


I have downloaded who crashed. This is the report I was provided:

On Sat 11/16/2013 7:14:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111613-22354-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800FB9A028, 0xBF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

I have bolded the significant factors I see in this report.
Any recommendations would very helpful. The more I learn about computers and fixing my problem, the more fulfilled I am!
 
Upvote 0 Downvote
R

RAZZCAZZ

Honorable
Dec 12, 2013
6
0
10,510
I am also using a Z87 motherboard that has the new AI suite for easier BIOS management. In regards to my hal.dll error being a possible cause of my BSOD, I read that some recommendations were to change the voltage output to my CPU. As a noob, I don;t exactly what good voltage, CPU frequency, and heat numbers are. Also, the AI suite poses as another issue due to navigation and finding what I'm looking for if I were to change my voltage output.
 
Upvote 0 Downvote
R

RAZZCAZZ

Honorable
Dec 12, 2013
6
0
10,510


I see a lot of WMI, Kernel-Event Tracing, and Kernel PnP, .net runtime error, and cap12 on the event log. Is there something specific I should be looking for and would it be helpful I ctrl+v the info provided in my event log?
 
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