Prstorero

Stressed things for a bit and haven't had any crashes, I feel safe to say the new CPU solved the issue. I went ahead and marked one of your replies as the solution @code_

So far so good with the new CPU, no crashes yet. I'm getting drivers installed and will be doing updates. Once all that is done I'll run some stress tests!

Yeah, that will be worth exploring if the CPU doesn't solve the issue. There don't seem to be a lot of options for itx am4, so we'll see what happens tomorrow. Hoping I don't have to return two motherboards lol.

F13 actually isn't a supported BIOS for this board. I struggled with this for a while the other day, it turns out this is the page for what I have: https://www.gigabyte.com/Motherboard/B550I-AORUS-PRO-AX/support#support-dl-bios (bookmarked since it was such a pain to find the first time). The board came with FB and I had tried upgrading it to FCc which didn't change anything. Note 1.3 and 1.2 seem the same based on the fact they list the same checksum for the file. When you just Google the board, it brings up version 1.0, which I'm not sure if they make anymore. But I have either 1.2 or 1.3 which don't support the bios files for 1.0

Thanks. I'm wondering the same, but don't have high hopes it's the memory since I tried two different sets that have been in use for years in their prior systems with 0 crashes with heavy use. Of course that doesn't mean it's not possible and I plan to let memtest run until tomorrow morning to see if any errors do happen. I'll definitely make an update once the new CPU comes in to see if that solves the problem.

I went ahead and ordered one - it should be here tomorrow morning for me to try out. It's a bit hard to say what the most common was, but probably between ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY and KMODE_EXCEPTION_NOT_HANDLED Edit: It does not show an actual error code, unfortunately. Just the worded stop code. Example:

I have tried booting Windows installation media from a flash drive, it results in an immediate BSOD as well. The drive that had the OS install wasn't a factor as it was removed from the board. I can get into the BIOS and memtest has been running fine. I had also tried a USB containing linux to have something to try that wasn't Windows-based and that crashes during the boot process as well.

Hey everyone. After a lot of testing and trying to rule things out, I'm pretty stumped at the moment and hoping you guys have some ideas for what else I could potentially try. OS - Windows 11 (note crashing also happens booting flash drives of a windows installation media and Macrium) x86 (32-bit) or x64 - 64 bit What OS was originally installed on the system - Nothing, Windows 11 installed fresh Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from a retailer) - Purchased by me Age of system (hardware) - All components are new except the RAM, which was purchased January 10th 2019 Age of OS installation - have you re-installed the OS - Brand new install CPU model - Ryzen 5600G Video Card model - Integrated graphics MotherBoard - (if NOT a laptop) - Gigabyte B550I AORUS PRO AX Mini ITX AM4 Motherboard Power Supply - brand & wattage (if laptop, skip this) - EVGA SuperNOVA 650 GM 650 W 80+ Gold System Manufacturer - Myself Exact model number (if OEM or laptop) - N/A Laptop or Desktop - Desktop The problem: I get either an immediate BSOD or shortly after attempting to boot some media. I've tried booting a new SSD with a fresh copy of Windows 11, a flash drive containing Windows 11 installation media, and a flash drive containing Macrium Reflect. All of these experience the same issue. I have gotten numerous BSOD's, each of which will be listed below. The first occurrence: I installed some Windows updates and rebooted after installation, then was never able to boot again. But I feel that this is coincidental given the crashes when booting from flash drives BSOD's that happened: CRITICAL_PROCESS_DIED (only saw this one the couple times when Macrium managed to boot to crash later randomly or when attempting to shut down) ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY KMODE_EXCEPTION_NOT_HANDLED PAGE_FAULT_IN_NONPAGED_AREA What I have tried: Remove all hardware except what's necessary including the SSD to just boot flash drives (including SSD being removed to rule out faulty Windows driver) A different PSU from my old system that has been running perfectly for 5 years New motherboard Different set of RAM I tried a set from my old system, same issues occurred I started to wonder if the sticks I had from both systems weren't on the QVL for the board, but it turns out that one set is I did one run of memtest86 on the QVL RAM for 9 hours overnight and had 0 errors Only run on one of the sticks, which is all I was using for testing at the time One RAM stick at a time trying different slots Updated UEFI BIOS I think that covers all the things I've tried. I'm currently in the process of running memtest again but plan on this run being for 24+ hours to see what the result is. I don't hold a lot of hope for this being the issue since there hasn't been a single crash in the old system for years, but I suppose you never know. I'm out of ideas aside from replacing the CPU. I know it's not typically likely, but I would like to see if anyone has additional ideas before I pull the trigger on a CPU replacement to try that.

I did not get the time to test the old GPU in the same configuration, but there has not been one instance of the screen not waking up in over a week now, so I'm comfortable to mark this as solved. I strongly believe the issue was a dying PCI-E slot.

Alright so the new GPU came in yesterday. After putting it in and booting up the system, it ended up completely freezing on the lockscreen. I decided to go into the BIOS, and it froze there as well. Long story short, it seems the PCI-E slot started malfunctioning. As soon as I moved the card to another one, it booted up flawlessly with no freezing whatsoever. So the initial problem to begin with may very well have been the slot starting to go bad. Unfortunately I don't have the time to put the old GPU back in this weekend and see what happens, but that's my suspicion right now.

I just placed an order for a new GPU. Last night when updating the drivers, the screen froze and became unresponsive. Upon a reboot, the GPU fans got extremely loud and it took about 8 restarts to get the system to boot normally, and even then there were all sorts of artifacts covering the top quarter of the display, so this thing was definitely on its last legs. The card will be here Friday and I'll be sure to update this after I install and test it.

Hmm dang. Guess it may be time to just buy a new one, kind of a shame haha. I updated the drivers again due to all the crashes from before, so if it keeps happening, I guess I'll just have to get a new one.

Do you mind if I ask how long you had yours for? This one has been running with no problems since 2011, so it seems strange I would just now find out it's faulty. I would have to buy a new one to test it as I don't have any spares, so I'm trying to rule out any possibilities before needing to buy one.

New update: I just got home and was told it restarted for a windows update. When I went to move the mouse, the screen didn't come on. I checked what the update was and it was audio drivers, which failed to install. I also looked at the reliability history again and there's over 20 hardware errors in there. I didn't go through each one, but all the ones I did open pointed to NVIDIA. So since the screen didn't wake, this older graphics driver didn't seem to work, and I can't go any older since the crashes would probably become a lot worse. Oh ya and there was also a BSOD when I turned the system back on after a force shut down for "Video TDR Failure", but that's probably related to the non-Windows 10 supported graphics driver. Not really sure what to try at this point, any other suggestions, @Tedster?

Thought I would give an update of how things are going. So far I haven't had any instances of the screen not waking (but sometimes it can take a day or two to happen), but I have noticed three times in one day that the display driver stopped working and recovered. And the current driver is only from July, so things may get even worse if I try running an older one. So far it seems it's a trade-off between newer drivers with monitor wake up issues or older drivers with crashing issues. I'd still like to test it over today and tomorrow before trying to draw any real conclusions, but this is what I think so far. Edit: I just pulled up the reliability report and it lists 6 hardware errors in less than an hour time span. All but one of them list "LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys" as the bucket ID. So it does seem like the older graphics driver is crashing quite a lot. It looks like an older driver version on Windows 10 won't be a solution if it causes that many crashes.