stop error 7e

I get 0x0000007e (0xc0000420, 0x814a636e3, 0x85c074cc, 0x85c071c8) after upgrade is initiated. It successfully copies Vista install files to my XP Pro system, reboots at appropriate time and upon first boot to Vista install environment I get the BSOD message as stated above. I have a ASUS mainboard with most recent BIOS, Athlon 3200+, 1GB RAM. The only vista install newsgroup messages with a similar stop error is related to install as Virtual Machine. This is an in place upgrade on physical machine.

A search on the Microsoft Knowledgebase on "Error 0x0000007e yields this kb article: http://support.microsoft.com/kb/330182/en-us
While it applies to XP it seems to give some good leads.
"violentce" wrote in message

I get 0x0000007e (0xc0000420, 0x814a636e3, 0x85c074cc, 0x85c071c8) after upgrade is initiated. It successfully copies Vista install files to my XP Pro system, reboots at appropriate time and upon first boot to Vista install environment I get the BSOD message as stated above. I have a ASUS mainboard with most recent BIOS, Athlon 3200+, 1GB RAM. The only vista install newsgroup messages with a similar stop error is related to install as Virtual Machine. This is an in place upgrade on physical machine.

"violentce"--
I translate your post to mean (correct me if I am wrong) that you tried to upgrade to some unnamed build of Vista from XP and Vista never saw the light of day on your box. You typed
"upon first boot to Vista install environment I get the BSOD message"
You mean you didn't make it through setup and your upgrade to Vista is unsuccessful. I understand the need for testing of the upgrade by MSFT.
The KB that Colin proferred to you (while many XP KBs, tweaks, regedits, ect. will work in Vista) was aimed at an XP that has the 7e stop error and won't boot. Those type KBs might apply if that were the case. But they aren't going to help in setup of Vista. If for example, you had a memory stick that was incompatible or loose (we see that all the time as the cause of this error in XP--but it's a stop error with a very wide range of etiology) and an XP on the box that won't boot with a 7E it might apply.
Here, unless I misread, you're dealing with a setup that won't complete when you try to upgrade XP to Vista. Setups that botch can and have displayed a wide range of stop errors with the Vista beta.
My recommendation is that you try reburning the ISO, and don't upgrade. We have hashed over the semantics of "clean install in this group and the relative vista clean install.
I would reburn the ISO and take advantage of in setup the option that Colin calls an advanced option to target Vista to a volume or drive that has nothing else on it.
Here are my recommendations of how to burn:
Reburn Option:
1) Burn slowly. 4X should be fine. Some of this probably varies with the DVD writerand the media.
2) Make sure to select an ISO tab if there is one on the burning software, and make sure to close the session on the burn.
3) Try this tweak on your Windows XP drive and burn from there:
Get to Dev Manager by typing devmgmt.msc in run/win key + pause break or Rt.click My Computer>Prop>hardware tab>Device Manager if you like 5 steps instead of one cmd. If you're set to PMI here change to DMO and if set to DMO change to PMI using these 5 steps:
1) Click the + in front of IDE ATA/ATAPI Controllers
2) Double Click the Secondary IDE Controller
3) Click Advanced Settings
4) Under Device 1  Next to Transfer Mode choose DMA (or vise versa)>Click OK
5) Reboot your System
6) Check your burn with a CRC utility and the links for this are below including the direct Taco Bell link. It is very classy, sophisticated, and very Wagner Edstrom/McCann Ericson esque for MSFT to adopt a Taco Bell url for their public Beta 2 CRC checker. *Rock on Redmond Rednecks.*
Obtain CRC Utility for Vista Beta 2 Here: (The CRC utility is a way to check the integrity of the ISO Burn which is probably where your problem lies--it's #1 on the list):
Here's a link:
The CRC utility for Beta 2 is contained here (Scroll down to the bottom under "Additional Information"
Microsoft® Windows® Software Development Kit (SDK) for Beta 2 of Windows Vista and WinFX Runtime Components http://www.microsoft.com/downloads/details.aspx?FamilyId=13F8E273-F5EA-4B7B-B022-97755838DB94&displaylang=en
Additional Information:
To verify that your download of an ISO file for the Windows SDK Beta 2 build is not corrupt, download the CRC Utility. (Note: this is not a Microsoft application. Use at your own risk.)
To run the CRC test, open a command prompt and run the utility. providing it the name of the file (i.e. crc c:\6.0.5383.1.1.WindowsSDK_Vista_idw.DVD.Rel.img) The CRC utility will run two tests on the ISO: it will verify if the ISO is valid, and it will give the AutoCRC signature for the file. The AutoCRC signature for the Windows SDK Beta 2 ISO is 0x28434EEF. You should also confirm the size of the ISO is correct: 1.14 GB (1,229,355,008 bytes).
If it fails any of these three tests, re-download the ISO.
I really like the direct link to it though if you right click CRC here>left click Properties: http://tacobell.iexbeta.com/longhorn/crc.exe
I also understand the need for MSFT to get off its ass and acknowledge on a public site bugs, whether it has fixed them, and what it is doing about them --i.e. "we don't have a clue if they'll be fixed; we have this fixed in RC1 or RC2" or "we have this in the never fix 'cause we can't category" instead of the rambling incomplete "advertisements for marketing" of a few things that will be in RC1 selectively named on blogs like Nick White's Technet so-called Vista Team blog. Here's the typical MSFT cheerleading doc on RC1 (I have posted at length that sending feedback to MSFT is like yelling at the quaterback during an NFL team on TV--he's not getting his plays from you--and you can email the team to try to submit your plays but good luck--Think Bill Purcell:
From Nick White at MSFT in his cheerleading doc on his Vista Cheerleading Blog, on RC1 (which fails to name bugs reported and fixed--this could easily done on a MSFT site). While many builds have had 5000 or so bug submissions, MSFT has the SQL and Cluster servers (they make the software) to sort them and categorize them and list them).
Nick White's [MSFT "Vista team" which I don't know 'cause he doesn't say--he IDs himself this way:
"Hi, my name's Nick White. I work on the Windows Vista Launch Team and manage this, the Windows Vista blog."
Cheerleading Blog on RC1:
While some of these changes may seem small, when you realize that they will affect hundreds of millions of people -- and in some cases, those people will notice the benefit every time they use the operating system -- well, in all it's really pretty awesome. Here are just a few of the changes we've implemented as a direct result of your feedback from Beta 2. Many of these changes are in recent post-Beta 2 builds, and all will definitely be included in our RC-1 release.
From the shell team, changes to Explorer include:
a.. Brought back List mode in our List views b.. The folder tree will now persist in all modes of the Explorer c.. Brought back property editing in Details Pane, and fixed truncation issues in the Details Pane d.. Implemented major performance gains when browsing slow volumes and network shares e.. Made it so .zip and .cab files are sorted along with files, not along with folders f.. Added more polish to Classic-themed Explorer g.. Fixed many heavily-reported drawing artifacts and fit-and-finish bugs Next, while we continue to work on overall system search performance, we've made some pretty cool changes to it for this cycle:
a.. Right-clicking on Start Orb and selecting "Search" now takes you directly to the Search Explorer where you can execute a wider search of the entirety of your PC b.. Updated Search Pane UI; now it's on by default in the Search Explorer and optional in all the other Explorers. It's also more easily read when using Glass c.. Simplified Advanced Search UI found under the advanced drop-down menu Sharing and networking has changed for the better in the following ways:
a.. Re-designed the Network and Sharing Center -- we got a lot of feedback on this one, and hopefully the new design meets everyone's expectations a.. Consolidated the sharing & networking control panels into a single control panel b.. Improved visual design and text simplification of Network & Sharing Center to make it more task-oriented c.. "Mini-map" icons are clickable (e.g., Computer, Network, Internet browser) d.. Integrated sharing controls into the Network and Sharing center a.. Global control for enabling/disabling file sharing b.. Added a drop-down of user accounts to the sharing wizard. This will now link to your Active Directory listings or else show other accounts on the same PC e.. Improved dialog box that helps you determine what type of network (public/private) you are on f.. Text updates for links in left pane g.. Improved usability for "not connected" state b.. When connecting to a network, you should see: a.. Improved detection of existing connection b.. No UAC elevation when connecting to a wireless connection c.. Access to Properties for networks with saved settings now available via the right-click menu c.. The Network Explorer has a number of changes that will help with device discovery. It also features default icons for a number of network device classes such as media players, Xbox, projectors, etc. d.. The Network System Tray is now easier to see and has been changed to give more "clickable area" around the icon itself e.. Finally, for those folks with multiple users on the same PC, we've added support for per-user MIME types The Windows Media Center team has been hard at work too. They have:
a.. Tuned overall Windows Media Center performance. You should see some fairly substantial gains in the post-Beta 2 builds b.. Reduced the number of reliability issues. Fewer crashes and great video playback -- who wouldn't want that? J c.. Tweaked a lot of little UI elements for better usability One thing to check out: When using an Xbox 360 as a Media Center Extender, the remote experience is now full-fidelity. It looks and performs exactly like you're using the PC.
Our security teams have also been listening to you. The System Integrity team has simplified the "out-of-the-box" Windows BitLocker user interface. Its new UI now makes it much, much easier for a Windows Vista Ultimate user to be able to setup BitLocker on TPM 1.2-enabled hardware. The administrator of an Enterprise edition system still has access to all of the features and functionality that BitLocker supports through scripting and command line tools.
Finally, we've gotten lots of great feedback on User Account Control. This is definitely a big feature for this release as far as security goes, and here's how we're making it better post-Beta 2:
a.. Deleting a shortcut from the desktop will no longer require elevation for administrators
b.. Task Manager launches right away and allows the user to elevate later
c.. Copying or moving multiple files to protected folders should require only one prompt to gain access
d.. The Find New Hardware experience has been changed to remove the UAC prompt until the user is ready to install the device
e.. "Set Focus" work has been done so that UAC prompts from applications running in the background do not interrupt users' workflow. The users will instead see a blinking item in the taskbar in these situations
f.. The OS has been scrubbed for UAC prompts, the net benefit being that the number of UAC prompts is now reduced
g.. A much-requested feature from our IT community: Elevated command prompts are distinguished by prefixing "Administrator:" to the title
h.. We've added a new ActiveX Installer Service so that administrators can give Standard Users permissions to install controls from trusted sites
i.. All UAC prompts have been scrubbed so as to be more consistent and informative, and also to provide users with improved context for deciding whether to permit/deny the prompt
Whew, that's quite a list! Like I said, we're all hard at work delivering the best version of Windows yet, so please don't stop sending us feedback. Your suggestions could end up affecting hundreds of millions of people!
Upgrading from XP is in the category "it ain't fixed yet." A high percentage of them are failing.
Good luck,
CH


"violentce" wrote in message

I get 0x0000007e (0xc0000420, 0x814a636e3, 0x85c074cc, 0x85c071c8) after upgrade is initiated. It successfully copies Vista install files to my XP Pro system, reboots at appropriate time and upon first boot to Vista install environment I get the BSOD message as stated above. I have a ASUS mainboard with most recent BIOS, Athlon 3200+, 1GB RAM. The only vista install newsgroup messages with a similar stop error is related to install as Virtual Machine. This is an in place upgrade on physical machine.