BSOD every day, different each time

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Code:

BugCheck A, {fffff8a01ac74000, 0, 0, fffff80002c95798}

Probably caused by : memory_corruption ( nt!MmProbeAndLockPages+118 )

Followup: MachineOwner
--------------------------------------------------------------------------------
BugCheck 50, {fffffb94047dcce8, 0, fffff80002c4873b, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+27f )

Followup: MachineOwner
----------------------------------------------------------------------------------
BugCheck 1A, {411, fffff6fc00014558, 28ab882, ffff00fc00014559}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6071 )

Followup: MachineOwner
---------

As a further test, do a Clean Reinstall - Factory OEM Windows 7 .... do exactly what is stated there. Dont install Intel and Marvell storage controllers.

Let us know how it goes.

Did you use memtest86+ per the tutorial's instructions? If not please do so. New hardware can be bad too and you BSOD is blaming memory corruption which can be memory anywhere in the system from RAM to the GPU memory. You said the voltages are ok, what are they in Windows? This free program can show you. HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools

Pull all the PSU cables, RAM and GPU and reinstall everything taking extra care to confirm they are fully seated/connected.

To better help us to help you would you please add your systems specs? Here's the correct way to do it. :SystemInfo See Your System Specs Under System Manufacturer/Model Number add whether it is a desktop or laptop and whether self built. Very important

Log in to Seven Forums and you will be able to transfer the info directly to the specs page in your profile from within the System Info app.

Your System Specs here.

After doing this your specs will be available in each of your posts.
Click on My system Specs in the lower left of this post to see how it should look.:)
Full instructions are in the tutorial.

Hi Basildane, welcome to 7F! :)

The memory corruption from your .dmp's indicates either faulty memory and/or drivers, you're getting a pool leak from somewhere: Troubleshooting Pool Leaks Part 5 ? PoolHitTag - Ntdebugging Blog - Site Home - MSDN Blogs.

To narrow this down, Please, uninstall everything, but the OS, we want a "Bare-bones" system. If you are having BSODs on every startup you may just have to do another "Clean Install" to work around the BSODs.

Personally I would like to see a clean install just to see if the machine would startup without a BSOD, then do this list one at a time with restarts after each to see where the BSODs start:

• Run Windows Updates.

• Use Internet Explorer only, other browsers can come later.

• Use Microsoft Security Essentials (MSE) to test, Sophos can come later.

• No Office 2010. It can come later.

• Please, no java or flash especially java, unless you are a gamer and one of the games you play requires java, you would be surprised at how well you can live without java. Either one of these can come later.

• Don't install the storage controllers as Arc has suggested, they can come later.

• Please fill out your System Specs, since this is your build, be specific! System Info - See Your System Specs

If you have a BSOD before you even run the Updates I would suspect a hardware failure somewhere.

• Did you check for compatibility of all the hardware components before you purchased them?

• Did you install the CPU?

• A cracked Motherboard (MB) i.e. bad solder joints.

• Mis-matched RAM, it can happen even straight from the vendor.

• Everything plugged in correctly?

I see Britton has replied, hopefully we have given you some "food for thought".