Getting frequent BSOD,Help...

I am getting BSOD error every few minutes after i switch on my pc.
page_fault_in_nonpaged area

I did memtest86 and found no errors.
Thanx in advance.

You have to love consistency.
All seven (7) dump files;

Code:

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: b3f1e000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 82e0184a, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000000, (reserved)
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d81718
Unable to read MiSystemVaType memory at 82d61160
 b3f1e000 
FAULTING_IP: 
nt!MiCompressRelocations+3d
82e0184a 0fb731          movzx   esi,word ptr [ecx]
MM_INTERNAL_CODE:  0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  explorer.exe
CURRENT_IRQL:  0
TRAP_FRAME:  a580b9e8 -- (.trap 0xffffffffa580b9e8)
ErrCode = 00000000
eax=7ffffa5a ebx=00000000 ecx=b3f1e000 edx=00000000 esi=00000000 edi=b3f1d4b4
eip=82e0184a esp=a580ba5c ebp=a580ba7c iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!MiCompressRelocations+0x3d:
82e0184a 0fb731          movzx   esi,word ptr [ecx]       ds:0023:b3f1e000=????
Resetting default scope
LAST_CONTROL_TRANSFER:  from 82c5f5f8 to 82c9e8e3
STACK_TEXT:  
a580b9d0 82c5f5f8 00000000 b3f1e000 00000000 nt!MmAccessFault+0x106
a580b9d0 82e0184a 00000000 b3f1e000 00000000 nt!KiTrap0E+0xdc
a580ba7c 82e216cd b3e00000 00047e1c 00000008 nt!MiCompressRelocations+0x3d
a580bb2c 82e3c8a9 c2b43000 a580bbb4 00000003 nt!MiRelocateImage+0x430
a580bc50 82e49e51 a580bca4 00000001 00000000 nt!MmCreateSection+0x797
a580bcc4 9165127b 0216e33c 00000001 00000000 nt!NtCreateSection+0x16e
WARNING: Stack unwind information not available. Following frames may be wrong.
a580bd10 82c5c42a 0216e33c 00000001 00000000 klif+0x3027b
a580bd10 77a464f4 0216e33c 00000001 00000000 nt!KiFastCallEntry+0x12a
0216e50c 00000000 00000000 00000000 00000000 0x77a464f4
STACK_COMMAND:  kb
FOLLOWUP_IP: 
klif+3027b
9165127b ??              ???
SYMBOL_STACK_INDEX:  6
SYMBOL_NAME:  klif+3027b
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: klif
IMAGE_NAME:  klif.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4daeb73f
FAILURE_BUCKET_ID:  0x50_klif+3027b
BUCKET_ID:  0x50_klif+3027b

All are for all practical purposes identical.
So let's start there.
Uninstall Kaspersky completely. (Excellent product, not knocking it, just want to move the diagnostic process along) Removal tool for Kaspersky Lab products . Replace it for now with MSE from here Spyware Protection | Free Spyware Protection | Microsoft Security Essentials (humor me).
If blue screens persists;
First make sure your machine is configured properly to facilitate the collection of .dmp files.

Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be found later
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

Then:
Please read the first post in this sticky thread here How to ask for help with a BSOD problem
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Additionally, if you haven’t already, please take some time and fill out your system specs in your forum profile area Help Us To Help You By Filling In Your System Specs. .
Good luck
Randy

thank you for the procedure....will try it and post here again..

Replacing kaspersky(using the removal tool) with mse did not work.

sysdm.cpl had only these options:

(none)
Kernel Memory Dump
Small memory dump (128 kB)

So i chose the 3rd one.[there was no "Small memory dump (256 kB)"].

I have attached new files.
Advance thnx.

Seven new dump files, all within 20 minutes of one another, practically identical but not completely with the previous seven.

Code:

BugCheck 10000050, {a811e000, 0, 82e0184a, 0}
Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiCompressRelocations+3d )
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: a811e000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 82e0184a, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000000, (reserved)
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d81718
Unable to read MiSystemVaType memory at 82d61160
 a811e000 
FAULTING_IP: 
nt!MiCompressRelocations+3d
82e0184a 0fb731          movzx   esi,word ptr [ecx]
MM_INTERNAL_CODE:  0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 82e216cd to 82e0184a
STACK_TEXT:  
8da0b6d4 82e216cd a8000000 00047e1c 00000008 nt!MiCompressRelocations+0x3d
8da0b784 82e3c8a9 a7b53000 8da0b80c 00000003 nt!MiRelocateImage+0x430
8da0b8a8 82e49e51 8da0b8fc 0000000d 8da0b950 nt!MmCreateSection+0x797
8da0b91c 82e1dc86 8da0b9ac 0000000d 8da0b950 nt!NtCreateSection+0x16e
8da0b998 82e1d6d4 8da0ba58 a793f710 00000001 nt!PfpFileBuildReadSupport+0xe4
8da0ba2c 82e1f0b4 00a0ba58 8da0bbb4 00000001 nt!PfpPrefetchFilesTrickle+0xdf
8da0bad0 82e1ed71 a7938000 a3b185c5 8da0bbc8 nt!PfpPrefetchRequestPerform+0x2a6
8da0bb24 82e3897f 8da0bbb4 04a1d001 a3b18509 nt!PfpPrefetchRequest+0x16e
8da0bbe8 82ea48f6 00f5fc64 00000014 04a1d001 nt!PfSetSuperfetchInformation+0x182
8da0bd20 82c5c42a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0xb00
8da0bd20 777664f4 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00f5fc7c 00000000 00000000 00000000 00000000 0x777664f4
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!MiCompressRelocations+3d
82e0184a 0fb731          movzx   esi,word ptr [ecx]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!MiCompressRelocations+3d
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  0x50_nt!MiCompressRelocations+3d
BUCKET_ID:  0x50_nt!MiCompressRelocations+3d

Let's start by checking memory.

Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
See this Guide to using Memtest 86+

While you're at it go ahead and run the native disk checker on your hard drive.
Launch an elevated command prompt and type
chkdsk C: /R
hit enter and answer yes (Y) when prompted and reboot.
Also keep an eye on your system temperatures. There are several decent free programs out there that will help you do this just Google "monitor windows 7 system temperatures"
Keep us posted
Randy

Performed memtest on both the rams individually in combinations with both the slots....found no problems.
It felt weird that bsod started two days after i installed max payne 3,so i googled it and found ppl having similar problem solved by updating windows.
I did it too and the BSODs stopped, so far no problems...will post here if anything happens again.
Thnx for d help so far...u and this forum rock.

Great to hear that you have managed to resolve your issue.
Thanks for posting back and updating your thread with that information.
So, you think your problem was resolved by updating Windows 7?
May I ask what updates did you apply? Service Pack 1? Did you basically catch up all your critical updates?
Thanks again for the follow up.

i originally intended to update up to sp1 (like the others with similar problems did),but the BSODs stopped b4 sp1 was installed, that is, when most of the important updates b4 sp1 had dwnloaded and installed.
Will put sp1 anyway..