Over the past month my Windows 10 has had 4 blue screens during which MS gathers and reports error codes. This process happens so fast I do not have time to read and record myself. Here is the data gathered after implementing the BSLOD Posting Instructions.
Uploadfiles.io - DESKTOP-N9L0O68-Fri_09_29_2017_225606_35.zip
Thanks
Last edited by lpatrick; 29 Sep 2017 at 23:15.
Hello,
All the crashes have been triggered by 0x124 errors which are usually indicative of a hardware problem. The usual procedure is to begin testing all your hardware with diagnostic tests to see if you can identify anything that is not functioning correctly. Before you do that I would also advise you to update your bios as this can sort out some BSOD issues related to hardware. If that does not help continue with the tests and report back the results.
https://support.hp.com/ie-en/drivers...29?sku=N0A87AA
Warning
If you're overclocking your system, revert back to stock clocks now.
Note
Test the system once the overclock is removed before continuing with the steps outlined below.
Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test
Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums
Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.
MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
- check the health,
- scan for errors, no quick scan but full scan
- run a benchmark.
It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
- the health,
- the error scan,
- the benchmark incl. following
- transfer rate,
- access time,
- burst rate,
- cpu usage.
Run Furmark for around 30 minutes.
Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.
Thank you for the thorough information. Truthfully, I am not confident in my ability to adequately run the specified tests and to ensure there is no overheating. With that said, I believe it best for me to have a professional repair person evaluate and if necessary repair? What should I tell them up front?
Hi Ipatrick,
Over the years, the only test that is difficult to use is MemTest86+, but only from time to time, because of booting problems where a few configurations need to be changed which we'll guide you through.
Please try to follow the instructions, if you have any questions about the test or instructions, please ask them beforehand :)
The computer manufacturer HP also has UEFI diagnostics.
Most computer manufacturers do not have the on board diagnostics.
Before servicing any computers they have you run these preliminary UEFI diagnostic tests.
They have some of the diagnostic already installed in the bios (memory, drive). But the full HP diagnostic tests are available from the HP link that philc43 inserted in post #2 (expand diagnostic and download and install hardware diagnostic version 6.4
This HP diagnostic can also be installed on a bootable flash drive using this source: HP PC Hardware Diagnostics | HP® Official Site
When running the HP diagnostics they are designed to abort testing when there is a fail. The earlier the test in the sequence of testing the more likely it it to abort the testing. So a battery failure will prevent all of the other testing.
So I would encourage you to go thorough the testing outlined by philc43 as they will provide more extensive testing of the hardware. At a minimum you can run the UEFI diagnostics overnight in the loop until failure mode. In the morning you will want to see at least 1 - 2 loops and if you see it still testing that is a good sign. Then click the keyboard escape key to abort the testing. View the logs to confirm the results. If there is a failure there will be a failure code that only HP can decipher.
As axe0 commented we can guide you through the component testing. Once you have all of the testing results you will better be able to make informed decisions about the computer. While the WHEA 0x124 is highly indicative of hardware problems there have been computers fixed by only finding software problems.
Last edited by zbook; 30 Sep 2017 at 18:43.
Thank you. I will carefully consider my next course of action.
Last edited by lpatrick; 30 Sep 2017 at 22:21.
WHEA 0x124 bugcheck can be caused by hardware, and hardware and software drivers but are most likely hardware.
So a methodical way is needed in the troubleshooting.
The bios is usually updated first.
Every update is different so the contents of the update would have to be read and evaluated to see what impact it could have.
The work up of WHEA is to update the bios, evaluate the drive and RAM/DIMM/Motherboard, and then stress test the CPU and GPU. The PSU will also be evaluated.
Usually when all of the above steps are completed the information indicates which hardware devices are ruled out and which ones still need troubleshooting and which component is the problematic. Once you know the problematic component you then can better make decisions about what can be repaired and what needs replacement.
Were you able to download and install the HP UEFI diagnostics?
Can you run them overnight with loop until failure and post the results into the thread.
Again the HP UEFI diagnostic studies can be downloaded either from the HP drivers with your computers serial or product number or directly from the web with the earlier link.
To run the HP UEFI diagnostics you will power on the computer and repetitively click on the F2 or F10 keys. In the bios then navigate to the UEFI diagnostics. The duration of testing is most influenced by the size of the drive and the memory. Again any component failure automatically aborts the testing with an HP error code. If there is no error code in the AM after overnight testing that is good news. Then press the escape key to abort testing and check the log to confirm the pass result as well as view prior results.
The HP UEFI diagnostics are a battery of tests that can easily be ran while sleeping. If these tests do not detect any underlying problem the above tests that philc43 displayed will be useful in the troubleshooting process.
The event log displays numerous problems with the Mcafee software.
In addition other software problems include settings for hibernation and fast startup.
Another problem is the bluetooth adapter.
These are software steps that you can do now:
1) Open administrative command prompt and type or copy and paste these commands:
10 Ways to Open the Command Prompt in Windows 10
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) powercfg.exe /hibernate off
6) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
7) Uninstall Mcafee and turn on Windows defender:
Antivirus Software, Internet Security, Spyware and Malware Removal McAfee
Last edited by zbook; 30 Sep 2017 at 21:57.
Quote