Question I'm getting BSODs on an Asus computer, but no dump files are created ?

Page 3 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
ubuysa said:
TBH I would uninstall Armory Crate in its entirety and also uninstall any ASUS management tools you may have installed.

The error 41 you're seeing is a symptom not a cause. All it tells you is that Windows wasn't shut down properly. It's issued after Windows has rebooted. Look through the System log at entries earlier than the error 41 for Kernel Boot entries, you'll find one that tell you the date and time when the system restarted. The entries immediately preceding this are those written just as the system crashed. Also look in the Application log for entries written just before the crash time.
Click to expand...
I checked Event Viewer, and before the Kernel-Power ID 41, I saw volmgr 161, Hyper-V-Hypervisor 167 and EventLog 6008.
 
That 6008 is interesting, it's a 'forced shutdown' message. Can you please upload your System and Application logs so we can see everything in there....

1. Enter the command eventvwr into the Run command box. The Event Viewer will open.
2. Locate the Windows Logs folder in the left hand pane and expand it by clicking on the arrow (>) to the left of it.
3. Right-click on the Application entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'Application' (an .evtx suffix will be added automatically).
4. Right-click on the System entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'System' (an .evtx suffix will be added automatically).
5. Zip the Application.evtx and System.evtx files together and upload the zip file to cloud storage
 
ubuysa said:
That 6008 is interesting, it's a 'forced shutdown' message. Can you please upload your System and Application logs so we can see everything in there....

1. Enter the command eventvwr into the Run command box. The Event Viewer will open.
2. Locate the Windows Logs folder in the left hand pane and expand it by clicking on the arrow (>) to the left of it.
3. Right-click on the Application entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'Application' (an .evtx suffix will be added automatically).
4. Right-click on the System entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'System' (an .evtx suffix will be added automatically).
5. Zip the Application.evtx and System.evtx files together and upload the zip file to cloud storage
Click to expand...
Here are the logs.
Application and Storage.zip
 
I'm pretty sure that this is hardware related because I can see the critical error 41 messages (which only indicate that Windows didn't shutdown properly) but with nothing in the lead up to the crash to account for the crash. That's most usually a hardware failure that Windows disn't even see coming.

One interesting thing I do note however is that many of these error 41 messages (but certainly not all of them) occur at around the same time of day. Bear in mind that timestamps are normalised in the Event Viewer to the timezone of the person viewing them and I'm 3 hours ahead of UTC here in Greece. Here's just a couple of examples but there are other matches....

03/11/2024 08:07:33
31/10/2024 08:07:27

25/10/2024 06:45:53
01/10/2024 06:46:10
21/09/2024 06:40:57
10/09/2024 06:45:22

There are others, but those 06:40 to 06:46 error 41 messages stand out as unusual. It's rare to see crashes happeneing on different days at the same sort of time.

I wonder whether there is something environmental in your home cxausing these BSODs? I did have a user some years ago who had WHEA BSODs regularly and which we couldn't track down. They stopped when he moved house. Decades ago I diagnosed a WiFi networking problem that turned out to be an arcing light switch next to the wireless router. These things do happen.

Do you have a willing friend who will let you setup your rig at their house for a few days? As soon as you get a BSOD at your friend's house you can stop the test and come home because that will show it's not environmental. I really do think this is worth doing given the difficulties in tracking these BSDOs down.
 
  • Like
Reactions: Ralston18
ubuysa said:
I'm pretty sure that this is hardware related because I can see the critical error 41 messages (which only indicate that Windows didn't shutdown properly) but with nothing in the lead up to the crash to account for the crash. That's most usually a hardware failure that Windows disn't even see coming.

One interesting thing I do note however is that many of these error 41 messages (but certainly not all of them) occur at around the same time of day. Bear in mind that timestamps are normalised in the Event Viewer to the timezone of the person viewing them and I'm 3 hours ahead of UTC here in Greece. Here's just a couple of examples but there are other matches....

03/11/2024 08:07:33
31/10/2024 08:07:27

