Bluescreen stop 0x0000007E

Similar Questions

• error message on bluescreen stop: 0x0000007e (0xc000001d, 0x8aaa7bae, 0xac446c08, 0xac446904)

  XP sp3 and the above error popped up for the first time running.  Any help would be great.

  Thank you, Gary

  Hi Gary,.

  1. don't you make changes to your computer, after which the issue started?

  Follow these steps and check if the problem persists.

  Step 1:

  Start your computer in safe mode and check if the problem persists.

  Step 2:

  If the problem does not occur in the safe, I suggest that you can start your computer in a clean boot State, and check if the problem is related to a software conflict of third.

  Note: The steps to restart your computer as usual.

  Step 3:

  You can also follow the steps in this article and check if that helps.

  http://support.Microsoft.com/kb/827663

  Note: The error code does not match your error code, but the steps still hold good.

• Unable to start - blue screen STOP: 0X0000007E

  original title: STOP: 0X0000007E (0XC0000005, 0X89B16963, 0X8B76B87C, 0X8B76B578)

  I was working on my laptop Acer Aspire and suddenly my restarted windows and then leave her unable to start and just show a blue screen with the error code as STOP: 0X0000007E (0XC0000005, 0X89B16963, 0X8B76B87C, 0X8B76B578).

  I tried to run in safe mode, then even I tried all the options available in the Advanced menu to restart that we get after pressing F8 but just fails. Repair of the system showed the error Impossible to repair in the same way his unable to restore and unable to start with last successful boot setting.

  Kindly let me know what to do I have lots of important data in my hard drive that I don't want to lose.

  Hello

  Unless the drive itself is completely fried the data on disk can be recovered by putting the hard drive
  in another computer as 2nd or a case of external hard drive using a USB connection - then the data
  likely to be backed up or copied to other media.

  Of course, the major problem is that the system does not boot even in Safe Mode.

  Setup/settings (BIOS/CMOS) often F2 so screen shows that it boots CD/DVD on the 1st in the boot order-
  Start with a Windows 7 disc and try the Startup Repair tool. Also, try restoring the system from there. (Don't forget to)
  Set the boot order to when.)

  Those who cannot not helped at all and will need you the help of a real computer store (no leeks and)
  Displays a BestBuy or other stores) or system manufacturer support.

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

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

  Check this thread for more information on using BlueScreenView, MyEventViewer and other methods of
  Troubleshoot the BlueScreens - top 3 answers.

  http://social.answers.Microsoft.com/forums/en-us/vistarepair/thread/3deab2fa-4000-4136-8c78-a3d22b1db009

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

  The system has RAID? If so, it is very suspicious.

  This error is usually a driver problem and display adapter (video) driver is the most suspicious if she
  may be others. Antivirus/antispyware/security programs, equipment (heat) and major software problems
  can also cause the error. When you get to the section of the driver to use the Troubleshoot utility my generic
  methods in the next message and then return to the if necessary troubleshooting tool.

  Have you recently added hardware or drivers updated? Don't forget to look in Control Panel - Windows
  Updates to see if all drivers have been updated it. Other donor opportunities include the antivirus/anti-
  spyware/security programs.

  When you get to the pilot and sections of the memory of the troubleshooter check the following message to
  update drivers and memory test and then return to the troubleshooter if necessary.

  BCCode: 7F 0x0000007E which is also 0x1000007E

  Cause

  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug control is a very common bug control. TO
  interpret, you must identify which exception has been generated.

  Common exception codes are:

  • 0xc0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation has occurred.

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

  Solve the problem

  If you do not have to debug this problem, you must use certain 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
  • Reference of the manufacturer for driver updates.
  • Try changing video cards.
  • Check with your hardware vendor for updates to the BIOS.
  • Disable the BIOS memory options such as implementing caching or shading.

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

  If the exception code 0 x 80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system
  has been launched with the /nodebug. switch. This problem should occur infrequently. If it occurs repeatedly,
  Make sure that a kernel debugger is connected and the system is booted with the Switch/DEBUG .

  In case of exception code 0 x 80000002, the trap frame provides additional information.

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

  • Hardware incompatibility. Make sure all new hardware that is installed is listed in the
  • List of Microsoft Windows Marketplace tested products.
  • Service driver or defective peripheral system. A service driver or defective peripheral system can be
  • responsible for this error. Hardware problems, such as the incompatibilities of the BIOS, memory, conflicts
  • and IRQ conflicts can also generate this error.

  If a driver is listed by name in the bug check message, disable or remove that driver. Disable
  or remove drivers or services that have been recently added. If the error occurs during startup
  sequence and the system partition is formatted with the NTFS file system, you may be able to use safe
  Mode to rename or to delete the faulty driver. If the driver is used as part of the system startup procedure
  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 may be a third remote
  control program. If this software is installed, you can remove the boot of the computer service
  by using the Recovery Console, and then by removing the offending system service file.

  Check the system log in Event Viewer for additional error messages that might help identify the
  device or the driver that generated the bug check 0x7E.

  You can also disable memory cache BIOS may try to resolve the error. You should also
  Run the diagnostics of material, especially the scanner memory, which provides the manufacturer of the system.
  For more information about these procedures, see the manual of your computer.

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

  BCCode: 7F 0x00000007E who is also a 0x1000007E<-- read="">
  * 1141.html? order = votes http://www.faultwire.com/solutions-fatal_error/System-thread-exception-not-HANDLED-0x0000007E-
  -------------------------------------------------------------------------

  Look in the Event Viewer to see if something is reported on those.
  http://www.computerperformance.co.UK/Vista/vista_event_viewer.htm

  MyEventViewer - free - a simple alternative in the standard event viewer
  Windows. TIP - Options - Advanced filter allows you to see a time rather
  of the entire file.
  http://www.NirSoft.NET/utils/my_event_viewer.html

  Here are a few ways to possibly fix the blue screen issue. If you could give the blue screen
  info that would help. Such as ITC and 4 others entered at the bottom left. And all others
  error information such as codes of STOP and info like 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: 0 x 00000000 (oxoooooooo oxoooooooo oxoooooooo oxooooooooo)
  Tcpip.sys - address blocking 0 x 0 00000000 000000000 DateStamp 0 x 000000000

  It is an excellent tool for displaying the blue screen error information

  BlueScreenView scans all your minidump files created during ' blue screen of the.
  death ' crashes and displays information about all accidents of a table.
  Free
  http://www.NirSoft.NET/utils/blue_screen_view.html

  BlueScreens many are caused by drivers of old or damaged, in particular the video drivers
  However, there are other causes.

  You can do mode if necessary safe or the Vista DVD command prompt or
  Options recovery if your system is installed by the manufacturer.

  This tells you how to access the System Recovery Options and/or a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  You can try a system restore to a point before the problem started when one exists.

  How to make a Vista system restore
  http://www.Vistax64.com/tutorials/76905-System-Restore-how.html

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

  Start - type this into the search-> find COMMAND to top box and RIGHT CLICK-
  RUN AS ADMIN

  Enter this at the command 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 can give you the answer if there is a corrupted driver. (Does not work
  tell all possible driver issues).

  Also run CheckDisk, so we cannot exclude as much as possible of the corruption.

  How to run the check disk at startup in Vista
  http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

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

  Often drivers up-to-date will help, usually video, sound, network card (NIC), WiFi, part 3
  keyboard and mouse, as well as of other major device drivers.

  Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
  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
  quit unexpectedly
  http://support.Microsoft.com/kb/958233

  Troubleshooting, STOP error blue screen Vista
  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, it may be necessary.

  The Options or Vista recovery disk Startup Repair

  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 a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  I hope this helps.

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

