The PC exhibits unusual BSOD behavior upon awakening after component swaps.
The PC exhibits unusual BSOD behavior upon awakening after component swaps.
Absolutely, I'd still need to check the remaining three components. My focus is on isolating the problem and uncovering the main cause. The current specs are: PSU - Seasonic Vertex GX1000, MoBo - ASUS ROG STRIX B550-E, Cooler - Stock AMD, with the rest being peripherals. The RAM consists of two 16GB modules. I'm currently at work and haven't completed testing yet; I'll let you know once I'm back home.
how long you combined them for testing? It might be due to that. They probably worked well on older CPUs but could have issues with APUs because they rely heavily on RAM for graphics VRAM. Testing only with sticks in each set means mixing them can create minor discrepancies that might trigger crashes.
They've been utilized for a considerable period, having been present since 2021 with a consistent stock D.O.C.P. profile. It's important to remember that I also have a distinct Windows version where the Sleep function operates smoothly, which indicates the hardware is capable of managing Sleep and Wakeup effectively.
What is included in that sandbox environment? The number of programs varies. The variation might stem from different drivers. Unless you reviewed each one using a tool such as Driver View (refer to the spoiler) and verified they are exact versions, they won't match. No two installations are identical unless they were cloned without updates.
Spoiler
Download and execute Driverview -
http://www.nirsoft.net/utils/driverview.html
It only checks for installed drivers; it doesn’t install any (this is deliberate since third-party driver updaters often misinterpret).
When you launch it, switch the view tab to hide all Microsoft drivers, which will shorten the list.
Can you capture a screenshot from (and including) the driver name to (and including) the creation date?
Upload it to an image-sharing platform and share the link here—just curious about what you have since we can’t obtain any dumps.
It displays all installed drivers, but it can’t determine whether they are active. Other programs might be better at that.
Software testing of hardware can’t detect physical issues. It’s possible there’s a visible SSD fault not reflected in the reports.
I’m just trying to figure out possible reasons.
Both drives performed perfectly on the last build. You simply removed the GPU and swapped the CPU. Unfortunately, no tests were run for an AMD CPU. The only driver I have is Prime95, which tends to run long and hot—up to 17 hours.
So I got back home and started testing. Here are the outcomes of what I've accomplished so far.
I ran memtest86 using just one 8GB stick; there were no errors in roughly an hour of testing, and all four passes completed successfully.
But the problem continues, though in a different manner this time. Now the system doesn’t even have time to trigger a BSOD or attempt to generate a dump file. When I power it on, it crashes immediately and restarts from the beginning, as if I had pressed "Shutdown" instead of Sleep.
Below is the event viewer after a failed wakeup. The same codes appear for the dump file, but no BSOD is visible.
UAC was active, the paging file was enabled, and the service in services.msc was set to Manual. Still, there are no dump files on C:\Windows\Minidump, and the folder hasn’t even been created by the system.
The Sandbox environment has only the essentials—it’s quite minimal.
Here’s a list of the programs installed in the Sandbox compared to my main system, which has significantly more installed applications.
Unlike my primary system, this one is much lighter, for a reason.
Below are the screenshots from DriverView as requested:
Main system
Sandbox
I haven’t managed to reproduce a BSOD at the moment, even after reinstalling the other three drives. It just crashes and restarts immediately, just like with a single drive. No BSOD appears, but the Event Viewer records the same issue:
"Dump file creation failed due to error during dump creation."
I’m not sure what changed, but I’ve noticed this pattern before. The original BSOD was quite unusual—mainly a black screen followed by a system crash whenever trying to wake up from sleep.
Any suggestions, guys? Maybe reviewing the drivers list could help identify something I missed.
By the way, just to note for the tests, I also tried disabling all non-Microsoft startup programs, but it made no difference. I didn’t log in to my account either; I put the PC to sleep from the lockscreen without entering my password, and the result was the same.
Please download and execute the SysnativeBSODCollectionApp, then upload the generated zip file to a cloud storage with a shareable link. This tool compiles all relevant troubleshooting information we anticipate needing. It does not gather any personal data. It is utilized by several well-regarded Windows help forums, including this one. As a senior BSOD analyst on the Sysnative community where it originated, I can confirm its safety.
You may review the contents of the zip file before uploading, as most files are text documents. Avoid modifying or removing any files. For a detailed explanation of each file’s purpose, refer to the provided documentation here.
It seems there might be concerns about the software you're using. I understand you're not seeking assistance with those particular programs, but I'm wary of supporting systems that could involve legal issues.
I recognize your decision not to assist here, thank you for your support thus far. I was also aware this would be observed, yet I didn’t remove any entries from the logs.
I still hope not all of you share the same view, since judging someone based on their system programs isn’t fair, especially when the real problem lies elsewhere. The way people access media shouldn’t become a subject of debate or discussion.
If what you’re saying stems from something in the logs suggesting my issue might be linked to one of these programs, it could shift how I see your point.
Spoiler: Being a woman and voting used to be illegal, just like being Black and free was once against the law in America. Outsourcing child labor overseas is seen as legal, while morality and legality don’t always align. Piracy isn’t a lost sale—it’s a transaction that never existed.
Many things seem unreasonably illegal, and I live in a country where rules differ. If you missed this, you’re joining a group of people who once sold their own computer parts to survive.