The dump file still lists the RAID as the cause.
Also, what kind of memory do you have? If you need help getting this information, use HWiNFO64 Download and use Save Report. Save it as an html file and choose where to save it using the Browse button that appears when you click Save Report. Then hit next and finish saving it by following the wizard for Save Report. You can upload the html file on here for us to view and give you further advice.
I don't recall the specific type of memory I purchased when I built the computer. I ran the program from your last post and will include that information here. I ran the windows memory diagnostics for 5 passes in the extended testing mode and it found no errors.
Your motherboard memory qualified vendors list also supports the above post in a way.
Might be worth looking into what your CPU supports for frequencies. If you are overclocking, you may be pushing it with your current RAM.1. Due to CPU spec., AMD 100 and 200 series CPUs support up to DDR3 1066Mhz. With ASUS design, this motherboard can support up to DDR3 1333MHz.
2. When overclocking, some AMD CPU models may not support DDR3 1600 or higher frequency DIMMs.
I am not overclocking. Call me a wuss, but when I spent $300(at the time) for a new CPU I wasn't going to risk frying it by overlocking it even though i know it could probably handle some overlocking. As long as it runs my games smoothly I am not interested in squeezing that extra 5 fps when what I experience now works.
Couldn't agree more with you. I've never overclocked any of my hardware for the same reason, plus it voids the warranty for most hardware. I think that warning about going above 1333 MHz may still apply even without overclocking for some CPUs based on what Dave76 was saying, which makes sense. If it has issues with a RAM frequency during overclocking, it stands to reason it may also have issues without overclocking on some units.
so I guess my next step is to go back to a system restore point prior to last Sunday since that is when this all began? If the RAID controller is still showing as the issue, but I have updated it (as far as I can tell) to the latest version of the drivers available, what other step regarding the RAID controller can I take?
Backup your important files and try resetting the RAID controller. You may have to do a clean install of Windows afterwards, but hopefully just resetting it will not erase the data. My understanding is that it most likely will, however, which is one of the many reasons RAID is recommended against.
I'm assuming you are referring to going into the RAID controller and deleting my existing array and creating another? If this is the main cause of this issue I am not opposed to doing away with the RAID setup altogether and just running each drive separately, but would I be inviting a whole new host of problems besides having to restore my data by doing that?
Do you have a hardware RAID, software RAID, or hybrid RAID? I'm trying to read up on these to determine if removing your RAID setup will cause any issues. This really isn't my forte, so if you want better advice, I would suggest starting a thread in Hardware and Devices asking the same question posed in your previous post. :)
Quote