BSOD playing everything, error 0x0000003d

[Rzff]

Hi everyone
I'm getting BSOD while playing every game I've tried. It's started about 6 months afer I've got my notebook (HP Pavilion dv6; Win7 Home Premium x64 OEM, 4 GB RAM, AMD Athlon II Dual-Core 2GHz, ATI Radeon HD 4500/5100 series). I've tried to solve them by another FAQs but with no result, so any help will be appreciate.
BSOD reports are attached by directions.

 

[writhziden]

[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\Rzff\Windows_NT6_BSOD_jcgriff2\030812-17206-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 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c5c000 PsLoadedModuleList = 0xfffff800`02ea1670
Debug session time: Thu Mar  8 10:53:13.960 2012 (UTC - 7:00)
System Uptime: 0 days 0:15:20.490
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff800047cf110, 0, 0, fffff80002c1d808}

Probably caused by : ntkrnlmp.exe ( nt!KiInterruptDispatchNoLock+163 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff800047cf110
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff80002c1d808

Debugging Details:
------------------


CONTEXT:  fffff800047cf110 -- (.cxr 0xfffff800047cf110)
rax=fffff800047cfb00 rbx=0000000000000000 rcx=fffff80002c43460
rdx=0000000000000000 rsi=fffff80002c43460 rdi=0000000000000001
rip=fffff80002c1d808 rsp=fffff800047cfaf8 rbp=fffff800047cfb80
 r8=fffff80002e5ccc0  r9=000000002e69bc38 r10=0000000000000f51
r11=00000000001f0000 r12=fffffa8004e92580 r13=fffffa8004e32500
r14=fffffa8004e92500 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
hal!HalpHpetClockInterrupt:
fffff800`02c1d808 fff3            push    rbx
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3D

PROCESS_NAME:  System

CURRENT_IRQL:  d

LAST_CONTROL_TRANSFER:  from fffff80002cd5173 to fffff80002c1d808

STACK_TEXT:  
fffff800`047cfaf8 fffff800`02cd5173 : fffff800`02cd51a0 00000000`00000000 fffffa80`04408668 00000000`00000000 : hal!HalpHpetClockInterrupt
fffff800`047cfb00 fffff880`018617f2 : fffff800`02ce24a9 00000000`001dba48 fffffa80`04e32598 fffff800`02e5ccc0 : nt!KiInterruptDispatchNoLock+0x163
fffff800`047cfc98 fffff800`02ce24a9 : 00000000`001dba48 fffffa80`04e32598 fffff800`02e5ccc0 00000000`00000001 : amdppm!C1Halt+0x2
fffff800`047cfca0 fffff800`02cd093c : fffff800`02e4ee80 fffff800`00000000 00000000`00000000 fffff880`05dd4480 : nt!PoIdle+0x52a
fffff800`047cfd80 00000000`00000000 : fffff800`047d0000 fffff800`047ca000 fffff800`047cfd40 00000000`00000000 : nt!KiIdleLoop+0x2c


FOLLOWUP_IP: 
nt!KiInterruptDispatchNoLock+163
fffff800`02cd5173 f685f3000000ff  test    byte ptr [rbp+0F3h],0FFh

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiInterruptDispatchNoLock+163

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff800047cf110 ; kb

FAILURE_BUCKET_ID:  X64_0x3D_nt!KiInterruptDispatchNoLock+163

BUCKET_ID:  X64_0x3D_nt!KiInterruptDispatchNoLock+163

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\Rzff\Windows_NT6_BSOD_jcgriff2\030812-19000-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 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c54000 PsLoadedModuleList = 0xfffff800`02e99670
Debug session time: Thu Mar  8 10:18:37.005 2012 (UTC - 7:00)
System Uptime: 0 days 0:54:33.534
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {15de, d, 1, fffff80002ccd1c7}

Probably caused by : ntkrnlmp.exe ( nt!KiInterruptDispatchNoLock+1b7 )

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

0: 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: 00000000000015de, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000001, 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: fffff80002ccd1c7, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f03100
 00000000000015de 

CURRENT_IRQL:  d

FAULTING_IP: 
nt!KiInterruptDispatchNoLock+1b7
fffff800`02ccd1c7 48018140470000  add     qword ptr [rcx+4740h],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c970 -- (.trap 0xfffff80000b9c970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000015de rbx=0000000000000000 rcx=fffff80002e46e80
rdx=000005f100000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ccd1c7 rsp=fffff80000b9cb00 rbp=fffff80000b9cb80
 r8=0000000000017888  r9=0000000000000000 r10=0000000000000000
r11=fffff80000b9caa0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz ac po nc
nt!KiInterruptDispatchNoLock+0x1b7:
fffff800`02ccd1c7 48018140470000  add     qword ptr [rcx+4740h],rax ds:fffff800`02e4b5c0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cd01e9 to fffff80002cd0c40

STACK_TEXT:  
fffff800`00b9c828 fffff800`02cd01e9 : 00000000`0000000a 00000000`000015de 00000000`0000000d 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c830 fffff800`02ccee60 : fffffa80`05914b50 fffff880`050034c1 fffffa80`05914b50 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c970 fffff800`02ccd1c7 : 00000000`00000000 fffff800`02e54c01 fffffa80`036b8240 00000000`00000001 : nt!KiPageFault+0x260
fffff800`00b9cb00 fffff880`044037f2 : fffff800`02cda4a9 00000000`001dba3e fffffa80`05a31928 fffff800`02e54cc0 : nt!KiInterruptDispatchNoLock+0x1b7
fffff800`00b9cc98 fffff800`02cda4a9 : 00000000`001dba3e fffffa80`05a31928 fffff800`02e54cc0 00000000`00000001 : amdppm!C1Halt+0x2
fffff800`00b9cca0 fffff800`02cc893c : fffff800`02e46e80 fffff800`00000000 00000000`00000000 fffff880`04887588 : nt!PoIdle+0x52a
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInterruptDispatchNoLock+1b7
fffff800`02ccd1c7 48018140470000  add     qword ptr [rcx+4740h],rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiInterruptDispatchNoLock+1b7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiInterruptDispatchNoLock+1b7

BUCKET_ID:  X64_0xA_nt!KiInterruptDispatchNoLock+1b7

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

[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\Rzff\Windows_NT6_BSOD_jcgriff2\030812-25927-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 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c5b000 PsLoadedModuleList = 0xfffff800`02ea0670
Debug session time: Thu Mar  8 08:51:01.286 2012 (UTC - 7:00)
System Uptime: 0 days 0:23:23.815
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3063636239663633
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

EXCEPTION_RECORD:  fffff8800391b808 -- (.exr 0xfffff8800391b808)
ExceptionAddress: fffff80002cce240 (nt!KeAccumulateTicks+0x0000000000000150)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff8800391b8b0 -- (.trap 0xfffff8800391b8b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000344bd2906 rbx=0000000000000000 rcx=fffff880009e8180
rdx=0000000000002711 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cce240 rsp=fffff8800391ba40 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=0000000000008fb0
r11=fffff880009e8180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po nc
nt!KeAccumulateTicks+0x150:
fffff800`02cce240 488b4618        mov     rax,qword ptr [rsi+18h] ds:5ed0:00000000`00000018=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ccf5fe to fffff80002cd7c10

STACK_TEXT:  
fffff880`0391a8e8 fffff800`02ccf5fe : 00000000`00000000 fffffa80`04421c38 fffff880`0391b060 fffff800`02d03830 : nt!KeBugCheck
fffff880`0391a8f0 fffff800`02d034fd : fffff800`02ee1488 fffff800`02e1fc8c fffff800`02c5b000 fffff880`0391b808 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`0391a920 fffff800`02d022d5 : fffff800`02e220fc fffff880`0391a998 fffff880`0391b808 fffff800`02c5b000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0391a950 fffff800`02d13361 : fffff880`0391b808 fffff880`0391b060 fffff880`00000000 00000000`00002711 : nt!RtlDispatchException+0x415
fffff880`0391b030 fffff800`02cd72c2 : fffff880`0391b808 fffff880`009e8180 fffff880`0391b8b0 fffff880`009f2f40 : nt!KiDispatchException+0x135
fffff880`0391b6d0 fffff800`02cd541f : fffff880`0391b8b0 fffff880`044d7a0d fffffa80`05a05d00 fffff880`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0391b8b0 fffff800`02cce240 : 00000000`00000000 fffffa80`059d4100 00000000`00000001 fffff880`0391bb80 : nt!KiInvalidOpcodeFault+0x11f
fffff880`0391ba40 fffff800`02ce3f58 : 00000000`00000000 fffffa80`04129b50 00000000`00002711 fffff800`02ce3760 : nt!KeAccumulateTicks+0x150
fffff880`0391bad0 fffff800`02ce3ce1 : 00000000`00000000 fffff880`0391bb80 fffff880`009e8180 00000000`00000001 : nt!KeUpdateRunTime+0xb8
fffff880`0391bb00 fffff880`04b207f2 : fffff800`02ce14a9 00000000`001dba2b fffffa80`059d4278 fffffa80`05a05dc0 : nt!KiSecondaryClockInterrupt+0x131
fffff880`0391bc98 fffff800`02ce14a9 : 00000000`001dba2b fffffa80`059d4278 fffffa80`05a05dc0 00000000`00000000 : amdppm!C1Halt+0x2
fffff880`0391bca0 fffff800`02ccf93c : fffff880`009e8180 fffff880`00000000 00000000`00000000 fffff880`01e5ca00 : nt!PoIdle+0x52a
fffff880`0391bd80 00000000`00000000 : fffff880`0391c000 fffff880`03916000 fffff880`0391bd40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
amdppm!C1Halt+2
fffff880`04b207f2 c3              ret

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  amdppm!C1Halt+2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: amdppm

IMAGE_NAME:  amdppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

FAILURE_BUCKET_ID:  X64_0x1E_0_amdppm!C1Halt+2

BUCKET_ID:  X64_0x1E_0_amdppm!C1Halt+2

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


[/list]

1. This bugcheck occurs very infrequently... I am not familiar with it, but my guess would be an outdated driver causing it.
2. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
3. Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
   Thanks to JMH for helping with my understanding of this crash.

It would appear your processor is not functioning as it should. This may be due to out of date drivers. The following drivers are out of date. Normally, I will sort through them and give links to individual ones, but it is late here and I am tired. I may come back and do this in the morning.

iirsp	fffff880`01545000	fffff880`01556000	Tue Dec 13 14:47:54 2005 (439f418a)	00019fb9		iirsp.sys
nfrd960	fffff880`016be000	fffff880`016ce000	Tue Jun 06 15:11:48 2006 (4485ef94)	0000ffcb		nfrd960.sys
secdrv	fffff880`06d14000	fffff880`06d1f000	Wed Sep 13 07:18:38 2006 (4508052e)	00010b40		secdrv.SYS
adpu320	fffff880`01256000	fffff880`01285000	Tue Feb 27 17:04:15 2007 (45e4c6ff)	0003588d		adpu320.sys
adpahci	fffff880`01200000	fffff880`01256000	Tue May 01 11:30:09 2007 (46377921)	00058e0f		adpahci.sys
arc	fffff880`00edf000	fffff880`00ef8000	Thu May 24 15:27:55 2007 (4656035b)	00017fb4		arc.sys
SiSRaid2	fffff880`01800000	fffff880`0180e000	Wed Sep 24 12:28:20 2008 (48da86c4)	00011d5d		SiSRaid2.sys
sisraid4	fffff880`0180e000	fffff880`01826000	Wed Oct 01 15:56:04 2008 (48e3f1f4)	0001ec6b		sisraid4.sys
adp94xx	fffff880`01373000	fffff880`013ee000	Fri Dec 05 16:54:42 2008 (4939bf42)	0007c740		adp94xx.sys
lsi_fc	fffff880`01556000	fffff880`01575000	Tue Dec 09 15:46:09 2008 (493ef531)	0001dc09		lsi_fc.sys
arcsas	fffff880`014a3000	fffff880`014be000	Wed Jan 14 12:27:37 2009 (496e3ca9)	0001f176		arcsas.sys
ql2300	fffff880`0185a000	fffff880`019fe000	Thu Jan 22 16:05:06 2009 (4978fba2)	0017acdb		ql2300.sys
vsmraid	fffff880`01830000	fffff880`0185a000	Fri Jan 30 18:18:57 2009 (4983a701)	00028def		vsmraid.sys
elxstor	fffff880`014be000	fffff880`01545000	Tue Feb 03 15:52:11 2009 (4988ca9b)	0008214f		elxstor.sys
stexstor	fffff880`01826000	fffff880`01830000	Tue Feb 17 16:03:36 2009 (499b4248)	0000b026		stexstor.sys
usbfilter	fffff880`045dc000	fffff880`045e9000	Mon Mar 09 05:49:01 2009 (49b5022d)	00017326		usbfilter.sys
amdsbs	fffff880`012a3000	fffff880`012ea000	Fri Mar 20 12:36:03 2009 (49c3e213)	0003938a		amdsbs.sys
btwl2cap	fffff880`06ae3000	fffff880`06aef000	Fri Apr 03 18:28:45 2009 (49d6a9bd)	00009866		btwl2cap.sys
lsi_scsi	fffff880`01588000	fffff880`015a7000	Thu Apr 16 16:13:50 2009 (49e7ad9e)	0002a7b5		lsi_scsi.sys
HpqKbFiltr	fffff880`04400000	fffff880`0440c000	Wed Apr 29 07:48:30 2009 (49f85aae)	00006ec8		HpqKbFiltr.sys
AtiPcie	fffff880`023da000	fffff880`023e2000	Tue May 05 09:00:22 2009 (4a005486)	000134c7		AtiPcie.sys
spldr	fffff880`02306000	fffff880`0230e000	Mon May 11 10:56:27 2009 (4a0858bb)	0000e0e9		spldr.sys
lsi_sas	fffff880`0102a000	fffff880`01047000	Mon May 18 18:20:23 2009 (4a11fb47)	000230a6		lsi_sas.sys
lsi_sas2	fffff880`01575000	fffff880`01588000	Mon May 18 18:31:48 2009 (4a11fdf4)	0002002e		lsi_sas2.sys
megasas	fffff880`015a7000	fffff880`015b3000	Mon May 18 19:09:46 2009 (4a1206da)	000169a1		megasas.sys
ql40xx	fffff880`016f9000	fffff880`01758000	Mon May 18 19:18:11 2009 (4a1208d3)	00029201		ql40xx.sys
MegaSR	fffff880`0161a000	fffff880`016be000	Mon May 18 19:25:54 2009 (4a120aa2)	00052e51		MegaSR.sys
Rt64win7	fffff880`04598000	fffff880`045d1000	Fri May 22 08:52:30 2009 (4a16bc2e)	00041606		Rt64win7.sys
AtiHdmi	fffff880`05d54000	fffff880`05d74000	Fri Jun 05 02:31:42 2009 (4a28d7ee)	0002234f		AtiHdmi.sys
ccHPx64	fffff880`04800000	fffff880`04893000	Fri Jun 19 17:28:39 2009 (4a3c1f27)	0009176e		ccHPx64.sys
SymIMv	fffff880`037cc000	fffff880`037d7000	Mon Jun 22 17:11:56 2009 (4a400fbc)	00013911		SymIMv.sys
SRTSP64	fffff880`06ed7000	fffff880`06f55000	Mon Jun 22 20:45:21 2009 (4a4041c1)	0007bd8e		SRTSP64.SYS
SRTSPX64	fffff880`0364c000	fffff880`03660000	Mon Jun 22 20:47:54 2009 (4a40425a)	000138d2		SRTSPX64.SYS
SYMEFA64	fffff880`01400000	fffff880`01467000	Tue Jun 23 15:52:39 2009 (4a414ea7)	0006b5cb		SYMEFA64.SYS
SYMEVENT64x86	fffff880`01c4c000	fffff880`01c82000	Wed Jun 24 14:19:12 2009 (4a428a40)	0002b2e0		SYMEVENT64x86.SYS
btwavdt	fffff880`06765000	fffff880`067e0000	Wed Jun 24 23:50:13 2009 (4a431015)	0002ce2d		btwavdt.sys
btwrchid	fffff880`06aef000	fffff880`06af2880	Wed Jun 24 23:51:37 2009 (4a431069)	0000f764		btwrchid.sys
enecir	fffff880`04b98000	fffff880`04bb5000	Sun Jun 28 20:17:30 2009 (4a48243a)	00019675		enecir.sys

You can probably find most of these drivers and the links to the manufacturer sites at: Driver Reference Table (for the driver list)
and
Drivers and Downloads (for the manufacturer list)
Anything you have trouble finding, use Google. If you still cannot find the driver and manufacturer (we do recommend you get all drivers directly from the manufacturer and for the correct device), let us know and we will help find it.

Software & Driver Downloads HP Pavilion dv6-2020ec Entertainment Notebook PC - HP Customer Care (United States - English) may also help


I would also suggest running hardware diagnostics:

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • 
    Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.