Windows 10: Windows 10 x64 hal.dll+3587f

Hi, I own a HP 15-ab034tx Laptop which had Windows 8.1 pre-installed. I upgraded it to Windows 10 using an ISO (Upgrade not a clean install). It used to crash and show different BSOD , most of them were WHEA_UNCORRECTABLE_ERROR.

I decided to do a Clean Install and after that installed all drivers from the HP Drivers website.
It worked nicely that day, but the next day it crashed twice while starting up but the third time booted nicely.

BlueScreen View showed it was caused by hal.dll+3587f.

Please help me in solving this issue.

Here is the zip file asked in the tutorial.
Attachment 54351
DESKTOP-F8M4HAL-Sat_12_19_2015_161755_19.zip - Google Drive

:)

 

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 caused by hal.dll and ntoskernal.exe

Just today I received two BSODs, both were caused by hal.dll and ntoskernal.exe, and BlueScreenViewer showed these crash logs. The first apparently happened this morning when i wasn't using it, and the second while i was in the middle
of a game.

123016-18656-01.dmp

12/30/2016 1:16:47 AM

IRQL_NOT_LESS_OR_EQUAL

0x0000000a

ffffa58a`9f72c000

00000000`000000ff

00000000`000000a6

fffff803`37c50768

hal.dll

hal.dll+1aaa8

Hardware Abstraction Layer DLL

Microsoft® Windows® Operating System

Microsoft Corporation

10.0.14393.206 (rs1_release.160915-0644)

x64

hal.dll hal.dll+1aaa8 fffff80337812000 fffff80337887000 0x00075000 0x57dac91a 9/15/2016 11:15:22 AM Microsoft® Windows® Operating System Hardware Abstraction Layer DLL 10.0.14393.206 (rs1_release.160915-0644) Microsoft
Corporation C:\Windows\system32\hal.dll

ntoskrnl.exe ntoskrnl.exe+155829 fffff80337887000 fffff803380a7000 0x00820000 0x584a77f6 12/9/2016 4:23:02 AM Microsoft® Windows® Operating System NT Kernel & System 10.0.14393.576 (rs1_release_inmarket.161208-2252) Microsoft
Corporation C:\Windows\system32\ntoskrnl.exe

123016-16359-01.dmp

12/30/2016 11:39:41 AM

PFN_LIST_CORRUPT

0x0000004e

00000000`00000002

00000000`0003f063

00000000`0022efff

00000000`00000001

hal.dll

hal.dll+2277

Hardware Abstraction Layer DLL

Microsoft® Windows® Operating System

Microsoft Corporation

10.0.14393.206 (rs1_release.160915-0644)

x64 ntoskrnl.exe+14a6f0 C:\Windows\Minidump\123016-16359-01.dmp

hal.dll hal.dll+2277 fffff80388233000 fffff803882a8000 0x00075000 0x57dac91a 9/15/2016 11:15:22 AM Microsoft® Windows® Operating System Hardware Abstraction Layer DLL 10.0.14393.206 (rs1_release.160915-0644) Microsoft Corporation
C:\Windows\system32\hal.dll

ntoskrnl.exe ntoskrnl.exe+1a6a11 fffff80387a13000 fffff80388233000 0x00820000 0x584a77f6 12/9/2016 4:23:02 AM Microsoft® Windows® Operating System NT Kernel & System 10.0.14393.576 (rs1_release_inmarket.161208-2252) Microsoft
Corporation C:\Windows\system32\ntoskrnl.exe

My specs are:

CPU: AMD FX(tm)-6300 Six Core Processor 3.50GZ

RAM: Ares 2x4gb DDR3 RAM sticks

GPU: Radeon R9 200 Series

HDD: Seagate Barracuda ST100dM003 1TB

MOTHERBOARD: Gigabyte 78LMT-USB3 Socket AM3

BIOS: Award Modular BIOS v6.00PG

PSU: EVGA 500W Bronze

OS: Microsoft Windows 10 (build 14393), 64-bit

I think I have all the latest drivers, but could it be a hardware problem? I've had troubles in the past with my build and had to get a replacement hard drive, as well as reinstall Windows 10 many times. The most recent one was back
in August, I reinstalled windows 10 form a USB drive and installed all the drivers form the disks my parts came with, I had also had computer get just an empty red screen, as well as completely freeze up while playing two separate games but they seemed to
have stopped after i updated my graphics driver. Also please point out any formatting issues with my post, and any help would be appreciated, thanks.

 

Hi haiderali,

Please upload a new zip file, the zip files are empty

 

I am sorry for that. I have updated the links.
Thank You

 

There are 2 things you need to do.
1. Visit Windows Update and install every update, but watch out with drivers as they may give trouble when the drivers are coming from more then 1 source.
2. Remove every bypass/crack and related software on your system, we can't proceed until this has been done per the forum rules.

Forum rules

 

I uninstalled the KMS Service, and I am downloading the few updates.

I would like to point out that before Clean Installing, the previous Windows 10 had all of these updates installed.

 

You clean installed because you thought it would fix the bluescreens or had you done an upgrade?

 

As I said before, my laptop had Windows 8.1, but it used to crash a lot. I upgraded to Windows 10, to solve the BSODs, although the frequency was reduced, it still used to crash. It had all latest Windows Updates Installed.

I did a Clean Install to solve the BSODs, as i thought the corrupted stuff had carried during the upgrade. The Clean Install reduced the BSODs greatly. No BSOD on the day of install, and only two on startup on the next day morning. No BSOD till evening.

 

Alright, I might not have read everything proper, thanks for making it more clear *Smile

Let me know how it goes after the updates have been installed.

 

So, I have installed all Windows Updates, except for 1 which Upgrades my OS To Fall Build. It is too big to download and has downloaded 10% till now.

Also, my laptop crashed thrice today after the updates were installed yesterday.
One of them was caused by ntoskrnl.exe
And the other two were by hal.dll

Here is the DM Log Collector File:
Attachment 54969

 

Code: <ActivePartialProductKey>T83GX</ActivePartialProductKey> <ActiveProductKeyPid2>00331-10000-00001-AA941</ActiveProductKeyPid2> <OSVersion>10.0.10240.2.00010100.0.0.048</OSVersion> <ProductName>Windows 10 Pro</ProductName> <ProcessorArchitecture>x64</ProcessorArchitecture> <EditionId>Professional</EditionId> <BuildLab>10240.th1_st1.151104-1714</BuildLab> <TimeZone>India Standard Time(GMT+05:30)</TimeZone> <ActiveSkuId>2de67392-b7a7-462a-b1ca-108dd189f588</ActiveSkuId> <ActiveSkuDescription>Windows(R) Operating System, VOLUME_KMSCLIENT channel</ActiveSkuDescription> <ProductUniquenessGroups>55c92734-d682-4d71-983e-d6ec3f16059f</ProductUniquenessGroups> <ActiveProductKeyPKeyId>08e404fb-41f3-77ac-59ef-6e9f2d3f499d</ActiveProductKeyPKeyId> <ActiveProductKeyPidEx>03612-03311-000-000001-03-16393-10240.0000-3532015</ActiveProductKeyPidEx> <ActiveProductKeyChannel>Volume:GVLK</ActiveProductKeyChannel> <ActiveVolumeCustomerPid>55041-00168-310-229975-03-1033-7601.0000-2142015</ActiveVolumeCustomerPid> <OfflineInstallationId>678168392406557614226342648362279943920026588633107972507355842</OfflineInstallationId> <DomainJoined>false</DomainJoined>[/quote] Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.

Forum rules

We don't give support to piracy, that is the point!