RAID Controller causes bluescreens, error BCCode: 51

[Dave76]

Good results on memtest86+, but I wouldn't rule out the RAM. That is the best known RAM test, it may still be in need of some adjustments.
After going through several of your debug files, there is a general theme of memory issues, which leads me to suspect the RAM. Although could be the graphics RAM or the corrupt file system/HDD error for the page file.

The other issue I see is on the forth BIOS screen shot, CPU temp 49°C, that is hot for an AMD CPU, they usually run very cool.
You need to remove the CPU cooler, clean surfaces with alcohol, re-apply thermal paste. Make sure the CPU cooler is firmly attached, too loose or too tight will cause high temps.
You should run a CPU stress test to verify.
OCCT stability checking tool Run the CPU:OCCT test for at least 30 minutes, be sure to monitor your CPU and GPU temps.
Set the time before you start.
When its done, pass or fail, it will make some graphs. Post these here as they are useful for analyses.

Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Max CPU core temp for your CPU is 76°C.

Find the CPU/NB and DRAM voltage in your BIOS. If it's on 'Auto' you may need to increase it by the smallest amount available to get the actual voltage reading.
We can make a couple of RAM settings changes with the above information, and see if they will make a difference.

Let us know if there are any more crashes, as always, post the full crash reports.

Do you know what 'MR_MONITOR' might be related to?
It's showing a lot of errors in your App Events Log.
There are also a lot of USB errors, not much info to go on but I would suspect the wireless USB dongle.

 

[drfsupercenter]

MR_MONITOR is most likely MegaRAID's monitoring service. For some reason, every time I boot Windows, it gives a RAID error, even though the array supposedly works fine. My friend and I tried updating the controller's BIOS and still haven't figured anything out about why it's doing that.

As far as the CPU goes, I am just using the stock AMD heatsink, though I have moved it around between a couple motherboards, each time using rubbing alcohol to get the thermal paste off and re-applying Arctic Silver myself.


It ultimately comes down to the fact that the computer wasn't crashing at all before adding the RAID controller. It may report it as a memory error, but I'm like 99% positive it has to do with that RAID controller... and given that it does work and I can create a partition on the drive, I'm not sure why it's crashing Windows like that.

I enabled the driver verifier... will that display more detailed info the next time it crashes?

--EDIT--

Just rebooted the computer with the RAID controller enabled and here's what it does:

 

[drfsupercenter]

OK, so I was moving some files over to the RAID array, and it crashed sometime during the night.

When I had my mom hit the reset button, there was no message that Windows had recovered from an error. I have Verifier.exe running... how do I share the results with you guys?

 

[Dave76]

Driver Verifier will stress the drivers, when it finds a bad one it normally causes a BSoD and generates a crash file.
Check the crash folder, if there is a new crash dump, upload the full crash report files.

 

[drfsupercenter]

Hmm. It doesn't look like there are any new .dmp files. Like I mentioned, while running Verifier, when my system would crash, upon reboot it would not say "your system has recovered from a crash"

What can be done about this? I'm 99% certain it's an issue with the RAID driver, as it will only crash when the RAID controller is enabled, but the verifier tool doesn't seem to be working.

 

[Dave76]

It's unusual but does sometimes happen that no crash files are generated.
Seems you have isolated and found the RAID card drivers to be the cause of the crashes, check for an updated driver from the manufacturer. If there are none, you may have to consider getting a new RAID card.

I would suggest to go over the RAM settings and voltages as mentioned earlier, this has fixed many system errors/crashes and is worth a look.
Your system, your choice.

 

[drfsupercenter]

OK, so, I got it to stop bluescreening by removing the "feature unlock key", which [I thought might be a bootleg given that the seller shipped it from Asia.

Now I can only do RAID1 or RAID0, but at least it works for testing.

However, I still get that error every time I boot. Googling it would suggest that the only course of action is to RMA it, and even then, some people are reporting that even with replacements, it still has the same problem.

Does anybody know of a CHEAP RAID controller that will work with Windows 7 driver-wise? The catch is it MUST support 3TB drives... a lot of the older Dell PercRAID cards are quite cheap, but those don't support 3TB drives.

 

[Dave76]

Good news you found the cause.

Sorry, I don't use RAID cards.

Have a look at this, check if it has the specs you want.
HighPoint 2nd Generation RocketRAID 600L
Review: HighPoint Announces 2nd Generation of SATA 6Gb/s Host RAID Controller