Windows 10: BSOD - hal.dll+395cf & ntoskrnl.exe+16c310

Hello Guys, me . New to this forum.

I am getting this error for last weeks. My computers get constant BSOD whenever I try to run my PC.

Ram Checked : MemTest = Passed
HDD Checked : HDD Tune Pro Passed & Windows Terminal CHKDSK = Passed
PSU Checked : Brand New & checked with my brothers PC = Passed
BIOS Checked : Updated to latest version F10

Now running BlueScreenView on Safe Mode, since I can't run my PC in normal mode. It just constantly showed BSOD & restart.

*** In Safe mode, my Dual Core i3 shows 4 CORES :/

*** Since my CPU has stock cooler, I don't overclock it.

SystemInfo : http://www.filedropper.com/systeminfo_2
DxDiag : http://www.filedropper.com/dxdiag_9
Dump File : http://www.filedropper.com/060617-16406-01

:)

 

hal.dll+35f1f bsod error in Windows 10

OT- hal.dll+35f1f bsod

Hello,

There was a bsod just now, which is the first time I've experienced it - and should I be worrying about it?

This is what I got from BlueScreenView:

071816-24656-01.dmp

18/7/2016 8:23:23 PM

0x00000124

00000000`00000000

ffffe000`2db12028

00000000`b2000000

00000000`00100402

hal.dll

hal.dll+35f1f

x64

ntoskrnl.exe+142940

C:\WINDOWS\Minidump\071816-24656-01.dmp

What caused this? Thanks!

 

BSOD 0x00000133, ntoskrnl.exe+16c310

Hi experts,

I'm getting accidental BSODs with 0x00000133, ntoskrnl.exe+16c310 on my new laptop Lenovo Ideapad 510 with fresh Win 10 (with Creators Update).

Link to minidumps stored on my OneDrive -
minidumps

Could you please check what could be causing this?

Thank you!

 

Hi there,

Code: 0x00000124: WHEA_UNCORRECTABLE_ERROR (7.06.2017 08:16:50) [Windows 10] CAUSED BY: 0x124_GenuineIntel_PROCESSOR_MAE [18.07.1979] hal.dll (Hardware Abstraction Layer DLL. NO Driver) WHEA Notify: Machine Check Exception Type: Micro-Architectural Error Error: Unknown (Proc 3 Bank 2) PROCESS: System[/quote]


0x124



WHEA_UNCORRECTABLE_ERROR

A 0x124 is one of the worst STOP codes to encounter for the sole reason that the dump files usually give nothing away as to the cause of the problem. WHEA (Windows Hardware Error Architecture) errors signify a problem with hardware but very rarely pinpoint the culprit. In these scenarios it is advised to run a series of hardware stress and diagnostic tests to try and pinpoint the problem. A template is offered below which covers the four main components (GPU, CPU, RAM, HDD) and gives you a fighting chance of narrowing down the problematic device.

Generic "Stop 0x124" Troubleshooting Steps:

1) Ensure that none of the hardware components are overclocked. Overclocking means pushing the components beyond what they were designed for. If you do not know what that is you probably are not overclocking so go to the next step
2) Ensure that the machine is adequately cooled. If this is a laptop use compressed air to carefully blow out the heat pipe and fan when the computer is turned off. If a desktop take the side cover off and blow a fan on the components
3) Update all hardware-related drivers: video, sound, RAID (if any), etc. Do not rely on windows when it says the most recent driver is installed. It may be the most recent but it may also be corrupt.
4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS. Check with the computer maker for directions on this procedure and as usual it is always a good idea to back up your data.
5) Update ALL OS Windows updates
6) Stress test the major components. Start with RAM, CPU, HD, etc.
For RAM, use Memtest. Instructions for which can be found here.
Computers are extremely sensitive to problematic ram so any errors on memtest should be considered an issue and even a clear report for less than 8 passes can give a false negative.
For CPU use Prime95
For hard drives, use CHKDSK /F finds any problems on the drive(s), notably "bad sectors". You should also go to the HD maker and download and run their HD checking utility
7) Perform a "vanilla" (clean) re-installation of Windows: Install nothing that is not from the OS (not even Malware) until you have seen that the computer is not crashing in this state.
When the vanilla installation has run long enough that you are convinced it is OK, start installing updates and applications a few at a time, and wait until you are again convinced it is OK. If the crashes resume it is obviously the last group of installations that is the issue and remove them.
8) Re-seat all connectors, ram modules, etc. You can use the same can of compressed air to clean out the RAM DIMM sockets as much as possible.
Only attempt this if you are FULLY knowledgeable about the procedures.
9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.






Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.






