STOP 0x0000007E Error | Tips & Solutions
As a rule, the STOP 0x0000007E Error and BSOD appear at startup after Windows upgrade. The complete error message is similar to the following:
STOP: 0x0000007E (0xc0000005, 0x804E518E, 0xFC938104, 0xFC937E04) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Using 3 or 4 RAM Modules
STOP 0x0000007E often occurs when you install more than 2 RAM modules on a computer with a 64 bit Vista. First of all, make sure the motherboard supports that memory size. In addition, test all the new modules with MemTest. If all is correct and flawless, install the KB929777 for Vista.
##STOP 0x0000007E and Checked DVD Build of Vista I Some users report the STOP 0x0000007E when installing or trying to boot from checked DVD Build of Vista I. The error message looks like this:
STOP 0x0000007E (0xC0000420,0x850922EE,0X858056B8,0X858053B4)
And includes the acpi.sys file in a string like the following:
acpi.sys - Address 850922EE base at 85044000, Datestamp 4549ac8d
Try entering BIOS setup, restore default settings and enable plug and play option.
STOP 0x0000007E error and other Windows errors are often caused by egistry errors. Corrupt registry entries accumulate as you delete on install new programs, resulting in software and hardware conflicts and slowing down your computer. You should check your registry for orphaned entries and remove them, very often that helps resolve errors.
If you are not a computer pro you would hardly understand what the registry contents represent and there is a risk to damage important entries and disable the system. In this case we would not recommend to check and repair your registry manually. Use special software to repair your registry.
If you encounter 0x0000007E for the first time, rebooting your computer may help. But as the number of invalid registry entries grows, the errors will appear with an increasing frequency.
Error after Windows XP Upgrade
This is a common occurrence of 0x0000007E. The message looks like this (the parameters besides 0x0000007E may vary):
STOP: 0x0000007E (0x0000007E, 0x804E518E, 0xFC938104, 0xFC937E04) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
WUSB54GCx86.sys- Address 92D89498 base at 92D7c000, Datestamp 45c04cc9
Microsoft suggests the following possible causes:
- lack of disk space
- incompatible BIOS settings or outdated BIOS
- incompatible/ damaged video drivers or system service
- third-party remote control programs
When the cause of 0x0000007E error is not obvious, we recommend to make your computer configuration as simple as possible, use as little devices as you can and remove or disable third-party drivers before you start troubleshooting. If the error disappears, start adding new devices and install drivers one by one until the error occurs again (if at all). This method helps detect the source of the 0x0000007E error and works with other Windows BSOD errors.
Make sure you have enough disk space. Start up in Safe mode and delete old/ unnecessary/ temporary files if the space is insufficient. Alternatively, you can use an operating system on another hard drive with sufficient disk space to access the files on your current hard drive.
You might need to update BIOS (contact your vendor for the update) to resolve 0x0000007E.
Often, 0x0000007E error message includes Win32k.sys that indicates a conflict with a third-party remote control program. Use Recovery Console to delete the problematic service file.
Incompatible drivers are another possible cause of 0x0000007E. If the error message includes a driver's name or another file's name, disable it, update or remove if updating doesn't help. (The example above points to WUSB54GCx86.sys, a driver for wireless USB adapter). Remove newly installed drivers. If 0x0000007E problem remains after driver update, remove all drivers not digitally signed by Microsoft and all third-party drivers (remover them form %Windir%\System32\Drivers to another folder. You can do so by accessing your hard disk from Windows installation on another hard drive or Recovery Console.) Attention! Don't remove IDE or SCSI controller drivers, or files with 13/8/2001 creation date!
We hope the steps above helped you resolve 0x0000007E. If nothing of the above helped, use the following solution: