Without going back and looking, this is about the third dump that network drivers have been named in dump reports. The last time when all indications were the hard drives, athrx was mentioned. But, since everything else was storage related, I assumed that it was probably a read error when the driver was requested from the hard drive. It was the only error which was not storage/hard drive related. Under any other circumstance, I would think this was a memory problem. When ram errors occur, whatever driver is most in use gets the blame. So, you end up getting different error codes and different drivers named each time. What that means, at least from my perspective, is a memory error is the worst thing that you can have. Because of what I just explained, the dump files cannot be relied upon. What we are seeing is typical of ram problems. The only exception is that yours all seem to be when Cubase is being used.
To be quite honest, I am not familiar with how Cubase works. I know what it is, but not how it works. For example, in a gaming situation, there are a lot of drivers in use. But there are constant read/write operations going on to write data to and read from the hard drive. Much of that data is stored in ram until it is needed. If drivers are not involved in the crash, I tend to look at ram and hard drive, if I explained it right. My guess would be that Cubase is similar when in operation.
We can run memtest86+ to test the ram and see if it is that and we can run Driver Verifier to check the drivers. With Driver Verifier, there is a small chance that we can get caught in a situation to where there is no option other than a clean install. We take every precaution to see to it that an install does not happen. It has never happened to me, but I feel obligated to explain that. What it does is put extra stress on the drivers in hopes that the offending driver will cause the computer to crash and catch the offending driver. It is probably the only time you will ever want the computer to BSOD. I would request that you do not do either of those tests until I give you instructions on exactly how to do them. The downside to the memory test is that with your 16 GB of ram, the test will take around 20 hours to run and the computer cannot be used during the test because the test is actually run out of ram and the OS is not even loaded. For my purposes, I would prefer to run the memory test first, for reasons that are obvious. From what I gather based on the questions you have been asking, I think you would prefer to run Driver Verifier. I will leave that up to you which we do. But in my opinion we need to do something that will narrow down what is going on. As it stands right now, you are correct. Every time it is something different. As a practical matter, we don't even know whether it is a driver problem, hardware problem or a driver conflict. Your third option is very time consuming but can be really telling. You can perform a clean startup or a diagnostic startup. Almost all programs and services are shut down on startup. You start enabling programs a couple at a time until you start having BSODs again. You will then know which programs are suspect and with a little work can determine which one it is. This is how, but it takes a lot of time. When you enable a program or service, you have to use the computer that way until you determine it is or is not causing a problem, then enable a few more. This explains it in step by step instructions.
http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html
I will leave it up to you, which route you would like to take. If you have any questions, please let me know.
rb:
