BSOD on new build, no reason

[frostisfrost]

Hi, I have read many threads on this topic. But I cant find any descent solution.

First of all, this is a custom build. And it is not a gaming computer and it is not an office computer. Its just a regular home computer that should manage heavy officework and light gameing.
Second, it is my friends build, aparently he saved 500 bucks by building than buying a finished product.

To list the components:
motherboard: gigabyte ga f2a88xm-d3h
RAM: kingstone hyperx fury red, 8Gb 1866mhz
CPU/Gpu: AMD A10 7870k 3,9GHz + radeon R7
PSU: Corsair CX600
HDD: samsung evo ssd and a ordinary WesternDigital 750 GB mechanic disc

So as you can see, it is not the best, and not the worst.. I mean come on, the CPU/GPU is like over the top maxed out for what he is gonna do with his box.. And the MOBO, is kinda... i dont know.. Its good, but i dont think its rigth..

Anyway.. It has BSOD from the start. From the first startup until he dumped it on me so I could fix it. (2 Months) And it is not coherent, 5-20 mins of doing nothing, crashdump. Starting up windows update, crashdump. Trying to install the drivers, crashdups. And so on. It is not a specific task that brings it to BSOD.
And there isnt one or two specific 'codes' that tells me whats wrong, sometimes it dumps without any code.

So. I have looked insie the box, the HDDs are in the right SATA ports (now, i switched them to right the right ones)

The RAMs are healthy and plugged in the right sockets.

I have unplugged the goddamn SSD, and installed windows again, installed the drivers.

The ones that I could before it BSOD. and after some errors I managed to install al the drivers, and it became more stable. I tried to update windows, and it BSOD. But again after some time, i managed to update it.
It's almost like roulette. You dont know if its gonna work or not. And when updates fails or get unfinished by the BSOD its not good for the computer. i know that.

I dont know whats wrong. right now its stable, but you have this sinking feeling in the gut that it's gonna happen again. And it does. After a couple of hours, like clockwork.
Im out of ideas. Can someone PLEASE give some more advice, and things I can test or do to fix/conclude whats wrong.

Best regards

 

[ModMonster]

Do you get the feeling its a software or hardware failure? Does the computer crash or does it suddenly loose all power? And what was the last time it crashed, how long ago, and what caused it?

 

[Shaun o]

When you faced with the problem you have.

The first thing to consider is checking what version of the motherboards bios firmware is running.
Then going to the bran maker of the motherboard with the model number.

Checking that the board will support the speed of memory in the system.
And also if the Kingston memory has been tested in the board via the memory QVL list.

You should then look at the Bios firmware update files, and look at the current revision of the bios firmware released for the motherboard.

And see if any stability fixes were added, if your version of the bios firmware of your motherboard is a early revision.
Consider flashing the bios of the board with the new firmware provided on the manufacturers website.

Take a memory stick out of the motherboard, write down the speed, latency timings of the memory and the voltages the memory runs at 1.5v without Xmp mode enabled in the bios.

And about 1.65v with Xmp mode enabled in the bios of the motherboard.
Look for any reference in the bios relating to the yype of memory the board can use.
If you have a ECC memory settings in the option of the bios for memory and it is enabled.
Sisable the option as the memory you have Is buffered memory. Setting ECC mode in the bios or if enabled will cause the system to crash.

Check that the auto detection of the memory it`s speed, latency settings and voltage have been set right if the board is set to auto detect the memory modules by default.

If the board has an Advanced Uefi bios mode make sure it is selected.
In the setting for the memory voltage set it to manual configuration.
Make sure the voltage is around 1.65v and what it should be if XMP memory mode in the bios is enabled.

And if you can increase the 1.65v of the memory by 0.250Mv Mv is milli volts.

The base speed setting for the Ram modules should be set to 933Mhz.
You are using DDR memory so that base value of 933Mhz is always times two.

933Mhz x 2 = 1866Mhz efective memory frequency.
Any higher base setting selected will result in a constant crash of it due to the memory being to overclocked.

 

[Shaun o]

When your faced with the problem you have.

The first thing to consider is checking what version of the motherboards bios firmware is running.
Then going to the brand maker of the motherboard with the model number of the board also in hand.

Checking that the board will support the speed of memory in the system.
And also if the Kingston memory has been tested in the board via the memory QVL list.

You should then look at the Bios firmware update files, and look at the current revision of the bios firmware released for the motherboard.

And see if any stability fixes were added, if your version of the bios firmware of your motherboard is a early revision.
Consider flashing the bios of the board with the new firmware provided on the manufacturers website.

Take a memory stick out of the motherboard, write down the speed, latency timings of the memory and the voltages the memory runs at 1.5v without Xmp mode enabled in the bios.

And about 1.65v with Xmp mode enabled in the bios of the motherboard.
Look for any reference in the bios relating to the yype of memory the board can use.
If you have a ECC memory settings in the option of the bios for memory and it is enabled.
Sisable the option as the memory you have Is buffered memory. Setting ECC mode in the bios or if enabled will cause the system to crash.

Check that the auto detection of the memory it`s speed, latency settings and voltage have been set right if the board is set to auto detect the memory modules by default.

If the board has an Advanced Uefi bios mode make sure it is selected.
In the setting for the memory voltage set it to manual configuration.
Make sure the voltage is around 1.65v and what it should be if XMP memory mode in the bios is enabled.

And if you can increase the 1.65v of the memory by 0.250Mv Mv is milli volts.

The base speed setting for the Ram modules should be set to 933Mhz.
You are using DDR memory so that base value of 933Mhz is always times two.

933Mhz x 2 = 1866Mhz efective memory frequency.
Any higher base setting selected will result in a constant crash of it due to the memory being to overclocked.

 

[frostisfrost]

ModMonster:
Last time it BSOD was about 10 minutes ago, it had run smoothly for about 4 hours. Then it crashed without warning. This time with the irql_not_less_or_equal, wich is strange since al drivers are up to date, no new hardware is installed (like a printer) and so on. At this point Im leaning towards a faulty Motherboard or some BIOS setting that is way off.

Shaun o:
I will look into it, And come back when I have checked BIOS update, and the memory settings. Thank you, I actually didnt think far enough to check the bios..

 

[frostisfrost]

Well, The memorys was overclocking, instead of 1866 it runned at 1867..
now it runs at 1866, well see if it dont bsod now. It might be why it can run for a couple of hours then crashdumps.
And I dont dare to flash the bios since it is not my computer, and I dont want buy a new motherboard.

EDIT: I changed the clockspeed of the RAM down to 1600mhz, since it crashed when it ran at 1866mhz, seems to run smoothly now (for about 2hours). If it still dumps after a couple of hours, I might need to tell him to buy a new mobo, or flash it. Thats the only option left when all drivers are up to date, HDDs are healthy, RAM healthy, windows healthy and CPU/GPU r healthy..