F5F Stay Refreshed Hardware Desktop Modern RIG BSODs seem to be becoming outdated.

Modern RIG BSODs seem to be becoming outdated.

Modern RIG BSODs seem to be becoming outdated.

X
xPumma
Member
186
10-06-2022, 05:14 PM
#1
Hey everyone! I recently installed a new setup and it's experiencing every possible BSOD. It's tough to pinpoint the cause because each error seems unique. I've changed the NVME, RAM, CPU, and power supply—nothing fixed. Now I'm stuck between a MOBO or a CPU issue. This is the stage where swapping components isn't easy since I already have another CPU available. Which one is more likely to be the problem? I've run intensive tests, and they finish smoothly until a crash later. It looks like it's not related to performance under load. Any advice would be super helpful. Hardware: CPU 7950X, GPU 7900X, MOBO ASUS TUF X670e+, PSU EVGA 1000W Gold GQ, RAM Corsair 32GB 6000MHz 36TXEPS, Cooler NH-D15, NVME SN850x 2TB & P3 2TB.
X
xPumma
10-06-2022, 05:14 PM #1

Hey everyone! I recently installed a new setup and it's experiencing every possible BSOD. It's tough to pinpoint the cause because each error seems unique. I've changed the NVME, RAM, CPU, and power supply—nothing fixed. Now I'm stuck between a MOBO or a CPU issue. This is the stage where swapping components isn't easy since I already have another CPU available. Which one is more likely to be the problem? I've run intensive tests, and they finish smoothly until a crash later. It looks like it's not related to performance under load. Any advice would be super helpful. Hardware: CPU 7950X, GPU 7900X, MOBO ASUS TUF X670e+, PSU EVGA 1000W Gold GQ, RAM Corsair 32GB 6000MHz 36TXEPS, Cooler NH-D15, NVME SN850x 2TB & P3 2TB.

H
Hapkidokane
Junior Member
5
10-13-2022, 07:40 PM
#2
No, not everything is in the BIOS.
H
Hapkidokane
10-13-2022, 07:40 PM #2

No, not everything is in the BIOS.

S
SushiCherry
Member
227
10-20-2022, 10:42 AM
#3
I started with the standard setup right away, including EXPO profiles both enabled and disabled. The issue persists with crashes.
S
SushiCherry
10-20-2022, 10:42 AM #3

I started with the standard setup right away, including EXPO profiles both enabled and disabled. The issue persists with crashes.

N
Nautilus12
Member
106
10-21-2022, 02:08 AM
#4
You could run a MemTest if the RAM reports issues, but since you're confident the RAM is fine, the motherboard might be the problem. This could help pinpoint the issue.
N
Nautilus12
10-21-2022, 02:08 AM #4

You could run a MemTest if the RAM reports issues, but since you're confident the RAM is fine, the motherboard might be the problem. This could help pinpoint the issue.

P
perrinoid
Member
137
10-21-2022, 08:30 AM
#5
I ran memtest and it succeeded beautifully. Tested on my system and a Kingston Fury model. I’ll check what I can do regarding the memory card swap.
P
perrinoid
10-21-2022, 08:30 AM #5

I ran memtest and it succeeded beautifully. Tested on my system and a Kingston Fury model. I’ll check what I can do regarding the memory card swap.

B
bigcackinator
Member
59
10-26-2022, 04:31 PM
#6
Have you shared the error codes from the BSOD? Have you performed a memory dump analysis using windbg? Refer to the guide on analyzing .dmp files in Windows 10 (helpdeskgeek.com) for instructions on examining a dump created during a BSOD. Move to the section "How to Analyze Windows Memory Dump Files Using WinDbg." Open the dump file. Consider configuring a fixed size for virtual memory on the non-OS drive. Turn off the page file on the OS drive. 32GB*1.5*3=144GB (147456MB)
B
bigcackinator
10-26-2022, 04:31 PM #6

Have you shared the error codes from the BSOD? Have you performed a memory dump analysis using windbg? Refer to the guide on analyzing .dmp files in Windows 10 (helpdeskgeek.com) for instructions on examining a dump created during a BSOD. Move to the section "How to Analyze Windows Memory Dump Files Using WinDbg." Open the dump file. Consider configuring a fixed size for virtual memory on the non-OS drive. Turn off the page file on the OS drive. 32GB*1.5*3=144GB (147456MB)