0x124 BSOD - Windows 7 x64 - Suspected CPU failure

R

red98

New member
Joined
Jun 23, 2015
Posts
4
Hello,

My PC is approximately 1 year old and it has not had any problems in the time I have been using it asides one dead hard disk a month ago. Now I get a BSOD and restart almost exactly 10 seconds after logging into my user account in Windows 7. The PC is as follows:

  • OS = Windows 7 Home Premium, 64 bit, full retail
  • Operating system was installed approx 1 year ago (July 2014)
  • CPU = Intel core i5 4590
  • Motherboard = Gigabyte H97-HD3
  • Graphics Card = NVidia GTX 660 2GB RAM
  • RAM = 2 x 4GB Corsair
  • PSU = Corsair HX520W
  • All components approx 1 year old (July 2014) except PSU which is ~5 years old

The PC will boot into safe mode and runs without problems there. It is a dual boot machine and will run the other operating system (OS X) fine without issues. If I start it in normal windows mode (i.e. not safe mode) and leave it at the log on screen it is fine. However almost precisely 10 seconds after logging into a user account it goes to BSOD (0x124). It is like the hardware is failing a test windows runs at user log on.

I have run the windows system dump analyzer and it informs me the problem is down to 'genuineintel' which I assume is the CPU. When I run HWMonitor in safe mode I can see all the usual information except for the CPU - this now shows no temperature information and only that each core is running at 3300Mhz. It also does not identify the CPU anymore, instead it names it 'Intel Core i3/i5/i7 4xxx'. This suggests to me something has failed in the CPU and I need to replace it.

However I am no expert and I would very much appreciate some guidance on the diagnosis. Any and all help most welcome.

I have read the forum instructions and attach the output of the Sysnative File Collection App. Unfortunately I cannot run a performance report - I just get an error message saying it cannot find the file path to run it so no output from that is attached.

View attachment SysnativeFileCollectionApp.zip
 
Hey red98, I may have similar problem. Are you using Eset Smart Security? Exactly 2 days ago I started getting 0x124, WHEA... error, file "ekrn.exe" was mentioned in minidump alongside with "0x124_GenuineIntel" and some "unidentified CPU error".
 
Yes, I am using ESET smart security. I have used it for several years with no problems but I'll try disabling it on the machine tonight and see what happens.

In safe mode I ran an intel processor health check and it reported no problems whatsoever. So perhaps my thoughts of a CPU problem were wrong.
 
Browse thru that Eset forum link that I posted, I think the most relevant information will be there (I am glad that som eset moderator is already examing this). I hope that our CPUs aren't faulty, that this is Eset's bug (for now they are saying something else :huh: - bug of some other software). My processor health check showed nothing=no problems for me neither.
 
Welcome to Sysnative - to both of you!

Great to see one new member helping out another in what must be a difficult time, thanks staffy.

No, it's not looking like a real CPU problem :thumbsup2:

As I mentioned to Red elsewhere:
It's possible that the error is down to some software/driver interference or that it's a motherboard or, probably less likely, a PSU problem, rather than a CPU fault.
Click to expand...

As far as as common drivers that are known to be involved in causing BSODs goes, ASUS/Gigabyte drivers don't have a great reputation historically, there are a number of them listed here, as well as many other known bad/suspect 'utility' drivers: Driver Reference Table - Common BSOD related drivers

If you both follow the request to switch to pre-release updates, as requested in #37 in the ESET forum, that should help both yourselves, and other ESET users, to get a rapid fix pushed out.

On a more general stability note - try to keep utility software drivers to a minimum, clean is good! I use DriverView, set to hide Windows drivers, to check the 3rd party drivers that Windows loads: DriverView: Loaded Windows Drivers List

Keep us updated, please, the real analysts here might want/need to dig deeper into this issue.
 
staffy - thank you for the link and your advice. It seems ESET and/or a clash with gigabyte drivers is the problem with my machine.

I have disabled ESET and no BSOD. Looks very much like a software problem which is a relief for me. I have installed an alternative firewall and antivirus package to ensure I have some coverage in the interim while I figure out what to do with ESET. I have tested all the memory and CPU with memtest and the Intel Processor Diagnostic Tool now and both pass without problems.

The CPU reporting information has re-appeared in HW monitor now too. All reporting the temperatures and CPU name correctly. All temperatures look in the normal range (~30 - 35C at idle dependent on ambient room temperature which is about 22C now). I should have realised the problem was windows dependent as when I looked at the CPU info in the BIOS it showed all the temperatures correctly there.

I'll get on with running driver view and sorting out this software problem. Auto updating is something I strive to avoid but clearly I've not been diligent enough.

Seems from the ESET forum that everyone there started having problems about 2 days ago (22 June) which is the same as when my first problem occurred. I note several people on the ESET forum report using the Gigabyte App Center software, I also use this but only for fan control. I would gladly replace it (it really is a horrible piece of software) but I can't find any alternatives. Speedfan seems to have stopped being updated and doesn't support the chipset on my motherboard unfortunately. If anyone has any recommendations for fan control software I'd love to hear them so I can banish Gigabyte App Center from my machine.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top