Random crashing for unknown reason

[Halopaneo]

Yes, the title is rather vague, but i'm so fed up with this problem I could punch a hole through my computer. I have really no idea of how to check for errors and such thingies on my computer, any who, back to the problem. Im running a HP Pavilion Elite HPE-140f, it worked fine at first but all of a sudden started freezing/crashing. In the beggining I thought it was only when I ran high-end games(ARMA 2, Crysis,etc.) then it started to happen with everything(Minecraft, web-browsing) I have checked multiple people who have the same computer who are having crashing problems, but none seem to be the same as my particular problem. If I could get your help with this it would be much appreciated, thank you!

 

[yowanvista]

Please follow these instructions
www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[Halopaneo]

Here's the crash report and HTML file.

Original OS is Windows 7 64 bit
OEM
Owned it for about 2 1/2 years

 

[yowanvista]

The Realtek NIC driver should be updated
Realtek

A hardware problem is the cause, either your CPu or RAM is defective

Run Prime 95 to test your CPU. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.

www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007b7d028, be000000, 800400}

Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : hardware

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: fffffa8007b7d028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, 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:  f

STACK_TEXT:  
fffff880`0316ca58 fffff800`03219a3b : 00000000`00000124 00000000`00000000 fffffa80`07b7d028 00000000`be000000 : nt!KeBugCheckEx
fffff880`0316ca60 fffff800`02dab513 : 00000000`00000001 fffffa80`07b7ed30 00000000`00000000 fffffa80`07b7ed80 : hal!HalBugCheckSystem+0x1e3
fffff880`0316caa0 fffff800`03219700 : 00000000`00000728 fffffa80`07b7ed30 fffff880`0316ce30 fffff880`0316ce00 : nt!WheaReportHwError+0x263
fffff880`0316cb00 fffff800`03219052 : fffffa80`07b7ed30 fffff880`0316ce30 fffffa80`07b7ed30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0316cc50 fffff800`03218f0d : 00000000`00000004 00000000`00000001 fffff880`0316ceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0316cc90 fffff800`0320ce88 : fffffa80`0a047000 00000000`00000003 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0316ccc0 fffff800`02c9952c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0316ccf0 fffff800`02c99393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0316ce30 fffff880`04c0397a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0318cb60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Rt64win7+0x397a


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

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

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

 

[Halopaneo]

Finished all 3 CPU tests with no errors, currently working on the ram stick tests.

 

[Halopaneo]

Just finished RAM tests with no errors

 

[yowanvista]

Is anything overclocked?

 

[Halopaneo]

I did another memtest and still nothing showed up, how exactly do I check for overclocking?

 

[yowanvista]

I did another memtest and still nothing showed up, how exactly do I check for overclocking?

Enter your BIOS and reset it to default values or set settings to 'Auto'

 

[Halopaneo]

Did a system default restore, also ran a registry cleanup

 

[Halopaneo]

After running registry cleaner, no more of the usual crashing, I now have for the first time seen the BSOD

 

[Halopaneo]

Registry Cleaner cleaned up a bunch of errors, and for the first time I actually saw the BSOD

 

[yowanvista]

Registry cleaners are not recommended, they tend to cause system instability.
Upload a new dump file for analysis

 

[Halopaneo]

2nd Report

here ya go

 

[yowanvista]

The latest dump file still indicates a hardware fault, software changes cannot fix it
Update your BIOS if a newer version is available
Please see this link for possible fixes
www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_[B]PROCESSOR[/B]_MAE

*******************************************************************************
*                                                                             *
*                        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: fffffa8007c33028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, 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:  f

STACK_TEXT:  
fffff880`031dda58 fffff800`02c15a3b : 00000000`00000124 00000000`00000000 fffffa80`07c33028 00000000`be000000 : nt!KeBugCheckEx
fffff880`031dda60 fffff800`02dd9513 : 00000000`00000001 fffffa80`079a3b80 00000000`00000000 fffffa80`079a3bd0 : hal!HalBugCheckSystem+0x1e3
fffff880`031ddaa0 fffff800`02c15700 : 00000000`00000728 fffffa80`079a3b80 fffff880`031dde30 fffff880`031dde00 : nt!WheaReportHwError+0x263
fffff880`031ddb00 fffff800`02c15052 : fffffa80`079a3b80 fffff880`031dde30 fffffa80`079a3b80 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`031ddc50 fffff800`02c14f0d : 00000000`00000004 00000000`00000001 fffff880`031ddeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`031ddc90 fffff800`02c08e88 : 00000000`00000000 00000000`ffffffff 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`031ddcc0 fffff800`02cc752c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`031ddcf0 fffff800`02cc7393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`031dde30 fffff880`0f25f086 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`031fdbc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : usbehci!EHCI_Get32BitFrameNumber+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

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

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

 

[Halopaneo]

Sorry bout me not responding,, but here's what happened. the computer was frustrating me beyond comprehension, I had enough money so i went and bought a new PowerSpec G212. Thank you for the help though.

 

[DELRAYSTAR]

HPE-140 random crash solution: clean graphics card

[FONT=&quot]I had the same issue with my HP HPE-140f. Here's how I fixed mine: Take the Nvidia GT 230 graphics card out of the machine and blow all of the caked dust out of the graphics card's heat sink. Although the card has 4 removable screws that appear to release the heat sink's plastic cover, they do not, and I would not force it. Instead use some wooden drink stirrers (to push the dust forward out of the heat sink between its fins) and a blower to blow the loosened dust out through the fan. The more dust that the heat sink accumulated, the less the fan was able to vent the heat, and the more frequently the computer froze.


[/FONT]