Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Monday, September 2, 2013

BCCode 50

El equipo se reinició después de una comprobación de errores. La comprobación de errores fue: 0x00000050 (0xfffff8800b130000, 0x0000000000000001, 0xfffff880050423bd, 0x0000000000000002). Se guardó un volcado en: C:\Windows\MEMORY.DMP

References to Vista also apply to Windows 7.

Have you added any hardware lately? Have you updated any driver just before these started? (Check
Control Panel - Windows Updates to see if any drivers were updated there about the time this started)
Main likely culprits are Video driver, other major drivers, memory, and antivirus/antispyware/security
products could be at fault as well as drive issues.

Use the troubleshooter below and refer to the next message for drivers and memory when you get to
those sections and then return back to the troubleshooter as needed.

BCCode: 50     0x00000050


The BCCode 50 usually occurs after the installation of faulty hardware or in the event of failure of installed
hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Another common cause is the installation of a faulty system service.
Antivirus software can also trigger this error, as can a corrupted NTFS volume.
Resolving the Problem Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see
if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run
hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's
manual for your computer.
Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so,
contact the manufacturer of the system service about a possible update. If the error occurs during system
startup, restart your computer, and press F8 at the character-mode menu that displays the operating system
choices. At the resulting Windows Advanced Options menu, choose theLast Known Good Configuration
option. This option is most effective when only one driver or service is added at a time.
Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it
does, contact the manufacturer of the program about a possible update.
Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must
restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for
problems between the SCSI controller and the disk.
Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the
device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.
BCCode: 50      0x00000050*1095.html?order=votes
Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot. To upload all screenshots, it would be best to:
  1. generate the images using the Snipping Tool,
  2. go to where the images are saved,
  3. right click in a blank area within the folder where the images are saved,
  4. create a new folder,
  5. name the folder CPUZ,
  6. select all the images,
  7. place the pointer over an image,
  8. press and hold down the left mouse button and drag the image (all images should move with it),
  9. drop the images into the CPUZ directory you created,
  10. create a compressed (zipped) folder of CPUZ
  11. upload the .zip file to the forums.
Run some hardware diagnostics:
  • If you are overclocking any hardware, please stop.
  • Run FurMark to test the display card for artifacts and temperature issues.
    FurMark Display Card Stress Test
  • Run Display card memory tests to check the display card for memory problems.
    Folding@home - DownloadUtils
  • Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Event Viewer. In Event Viewer, expand Windows Logs, click Application to let it load, right click Application and click Find.... Search for chkdsk or wininit to find the logs.
    For any drives that do not give the message:
    Windows has checked the file system and found no problems
    run disk check again as above. In other words, if it says:
    Windows has made corrections to the file system
    after running the disk check, run the disk check again.
    Check a drive for errors

    Open Event Viewer
  • Run all Basic tests with SeaTools: S.M.A.R.T. Check, Short Drive Self Test, Drive Information, Short Generic, and Long Generic. Run the tests for all HDDs.
    SeaTools for Windows

    SeaTools for DOS
    Hard Drive (HDD) Diagnostics
    Bootable Hard Drive Diagnostics
  • For your SSD, make sure the following are up to date:
    • SSD firmware
    • BIOS Version
    • Chipset Drivers
    • Hard disk controller drivers/SATA drivers
    • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  • Run Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.
    Test RAM With Memtest86+
  • Run Prime95 to test your CPU, RAM modules, and general hardware.
    Prime95 Hardware Stress Testing Steps

Outdated and Problematic Drivers:
You should update/replace/remove the following drivers. Any drivers that are known to cause BSODs, please remove the software or remove the drivers and then remove the device; steps to do so are given after the list of outdated drivers. If you have ASACPI.sys installed, make sure it is updated and not pre-2009; pre-2009 versions are known to cause BSODs:
speedfan.sys Sun Sep 24 07:26:48 2006 (45168798)

To update drivers, make sure to download the drivers from the manufacturer and not using 3rd party programs. Your drivers should be found from your motherboard support site (ASUS, Gigabyte, MSI, etc.) or your vendor support site (Dell, HP, Toshiba, Sony, etc.) first. If you have devices you bought yourself, the drivers for those devices need to be downloaded from the manufacturer support site for those devices. If you need help, let us know.

To remove drivers, do so by uninstalling the device or software associated with the driver. Devices can be uninstalled through device manager, and then the device itself should be physically removed from the system if possible.
Uninstall or change a program

Open Device Manager

Software Concerns:
Start Menu\Programs\GIGABYTE\ET6
Remove Gigabyte Easy Tune 6. It interfaces with the hardware to provide overclocking through software. Even without an overclock enabled, it can still cause crashes. If you used it to overclock, reset all values to their defaults prior to removing the software.
Uninstall or change a program

3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. Any drivers in red should be updated/replaced/removed. You can find links to the driver information and where to update the drivers in the section after the code box:
**************************Sat Jan 19 11:20:08.192 2013 (UTC - 7:00)**************************
speedfan.sys                Sun Sep 24 07:26:48 2006 (45168798)
intelppm.sys                Mon Jul 13 17:19:25 2009 (4A5BC0FD)
amdxata.sys                 Fri Mar 19 10:18:18 2010 (4BA3A3CA)
hcw18bda.sys                Tue Aug 31 07:48:24 2010 (4C7D0828)
atikmpag.sys                Tue Apr 19 19:22:32 2011 (4DAE3558)
atikmdag.sys                Tue Apr 19 19:53:29 2011 (4DAE3C99)
Rt64win7.sys                Tue Sep 27 08:50:33 2011 (4E81E2B9)
lvrs64.sys                  Tue Jan 17 23:40:36 2012 (4F166964)
lvuvc64.sys                 Tue Jan 17 23:41:08 2012 (4F166984)
RtHDMIVX.sys                Mon Jun  4 23:45:14 2012 (4FCD9CEA)
RTKVHD64.sys                Tue Jun 19 02:50:56 2012 (4FE03D70)
MpFilter.sys                Thu Aug 23 17:03:14 2012 (5036B6B2)
**************************Thu Jan 17 07:07:34.066 2013 (UTC - 7:00)**************************
avkmgr.sys                  Wed Sep 19 02:31:52 2012 (505982F8)
avipbb.sys                  Thu Nov 22 03:13:46 2012 (50ADFADA)
avgntflt.sys                Mon Nov 26 09:20:26 2012 (50B396CA)
Try removing one stick of RAM and seeing if the system behaves more stable. If not, remove the other stick and replace it with the first

No comments: