Random BSOD's Happening frequently, error 0x00000124

Hello and welcome HLL seems like you have a hardware problem and likely to be a hard drive or CPU one from what I have seen.
Now for starters mate run these in safe mode if necessary (if you haven't already)

https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
https://www.sevenforums.com/tutorials/433-disk-check.html < if necessary include the /f and /r in the command line as per Option2

if no go please run these

http://www.superantispyware.com/
http://www.malwarebytes.org/products/malwarebytes_free/
http://www.bleepingcomputer.com/download/adwcleaner/
ADW download from bleeping computer delete any rubbish found with the malware scans
(NB If one is running Kaspersky security it may rant about ADW - just ignore it or disable Kaspersky while the ADW is being used)

Now if you are worried re losing your data then back up now - just in case I use this as I like images rather than straight data back up
Imaging with free Macrium

I think you should also test the hard drive and one to use is this SeaTools for Windows | Seagate

if things do go pear shaped then there is another way of getting the data back but lets try this lot first.

I'll expand on what John's offered. 0x124s are a generic STOP code that indicate a hardware fault but, as is the case here, they rarely give a clue as to what the problem actually is. Certain software has been known to cause 0x124s in the past, mostly Gigabyte motherboard utilities, can I ask which of these you have installed? I'm also wondering if AVerMedia RECentral is contributing to the problem as it's been flagged in one of the four dump files in your logs. Could you let me know what RECentral does please as I've never heard of it.

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800fb39028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  RECentral.exe

CURRENT_IRQL:  f

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

I'm going to post a series of stress and diagnostic tests that we usually recommend to try and pinpoint the failing piece of hardware. If any of these duplicate anything you've done so far please carry them out again so you can inform us of the results.
It's worth noting that my old GTX 780 ran at 80°C all the time while under load so that's normal.

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.

Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four:GPU Stress Test

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 and abort the test if overheating occurs.

TWO

 RAM TEST

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

   Note

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.

THREE

 HDD TEST

Run SeaTools to check the integrity of your HDD (Do not perform on an SSD). SeaTools for DOS and Windows - How to Use

   Note

Do not run SeaTools on an SSD as the results will be invalid.

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 and abort the test if overheating occurs.

Yep Gav I saw the CPU cache issue and the some hard drive stuff but couldn't make out if there were any memory or GPU problems.

I am just interested in what the sfc and chkdsk and the malware scans throw up if anything because not being a fan of Norton was just wondering. .

No I don't like Norton either John personally.

Ok, so thank you for your replies. I have run most of the tests, I'll be running the Memory Test overnight, although I had run it before 8 times a few months ago as was suggested and it came back with 0 errors. I'll still run it again to be safe.

I ran the CPU's benchmark and was happy to have 0 errors and 0 blue screens during the 2 hours I ran it. The temperature didn't exceed 63c through out the entire thing, as I have a strong water cooler. Here is a snapshot of the test.

I then ran the tests on my HDD, and it passed all of them, not sure where the logs are for that but it did pass all of them, and I ran the windows error check and had 0 errors.

Next I did Furmark, which I have used before, and I ran it for 30 minutes and came back with no problems, my GPU heated up to 78c max during the process.

RECentral.exe is the recording software for the AverMedia U3, which I was using when I blue screened one of those times, though I use the software all the time and for hours on end without any problems. That and it is newer, I only started using it in March, and I've been having these BSOD'd way before.

I then ran Malwarebytes and scanned my system and had 0 viruses, or as they call it detected objects.

What else can you suggest? I have no idea why I am getting blue screens. Are there tests for my SSD, or Powersupply? Maybe my motherboard? Could it be something I'm running? Anyway, tomorrow I'll have the tests on the memory for you, though I'm positive there won't be anything.

Thank you for the help so far and I really hope we can solve this.

Edit: I just had an idea, instead of doing the memory test over night tonight, I'm going to run Minecraft and the AverMedia U3's capture program, RECentral overnight and see if I can get a bluescreen. It only happens randomly when recording, but I haven't ever tried to go for that many hours at once. I'll still do the memory test tomorrow if you want, I'll get the results for you tomorrow, sooner if it Blue Screens.

Well if you want to test the rail volts on the PSU use this I made up
Using HW Info
PART A:
You can test the volts on the PSU with HW Info HWiNFO, HWiNFO32/64 - Download < download the right bit version and close the right hand window select Sensors and scroll down to the power section where you will see what the volts are doing see my pic. In my pic the section (Nuvoton) with VBATT is a dead give away you are in the section for the rail voltages. There are other section titles and one that pops up often is ITE
Now the voltage on the different rails have to be within 5% =+/- of what is required or the machine will not work properly if at all.
See this for the rail voltage info
http://www.tomshardware.com/reviews/power-supply-specifications-atx-reference,3061.html (Section 2.)
The original right hand window shows the machine running and is handy for that but for looking at the components in some detail close it and use the main left hand side panel
FOR OTHER COMPONENTS
PART B:
Open each small square with + in it on the section the components are in and then click on the individual component/s (it will highlight in blue) - in the right hand side will appear all sorts of details including brands speeds and other essential info that particular device. See pic for example.
JUst PART A: for the PSU - the readout might be different form my pic and PART B: you can use to get very detailed info on other components.

To see if the PSU is large enough use thus eXtreme Power Supply Calculator - The only power supply calculator trusted by PSU manufacturers and computer enthusiasts it will give you the optimum plus a little over the top and most of us usually build in (I do) 25% overkill anyway cos you don't know down the track if you will need it or even just for peace of mind:)

Now if you have the Samsung Magician software on board then run the optimizing and other small testing parts with that.

That PSU stuff I sent you just need to follow the info and the screen that comes up as in my pic will show you the state of the volts and the different rails. Now if you saw that tomshardware ref then you will see the volts have to be within 5% +/- of the required volts for things to work or not or even be damaged (not likely in view of the PSU circuitry that will not allow the machine to power up if wrong).

Having said that not all machines are the same and yours might be very sensitive to even the slightest change in required volts. The section with Vbatt in it will show you the volts as I said in my pic of my Ivy Bridge Asus board it is just that Nuvoton is the Asus reference and it might well be something like ITE but the readout will be very similar.

If you could send back a snip of that section then it would be easy to et you know. See this http://www.vistax64.com/tutorials/148532-how-use-snipping-tool-vista.html copy the snip to your Picture then add it to Manage attachments (just below the post screen)

I am only saying this because the PSU is very often overlooked as a cause of problems in a machine even though they may not seem related. But if you don't think it is necessary then don't worry.

As for Windows 10 I am not going to make any comment only that my brother in the UK tried it and is desperately trying to get 7 or 8 back on his machine as he didn't like it at all.

HLLetsPlay said:

if you want me to still run the test on the ram I'll do it tonight.

Yes please.