Having trouble with BSODs

[sladeknight08]

Hello, this is my first time posting so I apologize in advance if I'm doing something wrong. Recently (the past 3 months) I've been having BSOD's at what seems to be random intervals--while playing games, while idling, and even when I'm on the internet. Thus far, I've BSOD'ed somewhere around a dozen times. I can't find much of anything online, but I thought I'd post here. I'm running Home Premium x64.

BCCode: d1
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFFA6000C042E0

C:\Windows\Minidump\Mini092510-01.dmp
C:\Windows\Temp\WER-42015-0.sysdata.xml
C:\Windows\Temp\WER24D8.tmp.version.txt


Please help!

 

[richc46]

http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL http://www.carrona.org/bsodindx.html#topUsual causes: Device driver

 

[sladeknight08]

I hope this helps. I'm not great with computers.

 

[sladeknight08]

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL Usual causes: Device driver

Device driver? Well, I reinstalled Windows 3 months ago, since I've done that has been when the BSOD's started. All I did was reinstall with the Windows disc, should I reinstall my drivers? Is that what it's referring to?

 

[richc46]

Its late here, Ill take care of this tomorrow. That notice is just a general description of the BC error. Ill post everything that should be done, tomorrow. Have a good night.
Not fair to you if I rush it.
But it looks like a Realtek driver may be the problem.

 

[richc46]

STOP 0x000000C2: BAD_POOL_CALLER Usual causes: Device driver, ?Memory
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL Usual causes: Device driver
Stop 0x00000009F

icrosoft (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\Temp1_Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\Mini061610-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Machine Name:
Kernel base = 0xfffff800`02003000 PsLoadedModuleList = 0xfffff800`021c7dd0
Debug session time: Wed Jun 16 01:28:48.284 2010 (GMT-4)
System Uptime: 0 days 1:09:47.306
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, 110b, 4040004, fffffa8004fcc3a0}
Unable to load image \SystemRoot\System32\drivers\tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
GetPointerFromAddress: unable to read from fffff8000222a080
Probably caused by : tdx.sys ( tdx!TdxMessageTlRequestComplete+3f )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000110b, (reserved)
Arg3: 0000000004040004, Memory contents of the pool block
Arg4: fffffa8004fcc3a0, Address of the block of pool being deallocated
Debugging Details:
------------------
 
POOL_ADDRESS:  fffffa8004fcc3a0 
FREED_POOL_TAG:  TdxB
BUGCHECK_STR:  0xc2_7_TdxB
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff800021363a5 to fffff8000205d4d0
STACK_TEXT:  
fffffa60`0171b868 fffff800`021363a5 : 00000000`000000c2 00000000`00000007 00000000`0000110b 00000000`04040004 : nt!KeBugCheckEx
fffffa60`0171b870 fffffa60`0398a723 : 00000000`00000008 00000000`00000000 00000000`00000000 fffff800`0252877b : nt!ExFreePool+0x48a
fffffa60`0171b920 fffffa60`00e3d9b0 : 00000000`00000000 fffffa80`049ee720 00000000`00000000 fffffa60`005f5d40 : tdx!TdxMessageTlRequestComplete+0x3f
fffffa60`0171b960 00000000`00000000 : fffffa80`049ee720 00000000`00000000 fffffa60`005f5d40 00000000`00000000 : tcpip+0x319b0
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
tdx!TdxMessageTlRequestComplete+3f
fffffa60`0398a723 488d15d6f9ffff  lea     rdx,[tdx! ?? ::FNODOBFM::`string' (fffffa60`0398a100)]
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  tdx!TdxMessageTlRequestComplete+3f
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: tdx
IMAGE_NAME:  tdx.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  49e02de4
FAILURE_BUCKET_ID:  X64_0xc2_7_TdxB_tdx!TdxMessageTlRequestComplete+3f
BUCKET_ID:  X64_0xc2_7_TdxB_tdx!TdxMessageTlRequestComplete+3f
Followup: MachineOwner
---------

 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\Temp1_Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\Mini072610-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Machine Name:
