Solved frequent BSOD's but only when idle, new build

[ken070]

Having trouble finding the cause of frequent BSOD's. They never seem to happen while actually using the computer (will go all day -- at least 7-8 hours -- if there's activity,) but will usually BSOD after 10-20 minutes of being idle (i.e. no mouse/keyboard activity.)

I don't think the computer has ever idled >30 minutes without a BSOD. It's gone hours (many times) while actually being used.

This is a (fairly) new build (few months old) and a very frustrating problem! Ran memtest86+ w/ no errors (10 passes.)

Any help on where to look next or things to try would be greatly appreciated.

 

[Boozad]

Welcome to 7F.

You're receiving 0x124s which are mostly hardware errors but rarely indicate what. However, looking at your logs I've found the following:

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  [COLOR=Red][B]ubssrv_oc_only[/B][/COLOR]

CURRENT_IRQL:  f

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

STACK_TEXT:  
fffff880`009bbb58 fffff800`0360da3b : 00000000`00000124 00000000`00000000 fffffa80`0e5e0028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`009bbb60 fffff800`031a0713 : 00000000`00000001 fffffa80`0e4d8930 00000000`00000000 fffffa80`0e4d8980 : hal!HalBugCheckSystem+0x1e3
fffff880`009bbba0 fffff800`0360d700 : 00000000`00000728 fffffa80`0e4d8930 fffff880`009bbf30 fffff880`009bbf00 : nt!WheaReportHwError+0x263
fffff880`009bbc00 fffff800`0360d052 : fffffa80`0e4d8930 fffff880`009bbf30 fffffa80`0e4d8930 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009bbd50 fffff800`0360cf0d : 00000000`00000008 00000000`00000001 fffff880`009bbfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009bbd90 fffff800`03600e88 : 00000000`00000000 00000000`00000010 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009bbdc0 fffff800`030877ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009bbdf0 fffff800`03087613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009bbf30 fffff800`0307fb08 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`07513638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!memmove+0x208

ubssrv_oc_only has been attributed to Gigabyte crapware in the past, and Gigabyte crapware has caused a fair few 0x124s in the past.

:ar: Uninstall any Gigabyte crapware you have installed.
:ar: If you're overclocking, stop. Revert your system to stock clocks.
​

 

[ken070]

Boozad, thank you for your very quick response. Here's a screenshot of the Gigabyte programs that are installed. Which ones qualify as "crapware"?

 

[Boozad]

Are there any that you actually use? I'd recommend uninstalling all of them to be honest.

 

[ken070]

Boozad, all Gigabyte programs were uninstalled and I'm happy to report that the computer has been idling since yesterday afternoon without a single BSOD. While we're not starting victory laps quite yet, this is 50x longer than it's ever idled without a BSOD. I'm pretty sure that was the problem, so I'm going to mark this thread "solved."

I really appreciate the very prompt response & assistance. This forum is GREAT!

 

[Boozad]

You're welcome Ken. If you experience more issues in future be sure to let us know and we'll help you get it sorted. Glad to hear all is well.