3 Replies Latest reply on Apr 14, 2011 11:52 AM by celda

    BSOD with stop 0x124

    celda

      Hello. I have new notebook Gigabyte m1405m http://www.gigabyte.com/products/product-page.aspx?pid=3360#sp with Core 2 Duo SU7300 and I am experiencing terrible problems with BSOD with stop code 0x124 in random time (about twice a day) with  no mutual actions. I tried two different HDD, two different Windows 7 64bit CZ installations, two different RAM modules.

       

      I have sent this laptop to local Gigabyte representative service, they tested this laptop for about 7 days and returned to me with "no malfunction discovered" statement.

       

      I have minidump files here http://media0.minidump.mypage.cz/files/media0:4da6b0a5cc671.rar.upl/minidump.rar

       

      Microsoft partner made an analyzis of dump here http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/456f620d-7dc7-4e5f-87c6-2e7379cf59f0

       

      with this

       

      *******************************************************************************
      *                                                                             *
      *                        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: fffffa8008a76038, 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:
      ------------------
      OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap
      BUGCHECK_STR:  0x124_GenuineIntel
      CUSTOMER_CRASH_COUNT:  1
      DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
      PROCESS_NAME:  sidebar.exe
      CURRENT_IRQL:  f
      STACK_TEXT: 
      fffff800`00ba8a98 fffff800`03019903 : 00000000`00000124 00000000`00000000 fffffa80`08a76038 00000000`b2000040 : nt!KeBugCheckEx
      fffff800`00ba8aa0 fffff800`031d65a3 : 00000000`00000001 fffffa80`08a76ea0 00000000`00000000 fffffa80`08a76ef0 : hal!HalBugCheckSystem+0x1e3
      fffff800`00ba8ae0 fffff800`030195c8 : 00000000`00000728 fffffa80`08a76ea0 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
      fffff800`00ba8b40 fffff800`03018f1a : fffffa80`08a76ea0 fffff800`00ba8e70 fffffa80`08a76ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
      fffff800`00ba8c90 fffff800`03018dd5 : 00000000`00000002 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
      fffff800`00ba8cd0 fffff800`0300ce88 : 00000000`0def8a9d 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
      fffff800`00ba8d00 fffff800`030befec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
      fffff800`00ba8d30 fffff800`030bee53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
      fffff800`00ba8e70 fffff800`030f5da9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
      fffff880`083371c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0x81
      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
      ---------
      |||||||||||||||||||||||||||||||||||||||||||
      Your BSOD is caused by your processor, contact Intel Technical Support for help.

       

      I have tried to contact Intel Support with no success, hence this is mobile CPU.

       

      I do not understand this analyzis. Thank you for any help.

       

      Thank you,
      Martin Celikovsky

        • 1. Re: BSOD with stop 0x124
          mechbob

          Can you hear the fans running , this sounds like overheating , could be contact between CPU and heat sink could be contact between graphics Chip.?? Do you have a way of monerting temps while machine is running this may help narrow it down ??

          • 2. Re: BSOD with stop 0x124
            mechbob

            Some people have gone to putting shims on the top of the graphics chip , Bronze shims , because the MFG. just put a pice of felt , which does not conduct heat transfer very well.

            • 3. Re: BSOD with stop 0x124
              celda

              Dear Robert,

               

              thank you very much. I have installed Core Temo now, but I dont think this is the problem, becouse I have ran some diagnostic tool with high cpu ans systame usage and it did not result in BSOD. Sometimes my 0x124 happens in completly still state...