Share via

Win7 blue screen error 0x0000007e (c0000005 .... )

Anonymous
2013-10-01T00:30:51+00:00

My computer crashed on boot up after I had to force restart while playing a game called Rumble Fighter.

I Know the error says "STOP : 0x0000007e (c0000005, 2, 3 , 4) 234 = parameters."

other information i can release is add. information such as:

BCCode: 1000007e

BCP1: C0000005

BCP2: 82C87781

BCP3: 8DF6F46C

BCP4: 8DF6F050

My laptop is a Samsung Rv511 and my OS is Win7 SP1.

my mini dump file: http://www.mediafire.com/download/bja7goe9o1bx1bb/MDMP.zip

All help is welcomed, thanks!

-Bill

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

  1. Anonymous
    2013-10-01T00:59:12+00:00

    Hi Bill,

    All of the attached dump files are of the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) bugcheck.

    This indicates that a system thread generated an exception which the error handler did not catch.

    We seem to be dealing with a variety of driver issues here, so let's analyze this closely:

    In a *1000007E bugcheck, the most important thing (generally) is the 1st parameter. In your case, the 1st parameter is always c0000005 which indicates an access violation occurred.

    If we run an .exr:

    0: kd> .exr 0xffffffff8291646cExceptionAddress: 82c85781 (nt!__InterlockedIncrement+0x00000005)   ExceptionCode: **c0000005 (Access violation)**^^ See?

    Now that we ran the .exr, let's go one step further and run a !thread to get the call stack:

    STACK_TEXT:  82916530 97aea725 00000000 8291654c 97ae548b nt!__InterlockedIncrement+0x5WARNING: Stack unwind information not available. Following frames may be wrong.8291653c 97ae548b 82916940 86898c2c 82916560 AMPPAL+0x137258291654c 97ae4ffc 829165d8 00000003 86898c40 AMPPAL+0xe48b82916560 97afa058 829165d8 86895478 86895460 AMPPAL+0xdffc82916580 97afa23b 829165d8 8689887c 00000000 AMPPAL+0x230588291659c 97aeb167 829165d8 0000000a 00000000 AMPPAL+0x2323b8291661c 8c11eeaa 8675b7b0 8291666c 868720e0 AMPPAL+0x1416782916650 8c11e9e9 c00000bb 8291666c 82916808 ndis!ndisPnPNotifyBinding+0x13b829166ec 8c0f5d99 868720e0 00000000 00000000 ndis!ndisPnPNotifyAllTransports+0x17b82916718 90d5d248 868720e0 82916808 82916744 ndis!NdisFNetPnPEvent+0x9982916728 8c0f5d77 871e5808 82916808 82916808 wfplwf!FilterNetPnPEvent+0x1482916744 90d71cfc 868720e0 82916808 82916770 ndis!NdisFNetPnPEvent+0x7782916754 8c0f5d77 869f8e10 82916808 82916808 pacer!PcFilterPnPEvent+0x1482916770 90d9425c 868720e0 82916808 8291679c ndis!NdisFNetPnPEvent+0x7782916780 8c0f5d77 8677b6c0 82916808 82916808 hssdrv6+0x125c8291679c 9c0393ba 868720e0 82916808 871dbb00 ndis!NdisFNetPnPEvent+0x77829167b4 8c0f5d77 871e5c08 82916808 90d8b1e0 nwifi!FilterNetPnPEvent+0xc6829167d0 90d8460b 868720e0 82916808 868720e0 ndis!NdisFNetPnPEvent+0x77829167ec 8c0cb35f 869fd008 82916808 877ed710 vwififlt!FilterNetPnPEvent+0x4182916860 8c0cdfa6 868720e0 00000000 00000000 ndis!ndisDevicePnPEventNotifyFiltersAndAllTransports+0xe282916898 8c0fcc61 00000000 829168c4 85679000 ndis!ndisPnPPortActivation+0x7b3829168b4 97638af8 868720e0 00000000 00580180 ndis!NdisMNetPnPEvent+0x768291691c 97638b84 868720e0 0000000a 82916940 bcmwl6+0x1caf882916990 97638e18 85679000 00000000 8df8749c bcmwl6+0x1cb84829169f0 9763dd77 8df8749c 8df873bc 85675000 bcmwl6+0x1ce1882916c38 9763ec38 85679000 0e040101 8df8749c bcmwl6+0x21d7782916c6c 9763f5bd 85677b10 0e040101 8df8749c bcmwl6+0x22c3882916ca8 9763f68e 82c17700 9763f7ff 85677a68 bcmwl6+0x235bd82916cc4 9763857a 01679000 85677a20 86872028 bcmwl6+0x2368e82916cdc 8c0ac2d6 85677a68 85677a48 82916d00 bcmwl6+0x1c57a82916cec 82e5f613 86872028 85677a48 871ad020 ndis!ndisDispatchIoWorkItem+0xf82916d00 82cc814b 85677a20 00000000 871ad020 nt!IopProcessWorkItem+0x2382916d50 82e5412b 80000000 a4f353c0 00000000 nt!ExpWorkerThread+0x10d82916d90 82cfb559 82cc803e 80000000 00000000 nt!PspSystemThreadStartup+0x9e00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

    Starting from bottom going upward, we have various bcmwl6.sys calls which is the

    Broadcom 802.11g Network Adapter driver. Going upward some more, we reach an hssdrv6.sys call which is the Hotspot Shield Routing Driver (more than likely the cause here). I have seen it and solved many cases in which it was the cause of the crashes. Let's continue though.... if we go upward some more, we reach a few AMPPAL.sys calls which is the Intel® Centrino® Bluetooth 3.0 + High Speed Virtual Adapter driver.


    Overall, as I said, Hotspot Shield is more than likely causing conflicts here. I recommend removal for troubleshooting purposes ASAP.

    Regards,

    Patrick

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments No comments