• Blue error screen Stop 0X0000007E (0XC0000005, 0X8070194F, 0XF78DAC30, 0XF78DA12C) and when ejecting a CD or DVD

  Blue error screen Stop 0X0000007E (0XC0000005, 0X8070194F, 0XF78DAC30, 0XF78DA12C) and when ejecting a CD or DVD

  Said event system category 102 event 1003 error view

  Error 1000007e, parameter1, parameter 2 8070194f, parameter3, parameter4 f78da92c f78dac30 c0000005.

  Customer says that has happened for about a year.  Don't know it please help

  Hello

  Use BlueScreenView, MyEventViewer and other methods of troubleshooting BlueScreens
  See the responses in this thread - high two answers.

  http://social.answers.Microsoft.com/forums/en-us/vistarepair/thread/842fa8cf-535e-4b5d-9416-85eb31edbe6f

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

  References to Vista also apply to Windows 7.

  This error (7th) is usually a driver problem and display adapter (video) driver is the most suspicious if
  It could be others. Antivirus/antispyware/security programs, major software and hardware (heat)
  questions can also cause the error. When you get to the section of the driver to use the Troubleshoot utility my
  generic methods in the next message and then return to the if necessary troubleshooting tool.

  Have you recently added hardware or drivers updated? Don't forget to look in Control Panel - Windows
  Updates to see if all drivers have been updated it. Other donor opportunities include the antivirus/anti-
  spyware/security programs.

  When you get to the pilot and sections of the memory of the troubleshooter check the following message to
  update drivers and memory test and then return to the troubleshooter if necessary.

  BCCode: 7F 0x0000007E

  Cause

  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug control is a very common bug control. TO
  interpret, you must identify which exception has been generated.

  Common exception codes are:

  0xc0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation has occurred.
  For a complete list of exception codes, see the Ntstatus.h file located in the inc directory
  the Microsoft Windows Driver Kit (WDK).

  Solve the problem
  If you do not have to debug this problem, you must use certain 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
  Reference of the manufacturer for driver updates.
  Try changing video cards.
  Check with your hardware vendor for updates to the BIOS.
  Disable the BIOS memory options such as implementing caching or shading.
  If you plan to debug this problem, you may find it difficult to get a stack trace. Parameter 2
  (the address of the exception) must identify the driver or function that caused the problem.

  If the exception code 0 x 80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system
  has been launched with the /nodebug switch... This problem should occur infrequently. If it occurs repeatedly,
  Make sure that a kernel debugger is connected and the system is booted with the/debug switch.

  In case of exception code 0 x 80000002, the trap frame provides additional information.

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

  Hardware incompatibility. Make sure all new hardware that is installed is listed in the
  List of Microsoft Windows Marketplace tested products.
  Service system or driver faulty device. A service driver or defective peripheral system can be
  responsible for this error. Hardware problems, such as the incompatibilities of the BIOS, memory, conflicts
  and IRQ conflicts can also generate this error.
  If a driver is listed by name in the bug check message, disable or remove that driver. Disable
  or remove drivers or services that have been recently added. If the error occurs during startup
  sequence and the system partition is formatted with the NTFS file system, you may be able to use safe
  Mode to rename or to delete the faulty driver. If the driver is used as part of the system startup procedure
  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 may be a third remote
  control program. If this software is installed, you can remove the boot of the computer service
  by using the Recovery Console, and then by removing the offending system service file.

  Check the system log in Event Viewer for additional error messages that might help identify the
  device or the driver that generated the bug check 0x7E.

  You can also disable memory cache BIOS may try to resolve the error. You should also
  Run the diagnostics of material, especially the scanner memory, which provides the manufacturer of the system.
  For more information about these procedures, see the manual of your computer.

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

  BCCode: 7F 0x0000007E<-- read="">
  * 1141.html? order = votes http://www.faultwire.com/solutions-fatal_error/System-thread-exception-not-HANDLED-0x0000007E-

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

  Look in the Event Viewer to see if something is reported on those.
  http://www.computerperformance.co.UK/Vista/vista_event_viewer.htm

  MyEventViewer - free - a simple alternative in the standard event viewer
  Windows. TIP - Options - Advanced filter allows you to see a time rather
  of the entire file.
  http://www.NirSoft.NET/utils/my_event_viewer.html

  Here are a few ways to possibly fix the blue screen issue. If you could give the blue screen
  info that would help. Such as ITC and 4 others entered at the bottom left. And all others
  error information such as codes of STOP and info like 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: 0 x 00000000 (oxoooooooo oxoooooooo oxoooooooo oxooooooooo)
  Tcpip.sys - address blocking 0 x 0 00000000 000000000 DateStamp 0 x 000000000

  It is an excellent tool for displaying the blue screen error information

  BlueScreenView scans all your minidump files created during ' blue screen of the.
  death ' crashes and displays information about all accidents of a table.
  Free
  http://www.NirSoft.NET/utils/blue_screen_view.html

  BlueScreens many are caused by drivers of old or damaged, in particular the video drivers
  However, there are other causes.

  You can do mode if necessary safe or the Vista DVD command prompt or
  Options recovery if your system is installed by the manufacturer.

  This tells you how to access the System Recovery Options and/or a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  You can try a system restore to a point before the problem started when one exists.

  How to make a Vista system restore
  http://www.Vistax64.com/tutorials/76905-System-Restore-how.html

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

  Start - type this into the search-> find COMMAND to top box and RIGHT CLICK-
  RUN AS ADMIN

  Enter this at the command 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 can give you the answer if there is a corrupted driver. (Does not work
  tell all possible driver issues).

  Also run CheckDisk, so we cannot exclude as much as possible of the corruption.

  How to run the check disk at startup in Vista
  http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

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

  Often drivers up-to-date will help, usually video, sound, network card (NIC), WiFi, part 3
  keyboard and mouse, as well as of other major device drivers.

  Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
  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
  quit unexpectedly
  http://support.Microsoft.com/kb/958233

  Troubleshooting, STOP error blue screen Vista
  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, it may be necessary.

  The Options or Vista recovery disk Startup Repair

  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 a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  I hope this helps.

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

