Overclock.net › Forums › Intel › Intel CPUs › Prime crashed after ~5 hours. (448K FFT) BSOD is 0x1A... Can running prime damage RAM?
New Posts  All Forums:Forum Nav:

Prime crashed after ~5 hours. (448K FFT) BSOD is 0x1A... Can running prime damage RAM?

post #1 of 7
Thread Starter 
...I've been told 0x1A = bad memory, but I had run multiple iterations of prime/IBT before this (including the suggested 1344, 1792, and 2688 FFT lengths for 20 mins each at 80-90% memory if I wanted stability for gaming), and the memory was never a problem.

However when I tried every possible configuration of RAM (stick 1 in original slot, stick 2 out; stick 1 in stick 2's original slot, etc.), it turns out that one of the sticks is bad and the other is fine (via Windows Memory Diagnostic and MemTest86+).

The previous BSODs I got with prime was me trying to push it to 4.5ghz with too little voltage so the BSOD had nothing to do with memory either.

What gives? Does this mean prime can damage memory?

specs:

i5-3570k
seasonic 620w
Asrock z77 extreme4
g.skill 8gb RAM (F3-12800CL9D-8GBXL)
post #2 of 7
It can't damage RAM that wasn't already bad.
post #3 of 7
It can't damage ram but only give you an indication of your defective ram.
Jay
(13 items)
 
  
CPUMotherboardGraphicsRAM
FX 8350 4.4Ghz at 1.36v GA 78LMT USB3 Rev 5.0 Sapphire R9 285 OC 16GB Kingston Savage Ram 
Hard DriveHard DriveCoolingOS
1TB Western Digital 500GB Seagate Barracuda Noctua NH-D15S Windows 8.1 
MonitorPowerMouseMouse Pad
Asus MG279Q Fressync OCZ ZS 650 Watt PSU Dragonwar ELE-G9 Dragonwar 
  hide details  
Reply
Jay
(13 items)
 
  
CPUMotherboardGraphicsRAM
FX 8350 4.4Ghz at 1.36v GA 78LMT USB3 Rev 5.0 Sapphire R9 285 OC 16GB Kingston Savage Ram 
Hard DriveHard DriveCoolingOS
1TB Western Digital 500GB Seagate Barracuda Noctua NH-D15S Windows 8.1 
MonitorPowerMouseMouse Pad
Asus MG279Q Fressync OCZ ZS 650 Watt PSU Dragonwar ELE-G9 Dragonwar 
  hide details  
Reply
post #4 of 7
Thread Starter 
Quote:
Originally Posted by Thracks View Post

It can't damage RAM that wasn't already bad.

Thanks, this makes me feel a lot better. How did it not detect the errors though when I was using close to 100% of available RAM for nearly every iteration of IBT/prime?
post #5 of 7
I've had RAM errors in Memtest on the 4 or 5th loop, which is like 7 hours of testing. RAM won't always error right off the bat.

On that board you should be able to 100% unlink your RAM. Set it to the rated voltage, speed, and timings and leave it there. Then just increase the multiplier. You really shouldn't be getting RAM errors when overclocking on Sandy/Ivy, unless you actually overclocked the RAM. If you did overclock the RAM, set it back to stock. If you didn't, run memtest on it overnight.
The Leviathan
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 6700k @ 4.7GHz MSI Z170A Gaming M7 12GB NVIDIA Titan X (Pascal) 32GB G.Skill Ripjaws V (DDR4 3200) 
Hard DriveHard DriveCoolingCooling
2x 1TB Samsung 960 PRO 193TB unRAID Server 3x 140mm Noctua NF-A14 Noctua NH-D15 
OSMonitorKeyboardPower
Windows 10 Pro x64 65" LG 65E6P (4K OLED) Ducky DK9008 Shine 3  Corsair AX860 
CaseMouseAudioAudio
Corsair Obsidian 750D Logitech G502 Proteus Sprectrum Denon X7200WA (Receiver) 2x Klipsch RF-7 (Front Speakers) 
AudioAudioAudioAudio
4x Klipsch RS-62 (Surround Speakers) Klipsch RC-64 (Center Speaker) 4x Klipsch CDT-5800-C II (Atmos Speakers) 2x SVS PB16-Ultra (Subwoofers) 
  hide details  
Reply
The Leviathan
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 6700k @ 4.7GHz MSI Z170A Gaming M7 12GB NVIDIA Titan X (Pascal) 32GB G.Skill Ripjaws V (DDR4 3200) 
Hard DriveHard DriveCoolingCooling
2x 1TB Samsung 960 PRO 193TB unRAID Server 3x 140mm Noctua NF-A14 Noctua NH-D15 
OSMonitorKeyboardPower
Windows 10 Pro x64 65" LG 65E6P (4K OLED) Ducky DK9008 Shine 3  Corsair AX860 
CaseMouseAudioAudio
Corsair Obsidian 750D Logitech G502 Proteus Sprectrum Denon X7200WA (Receiver) 2x Klipsch RF-7 (Front Speakers) 
AudioAudioAudioAudio
4x Klipsch RS-62 (Surround Speakers) Klipsch RC-64 (Center Speaker) 4x Klipsch CDT-5800-C II (Atmos Speakers) 2x SVS PB16-Ultra (Subwoofers) 
  hide details  
Reply
post #6 of 7
Thread Starter 
Quote:
Originally Posted by Murlocke View Post

I've had RAM errors in Memtest on the 4 or 5th loop, which is like 7 hours of testing. RAM won't always error right off the bat.
On that board you should be able to 100% unlink your RAM. Set it to the rated voltage, speed, and timings and leave it there. Then just increase the multiplier. You really shouldn't be getting RAM errors when overclocking on Sandy/Ivy, unless you actually overclocked the RAM. If you did overclock the RAM, set it back to stock. If you didn't, run memtest on it overnight.

Yeahp I set it to 9-9-9-24 and when I removed the faulty stick of RAM memtest ran without any problems, windows memory diagnostic ran without any problems either. I'm getting it RMA'd though as the store needs both sticks so I can get a replacement.

When they get here, should I run memtest with BOTH sticks in place already? Or 1 at a time?
post #7 of 7
1 at a time is preferred.
Jay
(13 items)
 
  
CPUMotherboardGraphicsRAM
FX 8350 4.4Ghz at 1.36v GA 78LMT USB3 Rev 5.0 Sapphire R9 285 OC 16GB Kingston Savage Ram 
Hard DriveHard DriveCoolingOS
1TB Western Digital 500GB Seagate Barracuda Noctua NH-D15S Windows 8.1 
MonitorPowerMouseMouse Pad
Asus MG279Q Fressync OCZ ZS 650 Watt PSU Dragonwar ELE-G9 Dragonwar 
  hide details  
Reply
Jay
(13 items)
 
  
CPUMotherboardGraphicsRAM
FX 8350 4.4Ghz at 1.36v GA 78LMT USB3 Rev 5.0 Sapphire R9 285 OC 16GB Kingston Savage Ram 
Hard DriveHard DriveCoolingOS
1TB Western Digital 500GB Seagate Barracuda Noctua NH-D15S Windows 8.1 
MonitorPowerMouseMouse Pad
Asus MG279Q Fressync OCZ ZS 650 Watt PSU Dragonwar ELE-G9 Dragonwar 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
  • Prime crashed after ~5 hours. (448K FFT) BSOD is 0x1A... Can running prime damage RAM?
Overclock.net › Forums › Intel › Intel CPUs › Prime crashed after ~5 hours. (448K FFT) BSOD is 0x1A... Can running prime damage RAM?