Random BSOD with Gigabyte Brix S (NUC type system)

SimonG · 12 Apr 2015

Hi guys,

I have a Gigabyte Brix S, a NUC type machine running an i5 5200U SOC, with 8GB DDR3L and a Samsung Evo 840 msata. I have had it about 3 days!

I have installed Windows 7 Home Edition 64 Bit, MS Office, Avast Anti Virus and other tools.

I was using the machine a few moments ago, writing an email as it happens, with a few Google Crome windows open and a MS Office Word Document open too, and the machine gave me a BSOD.

I have followed the instructions at the top of the forum and have attached my zip file for your perusal.

Any help you can give me will be appreciated.

Thanks in advance

Boozad · 12 Apr 2015

Welcome to 7F.

The single dump in your logs is showing a 0x124 which indicates a hardware error. Unfortunately, as with the vast majority of 0x124s it doesn't indicate what the exact problem is. The only way to identify the issue is to run a series of hardware stress tests and diagnostics.

STOP 0x124 Troubleshooting

Read carefully before proceeding.

Warning

If you're overclocking your system, revert back to stock clocks now.

Note

Test the system once the overclock is removed before continuing with the steps outlined below.

ONE

CPU TEST

Run Prime95 to stress test your CPU. Hardware - Stress Test With Prime95

Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them.

TWO

RAM TEST

Run MemTest86+ to analyse your RAM. RAM - Test with Memtest86+

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.[/note]

THREE

HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use

Run chkdsk Disk Check

FOUR

GPU TEST

Run Furmark to stress test your GPU. Video Card - Stress Test with Furmark

Note

Run Furmark for around 30 minutes.

Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them.

SimonG · 12 Apr 2015

Thanks for the response.

I'll get onto running those tests a little later today.

Out of interest, I notice that the Samsung Evo 840's had issues that may or may not have been rectified with a firmware update.

I have now run this update, and will continue to monitor the situation, but in the mean time, could the BSOD have been caused by the SSD and it's original dodgy firmware?

Again, thanks in advance

Boozad · 12 Apr 2015

It's a possibility I suppose although I can't say for certain. The SeaTools test probably isn't the best option for an SSD to be honest, a mistake on my part there. There are tools available on the Samsung website that will check the integrity of your SSD.