Frequent BSODs (With .DMP Files)

NatasOmega said:

I recently built my PC and have been experiencing random crashes very often.
Here are my specs:

Operating System: Windows 7 Ultimate x64

Motherboard: 4CoreDual-SATA2 R2.0 (URL)

PSU: (URL)

Processor: Pentium D 950 3.4GHz Dual-Core (URL)


RAM: 2x1GB DDR2 (URL)


CPU Fan: (URL)

Your .dmp file shows a stop error of 0x124 which is a general hardware error .. 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 0x124 - what it means and what to try

Thanks


Ken

Code:

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\010211-32000-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c56000 PsLoadedModuleList = 0xfffff800`02e93e50
Debug session time: Sun Jan  2 22:34:20.078 2011 (GMT-5)
System Uptime: 0 days 0:00:10.984
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

...................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80029bb8f8, 0, 0}

Probably caused by : hardware

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

1: 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: fffffa80029bb8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02fce6f0 fffff800`02f10a89 : fffffa80`029bb8d0 fffffa80`018da680 00000000`0000001a 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fcec10 fffff800`02df2667 : fffffa80`029bb8d0 fffff800`02e6b5f8 fffffa80`018da680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fcec40 fffff800`02d5ac45 : fffff800`02ecd360 fffffa80`029b3838 fffffa80`029b3830 fffffa80`018da680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fcec80 fffff800`02cd3961 : fffff880`0106de00 fffff800`02d5ac20 fffffa80`018da680 02010400`73020103 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fcecb0 fffff800`02f6ac06 : 656f6470`3172796e fffffa80`018da680 00000000`00000080 fffffa80`018c6040 : nt!ExpWorkerThread+0x111
fffff880`02fced40 fffff800`02ca4c26 : fffff880`009e9180 fffffa80`018da680 fffff880`009f3f40 72796431`67633065 : nt!PspSystemThreadStartup+0x5a
fffff880`02fced80 00000000`00000000 : fffff880`02fcf000 fffff880`02fc9000 fffff880`02fce3f0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

Thank you for the reply, I increased the voltage of my RAM and so far there hasn't been any random crashes.

TonyTiger2004 said:

NatasOmega said:

I recently built my PC and have been experiencing random crashes very often.
Here are my specs:

Operating System: Windows 7 Ultimate x64

Motherboard: 4CoreDual-SATA2 R2.0 (URL)

PSU: (URL)

Processor: Pentium D 950 3.4GHz Dual-Core (URL)


RAM: 2x1GB DDR2 (URL)


CPU Fan: (URL)

Like your post, Believe it or not thats very helpful information on here :)

Thank you . I tried to provide as much information as possible, I did some research on these threads before posting also.

cluberti said:

The error would indicate the CPUs were hung synchronizing with each other:

Code:

Proc. Info 0  @ fffffa80029bbb10
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80029bba08
Section       @ fffffa80029bbb90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
Error         : Internal timer (Proc 0 Bank 0)
  Status      : 0xa200000084010400

This is usually one of two reasons - one, the CPU really is going bad, and should be replaced (overclock, or simply a bad part off of the line that failed after some heat was encountered and brought out the flaw) or two, bad RAM (either bad or unstable). It's a hardware error for sure, but it's 99.9999999% of the time one of those two with that particular bugcheck code, callstack, and WHEA record.

It's most likely the RAM in my case. The CPU and RAM is both new, but the RAM was cheap and I read somewhere that skimping on RAM is not a good idea, lol. So far I haven't been having any crashes since I posted and messed around with my BIOS a little, but if the problems happen again I have a friend who's willing to take a look at my PC.
Thank you all for your replies .

Haha, thank you guys . You were very helpful. :)