BOSD after clean up

It says it is the network adopter driver. If the second scan comes free, we must to think it alternatively.

And yes, waiting for the dark world, too

i cant instal the second program i need an empy cd for that. or i have to find an usb wich proves problematic

Take your time
It is needed to decide whether the system is free from threats or not, specially where there is internet related crash out of no solid reason.

So for a fev day evrything was fine..and then today it happent twice :S

Mate I think its the time for a Clean reinstall now, as it is crashing on the same driver, again and again.

If it is simply a driver issue, the clean reinstall will recover it.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

*** 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+17aaa )

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

1: 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: fffff88001671360, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fc100
GetUlongFromAddress: unable to read from fffff800030fc1c0
 0000000001800135 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
ndis! ?? ::FNODOBFM::`string'+15cd
fffff880`01671360 8b4728          mov     eax,dword ptr [rdi+28h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880084a37a0 -- (.trap 0xfffff880084a37a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000001e0 rbx=0000000000000000 rcx=0000000000000b08
rdx=fffffa8004794a90 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001671360 rsp=fffff880084a3930 rbp=fffffa8005574000
 r8=fffffa8004ad7130  r9=0000000000000001 r10=0000000000000000
r11=fffffa80053051a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
ndis! ?? ::FNODOBFM::`string'+0x15cd:
fffff880`01671360 8b4728          mov     eax,dword ptr [rdi+28h] ds:00000000`00000028=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ec41a9 to fffff80002ec4c00

STACK_TEXT:  
fffff880`084a3658 fffff800`02ec41a9 : 00000000`0000000a 00000000`01800135 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`084a3660 fffff800`02ec2e20 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`04794a90 : nt!KiBugCheckDispatch+0x69
fffff880`084a37a0 fffff880`01671360 : fffffa80`06e829f0 fffffa80`05574000 fffffa80`000000a0 fffffa80`047b6230 : nt!KiPageFault+0x260
fffff880`084a3930 fffff880`04817aaa : fffffa80`053051a0 fffffa80`053051a0 fffffa80`04ad7130 fffffa80`05574000 : ndis! ?? ::FNODOBFM::`string'+0x15cd
fffff880`084a39d0 fffffa80`053051a0 : fffffa80`053051a0 fffffa80`04ad7130 fffffa80`05574000 fffffa80`05582740 : Rt64win7+0x17aaa
fffff880`084a39d8 fffffa80`053051a0 : fffffa80`04ad7130 fffffa80`05574000 fffffa80`05582740 00000000`000001c0 : 0xfffffa80`053051a0
fffff880`084a39e0 fffffa80`04ad7130 : fffffa80`05574000 fffffa80`05582740 00000000`000001c0 00000000`00000000 : 0xfffffa80`053051a0
fffff880`084a39e8 fffffa80`05574000 : fffffa80`05582740 00000000`000001c0 00000000`00000000 ffff0000`00000103 : 0xfffffa80`04ad7130
fffff880`084a39f0 fffffa80`05582740 : 00000000`000001c0 00000000`00000000 ffff0000`00000103 00000000`00000001 : 0xfffffa80`05574000
fffff880`084a39f8 00000000`000001c0 : 00000000`00000000 ffff0000`00000103 00000000`00000001 fffffa80`047b0000 : 0xfffffa80`05582740
fffff880`084a3a00 00000000`00000000 : ffff0000`00000103 00000000`00000001 fffffa80`047b0000 00000000`00000000 : 0x1c0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Rt64win7+17aaa
fffff880`04817aaa ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  Rt64win7+17aaa

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164d5d2

FAILURE_BUCKET_ID:  X64_0xD1_Rt64win7+17aaa

BUCKET_ID:  X64_0xD1_Rt64win7+17aaa

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

1: kd> lmvm Rt64win7
start             end                 module name
fffff880`04800000 fffff880`048d2000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Wed Apr 10 08:30:34 2013 (5164D5D2)
    CheckSum:         000DB44C
    ImageSize:        000D2000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

My instal was made by come tech firm i dont have a code.

lorddenis said:

My instal was made by come tech firm i dont have a code.

I can read you, my friend :) We are the same with keyboards
Now that's a problem. Do one thing as a more try. Uninstall and update the network driver.
First, download the network card driver from manufactuer's website. You have done it already. Perhaps there is a further update I guess.
Then reinstall the driver:

1. Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
2. Double click to expand "Network adaptors".
3. Right click your network card and click Uninstall.
4. Check "Delete driver software for this device" check box, click OK.
5. Restart the computer
6. If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually. Driver Install - Device Manager

Let us know the result?

Im sorry for my late replay. Working all the time. and today i went out.. its 4 in the morning.. im so drunk that ..well lets just say im drunk hahaha

so i did as instructed.. the windows configured the drivers at startup and now all i can do i wait and see if this happens again.

Thank you!

EDIT .
Like 30 seconds after i posted the post above i got a blue screan of death. and then the pc restarted tryed doing the SF-DIAGNOSTIC TOOL. 1 try got a BSOD, 2 try got a BSOD 3th try was a succes and the file is attached.

:/

Crashed on the same thing ... the Realtek network driver.

A new version is out on 2013/8/1, you may have a try ..... Realtek

But do it after the hangover is over

Not finding any real cause of failing the same thing over and over. We need to make it sure that it is not a network chip corruption, and so a clean reinstall was needed there.