Solved Windows 11 nightmare - Randomly crashing on new-build

I should also add that the removal of the MSI Centre software did have an effect on Event logging. With that software installed you were getting thousands of events recorded which if you go back through the event log you will find these have now stopped. This may also have contributed to the system speeding up a little.

philc43 said:

I should also add that the removal of the MSI Centre software did have an effect on Event logging. With that software installed you were getting thousands of events recorded which if you go back through the event log you will find these have now stopped. This may also have contributed to the system speeding up a little.

Click to expand...

Phil, I agree and I don't mind removing the MSI software, but my PC is has lots of RGB lighting and that's the only software that I know can control the LEDs lights. Is there an alternative that I can use? Or maybe reinstall MSI software, but disable it from running on start-up?

PS: I have checked the Event Viewer and unless I'm reading incorrectly, there are many Warning events.

Also what shall I do with the AMD External Events utility?

For any identified problematic services:

a) uninstall any software that are no longer used

b) uninstall and reinstall software that are needed

After the above steps recheck normal boot.

zbook said:

For any identified problematic services:

a) uninstall any software that are no longer used

b) uninstall and reinstall software that are needed

After the above steps recheck normal boot.

Click to expand...

The problem is that I need the AMD software and drivers for my integrated graphics, so I can't really uninstall it.

Seems like others too have had the same issue with this utility:

AMD External Events Utility Service

Almost all software can be uninstalled as a clean install.

Default windows drivers can typically be used until the better performing drivers are installed,

zbook said:

Almost all software can be uninstalled as a clean install.

Default windows drivers can typically be used until the better performing drivers are installed,

Click to expand...

I agree, but since last night, other than the AMD Events Utility, I've re-enabled all the rest of the start-up software within msconfig and the task manager and it works perfect now, so a very big thank to you guys (@zbook and @philc43). So we can safely say that the cause of slow boot time all along was the AMD Events Utility and I don't see any reason to uninstall everything else.

However, I still have a number of major issues to tackle:

• To diagnose why Event Viewer has a lot of warnings (Unless this is normal) - Do I need to do some sort of a V2 log for you?
• To eventually re-connect the other hard drives which at the time I felt were the cause of these issues (I will go into more detail about these at a later stage)

I would like to see a new V2 log, I agree you have found the cause of your slow boot. The warnings in event viewer are possibly related to MSI software and that's what I can look into for you.

Earlier in the thread the GPU drivers were replaced based on a live kernel dump.

The latest live kernel dumps on March 14 and 15 with bugcheck 144 displayed hardware ids related to the AMD chip set drivers.

If there are any hangs or freezes you can reinstall them while in safe mode.

Morning Phil.

HERE is the V2 log file. Please note that since uninstalling, I have not reinstalled the MSI software.

Thank you.

zbook said:

Earlier in the thread the GPU drivers were replaced based on a live kernel dump.

The latest live kernel dumps on March 14 and 15 with bugcheck 144 displayed hardware ids related to the AMD chip set drivers.

If there are any hangs or freezes you can reinstall them while in safe mode.

https://www.amd.com/en/support/kb/faq/gpu-driver-autodetect

Click to expand...

Thank zbook. So far since following phil's instructions in updating the drivers, I've not had a single incident of hanging or freezing, so I'm wondering whether I should mess about with the drivers again.

TCWindows said:

Morning Phil.

HERE is the V2 log file. Please note that since uninstalling, I have not reinstalled the MSI software.

Thank you.

Click to expand...

I would suggest that the best way to reinstall the software is to do it gradually - do not install the complete suite of software but try to install just the bits you need such as LED light control and gradually reintroduce the rest back item by item and observe the impact on your system. I am hoping that this is something that you can do but I have no direct experience of this particular software. Actually as a rule I tend to stay away from the motherboard utilities - they can be more trouble than they are worth.

The warnings in your latest event log are nothing to worry about. What I am interested to see is what happens when you start reinstalling the MSI software. As I mentioned before you had thousands of information entries from MSI which are just clogging up the event logs and are causing loads of unnecessary writes to the drive. This will be a matter to take up with MSI.

Thanks phil.

I've reinstalled the MSI software, but from that I only chose Mystic Light to allow control of RGB lights. I also noticed that MSI is stating that some of the device drivers (Bluetooth, AMD chipset, Realtek HD) drivers also need updating, but I didn't go ahead in case it messes things up.