Kernel base = 0xfffff800`02651000 PsLoadedModuleList = 0xfffff800`02815dd0
Debug session time: Mon Jul 26 20:17:06.107 2010 (GMT-4)
System Uptime: 0 days 0:53:02.008
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 1, fffffa6000c05318}
Unable to load image \SystemRoot\system32\DRIVERS\Rtlh64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rtlh64.sys
*** ERROR: Module load completed but symbols could not be loaded for Rtlh64.sys
Probably caused by : pacer.sys ( pacer!PcFilterSendNetBufferListsComplete+f4 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffffa6000c05318, address which referenced memory
Debugging Details:
------------------
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002878080
 0000000000000000 
CURRENT_IRQL:  2
FAULTING_IP: 
ndis!NdisFSendNetBufferListsComplete+148
fffffa60`00c05318 498917          mov     qword ptr [r15],rdx
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
TRAP_FRAME:  fffff8000369cb40 -- (.trap 0xfffff8000369cb40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa6000d640e0
rdx=fffffa8004711d60 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa6000c05318 rsp=fffff8000369ccd0 rbp=0000000000000000
 r8=0000000000000001  r9=fffffa8006a76780 r10=000000000000030f
r11=fffff8000369cd38 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
ndis!NdisFSendNetBufferListsComplete+0x148:
fffffa60`00c05318 498917          mov     qword ptr [r15],rdx ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800026ab26e to fffff800026ab4d0
STACK_TEXT:  
fffff800`0369c9f8 fffff800`026ab26e : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`0369ca00 fffff800`026aa14b : 00000000`00000001 fffffa80`048c4030 00000000`00000f43 fffffa80`06d04320 : nt!KiBugCheckDispatch+0x6e
fffff800`0369cb40 fffffa60`00c05318 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x20b
fffff800`0369ccd0 fffffa60`03d6f8f0 : 00000000`00000000 fffffa80`04eed1a0 fffffa80`06ce9010 fffffa80`048c4240 : ndis!NdisFSendNetBufferListsComplete+0x148
fffff800`0369cd40 fffffa60`00da724c : fffffa80`04eed1a0 fffffa60`00c5b110 00000000`00000001 fffffa80`041017e0 : pacer!PcFilterSendNetBufferListsComplete+0xf4
fffff800`0369cdb0 fffffa60`032f99d7 : 00000000`00000000 fffffa80`06a76780 00000000`00000000 fffffa80`06a76780 : ndis!NdisMSendNetBufferListsComplete+0x7c
fffff800`0369cdf0 00000000`00000000 : fffffa80`06a76780 00000000`00000000 fffffa80`06a76780 fffffa80`06a5f4c0 : Rtlh64+0x69d7
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
pacer!PcFilterSendNetBufferListsComplete+f4
fffffa60`03d6f8f0 4c8d5c2450      lea     r11,[rsp+50h]
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  pacer!PcFilterSendNetBufferListsComplete+f4
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: pacer
IMAGE_NAME:  pacer.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  49e02de0
FAILURE_BUCKET_ID:  X64_0xD1_pacer!PcFilterSendNetBufferListsComplete+f4
BUCKET_ID:  X64_0xD1_pacer!PcFilterSendNetBufferListsComplete+f4
Followup: MachineOwner
---------

crosoft (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\Temp1_Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\Mini090110-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0xfffff800`02660000 PsLoadedModuleList = 0xfffff800`02824dd0
Debug session time: Wed Sep  1 18:23:41.733 2010 (GMT-4)
System Uptime: 0 days 2:43:59.690
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8004bfea30, fffffa800695c050, fffffa8005228c60}
*** WARNING: Unable to verify timestamp for Rtlh64.sys
*** ERROR: Module load completed but symbols could not be loaded for Rtlh64.sys
Probably caused by : Rtlh64.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8004bfea30, Physical Device Object of the stack
Arg3: fffffa800695c050, Functional Device Object of the stack
Arg4: fffffa8005228c60, The blocked IRP
Debugging Details:
------------------
 
DRVPOWERSTATE_SUBCODE:  3
IRP_ADDRESS:  fffffa8005228c60
DEVICE_OBJECT: fffffa800695c050
DRIVER_OBJECT: fffffa80067c9060
IMAGE_NAME:  Rtlh64.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  45190cf7
MODULE_NAME: Rtlh64
FAULTING_MODULE: fffffa60036f3000 Rtlh64
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff800027157ed to fffff800026ba4d0
STACK_TEXT:  
fffff800`0369d9f8 fffff800`027157ed : 00000000`0000009f 00000000`00000003 fffffa80`04bfea30 fffffa80`0695c050 : nt!KeBugCheckEx
fffff800`0369da00 fffff800`026be3fd : fffff800`0369dad8 00000000`00000000 00000000`00000002 fffffa80`06959b01 : nt! ?? ::FNODOBFM::`string'+0x17cec
fffff800`0369da70 fffff800`026bd8d5 : fffff800`0369dcd0 fffffa60`00b99702 fffff800`0369dcc8 00000000`00000010 : nt!KiTimerListExpire+0x30d
fffff800`0369dca0 fffff800`026bdfaf : 00001970`4c51599b 00000000`00000000 fffffa80`00000010 fffff800`027d6a80 : nt!KiTimerExpiration+0x295
fffff800`0369dd10 fffff800`026be8d2 : fffff800`027d3680 fffff800`027d3680 00000000`00000000 fffff800`027d8b80 : nt!KiRetireDpcList+0x1df
fffff800`0369dd80 fffff800`0288b860 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
fffff800`0369ddb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_Rtlh64.sys
BUCKET_ID:  X64_0x9F_IMAGE_Rtlh64.sys
Followup: MachineOwner
---------

You gave me 8 dump reports, and 3 error codes as shown above. They indicate that the following drivers require to be updated.

Rtlh64.sys
tcpip.sys

Tcpip.sys is a Microsoft driver and probably not the true cause.

Update
Rtlh64.sys file description
Productname: Realtek 8101E/8168/8169 PCI/PCIe Adapters
Description: Realtek 8101E/8168/8169 NDIS6 64-bit Driver
Company: Realtek Corporation

Outdated Drivers

Rtlh64.sys   Tue Sep 26 07:20:23 2006 
peauth.sys   Mon Oct 23 07:57:00 2006 
Null.SYS     Thu Nov 02 05:37:15 2006 
swenum.sys   Thu Nov 02 05:37:33 2006 
intelppm.sys Sat Jan 19 00:52:45 2008 
Fs_Rec.SYS   Sat Jan 19 00:53:41 2008 
cdfs.sys     Sat Jan 19 00:53:45 2008 
Msfs.SYS     Sat Jan 19 00:53:55 2008 
bowser.sys   Sat Jan 19 00:54:51 2008 
luafv.sys    Sat Jan 19 00:59:06 2008 
msisadrv.sys Sat Jan 19 01:02:50 2008 
mssmbios.sys Sat Jan 19 01:02:54 2008 
fileinfo.sys Sat Jan 19 01:05:23 2008 
Dxapi.sys    Sat Jan 19 01:08:00 2008 
mountmgr.sys Sat Jan 19 01:28:01 2008 
mouclass.sys Sat Jan 19 01:28:05 2008 
kbdclass.sys Sat Jan 19 01:28:05 2008 
i8042prt.sys Sat Jan 19 01:28:08 2008 
mouhid.sys   Sat Jan 19 01:28:10 2008 
ksthunk.sys  Sat Jan 19 01:28:14 2008 
parport.sys  Sat Jan 19 01:28:36 2008 
serenum.sys  Sat Jan 19 01:28:36 2008 
serial.sys   Sat Jan 19 01:28:41 2008 
intelide.sys Sat Jan 19 01:28:56 2008 
crcdisk.sys  Sat Jan 19 01:30:12 2008 
vga.sys      Sat Jan 19 01:32:21 2008 
VIDEOPRT.SYS Sat Jan 19 01:32:25 2008 
WDFLDR.SYS   Sat Jan 19 01:32:33 2008 
monitor.sys  Sat Jan 19 01:32:34 2008 
Wdf01000.sys Sat Jan 19 01:33:27 2008 
WMILIB.SYS   Sat Jan 19 01:33:45 2008 
HIDPARSE.SYS Sat Jan 19 01:33:51 2008 
USBD.SYS     Sat Jan 19 01:33:53 2008 
usbuhci.sys  Sat Jan 19 01:33:56 2008 
usbccgp.sys  Sat Jan 19 01:34:04 2008 
umbus.sys    Sat Jan 19 01:34:16 2008 
mpsdrv.sys   Sat Jan 19 01:35:28 2008 
rspndr.sys   Sat Jan 19 01:35:48 2008 
lltdio.sys   Sat Jan 19 01:35:48 2008 
tunmp.sys    Sat Jan 19 01:36:30 2008 
netbios.sys  Sat Jan 19 01:36:35 2008 
nsiproxy.sys Sat Jan 19 01:36:45 2008 
ndistapi.sys Sat Jan 19 01:37:22 2008 
NDProxy.SYS  Sat Jan 19 01:37:26 2008 
asyncmac.sys Sat Jan 19 01:37:27 2008 
rasacd.sys   Sat Jan 19 01:37:30 2008 
rdpencdd.sys Sat Jan 19 01:42:03 2008 
RDPCDD.sys   Sat Jan 19 01:42:04 2008 
drmk.sys     Sat Jan 19 02:20:04 2008 
point64k.sys Tue Jun 03 00:51:47 2008 
skfiltv.sys  Thu Aug 14 02:48:33 2008

In addition:
If overclocking restore normal settings
SFC /scannow
System Files - SFC Command
Update outdated listed drivers. Update the one that is the potential cause of the BSOD. Update the others at your leisure, but it should be done. If the BSODs continue, I will suggest the Driver Verifier test to determine which of the old drivers need immediate attention.
Scan with your Anti Virus

How to Find Drivers
search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/

After performing all of the above, post back with any new BSOD reports, or indicate that the attempted repairs were successful.
If any links do not work, if clicked, please copy and paste to browser address bar.
Remember that several attempts may be required before we can solve your BSOD problem. These reports are not definitive but merely point the way to a solution.