5 Replies Latest reply on Jan 4, 2012 5:09 PM by Jason Tan

    Active system console causing BSOD on 2008 32-bit and 2008 R2


      We are experiencing some problems with Intel ASC 4.4 on 3420GPLC and 3420GPRX motherboards, on 3 out of 20 installed servers we get BSOD every few weeks. We have a different combination of firmware and driver versions (latest, one version old, few versions old), and 2008 32bit and 2008R2 operating systems. Bellow is  minidump crash analysis. Does anybody have simmlar issuses  or resoultion of this problem ?


      : kd> !analyze -v
      *                                                                             *
      *                        Bugcheck Analysis                                    *
      *                                                                             *
      A process or thread crucial to system operation has unexpectedly exited or been
      Several processes and threads are necessary for the operation of the
      system; when they are terminated (for any reason), the system can no
      longer function.
      Arg1: 00000003, Process
      Arg2: 85b49d90, Terminating object
      Arg3: 85b49edc, Process image file name
      Arg4: 81a6ea60, Explanatory message (ascii)
      Debugging Details:
      PROCESS_OBJECT: 85b49d90
      IMAGE_NAME:  _(M___
      MODULE_NAME: _(M___
      FAULTING_MODULE: 00000000
      PROCESS_NAME:  ASCServiceCreat
      BUGCHECK_STR:  0xF4_ASCServiceCreat
      CURRENT_IRQL:  0
      LAST_CONTROL_TRANSFER:  from 81adac20 to 81915b3f
      99a40ccc 81adac20 000000f4 00000003 85b49d90 nt!KeBugCheckEx+0x1e
      99a40cf0 81a392ed 81a6ea60 85b49edc 85b49fb8 nt!PspCatchCriticalBreak+0x73
      99a40d20 81a39294 85b49d90 85e9cd78 00000000 nt!PspTerminateAllThreads+0x2c
      99a40d54 81892c7a 00000074 00000000 0012ef34 nt!NtTerminateProcess+0x1c1
      99a40d54 77ae5ca4 00000074 00000000 0012ef34 nt!KiFastCallEntry+0x12a
      WARNING: Frame IP not in any known module. Following frames may be wrong.
      0012ef34 00000000 00000000 00000000 00000000 0x77ae5ca4
      STACK_COMMAND:  kb
      FOLLOWUP_NAME:  MachineOwner
      FAILURE_BUCKET_ID:  0xF4_ASCServiceCreat_IMAGE__(M___
      BUCKET_ID:  0xF4_ASCServiceCreat_IMAGE__(M___
      Followup: MachineOwner
        • 1. Re: Active system console causing BSOD on 2008 32-bit and 2008 R2
          Jason Tan



          Can you please provide more details on the system configuration you have ?


          System Board


          Firmware level, BIOS, BMC, FRU

          Operating System version and service pack


          Can you also please attach a SEL log ?


          Or you can contact Intel Customer Support at http://www.intel.com/support/9089.htm as they can provide immediate help and a path to escalation if needed.


          thank you,


          - jason

          • 2. Re: Active system console causing BSOD on 2008 32-bit and 2008 R2

            3420GPLC MBO, Xeon X3430, 2008 32-bit/SP2 . While exporting SEL from IASC, I've noticed that i have a gap in SEL (when viewed from IASC in date range  09/28/2011-12/02/2011). Exporting through IPMI connection works ok. BSOD was on 10/15/2011 and 11/28/2011, and system was rebooted via frontpanel. In both cases, after rebooting SEL recorded temperature, current, voltage and fan events. Also, debugging details for 11/28/2011 are slightly different:


            Caused by a session driver not freeing its pool allocations prior to a

            session unload.  This indicates a bug in win32k.sys, atmfd.dll,

            rdpdd.dll or a video driver.


            Arg1: 00000001, session ID

            Arg2: 00000608, number of paged pool bytes that are leaking

            Arg3: 00000000, number of nonpaged pool bytes that are leaking

            Arg4: 00000001, total number of paged and nonpaged allocations that are leaking.

                           nonpaged allocations are in the upper half of this word,

                           paged allocations are in the lower half of this word.


            Debugging Details:


            CUSTOMER_CRASH_COUNT:  1


            BUGCHECK_STR:  0xAB

            PROCESS_NAME:  csrss.exe

            CURRENT_IRQL:  0

            LAST_CONTROL_TRANSFER:  from 81c9527e to 81b13b3f


            90fa6bb4 81c9527e 000000ab 00000001 00000608 nt!KeBugCheckEx+0x1e

            90fa6bf0 81d165aa 85b3f918 00000001 000000aa nt!MiCheckSessionPoolAllocations+0x10b

            90fa6c40 81c38470 85b3b8e8 81b7ed00 90fa6c78 nt!MiDereferenceSessionFinal+0x104

            90fa6c50 81ad9741 00000000 00000000 85b3f8e0 nt!MiDereferenceSession+0x3e

            90fa6c78 81c5eb0a da28cb3b 85d062c0 00000000 nt!MmCleanProcessAddressSpace+0x70f

            90fa6cdc 81c3b457 00000000 85b3f8e0 85b3f901 nt!PspExitThread+0x65d

            90fa6cf4 81af9fba 85d062c0 90fa6d20 90fa6d2c nt!PsExitSpecialApc+0x22

            90fa6d4c 81a90d26 00000001 00000000 90fa6d64 nt!KiDeliverApc+0x1dc

            90fa6d4c 771e5ca4 00000001 00000000 90fa6d64 nt!KiServiceExit+0x56

            WARNING: Frame IP not in any known module. Following frames may be wrong.

            00f0fc9c 00000000 00000000 00000000 00000000 0x771e5ca4



            STACK_COMMAND:  kb



            81c9527e cc              int     3

            SYMBOL_STACK_INDEX:  1

            SYMBOL_NAME:  nt!MiCheckSessionPoolAllocations+10b

            FOLLOWUP_NAME:  MachineOwner

            MODULE_NAME: nt

            DEBUG_FLR_IMAGE_TIMESTAMP:  4dfb5603

            IMAGE_NAME:  memory_corruption

            FAILURE_BUCKET_ID:  0xAB_nt!MiCheckSessionPoolAllocations+10b

            BUCKET_ID:  0xAB_nt!MiCheckSessionPoolAllocations+10b

            Followup: MachineOwne



            We have already tested RAM for corruption and no errors where found. I need to mention that we have 20 indenticaly configured servers, same drivers, same OS and patch level.. All of them are power up in the morning, and powered off around 19-21 pm. Additionaly, UPS is also powered down, so MBO and BMC have fresh start every day.



            Additionaly, we had same BSOD  problem on 3420GPRX MBO, same CPU  with  current available firmware on 2008R2. In both cases, we are using Active System console 4.4.


            My best guess is a bug in IMB or video driver, since system does not have any video at the moment of crash.

            • 3. Re: Active system console causing BSOD on 2008 32-bit and 2008 R2
              Jason Tan

              The log event you sent indicates a pattern of what you described with a daily power off/on.


              On the day you said that a BSOD was experienced, 10/15/2011


              470        10/15/2011       7:04:26 OS Critical Stop #0x00     Run-time Stop                    


              471        10/15/2011       7:04:26 Temperature #0xF4         Unspecified Event Trigger                              


              472        10/15/2011       7:04:26 Voltage #0x03   Unspecified Event Trigger                              


              473        10/15/2011       7:04:26 Current #0x90    Unknown Event Trigger                   


              474        10/15/2011       7:04:26 Fan #0xDC           Unknown Event Trigger                   


              475        10/15/2011       7:04:26 Physical Security #0x60  Unknown Event Trigger   


              Was there an event or BIOS message that showed up on screen when this stop occurred ?


              Also, on the other systems that do not blue screen, do they have IASC installed on them ?

              • 4. Re: Active system console causing BSOD on 2008 32-bit and 2008 R2

                No, there where no BIOS messages on screen. Yes, all of our systems have ASC Console 4.4 installed.

                • 5. Re: Active system console causing BSOD on 2008 32-bit and 2008 R2
                  Jason Tan

                  Do you have any application (a part from IASC) that maybe causing the BSOD ? Do all of the non-failing systems have identical applications installed as compared to the failing systems ?


                  Can you run the SELVIEW utility & sysinfo & attach the results ? I know you did mention you were having issues exporting the SEL via IASC, can you run a separate SEL & SysInfo dump ?


                  System Event Log Viewer for UEFI, Windows and Linux

                  Intel® System Information Retrieval Utility for Windows*