25/10/2024 06:45:53
01/10/2024 06:46:10
21/09/2024 06:40:57
10/09/2024 06:45:22

There are others, but those 06:40 to 06:46 error 41 messages stand out as unusual. It's rare to see crashes happeneing on different days at the same sort of time.

I wonder whether there is something environmental in your home cxausing these BSODs? I did have a user some years ago who had WHEA BSODs regularly and which we couldn't track down. They stopped when he moved house. Decades ago I diagnosed a WiFi networking problem that turned out to be an arcing light switch next to the wireless router. These things do happen.

Do you have a willing friend who will let you setup your rig at their house for a few days? As soon as you get a BSOD at your friend's house you can stop the test and come home because that will show it's not environmental. I really do think this is worth doing given the difficulties in tracking these BSDOs down.
Click to expand...
Sadly no. One thing I do note is that the house I live in was built in the 1950s and I live in Canada. I wonder if my computer wasn't built for houses built during the era.
 
I know nothing about the internals of 1950's Canadian houses! If you have more than one power ring in the houes (and you most likely do) then try powering the PC from a different ring - that will likely mean moving it tempoirarily to a different room.

Do you have a surge protector between the PC and the wall socket? If not then get one. I use a UPS to power my PC and monitor, partly because we do sometimes get power outages here in Greece, but also because it isolates the PC from noise on the mains power.
 
ubuysa said:
I know nothing about the internals of 1950's Canadian houses! If you have more than one power ring in the houes (and you most likely do) then try powering the PC from a different ring - that will likely mean moving it tempoirarily to a different room.

Do you have a surge protector between the PC and the wall socket? If not then get one. I use a UPS to power my PC and monitor, partly because we do sometimes get power outages here in Greece, but also because it isolates the PC from noise on the mains power.
Click to expand...
I do have a surge protector.
 
I asked you in a couple of posts to start Windows in Safe Mode and see whether the BSODs continue in Safe Mode. Did you ever do that? Did the BSODs occur in Safe Mode?

This is an important test because if it does BSOD in Safe Mode we can be pretty confident that it's not Windows that's at fault but something else - hardware or environmental.
 
And I am curious about those closely timed events noted by @ubuysa in Post #54.

I will add the suggestion to take another look in Reliability History/Monitor and Event Viewer for any other captured activities just before or at those times.

Also take a look in Task Scheduler - there may be some "routine" action being triggered around those same times and causing subsequent issues.

As a simple guess: are those times around when the computer is usually booted up? If not, what else may be common or otherwise "routine" to those times?
 
  • Like
Reactions: ubuysa
Ralston18 said:
And I am curious about those closely timed events noted by @ubuysa in Post #54.

I will add the suggestion to take another look in Reliability History/Monitor and Event Viewer for any other captured activities just before or at those times.

Also take a look in Task Scheduler - there may be some "routine" action being triggered around those same times and causing subsequent issues.

As a simple guess: are those times around when the computer is usually booted up? If not, what else may be common or otherwise "routine" to those times?
Click to expand...
I have looked at the Task Scheduler, and it shows 154 tasks running. However, looking at View Reliability History, I see that ASUS System Analysis has stopped working.
 
ubuysa said:
I asked you in a couple of posts to start Windows in Safe Mode and see whether the BSODs continue in Safe Mode. Did you ever do that? Did the BSODs occur in Safe Mode?

This is an important test because if it does BSOD in Safe Mode we can be pretty confident that it's not Windows that's at fault but something else - hardware or environmental.
Click to expand...
Hello. I am facing a new issue here. MyASUS says that I need to update my BIOS from 304 to 330, however, when I try to update the BIOS, it says that the update has failed. I seriously need some help with this.
 
@SabbathFan

Troubleshooting is as much finding a problem as it is eliminating possible reasons for a problem.

You need to be methodical, careful, and look at things very closely. Details matter.

= = = =

154 Tasks running inTask Scheduler? Did you mean Task Manager or Process Explorer perhaps?

Take a couple of screenshots and post here via imgur (www.imgur.com)

Likewise per @ubuysa : PSU? Safe Mode?

