BSOD

[Inv1ctus]

Hello, I have this computer for about 45 days now and BSOD's would occur every few days but in the last few days they occur basically every few hours. I know it's related to ethernet network card and I've tried several different drivers, some older directly from HP site which said it fixes this BSOD problem but it did not. I'm currently using the latest drivers and it's been fine for two weeks, but now it started happening regularly. I've included the latest crash dump file. So could it be that there was some "left-overs" from previous drivers and this is causing the BSOD's and if yes, how would I know this is the issue? Thank You for Your help.

 

[ttran]

Hello, I have this computer for about 45 days now and BSOD's would occur every few days but in the last few days they occur basically every few hours. I know it's related to ethernet network card and I've tried several different drivers, some older directly from HP site which said it fixes this BSOD problem but it did not. I'm currently using the latest drivers and it's been fine for two weeks, but now it started happening regularly. I've included the latest crash dump file. So could it be that there was some "left-overs" from previous drivers and this is causing the BSOD's and if yes, how would I know this is the issue? Thank You for Your help.

Hi and Welcome to SF

This is pretty straight forward, Rt64win7.sys, which is your Realtek Ethernet driver cause this BSODs. Please download and install fresh copy of it

Work on the driver first, then you might want to do this as optional:

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

BUGCHECK SUMMARY:

[/U]
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.153\080510-18735-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a4f000 PsLoadedModuleList = 0xfffff800`02c8ce50
Debug session time: Thu Aug  5 10:17:13.616 2010 (UTC + 7:00)
System Uptime: 0 days 1:26:59.177
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1800135, 2, 0, fffff88001667c1e}

Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+118d2 )

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

 

[Inv1ctus]

Ok I did remove daemon tools and ran the SPTD uninstaller and computer was running for about 8 hours when another crash happened. Should I have manually deleted some sptd files from register or is the SPTD uninstall enough? do you have any other suggestions what I could do? Thank You.

 

[Tews]

Your .dmp file blames Rt64win7.sys (Realtek 8101E/8168/8169 PCI/PCIe Adapters Ethernet Driver) as the cause of your crash... download the latest version for your system from Realtec ..

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\080510-19531-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a11000 PsLoadedModuleList = 0xfffff800`02c4ee50
Debug session time: Thu Aug  5 08:02:31.844 2010 (UTC - 4:00)
System Uptime: 0 days 7:39:49.545
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1800135, 2, 0, fffff880014c0c1e}

Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+118d2 )

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: 0000000001800135, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880014c0c1e, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb90e0
 0000000001800135 

CURRENT_IRQL:  2

FAULTING_IP: 
ndis! ?? ::FNODOBFM::`string'+14dd
fffff880`014c0c1e 8b4728          mov     eax,dword ptr [rdi+28h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88007baa7a0 -- (.trap 0xfffff88007baa7a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000001e0 rbx=0000000000000000 rcx=00000000c00bfe21
rdx=fffffa8006b53b40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880014c0c1e rsp=fffff88007baa930 rbp=0000000000000001
 r8=fffffa800439a728  r9=0000000000000001 r10=fffff88007baaa24
r11=fffffa8004ecf1a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
ndis! ?? ::FNODOBFM::`string'+0x14dd:
fffff880`014c0c1e 8b4728          mov     eax,dword ptr [rdi+28h] ds:5ba0:00000000`00000028=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a80b69 to fffff80002a81600

STACK_TEXT:  
fffff880`07baa658 fffff800`02a80b69 : 00000000`0000000a 00000000`01800135 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`07baa660 fffff800`02a7f7e0 : fffffa80`048c6220 fffffa80`06b53b40 fffffa80`066bac5d 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`07baa7a0 fffff880`014c0c1e : fffffa80`06645e60 00000000`00000001 fffffa80`000001c0 fffffa80`06db5030 : nt!KiPageFault+0x260
fffff880`07baa930 fffff880`03a118d2 : fffffa80`04ecf1a0 fffffa80`04ecf101 fffffa80`0439a728 00000000`00000001 : ndis! ?? ::FNODOBFM::`string'+0x14dd
fffff880`07baa9d0 fffffa80`04ecf1a0 : fffffa80`04ecf101 fffffa80`0439a728 00000000`00000001 fffffa80`050acba8 : Rt64win7+0x118d2
fffff880`07baa9d8 fffffa80`04ecf101 : fffffa80`0439a728 00000000`00000001 fffffa80`050acba8 00000000`000001d8 : 0xfffffa80`04ecf1a0
fffff880`07baa9e0 fffffa80`0439a728 : 00000000`00000001 fffffa80`050acba8 00000000`000001d8 00000103`00000000 : 0xfffffa80`04ecf101
fffff880`07baa9e8 00000000`00000001 : fffffa80`050acba8 00000000`000001d8 00000103`00000000 00000000`00000000 : 0xfffffa80`0439a728
fffff880`07baa9f0 fffffa80`050acba8 : 00000000`000001d8 00000103`00000000 00000000`00000000 fffffa80`06b53b40 : 0x1
fffff880`07baa9f8 00000000`000001d8 : 00000103`00000000 00000000`00000000 fffffa80`06b53b40 00000000`00000000 : 0xfffffa80`050acba8
fffff880`07baaa00 00000103`00000000 : 00000000`00000000 fffffa80`06b53b40 00000000`00000000 00000001`00000014 : 0x1d8
fffff880`07baaa08 00000000`00000000 : fffffa80`06b53b40 00000000`00000000 00000001`00000014 fffffa80`06db5030 : 0x103`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Rt64win7+118d2
fffff880`03a118d2 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  Rt64win7+118d2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c21cf95

FAILURE_BUCKET_ID:  X64_0xD1_Rt64win7+118d2

BUCKET_ID:  X64_0xD1_Rt64win7+118d2

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