Sorry, MS Symbol Server was down for a while. I wasn't able to open the crashdumps properly. Regardless, it still doesn't look like they'll be of any help, so yeah, go ahead and turn on Driver Verifier again and see what we'll get from it.
Did you run Memtest at 7+ consecutive passes, btw?
I'm looking at the crashes, and I'm noticing a couple of patterns. One is that they seem to almost always involve memory/paging file activity, so we'll want to check both memory and drive. Do a CHKDSK (both options) followed by running a few Seatools tests - namely Short DST, SMART, and Short Generic, avoid all other tests. If you want, also provide us a snapshot of CrystalDiskInfo output.
You can also try recreating the paging file. You can do so by going into the paging file settings, which you can access by typing Advanced system settings in Windows start menu, then going to Performance Settings, then Advanced, then Change button for Virtual Memory. Once you're there, you can uncheck Automatically manage paging file size for all drives if checked, then select No paging file. It'll warn you, by accept the change anyways, then click OK then restart. Once you enter your system again, go back and revert the changes to how they were before. This will effectively recreate the paging file for your system.
That, or you can just load a livecd environment like PartedMagic from a disc and then go to your C: drive and delete the pagefile.sys file. Windows will recreate it at startup.
The other pattern I'm seeing is that both your Nvidia and Intel graphics drivers seem to always show up. While you did say you stopped usage of the onboard graphics by adding a video card, I'm still seeing the onboard graphics driver being loaded and showing up in the crash. Or am I reading things wrong and you removed the graphics card and it's still bugging out on the onboard?
Overall, this is most likely a hardware issue. Driver Verifier itself didn't catch anything suspect, so that means either the driver causing this problem isn't being loaded until later on in system usage (like when a service or application started running and loaded its own driver), and therefore wasn't added to the checklist for DV, or hardware is actually causing it and no manner of DV checks is going to catch any driver being the cause of it. Given the early hardware life, I will have to suspect the latter foremost.
I had memtest running for over 5 hours. I'm pretty sure it had passed 7 times as you had been pretty specific about it. Should I attempt to run it again?
I've run both chkdsk and the seatools tests and no errors have been found on the hard drive. I've attached a screenshot whilst running crystaldiskinfo as you requested.
Regarding the graphics cards, I re-installed windows yesterday in order to clear up all the clutter. Hardly got anything running now. There are no instances of the nvidia card running, just the onboard graphics. And, even in this stripped back state, I attempted to install a new version of Cubase that I've purchased and it bluescreened during installation.
Really frustrated now! How likely is it that the motherboard is the problem here?
I also flashed the bios up to the latest version.
Usually I've found if there's indeed hardware problems, but diagnostic tests and all show up clean for everything, than yes, often the case is that the motherboard is the problem. There are also the chances that the PSU or the CPU are causing it, with the PSU especially being a prime suspect, just because the integrity of everything else in the system relies solely on the PSU running ok.
I noticed you did not specify make and model of your PSU in your PC specs. This is disconcerting to me, as it means most likely you consider the PSU a non-crucial item, which would've affected your decision on what PSU you purchased. PSUs are more than just the wattage output they churn out, and even whether they're modular or not. The quality of its internal parts and their setup is crucial in determining their overall stability and reliability. Hence why it's necessary to both go for quality brand names as well as avoiding their budget models. While even the best PSUs still have the potential to bug out, I - as well as other techs I know - are well aware of the disparity in reliability between budget models/brands and top-line items. Personally, I recommend approaching this article for more info on the subject as well as some recommended models.
Anyways, the problem here is that if indeed we're dealing with a PSU/CPU/Mobo issue, there's really no way to discern which of them's causing it outside of swapping hardware (or buying expensive diagnostic kits). Hence why I call em the Trio of Trouble. At least you have warranties for all three items. I recommend that you start with the Mobo, then the PSU, then the CPU, if you decide to go for a one-by-one approach (or replace all three, or at least the PSU/Mobo).
I did indeed think about the PSU and replaced it, resulting in the same problem. To be fair I didn't spend a great deal on it though, but I didn't think a high end PSU would be a neccessity considering I removed my graphics card and was only running an i3 - Ace Black PSU 12cm Red fan PSUACE500BR - Scan.co.uk
I've been building PCs for years and this is the first time I've ever had this problem so I'm not convinced it's a PSU issue.
I'm going to test out another motherboard tonight and see how I get on. Like you said I have warranties for all items so I should be able to get a refund on whatever turns out to be the faulty item!
Many thanks again for all of your help so far, I really appreciate it.
Ok then. Mark this as solved if ever you discover what caused it.
Well I replaced the motherboard which didn't help. I decided to purchase a new PSU which also hasn't resolved the problem. The blue screens keep coming. That just leaves the CPU...
Is there anything else I can do to test this or is it a case now of contacting the supplier?
Again, many thanks in advance.
Supplier? Did you custom build this system or did you have it built for you? In any case, looks like the next part up is the CPU. That or you've been replacing bad PSUs with other bad PSUs.
Quote