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

Hi haiderali,

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

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

4) No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc).

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

Alright, I might not have read everything proper, thanks for making it more clear :)

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

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>

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

4) No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc).

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