Diagnostic Test

GPU TEST


Run FurMark - GPU Stress Test - Windows 10 Forums



Warning Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.






Diagnostic Test

CPU TEST


Run Prime95 - Stress Test Your CPU - Windows 10 Forums



Warning Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.






Diagnostic Test

HDD TEST


Run HDTune to check health and scan for errors.



Note It may take some time, but look for signs of any errors or failure.

You can also run a disk check using chkdsk. Refer to the tutorial for details of how to do this.

 

1. Run MemTest86+ on my 3 ram sticks. With 8+ passes found 0 error.
2. Run Prime95 for 2+ hours. 0 errors 75C max temperature.
3. Ensure that my CPU is non overclocked.
4. BIOS has been updated to F10 (latest)
5. Done ALL OS Windows updates.
6. Done all Drivers Update through windows updater
7. Performed a "vanilla" installation of Windows from offical webpage
8. Passed the Intel Processor Diagnostic Tool results

No BSOD after re-installtion of Windows, but when I tried to open AIDA64, it started giving me same errors *Sad
Since Prime95 shows me 0 error, I wish to try out AIDA, now i am in great peril. My both HDD (1TB Toshiba + 1TB WD Blue) giving me same BSOD (whea uncorrectable error)

Is there any way to check out Motherboard errors. I wants to make sure that main culprit maybe my Mobo (guessing)

 

System Info Here: http://www.filedropper.com/msinfo32_2
DxDiag :http://www.filedropper.com/dxdiag_10
Dump File Here:http://www.filedropper.com/060917-15218-01

 

The Ntoskrnl.exe BSOD error is commonly related to your RAM. So to fix this problem, you should able to check for your RAM problems by running Windows Memory Diagnostic.
Another way to test your RAM is using Memtest86+.
In addtional, you can also fix ntoskrnl.exe bsod, you may update your BIOS. Updating BIOS is an advanced method, however if you don’t make it properly, your PC will be permanently damaged, so be extra careful if you decide to perform this way.

 

Hi,
Where are you getting these file from?

Two computers? Please follow the BSOD up-load procedures on the forum...

BSOD - Posting Instructions

 

Sorry for late reply. Since PC is giving this error I got busy with my Laptop.

System Info Here: Free File Hosting - Online Storage; Upload Mp3, Videos, Music. Backup Files
DxDiag: http://www.filedropper.com/dxdiag_11
Dump File Here: Free File Hosting - Online Storage; Upload Mp3, Videos, Music. Backup Files

"1. Run MemTest86+ on my 3 ram sticks. With 8+ passes found 0 error.
2. Run Prime95 for 2+ hours. 0 errors 75C max temperature.
3. Ensured that my CPU is stock clocked.
4. BIOS has been updated to F10 (latest)
5. Done ALL OS Windows updates.
6. Done all Drivers Update only through windows updater
7. Performed a "vanilla" installation of Windows from offical webpage
8. Passed the Intel Processor Diagnostic Tool results"

 

Is there any news or did you fix the problem?

 

Please post an updated zip file: BSOD - Posting Instructions - Windows 10 Forums
If possible please post in English so that we can troubleshoot the logs.