BSOD after using computer a while, BCCode: 50

Yes there are files of the same name in other folders, some are dated 2004. Does that mean I should replace it with the one dated 2009 as well?

leoblack9 said:

Yes there are files of the same name in other folders, some are dated 2004. Does that mean I should replace it with the one dated 2009 as well?

No, you need it, but not the 2005 version.

Well the other similar files I've found are dated 2004. Or did you mean files dated pre-2005?

I'm still having BSODs after for some reason, I'm going to post the dump here

Your crashes indicate memory corruption, hard disk data corruption, hard disk errors, a bad hard disk connection, hard disk controller drivers corruption, or a virus.

• If you are overclocking any hardware, please stop.
  
  
• 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 Check Disk (chkdsk) - Read Event Viewer Log.
  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.
  
  
• Test your drive to make sure it is functioning properly by running all tests available with the Hitachi Drive Fitness Test
  
  
• Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the Good and Free system security combination. for better security steps and scanning tools. Make sure to update the security software before running the full scan.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

There are some gurus on here who recommend removing the ASUS AI suite software since it can be buggy and cause hardware related crashes. May be worth looking into.

writhziden said:

There are some gurus on here who recommend removing the ASUS AI suite software since it can be buggy and cause hardware related crashes. May be worth looking into.

Yes it seems that a lot of ASUS products are causing me trouble lately as zigzag pointed out in the earlier posts in this thread. Makes me think twice about buying some of their products in the future.

Contrary to what you've said about AI Suite I've read from other support sites that it fixes up the the problem with the Asacpi.sys related BSOD's (though I don't have any evidence to prove this aside from my experience that had no BSOD's pointing to Asacpi.sys after I've installed AISuite, which is enough evidence for me).

leoblack9 said:

writhziden said:

There are some gurus on here who recommend removing the ASUS AI suite software since it can be buggy and cause hardware related crashes. May be worth looking into.

Yes it seems that a lot of ASUS products are causing me trouble lately as zigzag pointed out in the earlier posts in this thread. Makes me think twice about buying some of their products in the future.

Contrary to what you've said about AI Suite I've read from other support sites that it fixes up the the problem with the Asacpi.sys related BSOD's (though I don't have any evidence to prove this aside from my experience that had no BSOD's pointing to Asacpi.sys after I've installed AISuite, which is enough evidence for me).

I suspect that the updated Asacpi.sys driver will take care of the BSODs related to it, as well in which case, uninstalling the AI Suite should not cause instability anymore.

Alright, will try that, also I will set the AiTweak (the Bios overclocking utility) settings to manual, to find out if it was another suspect--after I've installed AiSuite to see if it does actually cause something fishy in my system.

Another thing on my mind, do you think I should just do the memory swapping procedure though one my caveats is that I don't have spare motherboards or memory sticks to test so I may not fully know if either the mobo or the ram sticks are at fault.

For memory swapping, I assume you refer to the steps outlined in Memtest86+ if you get errors? I would recommend the memory swapping only if the software fixes do not resolve the problem.