New System Build- Mini-dumps attached

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by mccartm6, May 20, 2011.

  1. mccartm6

    mccartm6 New Member

    Joined:
    May 20, 2011
    Messages:
    4
    Likes Received:
    0
    Ok guys,

    I've been attempting to fix this for 2 weeks. Everything on this build is brand new.


    I've attached a system spec, the mini dumps. Id really appreciate advice on this as I've been into the bowels of Windows 7 following threads from across the internet and I've been unable to fix it.


    View attachment Minidump.zipView attachment System Details.txt


    Much appreciated
    Martin
     
  2. Saltgrass

    Saltgrass Excellent Member
    Microsoft Community Contributor

    Joined:
    Oct 16, 2009
    Messages:
    15,157
    Likes Received:
    393
    I am not the expert here, but you seem to have UltraISO installed and one of the drivers is from 2007. Are you using the latest version? This may not be the cause of your problems, but you might check for an update, or remove the program to test.

    C:\Program Files (x86)\UltraISO\drivers\ISODrv64.sys
    Image name: ISODrv64.sys
    Timestamp: Fri Apr 13 04:42:40 2007 (461F5090)
     
  3. mccartm6

    mccartm6 New Member

    Joined:
    May 20, 2011
    Messages:
    4
    Likes Received:
    0
    Okay so I upgraded ultraiso and did another memtest86 4passes it found nothing.. any other suggestions?
     
  4. kaos

    kaos Senior Member

    Joined:
    May 9, 2011
    Messages:
    1,747
    Likes Received:
    33
    ok lets look what we have here for you :)

    MINIDUMPS

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa800fff2028, be200000, 5110a}
    
    Probably caused by : hardware
    
    Followup: MachineOwner
    ---------
    
    0: 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: fffffa800fff2028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
    Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  f
    
    STACK_TEXT:  
    fffff800`00ba8a98 fffff800`03402903 : 00000000`00000124 00000000`00000000 fffffa80`0fff2028 00000000`be200000 : nt!KeBugCheckEx
    fffff800`00ba8aa0 fffff800`02f9a493 : 00000000`00000001 fffffa80`0db44a60 00000000`00000000 fffffa80`0db44ab0 : hal!HalBugCheckSystem+0x1e3
    fffff800`00ba8ae0 fffff800`034025c8 : 00000000`00000728 fffffa80`0db44a60 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
    fffff800`00ba8b40 fffff800`03401f1a : fffffa80`0db44a60 fffff800`00ba8e70 fffffa80`0db44a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff800`00ba8c90 fffff800`03401dd5 : 00000000`00000008 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff800`00ba8cd0 fffff800`033f5e88 : 00000005`0189dcd1 fffff800`03001e68 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff800`00ba8d00 fffff800`02e82fac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff800`00ba8d30 fffff800`02e82e13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff800`00ba8e70 fffff800`02e90485 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff800`00b9cbf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiTimerExpiration+0x175
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_VRF_PROCESSOR_CACHE
    
    BUCKET_ID:  X64_0x124_GenuineIntel_VRF_PROCESSOR_CACHE
    
    Followup: MachineOwner
    ---------
    
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {3914bdb3, d, 0, fffff80002edd5fc}
    
    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 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 000000003914bdb3, memory referenced
    Arg2: 000000000000000d, IRQL
    Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002edd5fc, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031080e0
    000000003914bdb3 
    
    CURRENT_IRQL:  d
    
    FAULTING_IP: 
    nt!KeUpdateRunTime+9c
    fffff800`02edd5fc 450fb6842470010000 movzx r8d,byte ptr [r12+170h]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff88002f1b900 -- (.trap 0xfffff88002f1b900)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000006a7bc4eb02
    rdx=0000000000001a60 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002edd5fc rsp=fffff88002f1ba90 rbp=0000000000000000
    r8=00000000002cbbd3  r9=00000000002cbbd3 r10=0000000000000c97
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!KeUpdateRunTime+0x9c:
    fffff800`02edd5fc 450fb6842470010000 movzx r8d,byte ptr [r12+170h] ds:3000:00000000`00000170=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ecfc69 to fffff80002ed0700
    
    STACK_TEXT:  
    fffff880`02f1b7b8 fffff800`02ecfc69 : 00000000`0000000a 00000000`3914bdb3 00000000`0000000d 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02f1b7c0 fffff800`02ece8e0 : 00000000`00000000 fffff880`009e9180 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`02f1b900 fffff800`02edd5fc : fffff800`03187000 00000000`00000000 00000000`00002711 fffffa80`0dbe9400 : nt!KiPageFault+0x260
    fffff880`02f1ba90 fffff800`02edd3a1 : 00000000`00000000 fffff880`02f1bb40 fffff880`009e9180 00000000`00000001 : nt!KeUpdateRunTime+0x9c
    fffff880`02f1bac0 fffff880`049529c2 : fffff800`02ede24a 00000000`00312cce fffffa80`0dbe94b8 fffff880`009f40c0 : nt!KiSecondaryClockInterrupt+0x131
    fffff880`02f1bc58 fffff800`02ede24a : 00000000`00312cce fffffa80`0dbe94b8 fffff880`009f40c0 00000000`00000001 : intelppm+0x39c2
    fffff880`02f1bc60 fffff800`02ed8ebc : fffff880`009e9180 fffff880`00000000 00000000`00000000 fffff800`02f89130 : nt!PoIdle+0x53a
    fffff880`02f1bd40 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd00 00000000`00000000 : nt!KiIdleLoop+0x2c
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    intelppm+39c2
    fffff880`049529c2 ??              ???
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  intelppm+39c2
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: intelppm
    
    IMAGE_NAME:  intelppm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd
    
    FAILURE_BUCKET_ID:  X64_0xA_VRF_intelppm+39c2
    
    BUCKET_ID:  X64_0xA_VRF_intelppm+39c2
    
    Followup: MachineOwner
    ---------
    
    
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa800f728028, be200000, 5110a}
    
    Probably caused by : hardware
    
    Followup: MachineOwner
    ---------
    
    0: kd> !anaylze -v
    No export anaylze found
    0: 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: fffffa800f728028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
    Arg4: 000000000005110a, 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:  
    fffff800`00ba8a98 fffff800`02e1f903 : 00000000`00000124 00000000`00000000 fffffa80`0f728028 00000000`be200000 : nt!KeBugCheckEx
    fffff800`00ba8aa0 fffff800`02fdc493 : 00000000`00000001 fffffa80`0f069ea0 00000000`00000000 fffffa80`0f069ef0 : hal!HalBugCheckSystem+0x1e3
    fffff800`00ba8ae0 fffff800`02e1f5c8 : 00000000`00000728 fffffa80`0f069ea0 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
    fffff800`00ba8b40 fffff800`02e1ef1a : fffffa80`0f069ea0 fffff800`00ba8e70 fffffa80`0f069ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff800`00ba8c90 fffff800`02e1edd5 : 00000000`00000008 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff800`00ba8cd0 fffff800`02e12e88 : fffff800`03040e80 fffff800`03040e80 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff800`00ba8d00 fffff800`02ec4fac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff800`00ba8d30 fffff800`02ec4e13 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff800`00ba8e70 fffff800`02ecb1a2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff800`00b9c520 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeferredReadyThread+0x2c2
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
    
    Followup: MachineOwner
    ---------
    
     
  5. kaos

    kaos Senior Member

    Joined:
    May 9, 2011
    Messages:
    1,747
    Likes Received:
    33
    ok start your pc up

    hold F8 as soon as it loads


    select SAFE MODE WITH COMMAND PROMT


    the pc then will load


    when the black box comes up

    type

    verifier /reset

    press enter

    restart ya pc n let me no how it goes..... u might be a happy person :D
     

Share This Page

Loading...