Extreme BSOD issues affecting a modern high-performance computer.
Extreme BSOD issues affecting a modern high-performance computer.
These logs are just raw data; they’re not very useful unless you spend time analyzing them. Tools like BlueScreenView or WinDbg provide better insights. ntoskrnl.exe usually shows a generic error message. BSV can help by filtering crash logs and displaying errors automatically.
Sorry, I didn’t want to seem too pushy. Really appreciate you responding while you’re busy! I’m just not sure how this information might help identify the reason behind my symptoms.
The issues I'm encountering with the BSV data suggest my RAM might be faulty, possibly due to a defective slot on the board. How have you previously checked the RAM? Did you simply swap it out? Or have you performed a memory test using Memtest86 after the replacement? Please confirm if you've completed that process. If either test reveals errors, your RAM or motherboard slots could be the problem. Since you experienced similar problems with two different systems, it's more likely the motherboard's RAM slots are affected. A reliable way to verify would be to individually test each RAM stick in its respective slot on the board, including both of your sticks. I recommend following up with additional testing as suggested. Based on what you've done so far, apart from further RAM checks, the only remaining options seem to be replacing the motherboard or PSU. Those are the primary possibilities left. If you're still facing difficulties, it might be beneficial to take your system to a repair shop for professional evaluation and stress relief.
Using one stick of RAM should allow you to start the system in any of the four slots. If a RAM stick isn’t working, it likely means either the slot is faulty or the stick itself is defective. You should check both sticks in the same slot to determine if the issue lies with that specific stick. Testing them in slots A1 and A2—where they function normally in other slots—would indicate the problem is with the slot, not the RAM.
Alright, I just removed my GPU and powered on the PC with RAM set to A2 and B2. Everything seemed normal and the system booted up. I took out both RAM sticks and inserted the first one into the A1 slot. After waiting five minutes, there was still nothing—no boot, no BIOS, no video signal. I then tried the second stick in A1, but again, no response. Given this, it seems likely the motherboard is faulty. I already gave the CPU a week to work in another machine without issues. Thanks for your help!
After reconsidering, I came across this forum discussion. Sam Forbis clarifies that it's more than just a suggestion—it's a necessity. The manual's diagram description can be confusing. You need to install the initial module in DIMMA2 first, and then you decide how to proceed afterward. When both sticks were connected to A1 and A2, they appeared in the BIOS, suggesting the issue isn't related to RAM. I think it's time for MemTest to verify things.
I’m starting memtest on the A2 B2 setup. If no errors appear, I’ll move to the A1 A2 configuration just to confirm. I also opened a gigabyte support ticket asking whether the board would boot with only A1 installed. I read about a chipset driver update and noticed a questionable changelog mentioning USB 4.0 stabilization fixes for ASMedia controllers like ASM4242. Since my board includes an ASMedia USB4 controller, that could be relevant. I’ll install the update and see if it helps (after all, this troubleshooting is tough). This is definitely the most challenging work I’ve ever done.
Bluescreenview (And WhoCrashed) isn't working well. It's a poor utility. Share the actual dump files. Visit C:\Windows\Minidump and verify you have any minidump files. If present, return to the Windows directory and move the Minidump folder to the Downloads folder (desktop works if OneDrive isn't syncing). Compress the moved folder and attach it to a post. Please follow instructions carefully—Windows doesn’t allow file changes there. EDIT: It seems the dump files weren’t mentioned in a previous update. The two Attempted_Write_To_Readonly_Memory references point to the AMD I2C controller. For the two Driver_Power_State_Failure crashes, they target different components. The first points to an ASMedia controller (no device ID found in the PCIe database), which could relate to SATA or USB. The second refers to the PCIe subsystem and provides a device ID that might indicate the connected port, though AMD often reuses IDs across ports. EDIT2: The ASMedia controller’s hardware ID is VEN_1B21&DEV_2423. The PCIe ID we have is VEN_1022&DEV_43F5 (VEN = vendor, DEV = device, 1022 = AMD). If you need more details, share additional dump files. BIOS is up to date, so reaching the source isn’t necessary. Consider updating the chipset from AMD. Gigabyte’s chipset drivers have had bugs recently. Also, Gigabyte Control Center has caused similar crashes; uninstall it if installed. Memory problems could be random, but they might explain the situation. More dump files would help clarify the issue.