Hello, I am having a very frustrating issue with my HP 800-060 Phoenix Desktop. I purchased the unit new last year from HP Direct. It came with Windows 8 installed and I ran Windows 8 without issue. After having the computer for a little while, I upgraded to Windows 8.1 after it was released. All the sudden, I started receiving BSOD's stating that hal.dll and ntoskrnl.exe where the causes. I went through a nightmare with HP tech support trying to resolve the issue and was unsuccessful in doing so. I completed a fresh install of Windows 8 and used the computer without ANY issues for some time. I thought maybe the last installation of 8.1 was corrupt so I decided to try 8.1 again, WHEA BSOD after BSOD over and over again. Ran stress test after stress test and even replaced a few hardware components like the PSU and the hard drive, still, no luck with 8.1. Rolled back to Windows 8 again and used the computer WITHOUT ANY ISSUES for nearly a year. Recently, I found that a BIOS update was released and updated it. Thinking that it may help 8.1 run on my machine and attempted the upgrade 1 more time. No go, WHEA BSOD numerous times over and over again. The way I am thinking, this cannot be a hardware problem because I can run Windows 8 for an extended period of time and not have 1 issue. As soon as I put 8.1 on this machine, noting but BSOD's pointing to hal.dll, and ntoskrnl.exe. This is getting old, i'm tired of re-installing the OS over and over again. I have no issue running Windows 8 but I would prefer to run 8.1. Can anybody tell me what is going on here? Some things I have noticed are that 8.1 will run fine for a couple of days upon a fresh install. After the first BSOD, it’s all downhill from there and they start happening sporadically, sometimes 5-10 a day. I have also noticed that they tend to happen when watching or doing anything video extensive which would lead me to believe that it’s the video card or driver but why is nothing happening running the Windows 8 OS, only the 8.1 OS. HP Tech Support gave up on me, $1000+ desktop, they refuse to help me anymore stating that nothing is wrong and request that I keep using Windows 8 without upgrading to 8.1.
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 4/24/2015 9:40:09 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042415-52984-01.dmp
This was probably caused by the following module: hal.dll (hal+0x37213)
Bugcheck code: 0x124 (0x0, 0xFFFFE00096007028, 0xF2000000, 0x10005)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 4/24/2015 9:40:09 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042415-52984-01.dmp
This was probably caused by the following module: hal.dll (hal+0x37213)
Bugcheck code: 0x124 (0x0, 0xFFFFE00096007028, 0xF2000000, 0x10005)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.