4 Replies Latest reply on May 5, 2011 4:43 PM by

    DX48BT12

    Zardoc

      Hi all,

       

      I am getting major crash reorts that seem to be related to my processor (Q9450). It could also be the board.

       

      Here is a crash report. I have 6 like it.

       


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


      Loading Dump File [C:\Windows\Minidump\121309-20982-01.dmp]
      Mini Kernel Dump File: Only registers and stack trace are available

      Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
      Executable search path is: C:\Windows
      Windows 7 Kernel Version 7600 MP (4 procs) Free x64
      Product: WinNt, suite: TerminalServer SingleUserTS
      Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
      Machine Name:
      Kernel base = 0xfffff800`02c09000 PsLoadedModuleList = 0xfffff800`02e46e50
      Debug session time: Sun Dec 13 22:15:14.029 2009 (GMT-5)
      System Uptime: 0 days 12:06:09.902
      Loading Kernel Symbols
      ...............................................................
      ................................................................
      .............................................
      Loading User Symbols
      Loading unloaded module list
      ..............
      *******************************************************************************
      *                                                                             *
      *                        Bugcheck Analysis                                    *
      *                                                                             *
      *******************************************************************************

      Use !analyze -v to get detailed debugging information.

      BugCheck 124, {0, fffffa8004b4e028, b2000040, 800}

      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: fffffa8004b4e028, Address of the WHEA_ERROR_RECORD structure.
      Arg3: 00000000b2000040, High order 32-bits of the MCi_STATUS value.
      Arg4: 0000000000000800, 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`042ffa98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


      STACK_COMMAND:  kb

      FOLLOWUP_NAME:  MachineOwner

      MODULE_NAME: hardware

      IMAGE_NAME:  hardware

      DEBUG_FLR_IMAGE_TIMESTAMP:  0

      FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

      BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

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

      0: kd> !analyze -v;!thread;r;kv;lmtn;lmtsmn;.bugcheck
      *******************************************************************************
      *                                                                             *
      *                        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: fffffa8004b4e028, Address of the WHEA_ERROR_RECORD structure.
      Arg3: 00000000b2000040, High order 32-bits of the MCi_STATUS value.
      Arg4: 0000000000000800, 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`042ffa98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


      STACK_COMMAND:  kb

      FOLLOWUP_NAME:  MachineOwner

      MODULE_NAME: hardware

      IMAGE_NAME:  hardware

      DEBUG_FLR_IMAGE_TIMESTAMP:  0

      FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

      BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

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

      Here is another one.

       

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


      Loading Dump File [I:\120109-20061-01.dmp]
      Mini Kernel Dump File: Only registers and stack trace are available

      Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
      Executable search path is: C:\Windows
      Windows 7 Kernel Version 7600 MP (4 procs) Free x64
      Product: WinNt, suite: TerminalServer SingleUserTS
      Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
      Machine Name:
      Kernel base = 0xfffff800`02c57000 PsLoadedModuleList = 0xfffff800`02e94e50
      Debug session time: Fri Nov 27 23:42:57.941 2009 (GMT-5)
      System Uptime: 1 days 11:50:26.321
      Loading Kernel Symbols
      ...............................................................
      ................................................................
      .................................................
      Loading User Symbols
      Loading unloaded module list
      ...............
      *******************************************************************************
      *                                                                             *
      *                        Bugcheck Analysis                                    *
      *                                                                             *
      *******************************************************************************

      Use !analyze -v to get detailed debugging information.

      BugCheck 101, {31, 0, fffff880009ef180, 1}

      Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

      0: kd> !analyze -v;!thread;r;kv;lmtn;lmtsmn;.bugcheck
      *******************************************************************************
      *                                                                             *
      *                        Bugcheck Analysis                                    *
      *                                                                             *
      *******************************************************************************

      CLOCK_WATCHDOG_TIMEOUT (101)
      An expected clock interrupt was not received on a secondary processor in an
      MP system within the allocated interval. This indicates that the specified
      processor is hung and not processing interrupts.
      Arguments:
      Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
      Arg2: 0000000000000000, 0.
      Arg3: fffff880009ef180, The PRCB address of the hung processor.
      Arg4: 0000000000000001, 0.

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


      BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

      CUSTOMER_CRASH_COUNT:  1

      DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

      PROCESS_NAME:  System

      CURRENT_IRQL:  d

      STACK_TEXT: 
      fffff880`03385528 fffff800`02c75443 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009ef180 : nt!KeBugCheckEx
      fffff880`03385530 fffff800`02cd15f7 : 00000000`00000000 fffff800`00000001 00000000`00001389 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
      fffff880`033855c0 fffff800`02c18895 : fffff800`02c3d3c0 fffff880`03385770 fffff800`02c3d3c0 2aaaaaaa`00000000 : nt!KeUpdateSystemTime+0x377
      fffff880`033856c0 fffff800`02cc53f3 : 00000000`51508824 fffff800`02e41e80 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
      fffff880`033856f0 fffff800`02cd6e00 : fffffa80`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
      fffff880`03385880 fffff800`02cb816c : fffffa80`00d55640 00000000`00000000 00000000`00000000 f8a01576`aba80400 : nt!KeFlushMultipleRangeTb+0x260
      fffff880`03385950 fffff800`02cb4a11 : fffffa80`039e5b60 00000000`00000000 fffff880`03385c58 00000000`00000000 : nt!MmSetAddressRangeModified+0x2b0
      fffff880`03385a50 fffff800`02cbc18b : fffffa80`06db2358 fffff800`00000001 00000000`00000001 00000000`00006000 : nt!CcFlushCache+0x561
      fffff880`03385b50 fffff800`02cbcd60 : fffff880`04249d00 fffff880`03385c58 00000000`00000000 fffff800`00000000 : nt!CcWriteBehind+0x1eb
      fffff880`03385c00 fffff800`02cd6161 : fffffa80`039e2be0 fffff800`02fc2504 fffff800`02ece140 fffffa80`00000005 : nt!CcWorkerThread+0x1c8
      fffff880`03385cb0 fffff800`02f6c166 : 480c080c`0c0c040c fffffa80`039e5b60 00000000`00000080 fffffa80`039ce890 : nt!ExpWorkerThread+0x111
      fffff880`03385d40 fffff800`02ca7486 : fffff880`03163180 fffffa80`039e5b60 fffff880`0316dfc0 0c080c0a`04040c04 : nt!PspSystemThreadStartup+0x5a
      fffff880`03385d80 00000000`00000000 : fffff880`03386000 fffff880`03380000 fffff880`033859f0 00000000`00000000 : nt!KxStartSystemThread+0x16


      STACK_COMMAND:  kb

      SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

      FOLLOWUP_NAME:  MachineOwner

      MODULE_NAME: Unknown_Module

      IMAGE_NAME:  Unknown_Image

      DEBUG_FLR_IMAGE_TIMESTAMP:  0

      FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

      BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

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

       

      I seems that the processor or something on the board is freaking out.

       

      I tried stock mem, resets, changed types, ran stock you neme it I tried it.

       

      Got any ideas??

       

      Thanks.