BSOD code 0x133 caused by hal.dll & ntsokrnl.exe

axe0 said:

Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

As expected, I got the following message:

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

I've uploaded the file to my G Drive, please check it here. Also to add, restarting time was still around 10-15 minutes.
Thanks again.

axe0 said:

The file opencl.dll and the source are corrupted.

Code:

2015-11-26 17:06:35, Info                  CSI    000058b1 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-26 17:06:35, Info                  CSI    000058b2 [SR] This component was referenced by [l:258{129}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10240.16384.RemoteFX clientVM and UMTS files and regkeys"
2015-11-26 17:06:35, Info                  CSI    000058b3 Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
  Found: {l:32 b:49za8C5TRgSaDSUdC64s2a49uEKeT5hcOPrm/k5k1Lk=} Expected: {l:32 b:3nQy34XEqrcTm+le3PyhNMbyrGuxiT2D5+L7RJQKKgM=}
2015-11-26 17:06:35, Info                  CSI    000058b4 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10240.16384_none_b928dea146e73395\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
  Found: {l:32 b:49za8C5TRgSaDSUdC64s2a49uEKeT5hcOPrm/k5k1Lk=} Expected: {l:32 b:3nQy34XEqrcTm+le3PyhNMbyrGuxiT2D5+L7RJQKKgM=}
2015-11-26 17:06:35, Info                  CSI    000058b5 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted

Please try following command in admin command prompt

Code:

DISM /Online /Cleanup-Image /RestoreHealth

If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial

Tried 'DISM' and it failed for the first time; however, fixed it and the restoration was successful. I wonder, is there any way to make sure that the "OpenCL.dll" is fixed/or the other errors, if any?

axe0 said:

DISM is used to restore SFC.

Please run sfc/scannow in admin command prompt, reboot and run sfc/scannow again.

Gotcha! On it

axe0 said:

DISM is used to restore SFC.

Please run sfc/scannow in admin command prompt, reboot and run sfc/scannow again.

Ran the scan multiple times over a period of 2 days and always it said "Windows Resource Protection did not find any integrity violations."

So I hope that means everything is perfect? However, I've done nothing related to opencl.dll personally, is there anything I need to worry about? And BTW, the restart time is still around 4-5 minutes.

axe0 said:

DISM restored SFC, SFC restored the opencl.dll corruption.
You don't have to do anything more :)

To find out what is taking so long, we need a log of what is happening

• Search "msconfig" (without quotes) and press enter,
• go to the boot tab
• enable 'boot log'
• click ok > apply
• reboot when asked

The boot log file should be located at {windows partition}\Windows\, but I'm not sure exactly what it is called.

I apologize for a late reply. Anyway, I enabled Boot log and I'm attaching the same here. Let me know.