Windows 10: BSOD on random times,error 0x000000124

Hello sorry for taking so long to reply but there is a lot of workload.
I used the settings provided for the verifier and starting doing the tests for the hdd.i got a bsod at that time that i can only give you a screenshot of it.after restart verifier kicked in and after second reboot pc went into repair mode and went to an earlier state.so i have not the files to upload. i will do the verifier from post #22 as soon as possible and provide them to you. thank you and sorry for taking so long from my behalf.

 

Nice work making the images.
The windows driver verifier bsod window displayed the misbehaving driver:
Aicharger.sys
However this is code for something else as this driver is not on the list for your computer and in the information below it was last seen in 2013.
The stop code: WHEA Uncorrectable error or 124 was already know and is what you are troubleshooting.
Was it 2 reboots that triggered the advanced troubleshooting repair or was it just 1 reboot?

AiCharger.sys Asus Charger Driver
Likely BSOD cause - haven't seen recently (15Jan2013) http://support.asus.com/download/opt...x?SLanguage=en
Open each whocrashed and bluescreenview to see the latest information and post a new zip:
BSOD - Posting Instructions - Windows 10 Forums

 

it was 2 reboots
i have enable not the autorestart after bsod so i have to manually press restart button on tower

 

Check the PSU voltages: what are each 3.3v, 5v, and 12v values?

PSU - Test DC Output Voltage - Windows 7 Help Forums

 

hello (again i apologize for taking long to reply, i do extra hours at work).
i am trying to upload you the image from bios, 1 image or 5 or even a zip and i can't. have i exceed the maximum upload limit or something?
the voltages are +12v +5v +3.3v
intel cpu input is 1.856 (auto)
dram is 1.646 (auto)
cpu core voltage is 1.088 (auto)
cpu cache voltage is 1.170 (auto)

 

i finished the verifier test you asked on post # 22 and i got no bsod. pc run for about 40 hours straight. i also checked from cmd if it was running correctly with "verifier /querysettings"and it was. there are no new bsod to upload also i need help cause i can't upload images from bios. let me know if i have uploaded my max file size so i download all and i have it as well and then which one to delete from your data.
thank you in advance.

 

Use a camera or smart phone camera to take pictures and post images into the thread for anything when windows is not in use.

If Windows driver verifier has been run for 36 - 48 hours without a bsod it can be turned off.

When you are able to boot using windows please post a new zip:
BSOD - Posting Instructions - Windows 10 Forums

When you had the case open what were you able to see in the way of dust?
Were you able check wires or cables or re-seat components?
When you manually measured voltages what were the results?

Open device manager > click view > show hidden devices > post images of any yellow icons or devices without a name.

Please fill in the information about the computer's components and specifications:

How To Fill Out Your System Specs
How To Fill Out Your System Specs

System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Windows 10 General Tips Tutorials

In the left corner below in your post you find 'My System Specs'.

After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.

System Info - See Your System Specs - Windows 7 Help Forums

Please included this information that was not in the above links:
PSU, cooler, case, peripherals (mouse, keyboard, joystick, etc.)

 

system speccs are those of the 2nd pc

When you had the case open what were you able to see in the way of dust? no i cleaned it and it was cleaned at the retailer as well

Were you able check wires or cables or re-seat components? all cables were plugged in correctly and the screen on motherboard has AO indicator which means everything is plugged correctly

When you manually measured voltages what were the results? i dont have the tools to do so, i checked the values from bios.

i got a new bsod today with error code CLOCK_WATCHDOG_TIMEOUT it got stuck at 50% so i restarted my pc after 10 mins of waiting. so it wont be seen at the logs.
i can't upload any images or zip files.let me know if i have uploaded my max file size so i download all and i have it as well and then which one to delete from your data.

 

last logs
seems the files i tried to upload were too big

 

hello.
i've had many bsod again but none is beeing saved to. i checked to see if i have set something like overwrite previous or anything, i changed the manual reboot to autoreboot and again nothing.why is this happening?

 

Please post a new zip and whenever you have a bsod please post a new zip: BSOD - Posting Instructions - Windows 10 Forums


On the Ten Forums web site there is a section below your user name. It is in the left lower corner. It allows viewers of the webpage to see the information about the computer specifications. The specifications for multiple computers can be displayed.
Please update this section:

