New Build is freezing, is my Motherboard to blame?

Toggle sidebar Toggle sidebar
J

JulianGK

Reputable
Aug 25, 2015
6
0
4,510
Hi everyone,

This is my first posting to Tom's Hardware, I'm hoping your expertise can help me figure out what’s wrong with my computer.

The Computer (Custom built, no OC):
CASE: Fractal R5, 2 std. case fans via case controller / MB: Asrock z97 mod 1150 Extreme4 ATX Bios v.2.10 (Latest)
CPU: Intel i7-4790K / CPU Fan: Noctua NH-U14S with additional NF-A15 on CPU header,
PSU: EVGA Supernova 1000W P2 Modular Platinum / GPU: 1xSapphire R9 290 TRI-X OC 4GB
HD: Samsung 500 GB 850 EVO SSD & Seagate 3.5 inch 3TB Barracuda,
RAM: MUSHKIN 997083 Redline 8GB Kit (2 x 4GB) DDR3 2400MHz (PC3-19200) CL10
WLan: TP WDN4800 N900 / Display: Asus mg279q / KB&M: Logitech k740 & Razer Deathadder

The problem: For the past 2 months, since I built the PC, the computer has been randomly freezing once every one to two weeks. It always happens when I am at the windows desktop or using any internet browser. The screen turns black but doesn’t turn off, computer and keyboard are unresponsive (numlock test), no error message on motherboard when I look inside cabinet.
To solve it, I press the reset button and the computer reset but doesn’t do bios start up check instead freezes with a black screen and fans on GPU only goes to 100%. A second press on the reset button and computer finally boots up. Windows Event Manager has no errors or events to report besides a wrongful shutdown.

My testing: Several clean formats and several installs of windows 7 and later windows 10. Tried windows stock drivers, the many drivers from Asrock for MB and Bios and latest 3 catalyst drivers. Tried different monitor. Temp, stress, memory and hard drive testing all with perfect results. Tried running RAM at auto v1.5-1600mhz and XMP profile v1.65-2400mhz. Reseated memory, HD, graphic card. ~
Sadly I have no extra hardware to try changing them out one at a time to find the culprit. so I decided the most likely culprit was the graphic card. I RMA’ed it 2 weeks ago and ran the computer via the built in Intel GPU. Since then I have had 2 freezes, one with a black screen and one where screen showed static picture of web browser. However these times reset button did not work. I had to Hard power off and when I powered on it would boot normal on first attempt, (probably because no GPU to mess up the initial boot up attempt).

Based on all this I am leaning towards a motherboard fault, but as I have no other testing options I wanted to check with you guys before I took the step of RMA the motherboard. Your insight would be greatly appreciated.

Kindly
Julian

20150826_010055.jpg
 
Solution
O
The processors memory controller is supposed to work with 1.5 volt RAM .
Using 1.65 volt RAM voids the processors warranty

The most common cause of instability like this : RAM
Yours is massively overclocked and over volted

When you add 2 and 2 you often get 4

Also keep in mind that 2400 Mhz RAM that needs 1.65 volts is probably 1866 Mhz RAM that runs at 1.5 volts . Only the packaging changes . Set the vltage to 1.5 and slow the RAM down to its slowest XMP profile . You can try higher speeds later if it is stable
Sort by date Sort by votes
J

JulianGK

Reputable
Aug 25, 2015
6
0
4,510


The Ram is suppose to work at 1.65 volt, though I did also try it at 1.5v 1600mhz but problem continued as mentioned. I am not following why you think it is a RAM issue based on the symptoms I have written about, but if you have experience with this, I would defer to you and RMA it.
 
Upvote 0 Downvote
O

Outlander_04

Titan
BANNED
Nov 18, 2008
20,308
4
74,960
The processors memory controller is supposed to work with 1.5 volt RAM .
Using 1.65 volt RAM voids the processors warranty

