BSOD BCCode 124 between 20 minutes and 5 hours use, day in day out

lopuwin · 22 Jun 2016

essenbe said:

In hardware testing, the CPU is normally the last thing to suspect. Most are pretty hardy and rarely go bad, unless severely abused.

Well I can't say I abused it :)

I'm running memtest now for the next 16 hours or until 8 passes, interested to see what's up. Sorry I didn't post those screenshots, I started the memtest and went to bed so I don't want to stop it and take the ss's.

Talk soon :)

essenbe · 22 Jun 2016

essenbe said:

As expected, the dump file provided very little info other than a general hardware error. That error will mean that it is a general hardware error or a driver is bad enough to cause a piece of hardware to act like it is failing. These are not easy cases usually. We just try checking all hardware we can until we find the bad piece. Please be warned, at some point we will need to run memtest86+ and it will take you somewhere around 36-38 hours to run it. Please, while we are doing this, please don't run any tests or try any fixes unless we ask you to. It can confuse the whole process.

open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

I would also like you to install, if you don't already have it, CPUz (CPU-Z | Softwares | CPUID) Please post screenshots of the CPU, mainboard, Memory and SPD tabs. On the SPD tabs you can select each Dimm Slot. We only need the Dimm Slots that are populated with ram.

How long has this rig been built and did you build it? Has it been having this issue all along or did it start recently? If recently had you just added/replaced any hardware or installed any software? Any info you can give us will make the process easier on both of us.

Please look again at the above. Some of that will probably be useful. What Anti Virus are you running? I see some files that look like AVG and some that may be associated with Symantec. Are you running/connected to an Apache Server?

Can you offer any suggestions? I am looking at some of the files. They show your OS Install date as 4/2016 but when I look at the event log I see errors dated 2010.

You have too many items in startup.

Do you have CCleaner installed? If so you can go to tools > uninstall in the left column it will show all the software you have installed. At the bottom left is a button to export as text. I would like to see that. OR You can go to Control Panel > Uninstall a Program and make a screenshot and upload it here.

essenbe · 22 Jun 2016

lopuwin said:

essenbe said:

In hardware testing, the CPU is normally the last thing to suspect. Most are pretty hardy and rarely go bad, unless severely abused.

Well I can't say I abused it :)

I'm running memtest now for the next 16 hours or until 8 passes, interested to see what's up. Sorry I didn't post those screenshots, I started the memtest and went to bed so I don't want to stop it and take the ss's.

Talk soon :)

It takes me about 16-17 hours to run memtest on my 16Gb of ram. It will most likely take you twice that long. If you could, when the test is through, before you stop it, could you take a photo of the screen? It is more info for us. The quality is of little concern as long as we can see the writing on the screen. The errors in memtest will be red lines at the bottom. If you get one, stop the test. This is what errors look like

Attachment 388429

lopuwin · 22 Jun 2016

essenbe said:

lopuwin said:

essenbe said:

In hardware testing, the CPU is normally the last thing to suspect. Most are pretty hardy and rarely go bad, unless severely abused.

Well I can't say I abused it :)

I'm running memtest now for the next 16 hours or until 8 passes, interested to see what's up. Sorry I didn't post those screenshots, I started the memtest and went to bed so I don't want to stop it and take the ss's.

Talk soon :)

It takes me about 16-17 hours to run memtest on my 16Gb of ram. It will most likely take you twice that long. If you could, when the test is through, before you stop it, could you take a photo of the screen? It is more info for us. The quality is of little concern as long as we can see the writing on the screen. The errors in memtest will be red lines at the bottom. If you get one, stop the test. This is what errors look like

Attachment 388429

Sorry for not answering those other questions.

I ran sfc /scanow in elevated cmd and there were no corruptions but I have run it in the past after crashes and there were corrupt shit right after them so, I'd correlate it with that.

I will be leaving my computer on and going out to the country side while it does the mem test, probably it'll run for 20 hours or so. is there a chance it'll crash during the test.....?

this rig is about a year old but it was built out of another shittier rig and it has been a nightmare all it's life but it was always different problems, but now it's this, and it is ****ing with my workflow I can't stand it. And I built it, the case has been pushed to the limits lol

lopuwin · 22 Jun 2016

essenbe said:

lopuwin said:

essenbe said:

In hardware testing, the CPU is normally the last thing to suspect. Most are pretty hardy and rarely go bad, unless severely abused.

Well I can't say I abused it :)

I'm running memtest now for the next 16 hours or until 8 passes, interested to see what's up. Sorry I didn't post those screenshots, I started the memtest and went to bed so I don't want to stop it and take the ss's.

Talk soon :)

It takes me about 16-17 hours to run memtest on my 16Gb of ram. It will most likely take you twice that long. If you could, when the test is through, before you stop it, could you take a photo of the screen? It is more info for us. The quality is of little concern as long as we can see the writing on the screen. The errors in memtest will be red lines at the bottom. If you get one, stop the test. This is what errors look like

Attachment 388429

Oh and yeah I run different anti virus's on a monthly basis so this month has been avg, and yeah I run a mamp server for hosting my local sites for web dev.

essenbe · 22 Jun 2016

It's possible it could crash, but not likely. It's a computer, anything is possible. :)

essenbe · 22 Jun 2016

How are you hosting your sites now while running memtest?

lopuwin · 22 Jun 2016

essenbe said:

How are you hosting your sites now while running memtest?

I only run them when I'm doing local development or portforward http to show someone so I have mamp on a laptop too and can just move my workflow to laptop. I'm headed to the country side so the mem test is now going to be on for 30 - 40 hours. It did 2 passes in 12 hours btw, weird that it does 1 pass in 2 hours and then takes 10 hours to do another...?

essenbe · 22 Jun 2016

Yes, it is, but it has always done the first pass much faster than any other. Enjoy the countryside.

lopuwin · 25 Jun 2016

essenbe said:

Yes, it is, but it has always done the first pass much faster than any other. Enjoy the countryside.

The power went out for 15 minutes while I was away so I'm running it again, the blue screens are just unbearable now so I'll be doing everything I can to fix it. I'll be back with the memtest results :)