0x1000007e and 0x0000007e are the same problem, see:
Are you using Creative SoundBlaster? If so that may be the problem.
Go here and read the dumpfile:
If Startup Repair's repair mechanism doesn't work, then go back to its "Recovery Options menu" and select command prompt and try the bootrec switches.
The menu I refer to is in this set of directions with a grey background.
bootrec /rebuild BCD In Windows 7, you won't need the DVD to use these repair options, at long long last, but that doesn't help you here with Vista.
In my testing of the Win RE environment, System Restore from the Recovery link on your DVD is also a viable option. Sometimes it works when System Restore from Windows , and system restore from F8's options don't work so I urge you to try it.
If you can't obtain a Vista DVD, then here's what I'd do:
If you get into any of the other safe modes (4 from F8) and one from Startup Repair via the Recovery Link from the Vista DVD, you have many ways to hit system restore, but typing restrui into the run box or restore into the search box above the start button will work
So you have these to try:
From the Win RE Recovery link on your DVD:
From F8 System Restore via:
Safe Mode with Networking
Safe Mode VGA
Safe Mode with Command: At the prompt you would type the command to use for system restore at the safe mode cmd prompt is:
There is an additional tool that might help you in the Win RE panoply of tools. Its use is outlined here in this MSKB and that's bootrec.exe:
How to use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windows Vista
I would urge everyone, in the interest of having the maximum ability to repair Vista, to follow the directions that are linked here from the Win RE team's blog to load Win RE onto their hard drive, analagous to the way some of you loaded the Recovery Console onto your hard drive for use in Windows XP.
Files that help describe the problem:
Microsoft Online Crash Analysis'
There is an important tool that MSFT now provides with Vista SP1. SP2, and Win 7 that may help you:
**How to Make Vista Recovery Disc from MSFT with Startup Repair When You Don't Have a Vista DVD from a PC with Windows Vista SP1 or Newer**:
[Note: This comes from Microsoft. It is available in Vista with Service Pack 1 or Service Pack 2 and in Windows 7 when released. This gives you the same Startup Repair Options from Microsoft *Legally* that you would get on by purchasing a new Vista (or when it RTMs Windows 7 DVD]:
1) It's best to make this "recovery disc" which gives you access to Vista/Win 7's Startup Repair when Vista or Windows 7 is running well, and you aren't in trouble. But when many of you read this, you will be introuble and this is the way to get out. This will help you access StartupRepair to repair a Won't Boot Vista or Windows 7 when the cause is asoftware cause without a hardwarcomponent in the equation and this includes a corrupt driver.
You can do this on a computer running Windows Vista SP1, Windows Vista SP2, or Windows 7. Click Start>Programs>Maintenance>Create a System Repair Disc or simply type "maintenance" into the search box above the Start button.
The utility to make the system repair disc is located at
2) If you have a Vista or Windows 7 Won't Boot situation, and you didn't make this disc in advance--no problem. Either use another pc with Vista SP1 or Newer or borrow a friend's and follow the directions in #1 above.
3) If your friend has an operating system prior to Vista SP1, but has an internet connection on a device that can download files (a computer is best), simply download the .iso from Neowin's site, burn the .iso,and you
will have a Vista or Windows 7 Recovery disc with the full panoply of repair options, including the "bootrec switches" from the command promptthere.
This is a screenshot of the two ways to do this:
This is the link from Neosmart's website to download and burn the .iso that allows you to do the same thing as the Maintenance listing on the Vista SP1 and later Programs menu.
Windows Vista Recovery Disc (Vista Startup Repair .iso Download)
Anyone concerned with the legality, should not be. This is an option that Microsoft wisely elected to put into its operating system with Vista ServicePack 1, and included in Service Pack 2 and Windows 7.
Unfortunately, as of 4/11/09 Microsoft has written nothing in Windows Vista Help about this option, and it is a great feature that is not well known.
They have a decent explanation of Startup Repair, but no mention as to how to access it if you don't have a Vista DVD as shown at this link:
There is no mention at the Vista Help site, at http://support.microsoft.com, or at in any MSKB or in the Vista SP1 release notes.
This solves the problem of the 300 + OEM partners and Microsoft not shipping a Vista DVD with the purchase of a new computer. This has long been needed, and MSFT should be commended for making it available. I haven't seen it mentioned on any of the MSFT newsgroups, though it might have been but I have seen the complaint hundreds if not thousands of times in the last several years including on the XP groups that the person stuck with an XP or a Vista Won't boot blue screen does not have an XP or Vista DVD. This remedies that problem.
In addition, as a second choice (I would definitely try this first), you can use the F8 key to boot to the Windows Advanced Options menu and try those to access System Restore from the Safe Mode options there, or Last Known Good Configuration. Startup Repair and the Boot Rec switches are a considerable
improvement as to efficacy over the F8 (Windows Advanced) options and the now retired Recovery Console.
F8 Key Reaches the Windows Advanced Options Menu (One might work when another does not):
Should you choose to use Safe Mode with Command Prompt, you'll need to type the command for System Restore which is:
%systemroot%\system32\restore\rstrui.exe, and then press ENTER.
Click the Start button the select Run. In the Run box type eventvwr.msc and press the
Essentially the same error as 0x7E above.
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information.
My understanding is that the 0x1 are more likely to be hardware incompatabilities or defects while 0x0 versions are more likely to be software or driver related.
Describes the meaning of your four parameters
1 The exception code that was not handled
2 The address where the exception occurred
3 The address of the exception record
4 The address of the context record
0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.
This can be caused by anything from faulty RAM, an incorrect/corrupt device driver, poorly written/updated software and more commonly under Windows XP Service pack 2, malware/adware installations.
Applications that attempt to violate DEP will receive an exception with status code STATUS_ACCESS_VIOLATION (0xC0000005).
Note: It is possible to "Turn Off" DEP in the boot.ini file but this really would be a last step!
This option is only available on 32-bit versions of Windows when running on processors supporting no-execute protection. It enables no-execute protection (also known as Data Execution Protection - DEP), which results in the Memory Manager marking pages containing data as no-execute so that they cannot be executed as code. This can be useful for preventing malicious code from exploiting buffer overflow bugs with unexpected program input in order to execute arbitrary code. No-execute protection is always enabled on 64-bit versions of Windows on processors that support no-execute protection.
There are several options you can specify with this switch:
/NOEXECUTE=OPTIN Enables DEP for core system images and those specified in the DEP configuration dialog.
/NOEXECUTE=OPTOUT Enables DEP for all images except those specified in the DEP configuration dialog.
/NOEXECUTE=ALWAYSON Enables DEP on all images.
/NOEXECUTE=ALWAYSOFF Disables DEP. (This setting doesn't provide any DEP coverage for any part of the system, regardless of hardware DEP support. The processor doesn't run in Physical Address Extension (PAE) mode unless the /PAE option is present in the boot.ini file.)
My bet would be an incompatible antivirus / firewall (in this case it would be the virtual machine aspect ) if you have a third party one or an incompatible video card.