none
Windows Has Recovered From an Unexpected Error... RRS feed

  • Question

  • This keeps happening and its soooo frustrating!! Can anybody please help!? Pulling my hair out over here!!

     

    Problem signature:

      Problem Event Name: BlueScreen

      OS Version: 6.1.7600.2.0.0.256.1

      Locale ID: 1033

     

    Additional information about the problem:

      BCCode: 7f

      BCP1: 0000000000000008

      BCP2: 0000000080050031

      BCP3: 00000000000006F8

      BCP4: FFFFF80002881ED2

      OS Version: 6_1_7600

      Service Pack: 0_0

      Product: 256_1

    Tuesday, December 6, 2011 1:16 AM

Answers

  • BCCode: 7f 0x0000007f with the 00000008 parameter usually means a hardware issue.


    Have you added hardware or updated drivers recently? Check Control Panel - Windows
    Updates to see if any drivers have been updated there just before this started happening.

    For 7f - this could be a hardware issue such as poorly seated cards or memory, though there are
    other causes. Weak powersupply could also lead to this. Use the troubleshooters above and below
    and when you get to the  drivers and memory sections refer to my next message below and then
    return to the troubleshooters if needed

    If a PC remove ALL power. Open case, remove and reseat ALL cards, memory chips, and ALL
    cables (do not just try to snug) on both ends if they can be reached and on the device ends if not
    (removing the cables and reseating them helps to eliminate minor corrosion).

    Notice the 08 (double fault) as 1st parameter means the are likely two causes. Be sure to Update
    your drivers manually as using Windows Updates only finds certified drivers and Microsoft and
    the Device makers are far behind in that proces. Update NIC, WiFi, BIOS and Video/Display and
    other major drivers

    If a Laptop or a PC you might have to take to a shop (not BestBuy or other BigBox Stores) or your
    System maker's Support.

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

    BCCode: 7F   0x0000007F  which is the same as 0x1000007F

    The UNEXPECTED_KERNEL_MODE_TRAP bug check has a value of 0x0000007F. This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

    This trap could be a bound trap (a trap the kernel is not permitted to catch) or adouble fault(a fault that occurred while processing an earlier fault, which always results in a system failure).

    Parameters

    The first parameter that appears on the blue screen specifies the trap number.

    The most common trap codes include the following:

    • 0x00000000, or Divide by Zero Error, indicates that a DIV instruction is executed and the divisor is zero. Memory corruption, other hardware problems, or software failures can cause this error.
    • 0x00000004, or Overflow, occurs when the processor executes a call to an interrupt handler when the overflow (OF) flag is set.
    • 0x00000005, or Bounds Check Fault, indicates that the processor, while executing a BOUND instruction, finds that the operand exceeds the specified limits. A BOUND instruction ensures that a signed array index is within a certain range.
    • 0x00000006, or Invalid Opcode, indicates that the processor tries to execute an invalid instruction. This error typically occurs when the instruction pointer has become corrupted and is pointing to the wrong location. The most common cause of this error is hardware memory corruption.
    • 0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault

    CAUSE

    Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.

    A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same stack. For example, if two file system filter drivers are attached to the same stack and then the file system recurses back in, the stack overflows.

    Resolving the Problem

    Troubleshooting: If you recently added hardware to the computer, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. Run hardware diagnostics that the system manufacturer supplies to determine which hardware component failed.

    The memory scanner is especially important. Faulty or mismatched memory can cause this bug check. For more informaiton about these procedures, see the owner's manual for your computer. Check that all adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean.

    If the error appears on a newly installed system, check the availability of updates for the BIOS, the SCSI controller, or network cards. These kind of updates are typically available on the Web site or BBS of the hardware manufacturer.

    Confirm that all hard disk drives, hard disk controllers, and SCSI adapters are listed in the Microsoft Windows Marketplace Tested Products List.

    If the error occurred after the installation of a new or updated device driver, you should remove or replace the driver. If, under this circumstance, the error occurs during the startup sequence and the system partition is formatted with NTFS, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you have to start the computer by using the Recovery Console in order to access the file.

    Also restart your computer, and then press F8 at the character-based menu that displays the operating system choices. At theAdvanced Options menu, select theLast Known Good Configuration option. This option is most effective when you add only one driver or service at a time.

    Overclocking (setting the CPU to run at speeds above the rated specification) can cause this error. If you have overclocked the computer that is experiencing the error, return the CPU to the default clock speed setting.

    Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing the error. You can also disable memory caching of the BIOS to try to resolve the problem.

    If you encountered this error while upgrading to a new version of the Windows operating system, the error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. If possible, remove all third-party device drivers and system services and disable any virus scanners before you upgrade. Contact the software manufacturer to obtain updates of these tools. Also make sure that you have installed the latest Windows Service Pack.

    Finally, if all the above steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error.


    BCCode: 7F   0x0000007F  which is the same as 0x1000007F  <-- read this
    http://www.faultwire.com/solutions-fatal_error/Run-a-system-diagnostic-utility-supplied-by-your-0x1000007F-*1304.html
    Rich Prescott | Infrastructure Architect, Windows Engineer and PowerShell blogger | MCITP, MCTS, MCP

    Engineering Efficiency
    @Rich_Prescott
    Client System Administration tool
    AD User Creation tool
    Tuesday, December 6, 2011 1:41 AM