Unexpected Shutdowns

Question

Unexpected Shutdowns

K-T 0

These past few months, my computer has had several unexpected shutdowns, but I am not sure about the cause.

I initially thought it was just due to a bad battery (health at around 60%), but apparently the problem also occurs when plugged in and fully charged; it may have something to do with the CPU utilization, etc.

Most of the crashes are under EventID 41 with Bugcheck code 340.

Event log shared for reference:

https://drive.google.com/file/d/1FXFGtINaDQWr8t3blqnDpcyq77hEq4Z5/view?usp=sharing

Thanks!

0 comments

1 answer

Your answer

Answer 1

David-M 125K Independent Advisor

Hi. I'm David, and I'm happy to help you.

The event "Kernel-Power 41 (63)" is registered for all types of abrupt system shutdowns. Unfortunately, on its own, it is not an event that helps identify the root cause of the problem.

Please see if your computer created minidump files.

These files are in C:\Windows\Minidump.

(I have seen some cases where the folder is in the plural "Minidumps".)

(If you don't have the folder or no files in it, it means that the computer didn't create the files. In this case, let me know, and I'll proceed.)

Copy any files you have to your desktop and store them in a ZIP file. Then, upload the ZIP file to the cloud (OneDrive), choose to share it, and get the link.

Post the link to the ZIP file here so I can have a look.

Looking forward to your reply.

K-T 0 Reputation points

2026-09-05T02:21:29.0133333+00:00

Hello, here is the link:

It seems my system only created a dump file for one incident: https://1drv.ms/u/c/4d632483ba7f8181/IQCCsTDgqR40SrVDfxkgr2IpAUd1FpeC3vrQJ56eyJVuyCk?e=Qaiihq

I am not sure how relevant it would be for the current issue. However, I have already run chkdsk /f /r and DISM, and upon checking with CrystalDisk, the health of my drive seems to be good:

Despite this, the system still crashes from time to time.
David-M 125K Reputation points Independent Advisor

2026-09-05T13:43:50.56+00:00
Sorry for the delay in reply. I've been offline.

Thanks for the details.

The minidump is old, but I checked it anyway. The minidump does not mention any driver, only a generic system file.

The system has not been creating new minidumps, likely due to the type of crash occurring.

In this case, I suggest doing the following:

Go to the Asus website using the link below, download the drivers listed, and install them.

https://www.asus.com/supportonly/ux333fa/helpdesk_download/

Drivers suggested:

Intel Management Engine Interface

Intel(R) Serial IO SPI Driver

Intel(R) Serial IO I2C Driver

Intel(R) Serial IO UART Driver

Intel(R) Serial IO GPIO Driver

Intel Serial IO controller driver

(You will need to expand the Chipset category to find the mentioned drivers.)

(Extract the ZIP file and double-click the installation file to run it. Then, follow the on-screen instructions to install the driver.)

Then, restart (not shutdown) your PC and see if the system works stably.

If the crash occurs again after doing this, please let me know.

Feel free to ask any questions you may have.

Standard Disclaimer: There is a link to a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.
K-T 0 Reputation points

2026-09-05T15:50:24.3066667+00:00

Thanks, I will try it out. The problem though is that it's difficult to tell when it will crash; it can go several days without issue then suddenly crash out of nowhere. The system itself is quite old, so some part may be tied to that
David-M 125K Reputation points Independent Advisor

2026-09-06T14:09:29.07+00:00

Glad to help.

If you have any questions, don't hesitate to ask.
K-T 0 Reputation points

2026-09-06T14:33:36.3133333+00:00

I have already installed the drivers, and I will see if there will be a problem, but the interval between crashes can be quite tricky. Sometimes it's consecutive days, other times, it's a few weeks.

I read somewhere that the amount of free disk space is also an important factor since apparently Windows needs at least 25 GB or so free to create a dump file, otherwise, no dump file would be made. Is this actually the case?

Are there any other tests I can do for diagnostics, especially regarding hardware components? I'm speculating maybe the system is unable to cope with unexpected power spikes, especially since the battery is quite old; most of the crashes happened when the system was on battery power as far as I know, but there are a few that occurred when plugged in.
David-M 125K Reputation points Independent Advisor

2026-09-07T13:53:40.21+00:00

I have already installed the drivers, and I will see if there will be a problem, but the interval between crashes can be quite tricky. Sometimes it's consecutive days, other times, it's a few weeks.

I understand. Sometimes the system can remain stable for days before crashing again.

I read somewhere that the amount of free disk space is also an important factor since apparently Windows needs at least 25 GB or so free to create a dump file, otherwise, no dump file would be made. Is this actually the case?

No, it is not strictly the case that Windows requires 25 GB of free space just to create a minidump file. In your case, the specific type of crash occurring is likely the reason the system isn't creating a minidump. Outdated drivers might also be a factor. If another crash occurs, a minidump might be generated that helps identify the actual cause of the problem.

However, if you want to free up space on your C: drive, I suggest consulting the article below.

https://support.microsoft.com/en-us/windows/experience/storage-filemanagement/free-up-drive-space-in-windows

Are there any other tests I can do for diagnostics, especially regarding hardware components? I'm speculating maybe the system is unable to cope with unexpected power spikes, especially since the battery is quite old; most of the crashes happened when the system was on battery power as far as I know, but there are a few that occurred when plugged in.

It is possible to test some components via software, while others can only be tested physically using some profissional tools. Some manufacturers provide software that allows for the testing of certain components. In your case, you can use MyAsus. However, it has its limitations.

To thoroughly test the RAM, I suggest you use the free MemTest86 tool.

https://www.memtest86.com/download.htm

The deep scan can take a long time, depending on how much RAM you have. So do it at a time that suits you.

As for the other components, if MyAsus cannot test them, I am afraid you won't be able to test them using software. I have tried some programs that claim to test PC components, but none were reliable enough; they might indicate a problem that doesn't exist or fail to detect one that does.

Feel free to ask any questions you may have.

Standard Disclaimer: There is a link to a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.
K-T 0 Reputation points

2026-09-07T15:07:36.6966667+00:00

I see. Actually, upon re-checking the logs, I found bugcheck codes 0, 26, 30, and 122. Some say that code 122 might be hardware related, but I do wonder if this is indeed the case since tests so far cannot pinpoint anything.

Anyway, hoping for the best, but will report in case something comes up.
David-M 125K Reputation points Independent Advisor

2026-09-08T11:58:45.6266667+00:00

You are referring to WHEA_INTERNAL_ERROR, right? If so, and if it is caused by hardware, it typically involves the CPU, motherboard, or RAM. Testing the CPU and motherboard via software is unreliable. Therefore, software-based tests alone should not be used to rule them out as the cause of the crash. As for RAM, MemTest86 is very effective.

I wouldn't rule out the possibility that this error is caused by an issue with one of the drivers I suggested installing. So, it's worth continuing to monitor the system's behavior to see if the crash happens again.

Feel free to ask any questions you may have.
K-T 0 Reputation points

2026-09-11T01:03:47.63+00:00

Yes, but so far, the predominant bugcheck code is 340.

I must report that the system crashed again, with another instance of bugcheck code 340. No dump file was produced.

This is the event file for the latest instance:

https://1drv.ms/u/c/4d632483ba7f8181/IQCWtOazY_RSQZuqkzE9SNtqAT7ITnUpCwnuYgnDk7wBgjA?e=f8Hnud

Actually, there was a bugcheck code 122 the week prior. The event file for this corresponding instance is here:

https://1drv.ms/u/c/4d632483ba7f8181/IQCLo_ZqLSWTR6XaL8fvYrHQAbP0RP1uDxAssKmqT71Zj6g?e=YgsuUs