BSOD after fresh install

[peeld]

I was instructed by the PC shop to re-install windows 7 after they were unable to find any hardware problems which were causing my system to BSOD or randomly reboot.

Today I did a fresh install of Windows 7 Pro 64-bit, Office 2010 and install all important security updates. Within hrs of completing the installation my system has BSOD twice, for different reasons each time.

I would like some ammunition before heading back to the PC shop.

Any help in resolving this would be great.

Uploading dump collection for both crashes.

Also uploaded windows debug output.

Thanks

 

[yowanvista]

There is a high probability that your CPU is defective, are you overlocking?
Dumps directly blame a hardware fault in your CPU, i would recommend that you replace it
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

   Information

Go to your motherboard's website and check your version of your BIOS. See if there are any problems you are having that are solved by a a later version. I do not often recommend flashing the BIOS because there is a risk involved. If there is problem addressed by a BIOS that applies to your computer, consider flashing your BIOS to the latest version. If you choose to do this, flash you BIOS outside of Windows.

Run Prime 95 again to test your CPU and your ram. 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.

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007eae028, f2000000, 10005}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.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: fffffa8007eae028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, 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`031ddb58 fffff800`02a22a3b : 00000000`00000124 00000000`00000000 fffffa80`07eae028 00000000`f2000000 : nt!KeBugCheckEx
fffff880`031ddb60 fffff800`02be67d3 : 00000000`00000001 fffffa80`07eb1a60 00000000`00000000 fffffa80`07eb1ab0 : hal!HalBugCheckSystem+0x1e3
fffff880`031ddba0 fffff800`02a22700 : 00000000`00000728 fffffa80`07eb1a60 fffff880`031ddf30 fffff880`031ddf00 : nt!WheaReportHwError+0x263
fffff880`031ddc00 fffff800`02a22052 : fffffa80`07eb1a60 fffff880`031ddf30 fffffa80`07eb1a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`031ddd50 fffff800`02a21f0d : 00000000`00000008 00000000`00000001 fffff880`031ddfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`031ddd90 fffff800`02a15e88 : 00000000`00000002 fffff880`031d5180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`031dddc0 fffff800`02ad7f2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`031dddf0 fffff800`02ad7d93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`031ddf30 fffff880`047dec61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`031fdc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x2c61


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
---------

 

[peeld]

No I am not over clocking

I have updated the BIOS and started to run the test but the CPU temperature went up to around 100c so I stopped the test.

Do you recommend running the test if the temperature goes this high?

Thanks

 

[Jonathan_King]

The CPU temperature is most likely an indication of what your problem actually is -- overheating temps. Your CPU can supposedly operate safely at 90C, but even that, I'd be hesitant. Take off your CPU cooler and apply some Arctic Silver or similar paste. You may also invest in an aftermarket CPU cooler.

Also ensure no dust has built up in the case, blocking air filters and clogging heat sinks. Use a can of compressed air as necessary, but avoid the vacuum cleaner.

 

[Britton30]

Make sure you clean |carefully| the old thermal paste from your CPU and the base of your cooler.