stop error 7F, 00000008

Hi,

This is my generic how to for proper driver updates :

This utility makes it easy to see which versions are loaded :

DriverView - Free - utility displays the list of all device drivers currently loaded on your system. For
each driver in the list, additional useful information is displayed: load address of the driver, description,
version, product name, company that created the driver, and more.
http://www.nirsoft.net/utils/driverview.html

For Drivers check System Maker as fallbacks and Device Maker's which are the most current.
Control Panel - Device Manager - Display Adapter - write down the make and complete model of your
video adapter - double click - Driver's tab - write down the version info. Now click UPdate Driver (this
may not do anything as MS is far behind certifying drivers) - then Right Click - Uninstall - REBOOT
this will refresh the driver stack.

Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard if 3rd party with their
own software and drivers and any other major device drivers you have.

Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and then Device Maker's site
(Realtek, Intel, Nvidia, ATI as examples) and get their latest versions. (Look for BIOS, Chipset and software
updates at System Maker's site while there.)

Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN - REBOOT after each installation.

Always check in Device Manager - Drivers tab to be sure the version you are installing actually shows up. This
is because some drivers rollback before the latest is installed (sound drivers particularly do this) so install a
driver - reboot - check to be sure it is installed and repeat as needed.

Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check manually by model.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

How to Install a Device Driver in Vista Device Manager
http://www.vistax64.com/tutorials/193584-device-manager-install-driver.html

If you update drivers manually then it is a good idea to disable Driver Installations in Windows Updates,
this leaves Windows Updates ON however it will not install drivers which will usually be older and cause
issues. If Updates suggests a new driver then HIDE it (Right Click on it) and then go look for new ones
manually if you wish.

How To Disable Automatic Driver Installation In Windows Vista - Drivers
http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
http://technet.microsoft.com/en-us/library/cc730606(WS.10).aspx

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

To test RAM check here - let it run 4+ hours or so.
www.memtest.org

For the Vista Memory Diagnostic Tool

Start - type in Search box ->  Memory - find Memory Diagnostics tool at top of list - Right Click - RUN AS ADMIN
follow the instructions

Windows Vista: How to Scan / Test your RAM or Memory with Windows Vista Memory Diagnostic Tool
http://www.shivaranjan.com/2007/11/01/windows-vista-how-to-scan-test-your-ram-or-memory-with-windows-vista-memory-diagnostic-tool/

Test Your Computer’s Memory Using Windows Vista Memory Diagnostic Tool
http://www.howtogeek.com/howto/windows-vista/test-your-computers-memory-using-windows-vista-memory-diagnostic-tool/

Hope this helps.

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 a double fault (a fault that occurred while processing an earlier fault, which always results in a system failure).

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:<!---->
  • A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault. If you think this overview has occurred, use the !thread debugger extension to determine the stack limits, and then use the kb (Display Stack Backtrace) debugger command with a large parameter (for example, kb 100) to display the full stack.
  • A hardware problem.

<!---->

The less-common trap codes include the following:

• 0x00000001 — A system-debugger call
• 0x00000003 — A debugger breakpoint
• 0x00000007 — A hardware coprocessor instruction with no coprocessor present
• 0x0000000A — A corrupted Task State Segment
• 0x0000000B — An access to a memory segment that was not present
• 0x0000000C — An access to memory beyond the limits of a stack
• 0x0000000D — An exception not covered by some other exception; a protection fault that pertains to access violations for applications

<!---->

For other trap numbers, see an Intel architecture manual.

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.

Debugging: Always begin with the !analyze debugger extension.

If this extension is not sufficient, use the kv (Display Stack Backtrace) debugger command.

• If kv shows a taskGate, use the .tss (Display Task State Segment) command on the part before the colon.
• If kv shows a trap frame, use the .trap (Display Trap Frame) command to format the frame.
• Otherwise, use the .trap (Display Trap Frame) command on the appropriate frame. (On x86-based platforms, this frame is associated with the procedure NT!KiTrap.)

After using one of these commands, use kv again to display the new stack.

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 the Advanced Options menu, select the Last 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.

===============================================================

Look in the Event Viewer to see if anything is reported about those.
http://www.computerperformance.co.uk/vista/vista_event_viewer.htm

MyEventViewer - Free - a simple alternative to the standard event viewer of Windows.
TIP - Options - Advanced Filter allows you to see a time frame instead of the whole file.
http://www.nirsoft.net/utils/my_event_viewer.html

-------------------------------------------------------------------------
Also do this so you can see the likely bluescreens.

Windows Vista automatically restarts if your PC encounters an error that causes it to crash.
http://www.winvistatips.com/disable-automatic-restart-t84.html

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

Here are some methods to possibly fix the blue screen issue. If you could give the Blue Screen info that would
help. Such as the BCC and the other 4 entries on the lower left. And any other error information such as STOP
codes and info such as IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

As examples :

BCCode: 116
BCP1: 87BC9510
BCP2: 8C013D80
BCP3: 00000000
BCP4: 00000002

or in this format :

Stop: 0x00000000 (oxoooooooo oxoooooooo oxooooooooo oxoooooooo)
tcpip.sys - Address 0x00000000 base at 0x000000000 DateStamp 0x000000000


This is an excellent tool for posting Blue Screen Error Information

BlueScreenView scans all your minidump files created during 'blue screen of death' crashes,
and displays the information about all crashes in one table - Free
http://www.nirsoft.net/utils/blue_screen_view.html


Many BlueScreens are caused by old or corrupted drivers, especially video drivers however there are other causes.

You can do these in Safe Mode if needed or from Command Prompt from Vista DVD or Recovery Options if your
system has that installed by the maker.

This tells you how to access the System Recovery Options and/or from a Vista DVD
http://windowshelp.microsoft.com/Windows/en-US/Help/326b756b-1601-435e-99d0-1585439470351033.mspx

You can try a System Restore back to a point before the problem started if there is one.

How to Do a System Restore in Vista
http://www.vistax64.com/tutorials/76905-system-restore-how.html

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

Start - type this in Search Box ->  COMMAND   find at top and RIGHT CLICK  -  RUN AS ADMIN

Enter this at the prompt - sfc /scannow

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
generates in Windows Vista cbs.log
http://support.microsoft.com/kb/928228

The log might give you the answer if there was a corrupted driver. (Does not tell all the possible driver issues).

Also run CheckDisk so we can rule out corruption as much as possible.
How to Run Check Disk at Startup in Vista
http://www.vistax64.com/tutorials/67612-check-disk-chkdsk.html


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

Often updating drivers will help, usually Video, Sound, Network Card  (NIC), WiFi, 3rd party keyboard and
mouse, as well as other major device drivers.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

How to Install a Device Driver in Vista Device Manager
http://www.vistax64.com/tutorials/193584-device-manager-install-driver.html

How To Disable Automatic Driver Installation In Windows Vista - Drivers
http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
http://technet.microsoft.com/en-us/library/cc730606(WS.10).aspx

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

How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart unexpectedly
http://support.microsoft.com/kb/958233

Troubleshooting Vista Blue Screen, STOP Errors
http://www.chicagotech.net/vista/vistabluescreen.htm

Understanding and Decoding BSOD (blue screen of death) Messages
http://www.taranfx.com/blog/?p=692

Windows - Troubleshooting Blue Screen Errors
http://kb.wisc.edu/page.php?id=7033

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

In some cases this might be required.

StartUp Repair from Recovery Options or Vista disk

How to do a Startup Repair
http://www.vistax64.com/tutorials/91467-startup-repair.html

This tells you how to access the System Recovery Options and/or from a Vista DVD
http://windowshelp.microsoft.com/Windows/en-US/Help/326b756b-1601-435e-99d0-1585439470351033.mspx

Hope this helps.