• STOP: 0X0000007E (0X00000000, 0 X 0000005, 0 X 82699730, 0X82699A34)

  1. Remember - this is a public forum so never post private information such as numbers of mail or telephone!

  Ideas:

  • You have problems with programs
  • Error messages
  • Recent changes to your computer
  • What you have already tried to solve the problem

  Hello

  This error is usually a driver problem and display adapter (video) driver is the most suspicious if she
  may be others. Antivirus/antispyware/security programs, equipment (heat) and major software problems
  can also cause the error. When you get to the section of the driver to use the Troubleshoot utility my generic
  methods in the next message and then return to the if necessary troubleshooting tool.

  Have you recently added hardware or drivers updated? Don't forget to look in Control Panel - Windows
  Updates to see if all drivers have been updated it. Other donor opportunities include the antivirus/anti-
  spyware/security programs.

  When you get to the pilot and sections of the memory of the troubleshooter check the following message to
  update drivers and memory test and then return to the troubleshooter if necessary.

  BCCode: 7F 0x0000007E

  Cause

  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug control is a very common bug control. To interpret it, you must identify which exception has been generated.

  Common exception codes are:

  • 0xc0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation has occurred.

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

  Solve the problem

  If you do not have to debug this problem, you must use certain 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 cards.
  • Check with your hardware vendor for updates to the BIOS.
  • Disable the BIOS memory options such as implementing caching or shading.

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

  If exception code 0 x 80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system was launched with the /nodebug. switch. This problem should occur infrequently. If it occurs repeatedly, make sure that a kernel debugger is connected and the system is booted with the Switch/DEBUG .

  In case of exception code 0 x 80000002, the trap frame provides additional information.

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

  • Hardware incompatibility. Ensure that any new hardware that is installed is listed in the list of the products tested Microsoft Windows market.
  • Service driver or defective peripheral system. A chauffeur service or defective peripheral system could be responsible for this error. The hardware problems, such as BIOS incompatibilities, conflicts of memory and IRQ conflicts can also generate this error.

  If a driver is listed by name in the bug check message, disable or remove that driver. Disable or remove drivers or services that have been recently added. If the error occurs during the startup sequence and the system partition is formatted with the NTFS file system, you may be able to use Safe Mode to rename or to delete the faulty driver. If the driver is used as part of the start-up procedure of the system 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 may be a third-party remote control program. If this software is installed, you can remove the service by starting the computer by using the recovery and then Console by removing the offending system service file.

  Check the system log in Event Viewer for additional error messages that might help identify the device or driver responsible for control of bug 0x7E.

  You can also disable memory cache BIOS may try to resolve the error. You must also run the diagnostics of material, especially the scanner memory, which provides the manufacturer of the system. For more information about these procedures, see the manual of your computer.

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

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

  Look in the Event Viewer to see if something is reported on those.
  http://www.computerperformance.co.UK/Vista/vista_event_viewer.htm

  MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
  TIP - Options - Advanced filter allows you to see a period of time instead of the entire file.
  http://www.NirSoft.NET/utils/my_event_viewer.html

  Here are a few ways to possibly fix the blue screen issue. If you could give the info from the blue screen that would be
  Help. Such as ITC and 4 others entered at the bottom left. And any other information such as STOP error
  codes and info like 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: 0 x 00000000 (oxoooooooo oxoooooooo oxoooooooo oxooooooooo)
  Tcpip.sys - address blocking 0 x 0 00000000 000000000 DateStamp 0 x 000000000

  It is an excellent tool for displaying the blue screen error information

  BlueScreenView scans all your minidump files created during "blue screen of death," collisions
  Displays information on all the "crash" of a table - free
  http://www.NirSoft.NET/utils/blue_screen_view.html

  BlueScreens many are caused by old or damaged drivers, video drivers in particular, but there are other causes.

  You can follow these steps in the Safe Mode if necessary or the command prompt Vista DVD or Options of recovery if your
  system installed by the manufacturer.

  This tells you how to access the System Recovery Options and/or a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  You can try a system restore to a point before the problem started when one exists.

  How to make a Vista system restore
  http://www.Vistax64.com/tutorials/76905-System-Restore-how.html

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

  Start - type this in the search box-> find COMMAND at the top and RIGHT CLICK – RUN AS ADMIN

  Enter this at the command 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 can give you the answer if there is a corrupted driver. (Says not all possible driver problems).

  Also run CheckDisk, so we cannot exclude as much as possible of the corruption.
  How to run the check disk at startup in Vista
  http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

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

  Often drivers up-to-date will help, usually video, sound, network card (NIC), WiFi, 3rd party keyboard and
  smile, as well as of other major device drivers.

  Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
  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, STOP error blue screen Vista
  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, it may be necessary.

  The Options or Vista recovery disk Startup Repair

  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 a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  I hope this helps.
  Rob - bicycle - Mark Twain said it is good.

