Windows 10: BSOD - HP Envy hal.dll

I've had frequent BSODs for over 2.5 years spanning Windows 8, 8.1, and 10. Hardware diagnostics have showed no failures. The machine has been to repair 3 times with only the HDD replaced, which did not fix the problem. I have restored to factory settings at least 8 times with no joy. The errors can happen anytime, but most typically occur when the machine is left running unattended. In recently months the error is most often not visible and the machine has not rebooted but is sitting with a dark screen and the fans running hard. All drivers and software should be up-to-date and I've tried power setting changes, turning off notifications, and other minor fixes.

The latest HP Case Manager wants me to restore to Win8 and test for several weeks so I thought I'd try again.

My DM Log file is attached.

Thanks!

Nick

:)

 

Windows 10 BSOD

HP Envy h8-1450. Updated to Build 10586. Now getting BSOD, but only on my primary admin account.

BlueScreen view seems to implicate hal.dll and/or ntoskrnl.exe

Tried rolling back with no luck. Also, nothing found with SFC scan.

Thanks in advace,

Jeremy

 

bluescreen of death (BSOD) Stop error code 0x000000C5 (DRIVER_CORRUPTED_EXPOOL), which was caused by driver/software related

HP performed a hardware test and no hardware problems found. Brand new HP Envy desktop less than 30 days old. It continued to have BSOD and HP performed a factory re-set. PC still having BSOD issues. Any suggestions?

 

The first zip file was empty. Here is the complete one.

 

The 0x124 are hardware crashes, it can be said that you have a faulty component in your laptop which can't be easily replaced. I suspect it is the CPU given there are several internal timer errors on different cores of the CPU.
It would be better to either let it be replaced if you're still under warranty? or get a new laptop.
Code: =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe0017d669138 Section @ ffffe0017d6692c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 5 Bank 4) Status : 0xbe00000000800400 Address : 0x00007ffb3e29ee2b Misc. : 0x00007ffb3e29ee2b =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe00112868138 Section @ ffffe001128682c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 2 Bank 4) Status : 0xbe00000000800400 Address : 0x00007ffbe6f8e90f Misc. : 0x00007ffbe6f8e90f =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe0001de64138 Section @ ffffe0001de642c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 3 Bank 4) Status : 0xbe00000000800400 Address : 0x00007ffd3c46ff71 Misc. : 0x00007ffd3c46ff71 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe0004f01f138 Section @ ffffe0004f01f2c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 6 Bank 4) Status : 0xbe00000000800400 Address : 0xfffff803c366b2fa Misc. : 0xfffff803c366b2fa =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe0003b689138 Section @ ffffe0003b6892c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 5 Bank 4) Status : 0xbe00000000800400 Address : 0xfffff801eac7abee Misc. : 0xfffff801eac7abee =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe00165864138 Section @ ffffe001658642c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 3 Bank 4) Status : 0xbe00000000800400 Address : 0x0000000014630f61 Misc. : 0x0000000014630f61 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe001f1a89138 Section @ ffffe001f1a892c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 7 Bank 4) Status : 0xbe00000000800400 Address : 0xfffff803f39d2f54 Misc. : 0xfffff803f39d2f54 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe0014fa68138 Section @ ffffe0014fa682c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 4 Bank 4) Status : 0xbe00000000800400 Address : 0x00007ffdd432e909 Misc. : 0x00007ffdd432e909[/quote]

 

Thanks, axe0. I sent your findings to my case manager on the HP Escalations Team. He does not recognize your expertise and continues to insist that I restore my machine to Windows 8 and run it with no software installed until I get the BSOD again. This is the same run around I've gotten from HP support all along. I'm not sure I'll have the time before my warranty expires.

Can you recommend a computer brand that runs windows 8/10 well and has good support?

 

Hi nack34,

After you've tried it over and over again he keeps saying the same thing?

Unfortunately I cannot specify a computer brand which support is proper with a system capable of running Windows 8/10, mainly the support experience is different for many due to the different people helping others.
For computer brands I would recommend Toshiba, but I can't say anything about their support because I rarely had ever required customer support in general.