BSOD......

George1 · Mar 25, 2011

Computer history.
Built last June, and was the only time installing Windows 7(64 bit).
Had some problems, with motherboard(rev. 1) and had it replaced (rev. 2).
Replaced PSU as motherboard was not the problem, that problem resolved by replacing a bad PSU.

Checked CPU temps, OK.
No overclocking done.

Yesterday I got a message for a new download for my mouse, downloaded and installed it. Rebooted and no problems.
Also deleted pf files as I read that some could be left over from programs no longer used and they would be rebuilt with only what is needed. Saving boot time was the reason, I've been getting errors and warnings about the boot times taking too long.

The file is attached.

zigzag3143 · Mar 25, 2011

George1 said:
Computer history.
Built last June, and was the only time installing Windows 7(64 bit).
Had some problems, with motherboard(rev. 1) and had it replaced (rev. 2).
Replaced PSU as motherboard was not the problem, that problem resolved by replacing a bad PSU.

Checked CPU temps, OK.
No overclocking done.

Yesterday I got a message for a new download for my mouse, downloaded and installed it. Rebooted and no problems.
Also deleted pf files as I read that some could be left over from programs no longer used and they would be rebuilt with only what is needed. Saving boot time was the reason, I've been getting errors and warnings about the boot times taking too long.

The file is attached.

George hi and welcome

This one was caused by your Rt64win7.sys driver. Thats your realtek NDIS driver.

A simple re-install with the newest version should help.

Ken J

Code:

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\032511-16723-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`01c00000 PsLoadedModuleList = 0xfffff800`01e45e90
Debug session time: Fri Mar 25 11:43:12.630 2011 (GMT-4)
System Uptime: 0 days 0:03:19.146
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}

Unable to load image 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+17e7a )

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

6: 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: 
+5cc4952f0183dc4c
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880022461d8 -- (.exr 0xfffff880022461d8)
ExceptionAddress: fffff880017627c1 (ndis!ndisParseReceivedNBL+0x0000000000000081)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002246280 -- (.trap 0xfffff88002246280)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80075b1110
rdx=00009c0101000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880017627c1 rsp=fffff88002246410 rbp=0000000000000000
 r8=0000000000000600  r9=fffff880022464e0 r10=0000000000000000
r11=fffff880022464d8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
ndis!ndisParseReceivedNBL+0x81:
fffff880`017627c1 0fb64a0c        movzx   ecx,byte ptr [rdx+0Ch] ds:2950:00009c01`0100000c=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001c77ffe to fffff80001c80610

STACK_TEXT:  
fffff880`022452b8 fffff800`01c77ffe : 00000000`00000000 00000000`00000000 fffff880`02245a30 fffff800`01cac2a0 : nt!KeBugCheck
fffff880`022452c0 fffff800`01cabf6d : fffff800`01e87a10 fffff800`01dc3c78 fffff800`01c00000 fffff880`022461d8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`022452f0 fffff800`01caad45 : fffff800`01dc70fc fffff880`02245368 fffff880`022461d8 fffff800`01c00000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02245320 fffff800`01cbbdc1 : fffff880`022461d8 fffff880`02245a30 fffff880`00000000 00000000`0000003c : nt!RtlDispatchException+0x415
fffff880`02245a00 fffff800`01c7fcc2 : fffff880`022461d8 fffff880`02246500 fffff880`02246280 00000000`0000003c : nt!KiDispatchException+0x135
fffff880`022460a0 fffff800`01c7e5ca : ffff0000`03b2b189 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02246280 fffff880`017627c1 : 00000000`00004e84 fffffa80`06502880 00000000`00000006 fffff800`01c8cca1 : nt!KiGeneralProtectionFault+0x10a
fffff880`02246410 fffff880`01762592 : 00000000`00000000 fffff880`02246560 00000000`00000000 00000000`00000008 : ndis!ndisParseReceivedNBL+0x81
fffff880`02246460 fffff880`017629c5 : 00000000`00000000 fffffa80`063c0000 00000000`00000000 00000000`00000000 : ndis!ndisSortNetBufferLists+0xc2
fffff880`022464e0 fffff880`016dbcc1 : fffffa80`0710b1a0 00000000`00000002 00000000`00000001 fffff880`022469f0 : ndis!ndisMDispatchReceiveNetBufferLists+0xc5
fffff880`02246960 fffff880`04340e7a : fffffa80`071e9000 fffff880`04b8e650 00000000`00000000 fffffa80`075b2e20 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1
fffff880`022469b0 fffffa80`071e9000 : fffff880`04b8e650 00000000`00000000 fffffa80`075b2e20 00000000`00000001 : Rt64win7+0x17e7a
fffff880`022469b8 fffff880`04b8e650 : 00000000`00000000 fffffa80`075b2e20 00000000`00000001 00000000`00000006 : 0xfffffa80`071e9000
fffff880`022469c0 00000000`00000000 : fffffa80`075b2e20 00000000`00000001 00000000`00000006 0000000a`00000001 : 0xfffff880`04b8e650


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Rt64win7+17e7a
fffff880`04340e7a ??              ???

SYMBOL_STACK_INDEX:  b

SYMBOL_NAME:  Rt64win7+17e7a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ba73efa

FAILURE_BUCKET_ID:  X64_0x1E_Rt64win7+17e7a

BUCKET_ID:  X64_0x1E_Rt64win7+17e7a

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

6: kd> lmvm Rt64win7
start             end                 module name
fffff880`04329000 fffff880`04380000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Mon Mar 22 05:57:14 2010 (4BA73EFA)
    CheckSum:         0005CA6C
    ImageSize:        00057000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

George1 · Mar 25, 2011

Thanks, how do you find these drivers? I do a search but at times get different versions.
I went to realtek web site and searched for the driver but they don't have it.

Realtek

George1 · Mar 25, 2011

I found this one but doesn't specify the driver you mentioned.

Realtek

The package I looked at is: Win7 and WinServer 2008 R2 Driver
But I don't have WinServer I don't think.

Tews · Mar 25, 2011

Here is the latest version that I was able to find -=> Download

George1 · Mar 25, 2011

Thanks, I have the driver in my download directory, where do I move it so the OS will find it?

George1 · Mar 25, 2011

I got it installed. Went into device manager and found it on my computer using update.

Thanks all!!!.

BSOD......

George1

New member

My Computer

zigzag3143

New member

My Computer

George1

New member

My Computer

George1

New member

My Computer

Tews

Professional Lurker

My Computer

George1

New member

My Computer

George1

New member

My Computer