#################################################################
Here's the NEW V2 LOG - This was created after the MSI install and reboot of windows.
#################################################################

The new services installed by MSI include:

Service Name: NTIOLib_CC_COMM
Service File Name: C:\Program Files (x86)\MSI\MSI Center\Lib\SYS\NTIOLib_X64.sys
Service Type: kernel mode driver
Service Start Type: demand start
Service Account:

Service Name: GENERICDRV
Service File Name: C:\Program Files (x86)\MSI\MSI Center\Lib\SCEWIN\5.04.1144\amigendrv64.sys
Service Type: kernel mode driver
Service Start Type: demand start
Service Account:

Service Name: NTIOLib_MysticLight
Service File Name: C:\Program Files (x86)\MSI\MSI Center\Mystic Light\Lib\\NTIOLib_X64.sys
Service Type: kernel mode driver
Service Start Type: demand start
Service Account:

It does not appear as if the deluge of events from MSI has started back up but keep an eye on it.

As for the new drivers being suggested I would advise you to check on the Motherboard website for details of what improvements they bring. If they are something you want and are Windows 11 drivers then it could be worth installing - I would install via downloading them from the Motherboard website.

Thanks Phil. Since I'm not having any major issues now, I'm thinking of holding off installing anymore MSI drivers. I hope that is okay?

If so, would I be okay to discuss the issues with the ssd drive?

TCWindows said:

Thanks Phil. Since I'm not having any major issues now, I'm thinking of holding off installing anymore MSI drivers. I hope that is okay?

If so, would I be okay to discuss the issues with the ssd drive?

Click to expand...

Yes, please describe the problems and what you have done so far to investigate.

There were 4 new live kernel dump files:



Please run:



Gather_additional_dump_files.bat ─ Click here to go to the BSOD batch repository to download and run this batch file.


Monitor the computer using:

philc43 said:

Yes, please describe the problems and what you have done so far to investigate.

Click to expand...

Brilliant thanks Phil. I'll deal with zbook's request in obtaining the relevant files and once he's completed his diagnostics, I'll move onto connecting the SSD. However, I can let you know that when I connect SSD drive, although I don't have any issues with it, Windows Event Viewer shows that it has bad sectors (see zbook's post #12). But I want to add that prior to this drive, I had another previous SSD drive and Windows Event Viewer was doing the same with that too. I have tried to change the SATA cables and connectors on the motherboard to different ones, but this hasn't solved the issue.

zbook said:

There were 4 new live kernel dump files:

Code:

17/03/2022 11:59:28      0.27 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220317-1159.dmp
17/03/2022 16:39:58      0.32 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220317-1639.dmp
17/03/2022 21:02:38      0.27 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220317-2102.dmp
17/03/2022 22:15:29      0.27 C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20220317-2215.dmp

Please run:

https://www.tenforums.com/attachments/bsod-crashes-debugging/360137d1645183388-batch-files-use-bsod-debugging-tuneup_plus_log.bat

Gather_additional_dump_files.bat ─ Click here to go to the BSOD batch repository to download and run this batch file.


Monitor the computer using:

Reliability Monitor is the Best Windows Troubleshooting Tool You Aren’t Using

When it comes to hidden gems in Windows, nothing beats the Reliability monitor tool, hidden behind a link inside of another tool that you don’t use either. Why Microsoft doesn’t shine more light on this really useful troubleshooting tool, we’ll never know.

www.howtogeek.com

Click to expand...

Thanks zbook. I've attached the Live kernel reports, Tune-up log and Reliability History. Hope this is okay, but if you need anything else, please let me know.

Chkdsk / scan reported problems:





1) Uninstall Dropbox > reinstall dropbox


2) Run chkdsk /b /v


C:\WINDOWS\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y


Plan to run the chkdsk switches overnight.


3) After chkdsk has completed:

a) Run:
chkdskFromEvent.bat - Click here to go to the BSOD batch repository to download and run this batch file.

b) and post a new V2.



The reliability history is for your monitoring.

See chart and listed events.

@zbook - Thanks. I couldn't wait so I ran chkdsk straight away - There were a lot of stages of fixing files or something. After reboot I ran the chkdskFromEvent.bat and V2 Log - File links are:

V2 LOG
chkdskFromEvent.log