F5F Stay Refreshed Hardware Desktop You need assistance.

You need assistance.

You need assistance.

Pages (2): 1 2 Next
T
tippestwolf70
Member
227
01-12-2018, 08:28 AM
#1
Recently, my PC seems to stop crashing unexpectedly, no matter what I'm doing. It starts up normally but freezes under light stress. I've updated drivers and BIOS, even reset the system to check, but crashes still occur around 3 minutes into Rainbow Six Siege. The errors vary each time, but most point to memory management issues. My RAM tests show no problems. Help needed—I'm stuck.

System specs: Ryzen 7 2700X, MSI B450 Tomahawk (2×8GB), Corsair Vengeance RGB Pro DDR4 3200MHz, GTX 1060, 3GB Corsair H100i Pro AIO, 1TB Toshiba HDD, 650W 80+Bronze power supply.
T
tippestwolf70
01-12-2018, 08:28 AM #1

Recently, my PC seems to stop crashing unexpectedly, no matter what I'm doing. It starts up normally but freezes under light stress. I've updated drivers and BIOS, even reset the system to check, but crashes still occur around 3 minutes into Rainbow Six Siege. The errors vary each time, but most point to memory management issues. My RAM tests show no problems. Help needed—I'm stuck.

System specs: Ryzen 7 2700X, MSI B450 Tomahawk (2×8GB), Corsair Vengeance RGB Pro DDR4 3200MHz, GTX 1060, 3GB Corsair H100i Pro AIO, 1TB Toshiba HDD, 650W 80+Bronze power supply.

X
xxxLazersxxx
Member
117
01-12-2018, 09:30 AM
#2
Yes, it fits in slots 2 and 4. XMPP is active. Voltage is set to 1.35.
X
xxxLazersxxx
01-12-2018, 09:30 AM #2

Yes, it fits in slots 2 and 4. XMPP is active. Voltage is set to 1.35.

X
xEpicSniiperz
Member
65
01-12-2018, 09:52 AM
#3
Minimal load, the problem lies with the CPU cooling. After a few minutes (when idle), RAM might fail due to speed or voltage issues. The CPU itself could simply be overheating.
X
xEpicSniiperz
01-12-2018, 09:52 AM #3

Minimal load, the problem lies with the CPU cooling. After a few minutes (when idle), RAM might fail due to speed or voltage issues. The CPU itself could simply be overheating.

E
EPIC_GT
Member
219
01-26-2018, 06:03 AM
#4
Ram is located in channels 2 and 4, XMP protocol is active, voltage set at 1.35V.
E
EPIC_GT
01-26-2018, 06:03 AM #4

Ram is located in channels 2 and 4, XMP protocol is active, voltage set at 1.35V.

R
RebelliousOG
Member
52
01-26-2018, 06:40 AM
#5
I understand how to tell if it's your RAM, but there are other ways too.
R
RebelliousOG
01-26-2018, 06:40 AM #5

I understand how to tell if it's your RAM, but there are other ways too.

L
Liam_M_5000
Member
72
01-26-2018, 03:07 PM
#6
memtest86 appears to indicate a memory problem. Consider raising the SOC voltage slightly, around 1.05 or 1.1.
L
Liam_M_5000
01-26-2018, 03:07 PM #6

memtest86 appears to indicate a memory problem. Consider raising the SOC voltage slightly, around 1.05 or 1.1.

M
MafiaMoose
Junior Member
43
01-31-2018, 09:43 AM
#7
Test each stick individually to check if the issue appears consistently. If it occurs with every stick, it's unlikely to be a RAM problem (unless all are faulty, which is rare). Enter the BIOS and confirm you're using the default settings for CPU/ram timings.
M
MafiaMoose
01-31-2018, 09:43 AM #7

Test each stick individually to check if the issue appears consistently. If it occurs with every stick, it's unlikely to be a RAM problem (unless all are faulty, which is rare). Enter the BIOS and confirm you're using the default settings for CPU/ram timings.

D
DollynhoG4mer
Junior Member
1
02-02-2018, 10:17 AM
#8
Alright, give it a shot and let me know how it goes.
D
DollynhoG4mer
02-02-2018, 10:17 AM #8

Alright, give it a shot and let me know how it goes.

R
RockRippa
Junior Member
44
02-02-2018, 04:09 PM
#9
XMP functions as an overclock; if the processor can't handle it, that might be the issue.
R
RockRippa
02-02-2018, 04:09 PM #9

XMP functions as an overclock; if the processor can't handle it, that might be the issue.

T
TrebleClef16
Junior Member
3
02-03-2018, 07:23 AM
#10
I've tested each one individually, but the issue still happened with both.
T
TrebleClef16
02-03-2018, 07:23 AM #10

I've tested each one individually, but the issue still happened with both.

Pages (2): 1 2 Next