Actually I have one other that is identical, except the newer one has .2 ghz better. That one is running with the same specs as this one that I am on now. even the same case.
A new BSOD came up right after first logon, I saw the mini dump being created and the file name was rt64win, after a search noticed its the real tech driver. I have uploaded the new jcgriff file.
Thanks
Rt64win it is.. Re-install it
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\dmps\060211-26301-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 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02e1e000 PsLoadedModuleList = 0xfffff800`0305be50
Debug session time: Thu Jun 2 09:48:31.178 2011 (GMT-4)
System Uptime: 0 days 0:00:36.536
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
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
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88004115283, fffff88003153928, fffff88003153190}
Probably caused by : Rt64win7.sys ( Rt64win7+2283 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004115283, The address that the exception occurred at
Arg3: fffff88003153928, Exception Record Address
Arg4: fffff88003153190, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
Rt64win7+2283
fffff880`04115283 488bcf mov rcx,rdi
EXCEPTION_RECORD: fffff88003153928 -- (.exr 0xfffff88003153928)
ExceptionAddress: fffff88004115283 (Rt64win7+0x0000000000002283)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88003153190 -- (.cxr 0xfffff88003153190)
rax=0000000000000000 rbx=fffffa800e96a000 rcx=fffffa800e96a5f0
rdx=0000000000000000 rsi=fffffa800f6ffa00 rdi=fffffa800e96a5f0
rip=fffff88004115283 rsp=fffff88003153b60 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=fffffa800f6ffa60 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
Rt64win7+0x2283:
fffff880`04115283 488bcf mov rcx,rdi
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c60e0
ffffffffffffffff
FOLLOWUP_IP:
Rt64win7+2283
fffff880`04115283 488bcf mov rcx,rdi
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffffa800f6ffa00 to fffff88004115283
STACK_TEXT:
fffff880`03153b60 fffffa80`0f6ffa00 : 00000000`00000018 fffffa80`0e96a5f0 fffffa80`0e96a000 00000000`00000001 : Rt64win7+0x2283
fffff880`03153b68 00000000`00000018 : fffffa80`0e96a5f0 fffffa80`0e96a000 00000000`00000001 fffffa80`0f6ffa60 : 0xfffffa80`0f6ffa00
fffff880`03153b70 fffffa80`0e96a5f0 : fffffa80`0e96a000 00000000`00000001 fffffa80`0f6ffa60 fffffa80`0f6ffa50 : 0x18
fffff880`03153b78 fffffa80`0e96a000 : 00000000`00000001 fffffa80`0f6ffa60 fffffa80`0f6ffa50 fffff880`01436549 : 0xfffffa80`0e96a5f0
fffff880`03153b80 00000000`00000001 : fffffa80`0f6ffa60 fffffa80`0f6ffa50 fffff880`01436549 fffffa80`0e7031a0 : 0xfffffa80`0e96a000
fffff880`03153b88 fffffa80`0f6ffa60 : fffffa80`0f6ffa50 fffff880`01436549 fffffa80`0e7031a0 fffff800`03033500 : 0x1
fffff880`03153b90 fffffa80`0f6ffa50 : fffff880`01436549 fffffa80`0e7031a0 fffff800`03033500 fffffa80`0f6ffa50 : 0xfffffa80`0f6ffa60
fffff880`03153b98 fffff880`01436549 : fffffa80`0e7031a0 fffff800`03033500 fffffa80`0f6ffa50 fffffa80`0e7031a0 : 0xfffffa80`0f6ffa50
fffff880`03153ba0 fffff800`02e9b961 : fffff800`03033500 fffff800`03189820 fffff800`030335a0 002d0073`00000003 : ndis!ndisQueuedCheckForHang+0xa9
fffff880`03153cb0 fffff800`03131bc6 : 00000000`004c0060 fffffa80`0caa2b60 00000000`00000080 fffffa80`0ca7c9e0 : nt!ExpWorkerThread+0x111
fffff880`03153d40 fffff800`02e6cbc6 : fffff880`0308f180 fffffa80`0caa2b60 fffff880`0309a040 00010000`0000092d : nt!PspSystemThreadStartup+0x5a
fffff880`03153d80 00000000`00000000 : fffff880`03154000 fffff880`0314e000 fffff880`031539f0 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: Rt64win7+2283
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Rt64win7
IMAGE_NAME: Rt64win7.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8750a0
STACK_COMMAND: .cxr 0xfffff88003153190 ; kb
FAILURE_BUCKET_ID: X64_0x7E_Rt64win7+2283
BUCKET_ID: X64_0x7E_Rt64win7+2283
Followup: MachineOwner
---------