New
#261
The WHEA 0x124 BSOD can occur with over clocking, misbehaving drivers, etc.
Blue spinning pin wheel, program not responding?
-
-
New #262
It wouldn't surprise me that the Asus AI Suite software I had installed could have be related, it's known to cause a lot of problems. I'm so glad I've decided to do away with this on this current OS installation. With this new installation if the WHEA does happen to occur again I may be able associate any new program/event with the error. Hoping there won't be though.
-
New #263
Hi zbook,
Have just recovered from a lengthy internet outage. Here is the log I took yesterday but wasn't able to upload.
M-MAXIMUSXHERO (2018-04-26 20 09).zip
-
New #264
There were no new BSOD since the crash dump test on 4/18/2018.
There were no unexpected computer crashes since the same date.
There were no WHEA controlled or uncontrolled 0x124 errors since the same date.
Run administrative command prompt chkdsk /x /f /r on each of these partitions/drives using the syntax chkdsk /x /f /r C: or chkdsk /x /f /r D: changing the drive letter to the applicable drive.
DriveLetter Size (GB) Free (GB) Device Path
----------- --------- --------- -----------
C: 232.28 187.57 \Device\HarddiskVolume4
D: 14.4 10.96 \Device\HarddiskVolume9
E: 2794.39 2208.59 \Device\HarddiskVolume8
F: 931.39 77.96 \Device\HarddiskVolume6
Use the information in this link to find the chkdsk reports in the event viewer > copy and paste to notepad > post a one drive or drop box share link into the thread
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Tutorials
There were app crashes and the most frequent was Corsair.
So uninstall or uninstall and reinstall this software.Last edited by zbook; 26 Apr 2018 at 20:35.
-
New #265
Will get chkdsk logs asap. The Corsair crashes are common for almost all users of the software that I'm aware of. Do crash reports give any hint as to the cause of the crashes? There was an update to the software just released yesterday (version 3.2.87). I've updated the software to this version. Do you still recommend reinstalling it?
-
New #266
Ordinarily the apps are not troubleshooted but it stood out after the clean install.
Once the chkdsk are done you will complete the troubleshooting.
You know the methods to troubleshoot the dumps with Whocrashed and view the event logs.
Also you know how to troubleshoot the hardware.
So you should be in good shape.
-
New #267
chkdsk F:
chkdsk F 27-04-18.txt
chkdsk C:
chkdsk C 27-04-18.txtLast edited by Kol12; 27 Apr 2018 at 00:50.
-
New #268
Hi zbook,
Thanks again very much for the help you've provided, I appreciate it. Hopefully I've learned some things also. :)
Can I ask, is the log collector beta something you would use regularly to troubleshoot or even just check on a machine's general health? What do you generally look for in the logs and how do you filter what your looking for? The three main areas that appeared to be importance were disk and Windows file condition, driver/software and hardware error/crashes...
-
-
New #269
You are welcome.
A lot of progress was made.
There are 2 more partition chkdsk results pending.
The log collector can be used to collect files on the computer or you can view the files on your own.
If you backup files and make a backup image you will create a margin of safety in case there are any unexpected problems.
On a regular basis you can run tests that check the operating system and drive file system:
sfc /scannow
dism /online /cleanup-image /restorehealth
chkdsk /scan
These can be run as frequently as you like.
The drives can be tested every 6 months with HD Tune. And as the drive gets older you can check every quarter.
The above steps should enable you to monitor the computer performance over time.
Today you checked the event viewer for the the chkdsk logs.
It's a matter of preference the method used to view events.
The log collector will collect the important files and you can search for BSOD or WHEA.
If you use the event viewer the method is to use the right pane.
Click on create custom view > check the boxes for critical, warning, and error > in event logs check windows logs > OK
Then scroll to see the results.
-
New #270
The log collector is nice in that it compiles a lot of useful information all in one place but for general system checking it is probably easier to use Event Viewer. How do you filter things out from the log collector .txt event files? Do you need to know the key words eg WHEA, BSOD and use the find feature? What keyword/s are used to find the misbehaving drivers?
Quote
Related Discussions
