RAAAAAAGE (BSoD problem - nnrnstdi)

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


Loading Dump File [C:\Windows\Minidump\Mini080908-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 Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x83800000 PsLoadedModuleList = 0x83911e10
Debug session time: Sat Aug  9 16:26:56.179 2008 (GMT-5)
System Uptime: 0 days 5:18:16.880
Loading Kernel Symbols
.............................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 8, 0}

Unable to load image \SystemRoot\System32\Drivers\nnrnstdi.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nnrnstdi.SYS
*** ERROR: Module load completed but symbols could not be loaded for nnrnstdi.SYS
Probably caused by : nnrnstdi.SYS ( nnrnstdi+20f4 )

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: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 839315ac
Unable to read MiSystemVaType memory at 839117e0
 00000000 

CURRENT_IRQL:  2

FAULTING_IP: 
+0
00000000 ??              ???

PROCESS_NAME:  msnmsgr.exe

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  840047d8 -- (.trap 0xffffffff840047d8)
ErrCode = 00000010
eax=00000016 ebx=84004964 ecx=901cc0bc edx=8767f0c6 esi=901cc0bc edi=84004964
eip=00000000 esp=8400484c ebp=84004888 iopl=0         nv up ei ng nz ac pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010296
00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from 00000000 to 8388fd84

FAILED_INSTRUCTION_ADDRESS: 
+0
00000000 ??              ???

STACK_TEXT:  
840047d8 00000000 badb0d00 8767f0c6 00000075 nt!KiTrap0E+0x2ac
WARNING: Frame IP not in any known module. Following frames may be wrong.
84004848 8767f0f4 00000000 00000016 84004964 0x0
840048c8 8d0222ce 8573c008 00000016 84004964 nnrnstdi+0x20f4
840049d4 8d3a9b97 00000000 84004a28 8d3a9c6f tdx!TdxEventReceiveMessagesTransportAddress+0x48e
840049ec 84004a28 8d3a9d9d 857127e0 84004a14 tcpip!InetFilterDatagramBySessionInformationAf+0x27
84004a28 8d3a7904 00000000 00000001 00000000 0x84004a28
84004a74 8d3a77e4 86cdc370 0085d000 84004ab0 tcpip!UdpReceiveDatagrams+0x118
84004a84 8d3a51b4 84004a98 c000023e 00000000 tcpip!UdpNlClientReceiveDatagrams+0x12
84004ab0 8d3a4f84 8d3f6d38 84004b0c c000023e tcpip!IppDeliverListToProtocol+0x49
84004ad0 8d3a4eb3 8d3f69c8 00000011 84004b0c tcpip!IppProcessDeliverList+0x2a
84004b24 8d3a056e 8d3f69c8 00000011 00000000 tcpip!IppReceiveHeaderBatch+0x1da
84004bb4 8d3a47da 8c8ac0e8 00000000 8b9d0b01 tcpip!IpFlcReceivePackets+0xc06
84004c30 8d3a40f3 8c8c8698 9676dd10 00000000 tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x6db
84004c58 841c30b0 8c8c8698 9676dd10 00000000 tcpip!FlReceiveNetBufferListChain+0x104
84004c8c 841b58a2 008f3c58 9676dd10 00000000 ndis!ndisMIndicateNetBufferListsToOpen+0xab
84004cb4 841b5819 00000000 83854203 86c74488 ndis!ndisIndicateSortedNetBufferLists+0x4a
84004e30 84117fc6 86c74488 00000000 00000000 ndis!ndisMDispatchReceiveNetBufferLists+0x129
84004e6c 84117df3 004e9c00 84004f5c 84004f38 ndis!ndisDoPeriodicReceivesIndication+0x170
84004e90 838a9b92 869f4c18 00000000 a62f7f0a ndis!ndisPeriodicReceivesTimer+0x48
84004f88 838a9321 00000000 00000000 0012add7 nt!KiTimerExpiration+0x659
84004ff4 83890ecd a2d5fa70 00905a4d 00000003 nt!KiRetireDpcList+0xba
84004ff8 a2d5fa70 00905a4d 00000003 00000004 nt!KiDispatchInterrupt+0x3d
84004ffc 00905a4d 00000003 00000004 0000ffff 0xa2d5fa70
84005000 00000000 00000004 0000ffff 000000b8 0x905a4d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nnrnstdi+20f4
8767f0f4 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nnrnstdi+20f4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nnrnstdi

IMAGE_NAME:  nnrnstdi.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  46698812

FAILURE_BUCKET_ID:  0xD1_CODE_AV_NULL_IP_nnrnstdi+20f4

BUCKET_ID:  0xD1_CODE_AV_NULL_IP_nnrnstdi+20f4

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

0: kd> .trap 0xffffffff840047d8
ErrCode = 00000010
eax=00000016 ebx=84004964 ecx=901cc0bc edx=8767f0c6 esi=901cc0bc edi=84004964
eip=00000000 esp=8400484c ebp=84004888 iopl=0         nv up ei ng nz ac pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010296
00000000 ??              ???