BSOD - STOP error - even when PC idling. SF dump included

krakpot · 22 Oct 2014

Hi,

We bought this PC in june, we had a BSOD initially and I found it related to ESET. The PC has been fine since but we have had 3 x BSOD this week. The one this morning happened while the PC wasnt being used and I was talking to a colleague.

No programs have been installed recently but a lot of windows updates where installed last week.

Any help appreciated.

Cheers
Rich

koolkat77 · 25 Oct 2014

Welcome to the forum.

Uninstall ESET and replace with MSE for testing purpose.

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-

Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability
compared to other antivirus or internet security software. It is free and lightweight:-

Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Looks like a hardware error otherwise.
Test your Hardware for Stability and Heat Problems with Prime95. Be sure to keep an eye on your temperatures when running these tests, especially the Large FFTs:

Stress Test With Prime95

How to Stress Test a Video Card with Furmark:

Video Card - Stress Test with Furmark

Test your CPU Stability with IntelBurnTest:

CPU - Stress Test Using IntelBurnTest

[CODE]
Monitor the temps during the test.

Check for heating issues using Speccy or HWMonitor. Upload a screen shot with either of the tools:

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\SF_22-10-2014\SF_22-10-2014\102214-4321-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`03219000 PsLoadedModuleList = 0xfffff800`0345c890
Debug session time: Wed Oct 22 12:15:58.052 2014 (UTC + 6:00)
System Uptime: 1 days 0:04:59.168
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800d2d6028, bf800000, 124}

Probably caused by : GenuineIntel

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffffa800d2d6028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, 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:  SearchIndexer.

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02fdfa58 fffff800`03810a3b : 00000000`00000124 00000000`00000000 fffffa80`0d2d6028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`02fdfa60 fffff800`033a5463 : 00000000`00000001 fffffa80`0ceb8a20 00000000`00000000 fffffa80`0ceb8a70 : hal!HalBugCheckSystem+0x1e3
fffff880`02fdfaa0 fffff800`03810700 : 00000000`00000728 fffffa80`0ceb8a20 fffff880`02fdfe30 fffff880`02fdfe00 : nt!WheaReportHwError+0x263
fffff880`02fdfb00 fffff800`03810052 : fffffa80`0ceb8a20 fffff880`02fdfe30 fffffa80`0ceb8a20 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fdfc50 fffff800`0380ff0d : 00000000`00000004 00000000`00000001 fffff880`02fdfeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fdfc90 fffff800`03803e88 : 00000000`00000000 00000000`00000009 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`02fdfcc0 fffff800`0328d4ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02fdfcf0 fffff800`0328d313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fdfe30 fffff800`03286aa5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`07919860 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListResume16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

Followup: MachineOwner
---------

krakpot · 31 Oct 2014

Thanks for your reply.

Unfortunatly We have to use ESET here at work so that has to stay.

I run Prime to Stress the cpu and found it is getting way to hot (into the 90's) on a 4690K. So i have stopped it auto overclockign to 4.3ghz and lowered the vcore a little and it seems to be ok so far.

Thanks