Unable to boot - Blue Screen STOP: 0X0000007E

Hi,

Unless the drive itself is totally fried the data on the drive can be recovered by putting the hard drive

into another computer as 2nd or into a external drive case using a USB connection - then the data

can be backed up and/or copied to other media.

Of course the major issue is that the system will not even boot in Safe Mode.

Setup/Settings (BIOS/CMOS) often F2 so watch screen as it boots - set CD/DVD to 1st in boot order -

boot with a Windows 7 disk and try StartUp Repair. Also try System Restore from there. (Be sure to

set the boot order back when done.)

Those may not help at all and then you would need the help of a real computer shop (not leeks and

peeks at a BestBuy or other Big Box Stores) or the System maker's Support.

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

Here are the usual methods to troubleshoot bluescreens if you can gain some access and still have a

problem.

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

troubleshoot BlueScreens - top 3 replies.

http://social.answers.microsoft.com/Forums/en-US/vistarepair/thread/3deab2fa-4000-4136-8c78-a3d22b1db009

---

Does the system have RAID? If so that is very suspect.

This 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

Cause

The 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:

• 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 theinc directory of

the Microsoft Windows Driver Kit (WDK).

Resolving the Problem

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 listed in the
• Microsoft Windows Marketplace Tested Products List.
• 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

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 ofWindows. 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.

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.

---

Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.