BSOD on hp pavilion dv3-4160ee

[sofriendly]

hi guyes. I previously had laptop of dell inspiron n5010
, processor intel 2.4 core i5 RAM 4 giga, hard 500 giga, graphic card
ATI Mobility Radeon HD 5470 and it is running on windows 7 ultimate
64bit edition (not original). I used to have blue screen when the laptop
completes booting and I suspected the wireles alfa lan which was of model
AWUS036H to be the cause because the blue screen happens when
the utitility of that lan shows up.
I sold that laptop and bought new one which is hp pavilion dv3-4160ee
and it has the same garphic card ATI Mobility Radeon HD 5470 , processor
intel 2.5 core i5 RAM 4 giga hrad 500 giga, genuine windows 7 premium
home edition 64bit which is OEM (preinstalled on it) and I got the blue scren
two times till now and I have attached the necessary dump files
desdcribing the problem. please help me to identify the cause of blue screen.

 

[richc46]

Its your anti virus
Uninstall with the uninstall tool, from their website and use
Microsoft security essentials

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Low\Temporary Internet Files\Content.IE5\RN8VXO2R\Documents[1]\Windows_NT6_BSOD_jcgriff2\111710-31824-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c0e000 PsLoadedModuleList = 0xfffff800`02e4be50
Debug session time: Wed Nov 17 04:20:37.794 2010 (GMT-5)
System Uptime: 0 days 0:00:58.949
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff6fc4004f000, 2, 0, fffff80002c6d9c2}
Unable to load image \SystemRoot\system32\DRIVERS\klim6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klim6.sys
*** ERROR: Module load completed but symbols could not be loaded for klim6.sys
Unable to load image \SystemRoot\system32\DRIVERS\kl1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
[B]Probably caused by : klim6.sys ( klim6+2a3f ) This is your AntiVirus[/B]
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff6fc4004f000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c6d9c2, address which referenced memory
Debugging Details:
------------------
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb60e0
 fffff6fc4004f000 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!MmBuildMdlForNonPagedPool+132
fffff800`02c6d9c2 498b11          mov     rdx,qword ptr [r9]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
TRAP_FRAME:  fffff8800318abc0 -- (.trap 0xfffff8800318abc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000f20
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c6d9c2 rsp=fffff8800318ad58 rbp=fffff6fb7e200278
 r8=0000000000000800  r9=fffff6fc4004f000 r10=fffffa8009cd0000
r11=00000383c9cb73e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MmBuildMdlForNonPagedPool+0x132:
fffff800`02c6d9c2 498b11          mov     rdx,qword ptr [r9] ds:000e:fffff6fc`4004f000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002c7db69 to fffff80002c7e600
STACK_TEXT:  
fffff880`0318aa78 fffff800`02c7db69 : 00000000`0000000a fffff6fc`4004f000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0318aa80 fffff800`02c7c7e0 : 00000001`0000007f 00000000`00000800 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0318abc0 fffff800`02c6d9c2 : fffffa80`091c8a30 00000000`fffffdb0 fffff880`016605b1 00000000`0000000e : nt!KiPageFault+0x260
fffff880`0318ad58 fffff880`016605b1 : 00000000`0000000e 00000000`00000000 fffffa80`09cd0000 fffffa80`097ea160 : nt!MmBuildMdlForNonPagedPool+0x132
fffff880`0318ad70 fffff880`04ff5a3f : fffffa80`097ea160 fffffa80`094c37e0 fffffa80`086e5960 fffff800`02c8e2eb : ndis!NdisAllocateMdl+0x31
fffff880`0318adb0 fffffa80`097ea160 : fffffa80`094c37e0 fffffa80`086e5960 fffff800`02c8e2eb fffff880`00000000 : klim6+0x2a3f
fffff880`0318adb8 fffffa80`094c37e0 : fffffa80`086e5960 fffff800`02c8e2eb fffff880`00000000 00000000`0000000e : 0xfffffa80`097ea160
fffff880`0318adc0 fffffa80`086e5960 : fffff800`02c8e2eb fffff880`00000000 00000000`0000000e fffffa80`00000000 : 0xfffffa80`094c37e0
fffff880`0318adc8 fffff800`02c8e2eb : fffff880`00000000 00000000`0000000e fffffa80`00000000 fffff880`0232b246 : 0xfffffa80`086e5960
fffff880`0318add0 00000000`0000000e : fffffa80`094c37e0 fffff880`0163aa47 fffffa80`073883b0 fffff880`04a451fc : nt!IoAllocateMdl+0x7b
fffff880`0318ae20 fffffa80`094c37e0 : fffff880`0163aa47 fffffa80`073883b0 fffff880`04a451fc fffff880`0318aeb0 : 0xe
fffff880`0318ae28 fffff880`0163aa47 : fffffa80`073883b0 fffff880`04a451fc fffff880`0318aeb0 00000000`00000000 : 0xfffffa80`094c37e0
fffff880`0318ae30 fffffa80`075425f0 : fffffa80`097ea160 fffff880`04a4c5f3 fffffa80`086e5960 fffffa80`07542010 : ndis!NdisFreeNetBufferList+0x87
fffff880`0318ae60 fffffa80`097ea160 : fffff880`04a4c5f3 fffffa80`086e5960 fffffa80`07542010 00000000`00000000 : 0xfffffa80`075425f0
fffff880`0318ae68 fffff880`04a4c5f3 : fffffa80`086e5960 fffffa80`07542010 00000000`00000000 fffffa80`075425f0 : 0xfffffa80`097ea160
fffff880`0318ae70 fffffa80`086e5960 : fffffa80`07542010 00000000`00000000 fffffa80`075425f0 fffffa80`00000000 : kl1+0x3b5f3
fffff880`0318ae78 fffffa80`07542010 : 00000000`00000000 fffffa80`075425f0 fffffa80`00000000 fffff880`000701ac : 0xfffffa80`086e5960
fffff880`0318ae80 00000000`00000000 : fffffa80`075425f0 fffffa80`00000000 fffff880`000701ac 0c0036a6`3acac000 : 0xfffffa80`07542010
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
klim6+2a3f
fffff880`04ff5a3f ??              ???
SYMBOL_STACK_INDEX:  5
SYMBOL_NAME:  klim6+2a3f
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: klim6
IMAGE_NAME:  klim6.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a0d8120
FAILURE_BUCKET_ID:  X64_0xA_klim6+2a3f
BUCKET_ID:  X64_0xA_klim6+2a3f
Followup: MachineOwner
---------

The reports that you have submitted reveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receive the more clues are made available improving our chances of finding a solution to your problem. You may have to experience several more BSODs until the final answer is discovered.

Dump Kaspersky

If overclocking restore normal settings

SFC /scannow
System Files - SFC Command