Windows 7 x64 BSOD

debugger says it cannot identify the faulting driver and the 0x50 error suggests a driver file error. Most likely there is a problem with that file and it needs to be updated or replaced ?

most of your drivers are from july 2009 and your realtek nic driver is from jan 2010 so try updating all your drivers ?

please can you tell us what antivirus and or third party firewall are you using ?

I had a BSOD again.
After restart I had to Launch Startup Repair, because the computer didn't want to start Windows,
and I got IRQL_NOT_LESS_OR_EQUAL at the end of Launch Startup Repair.

After Windows started I got an DRIVER_IRQL_NOT_LESS_OR_EQUAL.
I've updated drivers for my network adapter.

Im seeing Klif.sys and Kl1.sys and other files associated with kapersky , did you use a trial version then unninstall it ?

I suggest you remove all remnants of kasperksy using the removal tool provided here by ice systems

then let us know how you get on

There are two thing that I want to say from the minidump check
First, I would recommend you to remove kapersky antivirus just for testing, because it appear as process during BSODs occur.
One of the minidump check indicate memory corruption, if uninstalling kapersky doens't work, I would suggest to download third party called memtest86, burn it to cd and let it run for at least 7 passes
Here is the bugcheck

Code:

BugCheck 50, {ffffd80003250b00, 0, fffff800030c7d97, 7}

Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+47 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffd80003250b00, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030c7d97, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000007, (reserved)
Debugging Details:
------------------

Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fa0e0
 ffffd80003250b00 
FAULTING_IP: 
nt!PspReturnQuota+47
fffff800`030c7d97 488b5d00        mov     rbx,qword ptr [rbp]
MM_INTERNAL_CODE:  7
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  avp.exe
BugCheck 50, {ffffda8006c17738, 0, fffff800031c1cbf, 7}

Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiLogPageAccess+10f )
Followup: MachineOwner
---------

Let us know if you need help

T