How To Fill Out Your System Specs
How To Fill Out Your System Specs
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Windows 10 General Tips Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums
Please include PSU, cooler, case, peripherals (mouse, keyboard, joystick) and please include anything attached to the computer by wireless or wired (printer, headset, xbox, etc.)


Please estimate the time interval between bsod.
How often do they occur? (times per day, or times per week)

1) Are your files backed up to where you can perform a clean install of windows 10 version 1703 as a "vanilla installation" ? That would be no third party drivers, no applications, no files.
2) Have you made an image of the drive?
3) Are you able to use the computer in safe mode?

 

system speccs are already provided on second pc tab.
the dmp files are not generated after bsod occurs.
about 1) i have done that already and got a bsod.i downloaded the windows 10 usb installation and first day i got bsod without anything else installed.
about 2) yes
about 3) yes and i have not gotten a bsod.
that bsod is really random as i have said. it might happen while i have just skype open or while i am running heavy games or even just watching a video.i have used the pc several times for more than 10 hours with no bsod and then after 20 mins it just pops.so it is totally random.

 

Under your username in the left lower corner is "my computer"
This section can be updated to display multiple computers.
Please update this section so that anyone on the webpage can view the computer's specifications.

Are you able to test the CPU with Prime95?
Duration, maximum temperatures.
Please post images into the thread.


Download and install Whocrashed and Bluescreenview
Resplendence Software - WhoCrashed, automatic crash dump analyzer
Blue screen of death (STOP error) information in dump files.

Open whocrashed > click analyze > post results into the thread
Above analyze click on tools > crash dump test > type: ACCEPT > post results into the thread

After the above post a new zip file: BSOD - Posting Instructions - Windows 10 Forums


Please uninstall advanced system care.

Please list all drivers that it has installed.

 

i updated the speccs, i hope you can see them now.

whocrashed below
Welcome to WhoCrashed (HOME EDITION) v 5.54
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...


Home Edition Notice
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.

System Information (local)
Computer name: DESKTOP-5LVHCU4
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\Windows
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., MAXIMUS VII RANGER
CPU: GenuineIntel Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17118896128 bytes total



Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 8/13/2017 3:28:15 PM your computer crashed
crash dump file: C:\Windows\Minidump\081317-22671-01.dmp
This was probably caused by the following module: hal.dll (hal+0x395CF)
Bugcheck code: 0x124 (0x0, 0xFFFFDD05BC2A2028, 0xBF800000, 0x124)
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. This problem might also be caused because of overheating (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.



On Sun 8/13/2017 3:28:15 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0xCF)
Bugcheck code: 0x124 (0x0, 0xFFFFDD05BC2A2028, 0xBF800000, 0x124)
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. This problem might also be caused because of overheating (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.



On Sat 8/12/2017 4:34:33 PM your computer crashed
crash dump file: C:\Windows\Minidump\081317-22453-01.dmp
This was probably caused by the following module: hal.dll (hal+0x395CF)
Bugcheck code: 0x124 (0x0, 0xFFFFC409887D0028, 0xBF800000, 0x124)
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. This problem might also be caused because of overheating (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.



On Thu 8/10/2017 2:19:08 PM your computer crashed
crash dump file: C:\Windows\Minidump\081017-24281-01.dmp
This was probably caused by the following module: hal.dll (hal+0x395CF)
Bugcheck code: 0x124 (0x0, 0xFFFFE28D7E3AF028, 0xBF800000, 0x124)
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. This problem might also be caused because of overheating (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.



On Sat 8/5/2017 1:06:09 PM your computer crashed
crash dump file: C:\Windows\Minidump\080517-18859-01.dmp
This was probably caused by the following module: hal.dll (hal+0x395CF)
Bugcheck code: 0x124 (0x0, 0xFFFFB08BFABF3028, 0xBF800000, 0x124)
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. This problem might also be caused because of overheating (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.




Conclusion
6 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

BSOD on random times,error 0x000000124 - Windows 10 Forums


temperatures of both hdd are normal

 

The system specs are still missing:
PSU cooler, case, peripherals (mouse, keyboard, joystick) and anything attached via wireless or wired ( printer, headset, xbox, etc)