Random BSOD in 15 mins when afk

PCBuilder9342 · 04 Dec 2014

Hi,

I just built this computer; it is my first build. I get the BSOD in about 10-15 mins of being afk and not using it at all. I get the codes OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 in an error message after the computer restarts and I log on. I have uploaded the zip file with this email. Can anyone help me figure out what is wrong? I have the current chipset and video card drivers.

Thanks,

koolkat77 · 06 Dec 2014

Welcome.

That's a 124 error.

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\GALAXYX-PC-Thu_12_04_2014_183023_65\120414-7035-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03417000 PsLoadedModuleList = 0xfffff800`0365a890
Debug session time: Fri Dec  5 05:10:27.821 2014 (UTC + 6:00)
System Uptime: 0 days 0:22:31.508
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8010448028, bf800000, 200401}

Probably caused by : GenuineIntel

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

6: 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: fffffa8010448028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000200401, 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:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0331fb58 fffff800`03a0ea3b : 00000000`00000124 00000000`00000000 fffffa80`10448028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`0331fb60 fffff800`035a3463 : 00000000`00000001 fffffa80`103d44e0 00000000`00000000 fffffa80`103d4530 : hal!HalBugCheckSystem+0x1e3
fffff880`0331fba0 fffff800`03a0e700 : 00000000`00000728 fffffa80`103d44e0 fffff880`0331ff30 fffff880`0331ff00 : nt!WheaReportHwError+0x263
fffff880`0331fc00 fffff800`03a0e052 : fffffa80`103d44e0 fffff880`0331ff30 fffffa80`103d44e0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0331fd50 fffff800`03a0df0d : 00000000`00000008 00000000`00000001 fffff880`0331ffb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0331fd90 fffff800`03a01e88 : 00000000`00000001 fffff880`03317180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0331fdc0 fffff800`0348b4ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0331fdf0 fffff800`0348b313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0331ff30 fffff880`103d1c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0333fb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

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

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try

PCBuilder9342 · 06 Dec 2014

Thank you for the info. I shall try these troubleshooting steps and reply with what happened, if anything.

PCBuilder9342 · 08 Dec 2014

Soooooo I tried doing a quick virus scan with Norton. About 5 seconds after executing the scan I got the same BSOD and 1033 ID upon reboot, *Facepalm* lol. I have now uninstalled Norton and installed Malwarebytes, which I have never had any problems with. I think this may have solved my problems as I left my computer running for about 15 mins without interaction and it did not BSOD on me. I will be leaving it running tomorrow throughout the day to see if this was the root cause, which I think it was.

PCBuilder9342 · 08 Dec 2014

Comp. has been running perfectly all day; no problems. Norton was the problem.