F5F Stay Refreshed Hardware Desktop BSOD recurrencely during setup suggests a potential memory problem.

BSOD recurrencely during setup suggests a potential memory problem.

BSOD recurrencely during setup suggests a potential memory problem.

U
UDK
Member
221
08-06-2022, 06:53 PM
#1
Hello! After assembling my first PC, I frequently encounter a BSOD every hour (sometimes more often). The error codes varied a lot and made me think about memory problems. Some applications would crash just before the BSOD appeared. Overall, the system runs smoothly—temperatures are low, software installs and games work fine. Here’s what I’m using: https://de.pcpartpicker.com/list/66KyQ6

To tackle the issue, I took these steps:
- Analyzed memory dumps from crashes; most showed generic kernel errors.
- Ran Windows Memory Diagnostic—it flagged hardware issues but didn’t give clear details.
- Updated BIOS to the latest version; it slightly improved stability (BSOD delayed).
- Disabled XMP to run RAM at 2133 MHz instead of 3200 MHz.
- Re-ran Memory Diagnostic, which still showed some problems but fewer.
- Attempted a Windows reinstall, encountering an error possibly linked to memory (code 0xc0000005).

Since I’m new to PC building, I’m anxious but determined. My next moves:
- Remove one RAM stick at a time to check if the problem persists.
- If that doesn’t help, consider testing with different RAM modules or checking for physical damage.
- Ask for more advice—maybe there’s a simpler fix I missed.

Thank you for your support; this situation is really stressful but I’m committed to fixing it.
U
UDK
08-06-2022, 06:53 PM #1

Hello! After assembling my first PC, I frequently encounter a BSOD every hour (sometimes more often). The error codes varied a lot and made me think about memory problems. Some applications would crash just before the BSOD appeared. Overall, the system runs smoothly—temperatures are low, software installs and games work fine. Here’s what I’m using: https://de.pcpartpicker.com/list/66KyQ6

To tackle the issue, I took these steps:
- Analyzed memory dumps from crashes; most showed generic kernel errors.
- Ran Windows Memory Diagnostic—it flagged hardware issues but didn’t give clear details.
- Updated BIOS to the latest version; it slightly improved stability (BSOD delayed).
- Disabled XMP to run RAM at 2133 MHz instead of 3200 MHz.
- Re-ran Memory Diagnostic, which still showed some problems but fewer.
- Attempted a Windows reinstall, encountering an error possibly linked to memory (code 0xc0000005).

Since I’m new to PC building, I’m anxious but determined. My next moves:
- Remove one RAM stick at a time to check if the problem persists.
- If that doesn’t help, consider testing with different RAM modules or checking for physical damage.
- Ask for more advice—maybe there’s a simpler fix I missed.

Thank you for your support; this situation is really stressful but I’m committed to fixing it.

E
ExplodingNt
Member
107
08-06-2022, 06:53 PM
#2
Because it's two sticks, test each one separately and try again. Consider running a memory check if one fails. Another option is to swap the slots on the motherboard—use the other two if possible. Keep them at their default speeds until you identify the issue.
E
ExplodingNt
08-06-2022, 06:53 PM #2

Because it's two sticks, test each one separately and try again. Consider running a memory check if one fails. Another option is to swap the slots on the motherboard—use the other two if possible. Keep them at their default speeds until you identify the issue.

P
PimQ1
Member
163
08-06-2022, 06:53 PM
#3
I concur with @Naijin – verify each memory stick using Passmark Memtest86, one at a time.
P
PimQ1
08-06-2022, 06:53 PM #3

I concur with @Naijin – verify each memory stick using Passmark Memtest86, one at a time.

I
iStrafeRunner
Member
169
08-06-2022, 06:53 PM
#4
This situation has been ongoing since the system was set up. Besides the changes you mentioned, I’d revert to the fundamentals. Run a temporary checker program such as hwinfo to spot any unusual readings—like one core running significantly hotter than others. Review the Windows event logs for WHEA errors (Event Viewer > Applications > Microsoft > Windows). Open the tower and verify all components are properly seated, connectors are secure, and fans are operating when under load. If cables are tightened too much during tidying, gently loosen them to test. It seems a memory issue might be involved, but you could also try installing a different SSD as another diagnostic step.
I
iStrafeRunner
08-06-2022, 06:53 PM #4

This situation has been ongoing since the system was set up. Besides the changes you mentioned, I’d revert to the fundamentals. Run a temporary checker program such as hwinfo to spot any unusual readings—like one core running significantly hotter than others. Review the Windows event logs for WHEA errors (Event Viewer > Applications > Microsoft > Windows). Open the tower and verify all components are properly seated, connectors are secure, and fans are operating when under load. If cables are tightened too much during tidying, gently loosen them to test. It seems a memory issue might be involved, but you could also try installing a different SSD as another diagnostic step.

R
RubenLexus
Member
63
08-06-2022, 06:53 PM
#5
Hey everyone, thanks for your help! I ran MemTest86 after rearranging the RAM sticks. The results showed some issues with stick A in slot 2 and stick B in slot 4. After swapping them around, the tests completed without errors. This suggests there might be a problem with slot 2. What should we do next?
R
RubenLexus
08-06-2022, 06:53 PM #5

Hey everyone, thanks for your help! I ran MemTest86 after rearranging the RAM sticks. The results showed some issues with stick A in slot 2 and stick B in slot 4. After swapping them around, the tests completed without errors. This suggests there might be a problem with slot 2. What should we do next?

K
kalleboii
Senior Member
738
08-06-2022, 06:53 PM
#6
Follow the motherboard guide step by step. The setup isn't about the number of slots—like 1, 2, 3, or 4. A bad slot could be just dirty, broken, or the CPU might have problems such as a bent pin or damaged controller.
K
kalleboii
08-06-2022, 06:53 PM #6

Follow the motherboard guide step by step. The setup isn't about the number of slots—like 1, 2, 3, or 4. A bad slot could be just dirty, broken, or the CPU might have problems such as a bent pin or damaged controller.