Win7 x64 Locking up & BSOD

[majikmark]

I was out of town for a few months & when I got home Windows said I had quite a few updates to install so I did. I don't know if that is what caused my problems or if there are other issues, but it seems like now anytime I try to do something on my computer (playing .mp3's in Winamp/Windows Media Player, watching .mkv files in VLC Player, downloading files with GrabIt, or copying/moving files around from drive Int./Ext. to drive) it will either freeze/lock up, or every once in a while I get a BSOD. I am running Win 7 Ultimate x64 with Service Pack 1 installed on a Biostar P4M90 motherboard with a Pentium 4 hyperthreading CPU & 2 gigs RAM. Can someone please tell me what's going on or how can I resolve this? Any help is greatly appreciated, I have tried to read the error logs but have no idea what I'm looking at.

Thank you so much for any help you can give.

 

[yowanvista]

Dumps directly blame your CPU, turn off any overclocking and reset your BIOS options to defaults
Test your CPU with Prime95 if the problem persists
http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

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

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff880009c7af0, 0, 0}

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 : intelppm.sys ( intelppm+39c2 )

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - Bugcheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: fffff880009c7af0
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

LAST_CONTROL_TRANSFER:  from fffff80002007818 to fffff80001a8b640

STACK_TEXT:  
fffff880`009c7ab8 fffff800`02007818 : 00000000`0000009c 00000000`00000000 fffff880`009c7af0 00000000`00000000 : nt!KeBugCheckEx
fffff880`009c7ac0 fffff800`02006f57 : 00000000`00000002 00000000`00000000 00000000`00000002 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`009c7c10 fffff800`01ffae88 : 00000000`00000000 fffff880`009bf180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`009c7c40 fffff800`01a89f2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009c7c70 fffff800`01a89d93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009c7db0 fffff880`029e69c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`009d2c98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x39c2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
intelppm+39c2
fffff880`029e69c2 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  intelppm+39c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_intelppm+39c2

BUCKET_ID:  X64_0x9C_GenuineIntel_intelppm+39c2

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

 

[majikmark]

There was another minidump file that was included, is that for the same thngr could that be a different issue?

 

[DeanP]

Upload the dump and read Yowan's advice.

 

[majikmark]

I am going to run the tests tonight since it says it could take quite a few hours. I uploaded 3 different minidump files in Minidump.zip, where one of them is for the MACHINE_CHECK_EXCEPTION, but the others are for something else. I just want to try to get it all worked out before I buy a new CPU, depending on what these CPU burn tests say. I don't overclock & I don't think I changed anything in the BIOS either. Would you please take a look at some of the other dump files as well? Thank you and sorry to be a pain.

 

[majikmark]

I did run the tourture test in Prime95 on my CPU & it came up as saying

[Mar 27 11:25] FATAL ERROR: Final result was 1B5E6FDE, expected: C6D800D6.
[Mar 27 11:25] Hardware failure detected, consult stress.txt file.
[Mar 27 11:25] Torture Test completed 11 tests in 1 hour, 15 minutes - 1 errors, 0 warnings.


Does that mean I need a new CPU? If I do get a new CPU will I have to reinstall Windows or can I just pop a Core2Quad in there and let it rip? If I reformat Windows would that solve my problem?

 

[DeanP]

You just need to replace the CPU, no need to reinstall Windows.