BSOD Various BCCodes 1a, d1, 24, 7e, 3b

Can you tell me, I can't find it, what the max GPU temp was? Also, I'm not sure about software readings of the voltages, but, if you will look, your +12V, +5V and +3,3V are all at the very bottom of the tolerable range. ATX Standards are +/- 5%. If you will look at the minimums, you will see they fall off to the very bottom of the standards range. Software readings are notoriously inaccurate. I use software too, but I use it only as a guideline. Those voltages would scare me.

OK, no problem, just let me know.

Just so you know, almost all of the Mark 3D tests are CPU+GPU tests, the scores depend on both. If you want to check the GPU, run the Ungine tests, they are GPU only tests and tend to stress the GPU a little more. I do use both for system stability but use Heaven for testing the GPU.

Yea, those voltages don't look much better than the other one. It could be the program too.

Here are what I found from the 3 dumps from today. I know you said you have run memtest86+ a couple of times, but this is what the dump file says.

Code:

Use !analyze -v to get detailed debugging information.
BugCheck A, {28, 2, 0, fffff8000331ad80}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
Followup: MachineOwner

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff880111c9fe2, fffff880092ab520, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1c5fe2 )
Followup: MachineOwner

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff96000087dd4, fffff88002a10ed0, 0}
Probably caused by : memory_corruption
Followup: memory_corruption

From a strict BSOD perspective, the memory corruption is more concerning than anything else. If there is a ram problem, it can cause a BSOD at any time doing any thing and whatever driver is most in use at the time will usually get the blame. So, from my perspective, if there is a memory problem, nothing in the dump files can be reliable. Let me show you. The second one today that blamed the Nvidia driver, when I dig down into the files, this is what it shows as the cause.

Code:

fffff880`092aa590  fffff880`00c87800Unable to load image \SystemRoot\system32\DRIVERS\amd_sata.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amd_sata.sys
*** ERROR: Module load completed but symbols could not be loaded for amd_sata.sys
 amd_sata+0x1800

Code:

fffff880`092aa018  fffff880`04bea29eUnable to load image \SystemRoot\System32\Drivers\dump_amd_sata.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dump_amd_sata.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_amd_sata.sys

Those are the causes of that dump and no where does it mention the Nvidia driver that was originally listed. There were some references to the Nvidia Display Driver, the NTFS file system the AMD sata, which are all mostly related to the hard drive. In all fairness the last one, dump_AMD_SATA is simply a way for the system to make room for the dump file to be written.