BSOD STOP 0x00000124; No particular occasion

[Golden]

Stab in the dark : what version of Chrome are you using?

 

[tmay]

I use firefox rather than chrome. Currently chrome is version 40.0.2214.115 though

Edit: Forgot to actually change my browser to firefox and chrome. All good now!

 

[Golden]

Thats fine - we have seen a few instances of BSOD using a beta Chrome build, but yours is OK, so we can rule that out.

 

[tmay]

Okay I can add that to my list of hardware/software that wouldn't cause it then

 

[Golden]

@Steve : is that a 4th Gen CPU on tmay's system?

 

[essenbe]

Yes.

 

[Golden]

Yes.

OK. Looks like Asus released a BIOS update to address issues with the Intel 4th Gen CPU's:

tmay's current BIOS = BIOS Version/Date American Megatrends Inc. 1504, 03/10/2013

This from ASUS for that mobo:

View attachment 352070

Motherboards - Z87-A - ASUS

Maybe a BIOS update solves the issue?

 

[essenbe]

Good catch, Golden. That could very well be the issue.

 

[tmay]

That was a really good catch! I'll update it and get back to you all soon

 

[Golden]

OK. tmay, please try a BIOS update. Go carefully.

 

[tmay]

Hey all,

I've successfully updated my BIOS without issue!

Prime95 or wait?

 

[essenbe]

You can try Prime, just watch the temps very closely and make sure you have a good monitoring program.

 

[tmay]

Okay, works for me. I'll give it a go when I get home today. Is Speccy an acceptable monitoring program?

 

[essenbe]

Yes, I'm sure it is OK. A lot of people here use it.

 

[tmay]

Hey Essenbe,

Some better news this morning! I ran Prime95 for about half an hour and the temps did not go any higher than 65!

 

[essenbe]

That's Great news. Is it from the bios update or did you do something else. It sounds like Golden may have very well solved the riddle.

 

[Golden]

Sounds promising....keep us updated on developments.

 

[tmay]

Hey Golden and Essenbe,

The only change I made since the last BSOD was a BIOS update. Haven't had any BSOD since then either! Some updates are failing but that's a different matter altogether.

Any other tests I should do?

 

[essenbe]

Please check and make sure your date and time are correct in the OS and in BIOS. Then 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.

 

[tmay]

"No integrity violations" was the result!