Issues with long disk management load times and slow shutdowns.
Issues with long disk management load times and slow shutdowns.
Interesting points to consider.
The "post mortem" rule is relevant.
Review Reliability History and Event Viewer once more for any error codes, warnings, or informational events that appeared when the card reader was removed.
These entries—whether present or gone—could hint at why Windows reacted negatively to the card reader's presence and impacted performance.
Thanks to @cruisetung for pointing this out, we can add another "gremlin" to the list.
Will do once I have access to the build at a later time. She is currently using it.
Regarding the card reader, it only uses an internal USB 2.0 header, which also handles power and supports one header that would normally accommodate two USB 2.0 ports.
In my previous build (Skylake), I had to swap out a card reader because it stopped recognizing my ID card.
For the replacement, I purchased an Akasa AK-IRC-09 card reader.
Details can be found here: https://www.akasa.co.uk/update.php?...AN...e_sub=CARD READERS&model=AK-ICR-09
It still functions well in my current Aurora build. I think the one in the Astral version might have compatibility issues with Windows 11, but it works without problems on Windows 7 or Windows 10, and it also runs fine with the Z97 chipset.
I’ll share screenshots later.
The Look and Reliability History doesn't provide much information. However, Event Viewer reveals a lot of details. Regarding Event Viewer, I can store parts of the logs—such as the moment when I removed the card reader—as *.evtx files if you're interested.
I also took over 200 screenshots and shared them online, but that was quite a bit for both of us.
On another note, setting up the build proceeded smoothly and MWB is now functioning without problems.
But I encountered this same problem recently, which almost caused me distress 😱.
Reddit post: https://www.reddit.com/r/gigabyte/commen..._error_on/
That issue is separate from what I'm discussing, but it might be useful if needed.
Interesting point: Disabling the SATA drive clears CMOS automatically on power-on. Re-enabling it clears CMOS again. For my specific motherboard (AsRock X870E Nova Wifi), this behavior seems consistent across different chipset versions. It could be a standard feature or tied to the chipset itself, possibly related to AMD hardware changes. If I make any hardware adjustments for the build, I’ll need to re-enable RAM EXPO, turn off Fast Boot, and adjust fan settings in UEFI.
Event Viewer may sometimes feel excessive, but it can still be searched and filtered to some degree, though it demands a bit of insight into what you're seeking. Powershell offers greater control over searches and the output format if you're interested in that approach. I’d likely begin with a search focusing on Disk related Error IDs, although this is mostly retrospective now that the issue has been identified.
Specifically, try narrowing Event Sources to "disk" and note that this is essentially a post-mortem analysis. If little is known, I start by reviewing logs, prioritizing entries with the highest counts, and sorting by Event ID to spot recurring patterns. Clearing logs can highlight newer or ongoing errors.
However, once the problem is resolved and everything is fine (🫰), it’s best to save these searches and post-mortem steps for future reference.
This task is above my skill level.
I performed it step by step when I unplugged the card reader, and at that moment there were no obvious ones.
I’m not sure what those IDs are. I only remember ID 41, Kernel Power, which connects to my hardware troubleshooting (PSU) problems. No idea about other IDs.
I’ll continue investigating Event Viewer further.
From Event Viewer, the only error IDs I see now are: ID 10010. Occasionally.
Before the fix, the error IDs were: 1, 7, 10, 11, 17, 20, 29, 30, 34, 124, 610, 3503, 6008, 7000, 7009, 7011, 7023, 7030, 7034, 7043, 10005 and 10010.
Everything was normal until two days after assembling the build.
I also noticed that IDs 1, 11, 610 and eventually 7 began to appear more frequently.
Spoiler:
Screens
Please let me know if this gives you everything you need.
Because I’m starting to notice errors every time I have to open Event Viewer again.