can a wrong Case Latency cause random crashes

Toggle sidebar Toggle sidebar
J

julienPC

Honorable
Nov 22, 2013
8
0
10,510
I'm new to PCs (I had Macs for 20 years). And this is my first real problem with the PC I built 3 months ago, also my first post here.

My computer crashes after about 10 minutes using it. Then it attempt to restart and crashed almost immediatly again and gets in a loop of restart and crashes. I have to switch everything up, unplug and wait in order to restart and get to the Bios or start in safe mode.
And I can't identify which process is making it crash as I don't get any crash report or alert message. It was stable for about 8 weeks after the build and the problems started two weeks ago. I'm using windows 7 and I tried to come back to a stable I thought was stable (early November). The first few crashes were giving me an alert message about failed over clocking but I didn't overclock anything. It's actually "under clocked" and I suspect this to be a possible source of the problem.

I have a P9X79 Mobo and I made the mistake of getting DRAM which wasn't in the Qualified Vendor List (QVL), I have - (4 X 8GB GSKILL DDR3 1866Mhz CL 8-9-9-24). The BIOS default settings run the DRAM at 1333Mhz.
If I use the XMP option it runs the the DRAM at 1867Mhz and the crashes issue remain.

Fact is the system worked for almost two months with the DRAM running a 1333Mhz. And when I test the DRAM with the tools provided with Windows 7 no errors are reported.

Can the wrong Case Latency cause crashes?

Should I replace my DRAM for something in listed in the QVL?

The learning curve is steep!
Thanks for your time!

---
Build:
OS: Window 7 Premium 64
MOBO: ASUS P9X79
CPU: i7 4930
MEMORY: 8Gx4 GSKILL F3-1866C8Q-32GTX
CPU: I7 4930K 3.4G 12M
WATER COOL CORSAIR H100I
GPU: AMD FirePro W9000
PSU: CORSAIR AX860I 860W
SSD: 240G KHX SH103S3/240G
HDD: Seagate 3T Baracuda
 
Solution
Tradesman1
Well glad to hear all is well, may have been a Win problem that was growing and finally noticed itself ;) Have fun ;) May want to close the thread
Sort by date Sort by votes
Tradesman1

Tradesman1

Legenda in Aeternum
Jun 5, 2013
67,883
40
126,960
Was this a single package of DRAM - the Tridents - or is it a combination of two 2 stick packages - if so are they the Tri's, RJ Xs or RJ Zs....let me know what model, there's a couple of things that can be the problem that normally is easily sovled
 
Upvote 0 Downvote
J

julienPC

Honorable
Nov 22, 2013
8
0
10,510


Thanks Tradesman1 for trying to help me.

yes - Single 32GB package purchased on Newegg. I can't tell what model which on is is (RJ Xs or RJ Zs) - it's not specified even on G.Skill's website. That's the complete reference: G.SKILL Trident X Series 32GB (4 x 8GB) 240-Pin DDR3 SDRAM DDR3 1866 (PC3 14900) Desktop Memory Model F3-1866C8Q-32GTX

New developments on my issue: The crash happens after about 6 minutes however the system started normally, in Safe Mode or I'm in the the BIOS, so it shouldn't be a driver issue, right?
The strange thing is the timing - always about 6 minutes.

Looking forward to hearing your ideas.
 
Upvote 0 Downvote
J

julienPC

Honorable
Nov 22, 2013
8
0
10,510


Thanks,
I did what you suggested - I updated the BIOS to the latest one, did the changes and it didn't sort out the issue with the computer crashing within 5 minutes.
After restart I got the window saying Overclocking Failed.

Since there was 2 new factors (new Bios and a modified XMP profile) I've tried to run the system again with XMP disabled to see if the new BIOS alone worked.
When I restarted I went in the BIOS and waited 7 minutes and it crashed.

I guess I need to troubleshoot using a Ram that's in the QVT, right?. I'm still puzzled it worked solidly for 2 months before the problem started.
 
Upvote 0 Downvote
J

julienPC

Honorable
Nov 22, 2013
8
0
10,510


No, the problem appeared after a routine OS updates. At one point I remember seeing the Corsair iLink dongle (that thing connected to the PSU) starting to flash intermittently orange instead of constant green so I updated the the driver (or is it firmware?). And it kept flashing orange. I still think that the other issue outside of the memory could be a bad management of the PSU given the way the computer behaves when it crashes: the computer will only successfully restart after 5 minutes off, like if there was a power overload that needed to dissipate.

I know there can be dozens of reasons a computer crashes - what really puzzles me is the lack of error message outside of the "overclocking failed". And also the fact that the computer worked for about 2 months without any problem.

I'm going to bite the bullet and just wipe everything clean and reinstall the system from scratch.
And if the problem persists with a fresh system then it's definitely a hardware problem.

Anyway, thanks for daring trying to help a rookie!


 
Upvote 0 Downvote
J

julienPC

Honorable
Nov 22, 2013
8
0
10,510


Well, for some reasons windows decided to launch a system repair and the issue was gone in 2 minutes. Conclusion: it was a system issue, I don't know which one because I can't find where those things are reported. Why it didn't do earlier - during one of the 50 reboot I did during the last 3 days? I have no idea. I wish I had learn something in the process.

Well, thank to you Tradesman1 I now know how to get my memory running normal speed. I'll try again as soon as I managed to organize a backup of the system in it's current stable form.




 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom