locked
bugcheck code 126 RRS feed

  • Question

  • Hi, I had continuosly crashed my windows 7, could you help me? This are the event properties:


     Nombre de registro:System
    Origen:        Microsoft-Windows-Kernel-Power
    Fecha:         23/05/2012 02:25:19 p.m.
    Id. del evento:41
    Categoría de la tarea:(63)
    Nivel:         Crítico
    Palabras clave:(2)
    Usuario:       SYSTEM
    Equipo:        Klaus-PC
    Descripción:
    Se reinició el sistema sin apagarlo limpiamente primero. Este error puede producirse si el sistema dejó de responder, se bloqueó o se interrumpió el suministro eléctrico de forma inesperada.
    XML de evento:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
        <EventID>41</EventID>
        <Version>2</Version>
        <Level>1</Level>
        <Task>63</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000002</Keywords>
        <TimeCreated SystemTime="2012-05-23T20:25:19.875000000Z" />
        <EventRecordID>19934</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>Klaus-PC</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">126</Data>
        <Data Name="BugcheckParameter1">0xffffffffc0000094</Data>
        <Data Name="BugcheckParameter2">0xfffff80002ac2914</Data>
        <Data Name="BugcheckParameter3">0xfffff88003916908</Data>
        <Data Name="BugcheckParameter4">0xfffff88003916160</Data>
        <Data Name="SleepInProgress">false</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
      </EventData>
    </Event>

    Could you help me?? I don't know what to do. 

    Thanks for your help.

    Wednesday, May 23, 2012 8:43 PM

Answers

  • Hi,

    Please see the bugcheck:

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

    This is a very common bugcheck.  Usually the exception address pinpoints

    the driver/function that caused the problem.  Always note this address

    as well as the link date of the driver/image that contains this address.

    Some common problems are exception code 0x80000003.  This means a hard

    coded breakpoint or assertion was hit, but this system was booted

    /NODEBUG.  This is not supposed to happen as developers should never have

    hardcoded breakpoints in retail code, but ...

    If this happens, make sure a debugger gets connected, and the

    system is booted /DEBUG.  This will let us see why this breakpoint is

    happening.

    Arguments:

    Arg1: ffffffffc0000094, The exception code that was not handled

    Arg2: fffff80002ac2914, The address that the exception occurred at

    Arg3: fffff88003916908, Exception Record Address

    Arg4: fffff88003916160, Context Record Address

    Debugging Details:

    ------------------

    EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x7E

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

    LAST_CONTROL_TRANSFER:  from fffff80002ab8070 to fffff80002ac2914

    STACK_TEXT: 

    fffff880`03916b40 fffff800`02ab8070 : 00000000`00000001 00000000`00000008 00000000`00000001 fffff800`02cfda40 : nt!ExpScanGeneralLookasideList+0x139

    fffff880`03916ba0 fffff800`02ab85c6 : 00000000`00000008 fffff880`03916c10 00000000`00000001 fffffa80`00000000 : nt!ExAdjustLookasideDepth+0x40

    fffff880`03916bd0 fffff800`02d64e6a : fffffa80`018d9660 00000000`00000080 fffffa80`018b7040 00000000`00000001 : nt!KeBalanceSetManager+0x1be

    fffff880`03916d40 fffff800`02abef06 : fffff800`02c40e80 fffffa80`018d9660 fffff800`02c4ecc0 c24c1ffc`c555c335 : nt!PspSystemThreadStartup+0x5a

    fffff880`03916d80 00000000`00000000 : fffff880`03917000 fffff880`03911000 fffff880`03916700 00000000`00000000 : nt!KxStartSystemThread+0x16

    FOLLOWUP_IP:

    nt!ExpScanGeneralLookasideList+139

    fffff800`02ac2914 f7f1            div     eax,ecx

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!ExpScanGeneralLookasideList+139

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4f76721c

    STACK_COMMAND:  .cxr 0xfffff88003916160 ; kb

    FAILURE_BUCKET_ID:  X64_0x7E_nt!ExpScanGeneralLookasideList+139

    BUCKET_ID:  X64_0x7E_nt!ExpScanGeneralLookasideList+139

    Followup: MachineOwner

    ---------

    About bugcheck 0x7E, please refer this article:

    http://msdn.microsoft.com/en-us/library/ff559239(v=vs.85)

    If the issue persists, , you can also contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently.

    Microsoft Customer Support Service (CSS)

    Regards,

    Leo   Huang


    Leo Huang

    TechNet Community Support

    • Marked as answer by Leo Huang Monday, June 4, 2012 2:51 AM
    Wednesday, May 30, 2012 2:48 AM

All replies

  • Please post a copy of your dumpfile as a shared file to your Sky Drive with a link here.
    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

    For advice on how to configure your system to create dump files please read:
    http://support.microsoft.com/kb/254649

    The dumpfile will be created at c:\windows\minidump. You may need to change your settings in Windows to be able to see the file. To show hidden files type Folder Options in the search box above the Start button and select View, Advanced Settings and verify that the box before "Show hidden files and folders" is checked and "Hide protected operating system files" is unchecked. You may need to scroll down to see the second item. You should also make certain that the box before "Hide extensions for known file types" is not checked.


    Hope this helps, Gerry

    Wednesday, May 23, 2012 8:51 PM
  • Thanks Gerry, I copied the dumpfile to my Sky Drive public carpet. if you need any aditional information, let me know. My Windows Live ID is klromero@hotmail.com.



    fco romero

    Thursday, May 24, 2012 12:13 PM
  • You need to post a link to your Sky Drive here.

    Hope this helps, Gerry

    Thursday, May 24, 2012 1:36 PM
  • Sorry, here is it.

    https://skydrive.live.com/redir.aspx?cid=b70a7ae8d98b885f&page=self&resid=B70A7AE8D98B885F!226&parid=B70A7AE8D98B885F!160&authkey=!An2qZc_RxMPxBI8&Bpub=SDX.SkyDrive&Bsrc=Share

    Best regards


    fco romero

    Thursday, May 24, 2012 2:44 PM
  • Hi,

    Please see the bugcheck:

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

    This is a very common bugcheck.  Usually the exception address pinpoints

    the driver/function that caused the problem.  Always note this address

    as well as the link date of the driver/image that contains this address.

    Some common problems are exception code 0x80000003.  This means a hard

    coded breakpoint or assertion was hit, but this system was booted

    /NODEBUG.  This is not supposed to happen as developers should never have

    hardcoded breakpoints in retail code, but ...

    If this happens, make sure a debugger gets connected, and the

    system is booted /DEBUG.  This will let us see why this breakpoint is

    happening.

    Arguments:

    Arg1: ffffffffc0000094, The exception code that was not handled

    Arg2: fffff80002ac2914, The address that the exception occurred at

    Arg3: fffff88003916908, Exception Record Address

    Arg4: fffff88003916160, Context Record Address

    Debugging Details:

    ------------------

    EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x7E

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

    LAST_CONTROL_TRANSFER:  from fffff80002ab8070 to fffff80002ac2914

    STACK_TEXT: 

    fffff880`03916b40 fffff800`02ab8070 : 00000000`00000001 00000000`00000008 00000000`00000001 fffff800`02cfda40 : nt!ExpScanGeneralLookasideList+0x139

    fffff880`03916ba0 fffff800`02ab85c6 : 00000000`00000008 fffff880`03916c10 00000000`00000001 fffffa80`00000000 : nt!ExAdjustLookasideDepth+0x40

    fffff880`03916bd0 fffff800`02d64e6a : fffffa80`018d9660 00000000`00000080 fffffa80`018b7040 00000000`00000001 : nt!KeBalanceSetManager+0x1be

    fffff880`03916d40 fffff800`02abef06 : fffff800`02c40e80 fffffa80`018d9660 fffff800`02c4ecc0 c24c1ffc`c555c335 : nt!PspSystemThreadStartup+0x5a

    fffff880`03916d80 00000000`00000000 : fffff880`03917000 fffff880`03911000 fffff880`03916700 00000000`00000000 : nt!KxStartSystemThread+0x16

    FOLLOWUP_IP:

    nt!ExpScanGeneralLookasideList+139

    fffff800`02ac2914 f7f1            div     eax,ecx

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!ExpScanGeneralLookasideList+139

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4f76721c

    STACK_COMMAND:  .cxr 0xfffff88003916160 ; kb

    FAILURE_BUCKET_ID:  X64_0x7E_nt!ExpScanGeneralLookasideList+139

    BUCKET_ID:  X64_0x7E_nt!ExpScanGeneralLookasideList+139

    Followup: MachineOwner

    ---------

    About bugcheck 0x7E, please refer this article:

    http://msdn.microsoft.com/en-us/library/ff559239(v=vs.85)

    If the issue persists, , you can also contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently.

    Microsoft Customer Support Service (CSS)

    Regards,

    Leo   Huang


    Leo Huang

    TechNet Community Support

    • Marked as answer by Leo Huang Monday, June 4, 2012 2:51 AM
    Wednesday, May 30, 2012 2:48 AM