When tension changes,BSOD may occur?!

PSU is power supply unit,in my case,it is in my SIG,its a thermaltake,600w,pretty good if you ask.
I am starting to believe more each day that the "shoe" or "zapatilla" is the whole responsable of this issue.
As soon as I get home,I'll try to test my PC on my room for one week to see if there are any changes regarding the BSODs

Well,this stuff is getting stranger every day!
Before I left off for Mendoza I managed to create 2 more accounts (One for my pop,one for my mom)....and changed my password to europa2010.
Now that I arrived those accounts have dissapeard....and my password has reverted back to the one I had before changing it.
Weird thing is....all the things that I downloaded after creating the user accounts are still there!
Its like System Restore went on somekind of strange rampage....

And look,first boot after leaving the computer off for one week,and it has come up with this (screenshot includes the memory,and both slot SPDs,plus this CCC (first time it comes up) error :


Uploaded with ImageShack.us

Well,at least my 16gb empire total war download is safe.....
Tomorrow I will move the computer to see if there are any changes.

PD:Found some minidumps,gonna upload them right now:

Bump,no reply in 12 hours.

Bump,no reply in 3 days!

ALSO,THE STRANGE STUFF DURING COLD BOOT IS STARTING TO APPEAR AGAIN!!!

Yesterday,1pm,cold boot,the desktop was screen and suddenly all the programs started to crash.
Today,it wouldnt start and after restart a BSOD came up,but without any memory_management or irql_less_than_equal:

Here is the description and the minidumps:

UProblem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA800583D060
BCP3: FFFFFA800583D340
BCP4: FFFFF80002F845D0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1]

OH NOES! THE MEMORY_MANAGEMENT IS BACK!!

It happened to me while I was watching a youtube video,the screen froze with a RRRRRRRRRR sound and then it BSOD'ed.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA800317BCB0
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

I beg someone to help me!!!

Bump,this is the fourth time :/

Jesus,could somebody just tell me what's wrong with the BSOD?
I mean,it has been one week since I posted the first minidump

010111-15350-01.dmp ‎01 ‎January ‎2011, ‏‎02:23:03

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa800250e630, ffff, 0}

Probably caused by : win32k.sys ( win32k!NtGdiCreateDIBSection+3e4 )

Followup: MachineOwner

010111-15490-01.dmp ‎01 ‎January ‎2011, ‏‎18:47:29

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa8c49ea5018, 0, fffff80002dd0314, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiEmptyWorkingSet+1e4 )

Followup: MachineOwner

012111-18688-01.dmp‎ 21 ‎January ‎2011, ‏‎13:31:07

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800583d060, fffffa800583d340, fffff80002f845d0}

Probably caused by : wininit.exe

Followup: MachineOwner

012211-15397-01.dmp ‎22 ‎January ‎2011, ‏‎23:46:33

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa800317bcb0, ffff, 0}

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

Followup: MachineOwner

Link to Error Code Details


Avast has been known to be a cause of BSOD's on some Win 7 systems.
Suggest that you uninstall Avast using the correct AV Uninstaller for your system until your issue is resolved.
Download Microsoft Security Essentials as its replacement.
Make sure Windows firewall is enabled!

Outdated Drivers:

Rt64win7.sys Thu Feb 26 09:04:13 2009 Realtek LAN RTL811

DRIVER_BIN64 Wed Aug 01 03:05:51 2007 ATI Tray Tools Uninstall

Just a drive by., haven't read the thread.

You have a 3 + year old drvier_bin.sys. With ATI graphic cards this version of the file has had problems with BSOD.

I agree wholeheartedly with Fimble Avira needs to be replaced with Microsoft Security Essentials.

http://www.avira.com/en/support-down...r-removal-tool

http://www.microsoft.com/security_essentials/



Also and much more importantly remove SPTD.SYS used in daemon tools and alcohol120. It is a huge cause of BSOD's.
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview


Finally, if you havent run memtest to check yours

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

Good luck


Ken J