The Return of the BSoD for No Apparent Reason

Arelem · 22 Jun 2015

I posted last week about my PC starting to BS0D shortly after start up. I waited a couple days to see if someone had time to help, but then I decided to rebuild the machine. The BSoDs did not return after the rebuild, so I closed the original thread. Now, 2 days after I rebuilt it, it has started BSoDing again.

1) The BSoD takes place roughly about 5 minutes after a full boot.
2) The PC does not BSoD in Safe Mode
3) Last week my basement flooded and I had turned the A/C to a lower temperature to help with the drying out. Last night, I returned the A/C to the higher temp, the BSoDs returned this morning. (The PC is NOT in the basement, its on the first floor of my house)
4) None of my usual maintenance software has been loaded on the PC yet. There is only my ESET anti-virus and Malwarebytes.
5) I ran Memtest+ for 5 cycles and it gave me no errors at all.

Please, can someone help me on this? I need this PC to search for a job. My laptop is dead, my tablet frequently locks up and the closest public PC I can get to is a 45 minute one way/$4.50 round trip bus ride away and has a daily waiting list of up to 3 to 4 hours. I really need help on this. This is about as close to begging as I can get without resorting to all caps.

Boozad · 22 Jun 2015

You're receiving 0x124s which are generic STOPs pointing to hardware failure, but, as is the case here, they very rarely point to the exact piece of hardware that's causing the issue. We normally recommend running a full suite of stress and diagnostic tests to weed out the problematic component here but I've noticed something showing in all of your dumps.

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: fffffa8017e55028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000200001, 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:  ekrn.exe

CURRENT_IRQL:  f

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

ESET has been flagged in every single dump. In my experience it's rare to get one piece of software showing in every 0x124 dump so it may be worth looking at that first. Uninstall ESET and install MS Security Essentials and MalwareBytes.

Note

Make sure you uncheck the 'Enable Free Trial' box when installing.

Test the system for stability and report back. If you receive any more new BSODs please run the Log Collector and upload the new logs.

Arelem · 22 Jun 2015

Thank you. I have uninstalled the ESET and MSE is currently running its initial scan. I'll let you know what happens over the next few hours, but things look good so far. It hasn't BSoDed yet since the last restart, almost 15 minutes ago.

That would be a kicker if it was ESET. I have been using it for over 3 years and never had a problem before.

Boozad · 22 Jun 2015

It may not be the culprit, like I say 0x124s are usually down to faulty hardware but it's worth ruling it out as it showed in every single dump file. Let us know how you get on.

Arelem · 23 Jun 2015

Twenty fours hours in and no more BSoDs. I went to the ESET site to post about it, only to find a thread started on their forums. Apparently I'm not the only person experiencing this. The ESET moderator told folks to try using some hotfix from MS, but those who tried it, said it didn't work. Another person who apparently could read .dmp files was calling it a "false 124 error".

So, until ESET gets their act together and figures it out, I guess I'm using MSE.

Boozad, thank you for your help. You are a life saver on this.

Boozad · 23 Jun 2015

I'm glad that your issue is sorted out mate. Shout if you need anything else.