Answer accepted by question author

  1. Anonymous
    2013-10-01T14:14:08+00:00

    Thank you all so much! Patrick I owe you my greatest gratitude.

    I uninstalled HSS and restarted but it didn't work, however I system restore'd and it worked after that point and I'm now happily surfing the web.

    This website is awesome and so are the people, I shall definitely use this website before I take it to the local repair man and get charged £50-£100.

    Thanks so much,

    Bill

    Was this answer helpful?

    0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Anonymous
    2013-10-01T01:27:05+00:00

    Patrick may indeed be correct that HotSpot Shield is the cause, especially if he has seen it

    cause similar issues in the recent past. Two observations which might be important is that

    the system might have been prone to instability and HotSpot send it over the edge and that

    the HotSpot drivers are dated 9/17/2013 which means they are likely the newest.

    Definitely check with HotSpot Support as their may be known issues. However be sure to update

    the system as much as possible which might remove the instability.

    I did notice that the two older BSOD events did not have HotSpot running however there were

    a while back and seem to be isolated events.

    Rob - SpiritX

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-10-01T01:07:48+00:00

    Hi,

    Driver Verifier can help find some BSOD issues :

    Using Driver Verifier to identify issues with Windows drivers for advanced users

    http://support.microsoft.com/kb/244617

    How To Troubleshoot Driver Problems in Windows Vista or 7.

    http://www.winvistaclub.com/t79.html 

    Using Driver Verifier

    http://msdn.microsoft.com/en-us/library/ff554113(v=VS.85).aspx 

    How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issues

    http://www.youtube.com/watch?v=\_VwIDD9xngM

    Driver Verifier

    http://www.techsupportforum.com/2110308-post3.html

    Using Driver Verifier

    http://www.faultwire.com/solutions/using\_driver\_verifier.php 

    How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issues

    http://www.youtube.com/watch?v=\_VwIDD9xngM 

    You can disable Driver Verifier

    http://support.microsoft.com/kb/244617 

    Start - type in Search box -> verifier /reset      hit enter to disable

    Use BlueScreenView to see if there is a driver specified in the error message. Also check with

    MyEventViewer at the time of the BlueScreen.

    If Driver Verifier creates a minidump upload it and post the link here so we can analyze it.

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

    References to Vista also apply to Windows 7.

    This is my generic how to for proper driver updates : (Check for BIOS and 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

    Installing and updating drivers in Windows 7 (updating drivers manually using

    the methods above is preferred to ensure the latest drivers from System maker

    and Device makers are found)

    http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.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.

    Stop Windows 7 from Automatically Installing Device Drivers

    http://helpdeskgeek.com/windows-7/stop-windows-7-from-automatically-installing-device-drivers/

    How To Disable Automatic Driver Installation In Windows 7 / Vista

    http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/

    Disable Windows Update Device Driver Search Prompt In Windows 7 / Vista (for

    Professional, Ultimate, and Enterprise)

    http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/

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

    Memory tests do not catch all errors such as mismatched memory (possible

    even for sticks that appear to be identical) and when faster memory is placed

    in system behind slower  memory. So it is best to also swap sticks in and out

    to check for those even if all memory tests fail to show a problem.

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

    For the Vista/Windows 7 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/

    How to Run the Memory Diagnostics Tool in Windows 7

    http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

    Hope this helps.


    Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle <- Mark Twain said it right!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-10-01T01:06:37+00:00

    Hi,

    Results verified by WinDBG, DumpCHK, and BlueScreenVIew.

    The Bug_Check was 7E CAUSE AMPPAL.sys which is the Intel Bluetooth Driver.

    BugCheck 1000007E, {c0000005, 82c59781, 8df7b46c, 8df7b050}

    Probably caused by : AMPPAL.sys ( AMPPAL+13725 )

    AMPPAL.sts dated 9/15/2011 Intel Bluetooth Driver.

    97cdd000 97d1d000   AMPPAL   T (no symbols)          

        Loaded symbol image file: AMPPAL.sys

        Image path: \SystemRoot\system32\DRIVERS\AMPPAL.sys

        Image name: AMPPAL.sys

        Timestamp:        Thu Sep 15 09:48:11 2011 (4E722C4B)

    1. Check with Samsung Support, their on-line documentation and drivers, and ask in

    their forums about any known issue. Update the Intel Bluetooth drivers - no newer

    re-install the same ones. Also check for BIOS, low level chipset drivers, and the major

    on-board and separate device drivers (see driver update methods in the next message.)

    BiosVersion = 03PA.M001.20110312.XW

    BiosReleaseDate = 03/12/2011 <-- check for updates to the BIOS, low level chipset

    drivers, and the major on-board and separate device drivers.

    SystemManufacturer = SAMSUNG ELECTRONICS CO., LTD.

    SystemProductName = RV411/RV511/E3511/S3511/RV711

    BaseBoardManufacturer = SAMSUNG ELECTRONICS CO., LTD.

    BaseBoardProduct = RV411/RV511/E3511/S3511/RV711

    Samsung - Support - click the "Laptops", "All in one", or other appropriate link

    http://www.samsung.com/us/support/main/supportMain.do

    Samsung - Visit Your Country Site

    http://www.samsung.com/us/common/visitcountrysite.html


    2. After checking at Samsung for newer Bluetooth drivers check at Intel.

    Intel Driver Update Utility <-- run this after checking with Samsung

    http://www.intel.com/p/en\_US/support/detect?redirector\_count=1&

    Intel Download Center

    http://downloadcenter.intel.com/

    Intel - Support - Community and Forums

    http://intelopenport.hosted.jivesoftware.com/community/tech


    3. If needed test the memory very thoroughly (see memory test methods in the next

    message).


    4. As needed use ALL the other methods in the troubleshooters below.


    5. If the issues continue run Driver Verifier to see if it can indicate a CAUSE (see Driver

    Verifier methods in the next message).

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

    Check these KB articles :

    "Stop 0x0000007E" or "Stop 0x00000050" Stop error message in Windows 7 or Windows

    Server 2008 R2

    http://support.microsoft.com/kb/979538 

    "Stop 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" error when the GPU

    is under heavy load conditions in Windows 7 or Windows Server 2008 R2

    http://support.microsoft.com/kb/983615


    Resolving stop (blue screen) errors in Windows 7 - has a section for if you can or can't start Windows.

    http://windows.microsoft.com/en-us/windows7/Resolving-stop-blue-screen-errors-in-Windows-7 

    See this thread for information on using BlueScreenView, MyEventViewer, and other methods

    to troubleshoot BlueScreens - top 3 replies (+1 other).

    http://answers.microsoft.com/en-us/windows/forum/windows_7-system/sometimes-i-get-a-blue-screen-when-using-ie-8/c675b7b8-795f-474d-a1c4-6b77b3fcd990---------------------------------------------------------------------------------------------

    References to Vista also apply to Windows 7.BCCode: 7E      0x0000007E  which is also 0x1000007EThis error is usually a driver issue and display adapter (video) driver is the most suspect

    though it could be others. Antivirus/antispyware/security programs, hardware (heat) and

    major software issues can also cause the error. When you get to the driver section of the

    troubleshooter use my generic methods in the next message and then return to the

    troubleshooter if needed.

    Have you added hardware recently or updated drivers? Be sure to look in Control Panel -

    Windows Updates to see if any drivers were updated there. Other lessor possibilities

    include antivirus/anti-spyware/security programs.

    When you get to the driver and memory sections of the troubleshooter refer to the next

    message to update drivers and test memory and then refer back to the troubleshooter

    if needed.

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

    BCCode: 7E      0x0000007E  which is also 0x1000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLEDThe SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000007E. This bug check indicates that a system thread generated an exception that the error handler did not catch.

    Important Info If You Have Received a STOP CodeIf you received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact info for Microsoft or your computer manufacturer, Contact Support.

    If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article Resolving STOP (Blue Screen) Errors in Windows.

    These actions might prevent an error like this from happening again:

    1. Download and install updates and device drivers for your computer from Windows Update.
    2. Scan your computer for computer viruses.
    3. Check your hard disk for errors.

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Parameters

    The following parameters appear on the blue screen.

    CauseThe SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check is a very common bug check. To interpret it, you must identify which exception was generated.

    Common exception codes include the following:

    • 0x80000002: STATUS_DATATYPE_MISALIGNMENT indicates an unaligned data reference was encountered.
    • 0x80000003: STATUS_BREAKPOINT indicates a breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.
    • 0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.

    For a complete list of exception codes, see the Ntstatus.h file that is located in the inc directory of the Microsoft Windows Driver Kit (WDK).

    Resolution

    If you are not equipped to debug this problem, you should use some basic troubleshooting techniques.

    • Make sure you have enough disk space.
    • If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
    • Try changing video adapters.
    • Check with your hardware vendor for any BIOS updates.
    • Disable BIOS memory options such as caching or shadowing.

    If you plan to debug this problem, you might find it difficult to obtain a stack trace. Parameter 2 (the exception address) should identify the driver or function that caused this problem.

    If exception code 0x80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure that a kernel debugger is connected and the system is started with the /DEBUG switch.

    If exception code 0x80000002 occurs, the trap frame supplies additional information.

    If you do not know the specific cause of the exception, consider the following issues:

    • Hardware incompatibility. Make sure that any new hardware that is installed is compatible with the installed version of Windows. For example, you can get information about compatibility with Windows 7 at the Windows 7 Compatibility Center.
    • Faulty device driver or system service. A faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.

    If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, 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 must start the computer by using the Recovery Console to access the file.

    If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, you can remove the service by starting the computer by using the Recovery Console and then deleting the offending system service file.

    Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x7E. 

    You can also disable memory caching of the BIOS might to try to resolve the error. You should also run hardware diagnostics, especially the memory scanner, that the system manufacturer supplies. For more information about these procedures, see the owner's manual for your computer.

    The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk drive. Check for and delete any temporary files that you do not have to have, Internet cache files, application backup files, and .chk files that contain saved file fragments from disk scans. You can also use another hard disk drive with more free space for the installation. You can resolve BIOS problems by upgrading the system BIOS version.

    BCCode: 7E    0x00000007E  which is also 0x1000007E <-- read this link

    http://www.faultwire.com/solutions-fatal\_error/SYSTEM-THREAD-EXCEPTION-NOT-HANDLED-0x0000007E-\*1141.html?order=votes 

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

    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


    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 InformationBlueScreenView scans all your minidump files created during 'blue screen of death'crashes, and displays the information about all crashes in one table - Freehttp://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.

    How to Boot to the System Recovery Options in Windows 7

    http://www.sevenforums.com/tutorials/668-system-recovery-options.html

    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 Windows 7

    http://www.sevenforums.com/tutorials/700-system-restore.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 Repair Windows 7 System Files with System File Checker

    http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

    How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program

    generates in Windows Vista cbs.log (and Windows 7)

    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 Windows 7

    http://www.sevenforums.com/tutorials/433-disk-check.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

    Installing and updating drivers in Windows 7 (updating drivers manually using the methods above

    is preferred to ensure the latest drivers from System maker and Device makers are found)

    http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html

    Stop Windows 7 from Automatically Installing Device Drivers

    http://helpdeskgeek.com/windows-7/stop-windows-7-from-automatically-installing-device-drivers/

    How To Disable Automatic Driver Installation In Windows 7 / Vista

    http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/

    Disable Windows Update Device Driver Search Prompt In Windows 7 / Vista (for Professional,

    Ultimate, and Enterprise)

    http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/


    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 (and Windows 7)

    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 Windows 7 disk

    How to Run a Startup Repair in Windows 7

    http://www.sevenforums.com/tutorials/681-startup-repair.html 

    How to Boot to the System Recovery Options in Windows 7

    http://www.sevenforums.com/tutorials/668-system-recovery-options.html

    How to Create a Windows 7 System Repair Disc

    http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html

    How to Do a Repair Install to Fix Windows 7

    http://www.sevenforums.com/tutorials/3413-repair-install.html

    Hope this helps.


    Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle <- Mark Twain said it right!

    Was this answer helpful?

    0 comments No comments