BIOS Update failure: any stated reasons or error codes?
 
Ralston18 said:
@SabbathFan

Troubleshooting is as much finding a problem as it is eliminating possible reasons for a problem.

You need to be methodical, careful, and look at things very closely. Details matter.

= = = =

154 Tasks running inTask Scheduler? Did you mean Task Manager or Process Explorer perhaps?

Take a couple of screenshots and post here via imgur (www.imgur.com)

Likewise per @ubuysa : PSU? Safe Mode?

BIOS Update failure: any stated reasons or error codes?
Click to expand...
https://imgur.com/a/CewxPW2
View: https://imgur.com/a/CewxPW2
 
Dates of interest:

When the final BIOS version (not some Beta version) was released for installation.

When the BIOS was installed (or attempted) on your system.

When the Update error occurred.

The other concern is to ensure : 1) that the BIOS version was directly downloaded from the manufacturer's website without error, and 2) that the BIOS version was correct for the motherboard.

The link is rog.asus.com so the download was direct.

Doublecheck that the correct BIOS was downloaded. Also check for a newer version.

= = = =

Still getting BSOD's - correct?

Reading back, I suggest that you open Reliabilty History/Monitor, take some screenshots, and post the screenshots here. Expand the screenshot window so all can be seen.

Take one screenshow with View by "Days" and a second screenshot with View by "Weeks".

Post accordingly.
 
Ralston18 said:
Dates of interest:

When the final BIOS version (not some Beta version) was released for installation.

When the BIOS was installed (or attempted) on your system.

When the Update error occurred.

The other concern is to ensure : 1) that the BIOS version was directly downloaded from the manufacturer's website without error, and 2) that the BIOS version was correct for the motherboard.

The link is rog.asus.com so the download was direct.

Doublecheck that the correct BIOS was downloaded. Also check for a newer version.

= = = =

Still getting BSOD's - correct?

Reading back, I suggest that you open Reliabilty History/Monitor, take some screenshots, and post the screenshots here. Expand the screenshot window so all can be seen.

Take one screenshow with View by "Days" and a second screenshot with View by "Weeks".

Post accordingly.
Click to expand...
Last BIOS version came out on May 6, 2024. I attempted to download it through MyASUS on December 12. That's the date the error occurred. Yes, I am still getting BSODs. I have opened up Reliability History and took two screenshots and posted them on Imgur.
https://imgur.com/a/vnQPNxA
View: https://imgur.com/a/vnQPNxA
 
Yes - the timeline window is helpful but you need to look at and show the Reliability details listed below the timeline window.

Clicking individual Errors (red circle), Warnings (yellow triangle), or informational events (blue circle) will provide more technical details about what happened. The technical details may or may not be helpful.

Note that on the right end of the timeline that the types of failures are presented. Namely Applications, Windows, Misc..

Take a closer look at the details available. Look for named apps, processes, services, and so forth.

Also run "dism" and "sfc /scannow" to find and fix corrupted files.

FYI:

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

The immediate objective being to just try cleaning up any corrupted or buggy files.

Or identify other problems. Could have been a corrupted update.
 
Ralston18 said:
Yes - the timeline window is helpful but you need to look at and show the Reliability details listed below the timeline window.

Clicking individual Errors (red circle), Warnings (yellow triangle), or informational events (blue circle) will provide more technical details about what happened. The technical details may or may not be helpful.

Note that on the right end of the timeline that the types of failures are presented. Namely Applications, Windows, Misc..

Take a closer look at the details available. Look for named apps, processes, services, and so forth.

Also run "dism" and "sfc /scannow" to find and fix corrupted files.

FYI:

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

The immediate objective being to just try cleaning up any corrupted or buggy files.

Or identify other problems. Could have been a corrupted update.
Click to expand...
Hello. Here are at least three more screenshots proving some of the issues I had, one of which is that ASUS System Analysis stopped working. I also ran "sfc /scannow" and it says that there were some corrupted files, and that they were fixed.
https://imgur.com/a/oxkgjvE
View: https://imgur.com/a/oxkgjvE
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom