Both look like they were caused by your Realtek driver Rt64win7.sys.
I would recommend updating your network card drivers in Device Manager.
Here is the analysis:
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Jonathan\Desktop\030510-52899-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e1d000 PsLoadedModuleList = 0xfffff800`0305ae50
Debug session time: Fri Mar 5 05:49:49.254 2010 (GMT-5)
System Uptime: 0 days 1:37:04.470
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {8, 2, 0, fffff800033fc33e}
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+10bb8 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800033fc33e, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c50e0
0000000000000008
CURRENT_IRQL: 2
FAULTING_IP:
hal!HalpDmaFreeMapRegisters+1a
fffff800`033fc33e 488b5a08 mov rbx,qword ptr [rdx+8]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880081e7800 -- (.trap 0xfffff880081e7800)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880081e7930 rbx=0000000000000000 rcx=fffffa8007685428
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033fc33e rsp=fffff880081e7990 rbp=0000000000000700
r8=fffff880081e7930 r9=fffff80003425c60 r10=0000000000000320
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
hal!HalpDmaFreeMapRegisters+0x1a:
fffff800`033fc33e 488b5a08 mov rbx,qword ptr [rdx+8] ds:00000000`00000008=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e8e469 to fffff80002e8ef00
STACK_TEXT:
fffff880`081e76b8 fffff800`02e8e469 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`081e76c0 fffff800`02e8d0e0 : 00000000`0000002e 00000000`00000000 00000000`00000000 fffffa80`04ceba20 : nt!KiBugCheckDispatch+0x69
fffff880`081e7800 fffff800`033fc33e : fffffa80`045a3030 fffffa80`045a3030 fffffa80`077088d0 00000000`00000001 : nt!KiPageFault+0x260
fffff880`081e7990 fffff800`033feb82 : fffffa80`076853b0 00000000`00000000 fffffa80`076853b0 00000000`000005dd : hal!HalpDmaFreeMapRegisters+0x1a
fffff880`081e79c0 fffff800`033fe825 : fffffa80`076913c0 00000000`00000710 00000000`00000000 fffffa80`04ab46d0 : hal!IoFreeMapRegisters+0x62
fffff880`081e7a30 fffff880`016708a1 : fffffa80`04ab4600 fffffa80`04ab44d0 fffffa80`07688010 fffffa80`045a3030 : hal!HalPutScatterGatherList+0xd5
fffff880`081e7a90 fffff880`04e56bb8 : fffff800`03032501 fffffa80`07688010 00000000`00000000 fffff800`03032501 : ndis!NdisMFreeNetBufferSGList+0x31
fffff880`081e7ad0 fffff800`03032501 : fffffa80`07688010 00000000`00000000 fffff800`03032501 00000000`00000000 : Rt64win7+0x10bb8
fffff880`081e7ad8 fffffa80`07688010 : 00000000`00000000 fffff800`03032501 00000000`00000000 fffff880`081e7c00 : nt!ExpWorkerSwapinMutex+0x21
fffff880`081e7ae0 00000000`00000000 : fffff800`03032501 00000000`00000000 fffff880`081e7c00 00000000`00000001 : 0xfffffa80`07688010
STACK_COMMAND: kb
FOLLOWUP_IP:
Rt64win7+10bb8
fffff880`04e56bb8 ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: Rt64win7+10bb8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Rt64win7
IMAGE_NAME: Rt64win7.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49a65b0d
FAILURE_BUCKET_ID: X64_0xA_Rt64win7+10bb8
BUCKET_ID: X64_0xA_Rt64win7+10bb8
Followup: MachineOwner
---------
Good luck!
~JK
Quote