• Windows 7 error Stop: 0x0000007E (0xFFFFF8001347FA1, 0xFFFFF880009A9258, 0xFFFFFFFFC000001D, 0xFFFFF880009A8AB0)

  Every time I restart my computer, I get the blue screen of death (the title of this post is the error since the last restart code failed.  System Restore does not work every time.  Last known good configuration does not work.  Usually, I just have to restart the computer several times until something finally works.

  The accidents began to occur in February after a Windows Update (not sure one).  A few days before that I had removed McAfee from the computer and installed Kaspersky, that came with my computer when I bought on Black Friday. I think it's probably one of those two things, the origin of the problem, but I have no idea what to do.

  I restart my computer several times during and after the installation of Kaspersky and all seemed well until the update. 

  Any ideas?

   

  Hello

  When you have installed Kaspersky and uninstalled McAfee you probably went from the stove in
  the fire. Franky, I would ditch as well in favor of Avast or MSE which are much more compatible. See
  My recommendations in a message below.

  Download and SAVE replacements but do not install before you delete these.

  Download - SAVE - go to where you put these UNZIP if necessary - just right-click on - RUN AS ADMIN-
  RESTART after each.

  McAfee removal tool
  http://service.McAfee.com/FAQDocument.aspx?ID=TS100507

  Kaspersky removal tool-
  http://USA.Kaspersky.com/support/home/anti_virus/208279463/?search=remove

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

  Since you have a complex scenario here is what I would try to do.

  Start mode safe mode using F8 as you start or do in regular windows when you can access.

  Use a System Restore Point before you removed McAfee and installed Kaspersky. This should
  also remove the influence of the issue of the possible update.

  How to do a system restore in Windows 7
  http://www.SevenForums.com/tutorials/700-system-restore.html

  Then I would run the tool to remove McAfee as above and install Avast and MSE.

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

  If subsequently, you have a problem to update or you want to manually - control panel - configuration
  Updates - left superiors change settings - set to download and inform you. Once you're of course updates
  are no longer a problem, you can reset to automatic.

  If you need to remove an update - on right lower Installed Updates - uninstall.

  Be sure to run the SFC and CheckDisk using the methods listed below.

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

  For troubleshooting in-depth:

  References to Vista also apply to Windows 7.

  This error (7th) is usually a driver problem and display adapter (video) driver is the most suspicious if
  It could be others. Antivirus/antispyware/security programs, major software and hardware (heat)
  questions can also cause the error. When you get to the section of the driver to use the Troubleshoot utility my
  generic methods in the next message and then return to the if necessary troubleshooting tool.

  Have you recently added hardware or drivers updated? Don't forget to look in Control Panel - Windows
  Updates to see if all drivers have been updated it. Other donor opportunities include the antivirus/anti-
  spyware/security programs.

  When you get to the pilot and sections of the memory of the troubleshooter check the following message to
  update drivers and memory test and then return to the troubleshooter if necessary.

  BCCode: 7F 0x0000007E

  Cause

  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug control is a very common bug control. TO
  interpret, you must identify which exception has been generated.

  Common exception codes are:

  0xc0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation has occurred.
  For a complete list of exception codes, see the Ntstatus.h file located in the inc directory
  the Microsoft Windows Driver Kit (WDK).

  Solve the problem
  If you do not have to debug this problem, you must use certain 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
  Reference of the manufacturer for driver updates.
  Try changing video cards.
  Check with your hardware vendor for updates to the BIOS.
  Disable the BIOS memory options such as implementing caching or shading.
  If you plan to debug this problem, you may find it difficult to get a stack trace. Parameter 2
  (the address of the exception) must identify the driver or function that caused the problem.

  If the exception code 0 x 80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system
  has been launched with the /nodebug switch... This problem should occur infrequently. If it occurs repeatedly,
  Make sure that a kernel debugger is connected and the system is booted with the/debug switch.

  In case of exception code 0 x 80000002, the trap frame provides additional information.

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

  Hardware incompatibility. Make sure all new hardware that is installed is listed in the
  List of Microsoft Windows Marketplace tested products.
  Service system or driver faulty device. A service driver or defective peripheral system can be
  responsible for this error. Hardware problems, such as the incompatibilities of the BIOS, memory, conflicts
  and IRQ conflicts can also generate this error.
  If a driver is listed by name in the bug check message, disable or remove that driver. Disable
  or remove drivers or services that have been recently added. If the error occurs during startup
  sequence and the system partition is formatted with the NTFS file system, you may be able to use safe
  Mode to rename or to delete the faulty driver. If the driver is used as part of the system startup procedure
  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 may be a third remote
  control program. If this software is installed, you can remove the boot of the computer service
  by using the Recovery Console, and then by removing the offending system service file.

  Check the system log in Event Viewer for additional error messages that might help identify the
  device or the driver that generated the bug check 0x7E.

  You can also disable memory cache BIOS may try to resolve the error. You should also
  Run the diagnostics of material, especially the scanner memory, which provides the manufacturer of the system.
  For more information about these procedures, see the manual of your computer.

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

  BCCode: 7F 0x0000007E<-- read="">
  * 1141.html? order = votes http://www.faultwire.com/solutions-fatal_error/System-thread-exception-not-HANDLED-0x0000007E-

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

  Look in the Event Viewer to see if something is reported on those.
  http://www.computerperformance.co.UK/Vista/vista_event_viewer.htm

  MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
  TIP - Options - Advanced filter allows you to see a period of time instead of the entire file.
  http://www.NirSoft.NET/utils/my_event_viewer.html

  Here are a few ways to possibly fix the blue screen issue. If you could give the info to blue screen
  This would help. Such as ITC and 4 others entered at the bottom left. And another error
  information such as the STOP codes and info like 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: 0 x 00000000 (oxoooooooo oxoooooooo oxoooooooo oxooooooooo)
  Tcpip.sys - address blocking 0 x 0 00000000 000000000 DateStamp 0 x 000000000

  It is an excellent tool for displaying the blue screen error information

  BlueScreenView scans all your minidump files created during 'blue screen of death '.
  hangs and displays information about all accidents of a table - free
  http://www.NirSoft.NET/utils/blue_screen_view.html

  BlueScreens many are caused by old or damaged, in particular the video drivers drivers however
  There are other causes.

  You can do mode if necessary safe or the Vista DVD command prompt or
  Options recovery if your system is installed by the manufacturer.

  How to start on the System Recovery Options in Windows 7
  http://www.SevenForums.com/tutorials/668-system-recovery-options.html

  You can try a system restore to a point before the problem started when one exists.

  How to do a system restore in Windows 7
  http://www.SevenForums.com/tutorials/700-system-restore.html

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

  Start - type this in the search box-> find COMMAND at the top and RIGHT CLICK – RUN AS ADMIN

  Enter this at the command prompt - sfc/scannow

  How to fix the system files of Windows 7 with the 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 cbs.log Windows Vista (and Windows 7)
  http://support.Microsoft.com/kb/928228

  The log can give you the answer if there is a corrupted driver. (Says not all possible
  driver problems).

  Also run CheckDisk, so we cannot exclude as much as possible of the corruption.

  How to run the check disk at startup in Windows 7
  http://www.SevenForums.com/tutorials/433-disk-check.html

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

  Often drivers up-to-date will help, usually video, sound, network card (NIC), WiFi, part 3
  keyboard and mouse, as well as of other major device drivers.

  Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
  http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

  Installation and update of drivers to 7 (updated drivers manually using the methods above is)
  to ensure that the latest drivers from the manufacturer of system and device manufacturers are are preferably)
  http://www.SevenForums.com/tutorials/43216-installing-updating-drivers-7-a.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
  quit unexpectedly
  http://support.Microsoft.com/kb/958233

  Troubleshooting Vista Blue Screen, error of JUDGMENT (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, it may be necessary.

  Startup Options recovery or Windows 7 disk repair

  How to run a startup repair in Windows 7
  http://www.SevenForums.com/tutorials/681-startup-repair.html

  How to start on 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

  I hope this helps.

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

• 6910p: STOP: 0x0000007e error

  I'm trying to install XP on an old portable 6910p.  Immediately after loading drivers, I get the dreaded BSOD:

  STOP: 0X0000007E (0XC0000005, 0XF74BE0BF, 0XF78DA208, 0XF78D9F08)

  PCI.sys - address F748E0BF base at F7487000, DateStamp 3b75d1ac

  Here are all the steps I took:

  different memory

  different (standard and SSD) HARD drive

  reset the bios

  bios update

  disabled the additional devices in the bios (bluetooth, wlan, etc.)

  charge sata drivers

  replace windows media

  Started from the external cd drive

  I don't see anything else to try... I'm out of ideas

  HP Compaq 6910p

  s/n: CND74525Z5

  It not.

  He had.

• "A problem has been detected and Windows has shut down to prevent damage to your computer"... * STOP: 0x0000007e (0x805c49b8, 0xf7a172b4, 0 x 80000003, 0xf7a16fb0)... blue screen

  Hello!

  For the life of me I can't figure out how to get my machine to boot successfully. Nothing changes when I choose Safe Mode, last known good Configuration, enable VGA Mode, booting, Directory Services Restore Mode or Debug Mode logging.

  It's very stressful, because I'm right smack dab in the Middle a semester at the College. I have most of what I currently need access to supported illuminates... but not quite all :( It is also very reassuring to be able to take care of the school of work away from the library of the University. Yesterday, my computer was working fine... I think that Windows has completed an update, if I can't remember now. As I woke up this morning, I was not able to boot all the way to Windows only once.

  My laptop is a HP Pavilion dv6000 running XP Media Center, and I have not installed new hardware since I bought the machine about 3 years ago.

  Here are more details, where they can help in the diagnosis of my problem:

  • ID of the system board: 30BB
  • Type of processor: Genuine Intel(r) CPU T2250
  • Processor speed: 1730 MHz
  • Total memory: 1024 MB
  • Video memory up to: 128 MB
  • BIOS version: F.06

  Here's the entire message to the blue screen:
  - - - - - - - - - - - - - - - - - - - -
  A problem has been detected and windows has shut down to prevent damage to your computer.

  If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:

  Make sure you have enough disk space. If a driver is identified in the stop message, disable the driver or check with the manufacturer for driver updates. Try changing video cards.

  Check with your hardware vendor for updates to the BIOS. Disable the BIOS memory options such as implementing caching or shading. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select advanced startup options, and then select Safe Mode.

  Technical information:

  STOP: 0X0000007E (0X805C49B8, 0XF7A172B4, 0 X 80000003, 0XF7A16FB0)
  - - - - - - - - - - - - - - - - - - - -

  I also learned to a blue screen that says something about "PAGE_FAULT_IN_NONPAGED_AREA". I think that this happens when I try to start safe mode.

  Also, I never did much with computer problems beyond what could be repaired with the restoration of the system... so not being is not able to boot at all me has to stop. Please, I beg you! Help me?!

  With great appreciation for your time,.
  Damaya

  Quick suggestion

  Some HP partition the hard drive. have you tried to type F11 or F12 during startup (before that he go to the option mode start screen)? It might take you for a HP recovery program in that partition (because windows don't be loading not to use that recovery)
  Good luck

• Stop: 0x0000007e (0xc000001d, 0 x 80537008, 0xba4c33b8, 0xba4c30b4)

  I received the following during startup error message:

  A problem has been detected and windows has been closed seeded to avoid damage to your computer

  If this is the first time you've seen this stop error screen, restart your computer.  If this screen appears again, follow these steps:

  Make sure you have enough disk space...

  Check with the hardware vendor for updates to the BIOS...

  Technical information:

  STOP: 0X0000007E (0XC000001D, 0 X 80537008, 0XBA4C33B8, 0XBA4C30B4)

  Help, please!

  Uninstall KB977165

  I deleted KB977165 as follows.

  Started by using BartsPECD or use your recovery CD

  Change directory to c:\windows\$ntuninstallkb977165$\spuninst

  Copy the file spuninst.txt spuninst.cmd

  Run the file spuninst.cmd

  He will be back on the change.

  I've been very successful with that.

• Im trying to install windows XP on a hard disk nine and im getting a blue screen Stop: 0x0000007E

  Stop: 0x0000007E (0xC0000005, 0xF748E0bF, 0Fx78DAZ08, 0xF78D9F08)
  PCI.sys - address f748E0BF base at F7487000, Datestamp 3b7d855c

  Hi martydh,

  Thanks for posting. This message is often caused by incompatible hardware. Please remove and unnecessary for PCI cards, cards AGP/PCI-E, external devices and use only the minimum amount of RAM you can. After doing this please try reinstalling the operating system. Also check with the manufacturer of your motherboard OEM or PC to see if it's updated controller drivers, that you can use.

  I hope this helps! Shawn - Support Engineer - MCP, MCDST
  Microsoft Answers Support Engineer
  Visit our Microsoft answers feedback Forum and let us know what you think

• Blue screen with STOP: 0x0000007E (0xc0000005, 0 x 00000066, 0xba4dbc40, 0xba4db93c)

  How to fix blue screen with STOP: 0x0000007E (0xc0000005, 0 x 00000066, 0xba4dbc40, 0xba4db93c)

  These accidents were caused by the corruption of memory (probably a driver).  Run these two tests to check your memory and find which driver is causing the problem.

  If you are overclocking reset all default before running these tests.
  In other words STOP!

  1 - Memtest.

  * Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. "http://www.memtest.org/#downiso"] Memtest86 + - Advanced Memory Diagnostic tool

  * Boot from the CD and let it run at least 5 or 6 passes.

  Remember, anytime Memtest reports errors, it can be bad RAM or a bad motherboard slot.

  Test the sticks individually and if you find a good, test it in all slots.

  Any error is indicative of a memory problem.

  If a well-known stick fails in a slot of motherboard, it's probably the slot.

  http://www.SevenForums.com/tutorials/105647-RAM-test-Memtest86.html

  2. Driver Verifier

  Using Driver Verifier is a dubious proposition. Most of the time it will crash and it will tell you what is the driver. But sometimes it will crash and will not tell you the driver. Sometimes it will crash until you can connect to Windows. If you can't mode without failure, then you will have to resort to editing the registry offline to disable driver verifier.

  I suggest that you first back up your data and make sure you have access to another computer so you can contact us in case of problems. Then do a system restore point (so you can restore the system using the functionality of Vista/Win7 Startup Repair).

  In Windows 7, you can do a startup repair disk by clicking Start... All programs... Maintenance... Create a system - with Windows Vista repair disc, you need to use your drive installation or from the "Repair your computer" option at the top of the Safe Mode menu.

  So, here is the procedure:
  -Go to start and type "auditor" (without the quotes) and press enter
  -Select 'Create a custom settings (for code developers)' and click 'Next '.
  -Select "Select individual settings from the list complete" and click "Next".
  -Select the entire document except for "Low resource Simulation" and click "next".
  -Select "Select driver names from a list", then click "next".
  Select all drivers that are NOT provided by Microsoft, and then click "Next".
  -On the next page, select "Finish".

  Restart the system and wait as he crashed to blue screen. Continue to use your system normally and if you know what are the causes of the crash, do it several times. The objective here is to get the system crash because Driver Verifier is stressing out the drivers. If it is not planted for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

  If you are unable to Windows because it crashes too early, try safe mode.
  If you can't mode without fail, try to use the system from the installation DVD restore to bring the system back to the previous point of restoration that you created.
  http://www.SevenForums.com/tutorials/101379-Driver-Verifier-enable-disable.html

  Further reading
  "http://support.microsoft.com/kb/244617"] using Driver Verifier to identify issues with Windows drivers for users advanced

• Stop: 0x0000007e (0xf77a52b2, 0xf7c84490, 0xc0000065, 0xf7c84190) fltmgr.sys - address f77a52b2 base at f778dooo, datestamp 480251da

  This error on a blue screen when I boot Windows xp pro. Welcome suggestions please.

  Hi John,.

  You can check the following thread link and advice given by Matthew_Ha, moderator of the Forum.

  http://answers.Microsoft.com/en-us/Windows/Forum/windows_xp-system/fltmgrsys-BSOD-when-repairing-Windows-XP/012f5f78-ABA7-4e4e-B41D-c877d343f15f

  You can read the following article and check.

  How to solve an error "Stop 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) code error" in Windows XP

• Impossible to reinstall Windows XP error: BSOD STOP: 0X0000007E (0XC0000005, 0XF78DA208, OXF78D9F08)

  Original title: BSOD

  tried to reinstall windows xp bsod STOP: 0X0000007E, (0XC0000005, 0XF78DA208, OXF78D9F08 * pci.sys_address more numbers to several numbers and a date stamp.)

  Hello

  1. How are you trying to install?

  2 do you use a full version Windows Setup disc or the recovery disk?

  3. at what stage of installation you get the error message?

  I suggest you try the steps from the link below and check if it helps.

  http://support.Microsoft.com/kb/330182

  Additional information:

  How to fix a computer that does not start: http://windows.microsoft.com/en-US/windows-xp/help/setup/how-to-fix-computer-that-will-not-start

  Hope this information is useful.

• blue screen STOP: 0x0000007E

  I use XP and this morning I received the following error message

  STOP: 0X0000007E (0XC0000005, 0X89B8E988, 0XF78DABE8, 0XF78DA8E4)

  I can't restart in safe mode and the research revealed no information about this error. It started when I tried to deactivate restore system., how to fix this?

  Hello

  1 did you changes to the computer before the show?

  You can try the troubleshooting provided in the links below steps to fix the problem.

  How to troubleshoot a Stop error 0x0000007E in Windows XP

  http://support.Microsoft.com/kb/330182

  Error after you upgrade a computer that uses one processor other than a processor of Intel for Windows XP Service Pack 2 or Service Pack 3 for Windows XP: "STOP: 0x0000007E"

  http://support.Microsoft.com/kb/953356

• Blue screen - Stop: 0x0000007E (0xC0000005, 0xF77AF756, 0xF7A0A430, 0xF7A0A12C)

  Original title: need help with Stop: 0x0000007E (0xC0000005, 0xF77AF756, 0xF7A0A430, 0xF7A0A12C)

  Can someone telll me how fix an error that says "Stop: 0x0000007E (0xC0000005, 0xF77AF756, 0xF7A0A430, 0xF7A0A12C)"?

  If the message under your STOP error message indicates this (probably not):

  WUSB54GCx86.sys - address 92 D 89498 base at 92D7c000, Datestamp 45c04cc9

  So the response from Microsoft support technician can help you.

  If the message under your STOP error message indicates this (most likely):

  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

  So the response from Microsoft support technician is not worth reading.

  If this is the case and you have an AMD processor, you must look at this article:

  http://support.Microsoft.com/kb/953356

  If we knew what was your system brand and model and a few other details when you made your initial post or someone have asked a few questions, you would have probably solved this problem in one or two cycles of message, but now 6 days.

  It is the shame that the MS Answers forum does not ask for any kind of information system when a new question is asked and we know absolutely nothing about your system.

  Not knowing the basic information a problem prolongs the frustration and the agony of these issues.

  Thank you MS Answers, allowing the resolution of simple problems as frustrating and a lot of time as possible.