BSOD seemingly random

Hello, BS Dang and welcome to the Forums. I need you to do something for me.

Please fill out your System Specs

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. System Info - See Your System Specs

I looked at your last 5 dump files and found

Code:

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
 the operating system. The only supported way to extend a kernel
 mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000000
Arg3: fffffa8009ede980
Arg4: 0000000000000000
Debugging Details:

Code:

BUGCHECK_STR:  0xc4_91
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  ExpressTray.exe

Why is Driver verifier enabled? Please turn it off Driver Verifier - Enable and Disable. What program does that go to? Either update the driver or uninstall it.

Code:

BugCheck A, {80, 2, 1, fffff80003091601}
*** WARNING: Unable to verify timestamp for mssmbios.s}s
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.s}s
Probably caused by : memory_corruption
Followup: memory_corruption

Code:

Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff880521bff42, 2, 1, fffff80003096ea8}
Probably caused by : memory_corruption
Followup: memory_corruption

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes all run in the same session to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask.

Please let me know the results.

Right, stop it. Did you use the link I gave you to download memtest86+?

OK, You will need a good GPU monitoring program and watch temps closely. If they go too high, stop the test. Run Furmark.
Video Card - Stress Test with Furmark Watch the temps and for artifacts. The temps will rise very high and very rapidly, watch them and if they get too high stop the test. Run the test until you see the temps level out and stop rising. Then stop the test. It should be just a few minutes. Post a screenshot just before you stop the test. This will tell you how. Screenshots and Files - Upload and Post in Seven Forums

Also, please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

That's a pretty high temp, but that test makes them high. Needless to say, if you are overclocking anything, set it back to defaults. Both the CPU and the GPU.

Please run Seatools for DOS, both the short and the long test SeaTools for DOS and Windows - How to Use

The next BSOD you get, upload the BSOD Posting instructions.

BS Dang, it's been almost 2 months. What are the results of the Seatools I asked you to run? Your dump files were unreadable for the most part. The errors I could detect were from system files that write to the hard drive.

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff800030c5ffc, fffff880029657e8, fffff88002965040}
Probably caused by : luafv.sys ( luafv!SynchronousFsControl+23e )

If you don't have a bad hard drive, your problem may be because of an illegal operating system. You have an OEM_SLP Key from an Acer/Gateway computer. That can only be used on the computer it came from the factory installed on. You have it on a retail Motherboard. The operating System could only be activated with a hacker's exploit that alters protected system files.

Counterfeit installations such as yours contain heavily modified code that causes the installation to behave it unexpected ways. Analyzing BSOD's and determining their causes on these sorts of installations is very unreliable. For this reason, many analysts won't attempt it.

My recommendation is to install a genuine Windows 7. This will minimize the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a Genuine Windows 7 installation, and are still experiencing BSOD's, we will be happy to help you solve them