The most common cause of instability like this : RAM
Yours is massively overclocked and over volted

When you add 2 and 2 you often get 4

Also keep in mind that 2400 Mhz RAM that needs 1.65 volts is probably 1866 Mhz RAM that runs at 1.5 volts . Only the packaging changes . Set the vltage to 1.5 and slow the RAM down to its slowest XMP profile . You can try higher speeds later if it is stable
 
Upvote 0 Downvote
Solution
J

JulianGK

Reputable
Aug 25, 2015
6
0
4,510


Thanks for your input outlander, I agree that trying ram at 1.5v at slower speed is worth trying but as I have mentioned I have already done this; running it originally at 1.5v 1600 mhz with the problem unchanged.

So problem remains unsolved.
 
Upvote 0 Downvote
M

mustermark

Reputable
Aug 26, 2015
3
0
4,520
My first guess would be a driver. Have you tried updating the BIOS. Could be a bad or outdated driver that has been updated since the mboard's production date. Should be an inWin BiosUpdateq, Utility that you installed with first boot from DVD that came in the mb's box. If not, the Asrock site should have both in support section, as they are a pretty solid co.
 
Upvote 0 Downvote
J

JulianGK

Reputable
Aug 25, 2015
6
0
4,510


Hi Mustermark, a solid suggestion, I thought the same and tried an earlier and the latest BIOS a month ago, sadly with no effect. I also tried google searching for people in a similar situation, especially in regards to MB and bios but no luck as this is a problem that can have many causes.
 
Upvote 0 Downvote
M

mustermark

Reputable
Aug 26, 2015
3
0
4,520


Julian,
Ok, we'll scratch that one. I use Linux and have occsionally experienced similar locks. It's been a while, so I'm not sure about matching processes with mswin.
The most frequent was one of the energy saving processes being linked to a screenlock. The screen/powersaver was autocfg'd without asking for input. A password to reopen the session monitor was never entered, and this caused the dialog box to never activate. Someone missed a line or two of code.
I only found this by check the sys cfg settings and unchecked a 'require a password' toggle. Other times have had to boot into a minimal session to recover settings.
Also, I've read of serious problems concerning firmware in new top-of-the-line power supplies. I can't remember whether the firmware was causing serious conflicts or the firmware was actually attacked by malware, the same kind of attack part of Stuxnet used, I believe. Might try an older (used or a friend's) power supply temp swap.
Don't know if this will help much.
mustermark
 
Upvote 0 Downvote
J

JulianGK

Reputable
Aug 25, 2015
6
0
4,510


Hi Mustermark, I dont have a power saver screen/screen lock activated on windows 10, and my computer is set to never go to standby. I'll try and get a second PSU to test out your theory. I thought about the driver issue and ill try to install the manufacturers drivers (not stock windows) for the rest of my devices *non-critical hardware i.e. Intel GPU *not used*, Monitor, keyboard*
I'll let you know how all this goes in a week or two. Thanks for your help.
 
Upvote 0 Downvote
J

JulianGK

Reputable
Aug 25, 2015
6
0
4,510


Computer just froze again, when I restarted it would not start up again. Asrock MB ran through the standard startup codes on MB (I looked in cabinet), Monitor was still turned off, all fans at 100% and nothing happened = no post screen. I tried the restart button a bunch of times, Clear CMOS, power off. It Kept doing the same thing. Finally I pulled Display cable out of r9 290, put it into Intel GPU and kept computer off for 1 min. Then tried again and it worked.
I seriously doubt this is a driver issue, I lean towards hardware, but who is the culprit? I'ts got to be one of the following
Asrock Extreme4
Evga 1000 Platinum G2
MUSHKIN 997083 Redline 8GB
(can't be R9 290 as fault still happened when it was away for testing)
Sadly I cant test those 3 parts as I dont have any spare. I think I will contact Asrock at this point to RMA as I am guessing this is the likely culprit unless anyone has a better idea.
 
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