I have Vista installed on my box at home and occasionally I will get a BSOD
and restart of the system. I have tried running the DUMP through the WINDBG
application but I am not that familiar with what I am supposed to be looking
for. I will post the output along with this post.
Start WINDBG Output:
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: C:\Windows\Symbols
Executable search path is:
Windows Vista Kernel Version 6000 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Kernel base = 0x82000000 PsLoadedModuleList = 0x82111db0
Debug session time: Fri Apr 6 19:59:08.126 2007 (GMT-4)
System Uptime: 0 days 1:11:03.052
Loading Kernel Symbols
.................................................. .
.................................................. .
.................................................. . ........
Loading User Symbols
Use !analyze -v to get detailed debugging information.
BugCheck A, {9275a540, 2, 0, 8208355e}
*** ERROR: Module load completed but symbols could not be loaded for
getnd6v.sys
Probably caused by : getnd6v.sys ( getnd6v+1369 )
Followup: MachineOwner
---------
kd> !sym noisy
noisy mode - symbol prompts on
kd> .reload
DBGHELP: C:\Windows\Symbols\ntkrpamp.pdb - file not found
DBGHELP: C:\Windows\Symbols\symbols\exe\ntkrpamp.pdb - file not found
DBGHELP: nt - public symbols
C:\Windows\Symbols\exe\ntkrpamp.pdb
Loading Kernel Symbols
.................................................. .
.................................................. .
.................................................. . ........
Loading User Symbols
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: 9275a540, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8208355e, address which referenced memory
Debugging Details:
------------------
DBGHELP: C:\Windows\Symbols\GETND6V.pdb - file not found
DBGHELP: C:\Windows\Symbols\symbols\sys\GETND6V.pdb - file not found
DBGHELP: C:\Windows\Symbols\sys\GETND6V.pdb - file not found
DBGHELP: d:\project\vt3119\ndis6\1.23-0030\src\i386\GETND6V.pdb - file not
found
*** ERROR: Module load completed but symbols could not be loaded for
getnd6v.sys
DBGHELP: getnd6v - no symbols loaded
DBGHELP: C:\Windows\Symbols\ndis.pdb - file not found
DBGHELP: C:\Windows\Symbols\symbols\sys\ndis.pdb - file not found
DBGHELP: ndis - public symbols
C:\Windows\Symbols\sys\ndis.pdb
DBGHELP: C:\Windows\Symbols\pacer.pdb - file not found
DBGHELP: C:\Windows\Symbols\symbols\sys\pacer.pdb - file not found
DBGHELP: pacer - public symbols
C:\Windows\Symbols\sys\pacer.pdb
DBGHELP: C:\Windows\Symbols\tcpip.pdb - file not found
DBGHELP: C:\Windows\Symbols\symbols\sys\tcpip.pdb - file not found
DBGHELP: tcpip - public symbols
C:\Windows\Symbols\sys\tcpip.pdb
I have run several commands that have appeared on several other posts that I
have seen on the web while searching for a possible solution. When the system
reboots I submit the error to Microsoft and the response that I received told
me that it was being caused by my video card. The error returned was "THREAD
STUCK IN DEVICE". I have an Nvidia GEForce FX 5700 LE. I have tried to get
the latest drivers for vista and have installed. Hopefully someone can shed
some light into the possible cause. Thanks in advance.
mreyeros wrote:
> I have Vista installed on my box at home and occasionally I will get
> a BSOD and restart of the system. I have tried running the DUMP
> through the WINDBG application but I am not that familiar with what I
> am supposed to be looking for. I will post the output along with this
> post.
>
> Start WINDBG Output:
>
>
> Microsoft (R) Windows Debugger Version 6.6.0007.5
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [D:\MEMORY.DMP]
> Kernel Summary Dump File: Only kernel address space is available
>
> Symbol search path is: C:\Windows\Symbols
> Executable search path is:
> Windows Vista Kernel Version 6000 UP Free x86 compatible
> Product: WinNt, suite: TerminalServer SingleUserTS
> Built by: 6000.16386.x86fre.vista_rtm.061101-2205
> Kernel base = 0x82000000 PsLoadedModuleList = 0x82111db0
> Debug session time: Fri Apr 6 19:59:08.126 2007 (GMT-4)
> System Uptime: 0 days 1:11:03.052
> Loading Kernel Symbols
> ..................................................
> ..................................................
> .................................................. ........
> Loading User Symbols
>
> Loading unloaded module list
> .........
> **************************************************
> *****************************
> * *
> * Bugcheck Analysis *
> * *
> **************************************************
> *****************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck A, {9275a540, 2, 0, 8208355e}
>
> *** ERROR: Module load completed but symbols could not be loaded for
> getnd6v.sys
> Probably caused by : getnd6v.sys ( getnd6v+1369 )
>
> Followup: MachineOwner
> ---------
>
> kd> !sym noisy
> noisy mode - symbol prompts on
> kd> .reload
> DBGHELP: C:\Windows\Symbols\ntkrpamp.pdb - file not found
> DBGHELP: C:\Windows\Symbols\symbols\exe\ntkrpamp.pdb - file not found
> DBGHELP: nt - public symbols
> C:\Windows\Symbols\exe\ntkrpamp.pdb
> Loading Kernel Symbols
> ..................................................
> ..................................................
> .................................................. ........
> Loading User Symbols
>
> Loading unloaded module list
> .........
> 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: 9275a540, memory referenced
> Arg2: 00000002, IRQL
> Arg3: 00000000, value 0 = read operation, 1 = write operation
> Arg4: 8208355e, address which referenced memory
>
> Debugging Details:
> ------------------
>
> DBGHELP: C:\Windows\Symbols\GETND6V.pdb - file not found
> DBGHELP: C:\Windows\Symbols\symbols\sys\GETND6V.pdb - file not found
> DBGHELP: C:\Windows\Symbols\sys\GETND6V.pdb - file not found
> DBGHELP: d:\project\vt3119\ndis6\1.23-0030\src\i386\GETND6V.pdb -
> file not found
> *** ERROR: Module load completed but symbols could not be loaded for
> getnd6v.sys
> DBGHELP: getnd6v - no symbols loaded
> DBGHELP: C:\Windows\Symbols\ndis.pdb - file not found
> DBGHELP: C:\Windows\Symbols\symbols\sys\ndis.pdb - file not found
> DBGHELP: ndis - public symbols
> C:\Windows\Symbols\sys\ndis.pdb
> DBGHELP: C:\Windows\Symbols\pacer.pdb - file not found
> DBGHELP: C:\Windows\Symbols\symbols\sys\pacer.pdb - file not found
> DBGHELP: pacer - public symbols
> C:\Windows\Symbols\sys\pacer.pdb
> DBGHELP: C:\Windows\Symbols\tcpip.pdb - file not found
> DBGHELP: C:\Windows\Symbols\symbols\sys\tcpip.pdb - file not found
> DBGHELP: tcpip - public symbols
> C:\Windows\Symbols\sys\tcpip.pdb
>
> READ_ADDRESS: 9275a540
>
> CURRENT_IRQL: 2
>
> FAULTING_IP:
> nt!memcpy+9e
> 8208355e 8a06 mov al,byte ptr [esi]
>
> DEFAULT_BUCKET_ID: VISTA_RC
>
> BUGCHECK_STR: 0xA
>
> PROCESS_NAME: Idle
>
> TRAP_FRAME: 820f0f6c -- (.trap ffffffff820f0f6c)
> ErrCode = 00000000
> eax=00000002 ebx=00000b28 ecx=00000056 edx=00000002 esi=9275a540
> edi=8669a15a eip=8208355e esp=820f0fe0 ebp=820f0fe8 iopl=0 nv up ei
> pl nz na po nc
> cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
> nt!memcpy+0x9e:
> 8208355e 8a06 mov al,byte ptr [esi] ds:0023:9275a540=??
> Resetting default scope
>
> LAST_CONTROL_TRANSFER: from 8208355e to 8208fc44
>
> STACK_TEXT:
> 820f0f6c 8208355e badb0d00 00000002 820f105c nt!KiTrap0E+0x2ac
> 820f0fe8 8324e369 8669a15a 9275a540 00000058 nt!memcpy+0x9e
> WARNING: Stack unwind information not available. Following frames may
> be wrong.
> 820f1008 83255030 851ad630 00000000 8669a15a getnd6v+0x1369
> 820f10d0 83255a3d 851ad630 851ad5b0 a5c03000 getnd6v+0x8030
> 820f1100 83255b61 80698000 8640b0e8 83255ad0 getnd6v+0x8a3d
> 820f111c 8072a521 00000000 851ad5b0 00000000 getnd6v+0x8b61
> 820f1144 80666ae4 8640b0e8 851ad5b0 00000000
> ndis!ndisMSendNBLToMiniport+0xb4 820f1164 80666b98 851ad5b0 851ad5b0
> 00000000 ndis!ndisFilterSendNetBufferLists+0x8b
> 820f117c 8a961e20 8a505760 851ad5b0 00000000
> ndis!NdisFSendNetBufferLists+0x18 820f11f8 80666b76 8a4e8008 851ad5b0
> 00000000 pacer!PcFilterSendNetBufferLists+0x232
> 820f1214 8072a64a 851ad5b0 851ad5b0 00000000
> ndis!ndisSendNBLToFilter+0x87 820f1238 8a68b453 862b7650 851ad5b0
> 00000000 ndis!NdisSendNetBufferLists+0x4f 820f12d0 8a689935 8a4f1008
> 00000000 820f1454 tcpip!FlSendPackets+0x4b7 820f1310 8a68af6a
> 8a6d49c8 00000000 00000000 tcpip!IppFragmentPackets+0x203 820f1348
> 8a68a601 8a6d49c8 820f1454 8a6d49c8
> tcpip!IppDispatchSendPacketHelper+0x259 820f13e0 8a689e01 000f1454
> 820f1590 850ea540 tcpip!IppPacketizeDatagrams+0x7ea 820f1538 8a68c2ea
> 00000000 00000007 8a6d49c8 tcpip!IppSendDatagramsCommon+0x4ab
> 820f1558 8a65b5d2 8ac93968 820f1570 fffffffc
> tcpip!IpNlpSendDatagrams+0x4b 820f15e0 8a65b52e 8ac93968 820f16c8
> 8a4fc448 tcpip!IppSlowSendDatagram+0x3e 820f1630 8a68d21b 8ac93968
> 00000001 820f16c8 tcpip!IpNlpFastSendDatagram+0x3fd 820f171c 8a68041e
> 93d28160 00000002 00008b00 tcpip!TcpTcbSend+0x48b 820f1748 8a68c5d7
> 00000001 00000000 820f182c tcpip!TcpFlushDelay+0xdb 820f1778 8a6913e4
> 8ac93f80 8ac8e000 8ac8e010 tcpip!TcpPreValidatedReceive+0x2bf
> 820f1794 8a69160b 8ac93f80 8ac8e000 820f17d0 tcpip!TcpReceive+0x32
> 820f17a4 8a683124 820f17b8 c000023e 00000000
> tcpip!TcpNlClientReceiveDatagrams+0x12
> 820f17d0 8a682ef4 8a6d4bac 820f182c c000023e
> tcpip!IppDeliverListToProtocol+0x49
> 820f17f0 8a682e23 8a6d49c8 00000006 820f182c
> tcpip!IppProcessDeliverList+0x2a 820f1844 8a67e4de 8a6d49c8 00000006
> 00000000 tcpip!IppReceiveHeaderBatch+0x1da 820f18d4 8a68274a 8a4e8460
> 00000000 94d4b001 tcpip!IpFlcReceivePackets+0xc06 820f1950 8a682063
> 8a4f1008 86430518 00000000
> tcpip!FlpReceiveNonPreValidatedNetBufferListChain+ 0x6db 820f1978
> 8072a0b0 8a4f1008 86430518 00000000
> tcpip!FlReceiveNetBufferListChain+0x104 820f19ac 8071cd7d 002b7650
> 86430518 00000000 ndis!ndisMIndicateNetBufferListsToOpen+0xab
> 820f19dc 8071c822 00000001 862b7650 806644d1
> ndis!ndisIndicateAllNetBufferLists+0x56
> 820f1b5c 80664526 8640b0e8 00000000 00000000
> ndis!ndisMDispatchReceiveNetBufferLists+0x132
> 820f1b78 8071c476 8640b0e8 86430518 00000000
> ndis!ndisMTopReceiveNetBufferLists+0x2c
> 820f1b94 806644f1 8640b0e8 86430518 00000000
> ndis!ndisMIndicateReceiveNetBufferListsInternal+0x 27
> 820f1bb0 8324e67e 8640b0e8 86430518 00000000
> ndis!NdisMIndicateReceiveNetBufferLists+0x20
> 820f1c10 8324e990 00000001 8324e8e8 866005f0 getnd6v+0x167e
> 820f1ca4 8071c086 8667e000 00000000 00000000 getnd6v+0x1990
> 820f1cc8 80664252 86600604 00000000 00000000 ndis!ndisMiniportDpc+0x81
> 820f1ce8 820a93ae 86600604 866005f0 00000000
> ndis!ndisInterruptDpc+0x8b 820f1d50 820912ae 00000000 0000000e
> 00000000 nt!KiRetireDpcList+0x147 820f1d54 00000000 0000000e 00000000
> 00000000 nt!KiIdleLoop+0x46
>
>
> STACK_COMMAND: kb
>
> FOLLOWUP_IP:
> getnd6v+1369
> 8324e369 8b4518 mov eax,dword ptr [ebp+18h]
>
> SYMBOL_STACK_INDEX: 2
>
> FOLLOWUP_NAME: MachineOwner
>
> MODULE_NAME: getnd6v
>
> IMAGE_NAME: getnd6v.sys
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 457ebd20
>
> SYMBOL_NAME: getnd6v+1369
>
> FAILURE_BUCKET_ID: 0xA_getnd6v+1369
>
> BUCKET_ID: 0xA_getnd6v+1369
>
> Followup: MachineOwner
> ---------
>
> kd> kb
> ChildEBP RetAddr Args to Child
> 820f0f6c 8208355e badb0d00 00000002 820f105c nt!KiTrap0E+0x2ac
> 820f0fe8 8324e369 8669a15a 9275a540 00000058 nt!memcpy+0x9e
> WARNING: Stack unwind information not available. Following frames may
> be wrong.
> 820f1008 83255030 851ad630 00000000 8669a15a getnd6v+0x1369
> 820f10d0 83255a3d 851ad630 851ad5b0 a5c03000 getnd6v+0x8030
> 820f1100 83255b61 80698000 8640b0e8 83255ad0 getnd6v+0x8a3d
> 820f111c 8072a521 00000000 851ad5b0 00000000 getnd6v+0x8b61
> 820f1144 80666ae4 8640b0e8 851ad5b0 00000000
> ndis!ndisMSendNBLToMiniport+0xb4 820f1164 80666b98 851ad5b0 851ad5b0
> 00000000 ndis!ndisFilterSendNetBufferLists+0x8b
> 820f117c 8a961e20 8a505760 851ad5b0 00000000
> ndis!NdisFSendNetBufferLists+0x18 820f11f8 80666b76 8a4e8008 851ad5b0
> 00000000 pacer!PcFilterSendNetBufferLists+0x232
> 820f1214 8072a64a 851ad5b0 851ad5b0 00000000
> ndis!ndisSendNBLToFilter+0x87 820f1238 8a68b453 862b7650 851ad5b0
> 00000000 ndis!NdisSendNetBufferLists+0x4f 820f12d0 8a689935 8a4f1008
> 00000000 820f1454 tcpip!FlSendPackets+0x4b7 820f1310 8a68af6a
> 8a6d49c8 00000000 00000000 tcpip!IppFragmentPackets+0x203 820f1348
> 8a68a601 8a6d49c8 820f1454 8a6d49c8
> tcpip!IppDispatchSendPacketHelper+0x259 820f13e0 8a689e01 000f1454
> 820f1590 850ea540 tcpip!IppPacketizeDatagrams+0x7ea 820f1538 8a68c2ea
> 00000000 00000007 8a6d49c8 tcpip!IppSendDatagramsCommon+0x4ab
> 820f1558 8a65b5d2 8ac93968 820f1570 fffffffc
> tcpip!IpNlpSendDatagrams+0x4b 820f15e0 8a65b52e 8ac93968 820f16c8
> 8a4fc448 tcpip!IppSlowSendDatagram+0x3e 820f1630 8a68d21b 8ac93968
> 00000001 820f16c8 tcpip!IpNlpFastSendDatagram+0x3fd
>
>
>
> I have run several commands that have appeared on several other posts
> that I have seen on the web while searching for a possible solution.
> When the system reboots I submit the error to Microsoft and the
> response that I received told me that it was being caused by my video
> card. The error returned was "THREAD STUCK IN DEVICE". I have an
> Nvidia GEForce FX 5700 LE. I have tried to get the latest drivers for
> vista and have installed. Hopefully someone can shed some light into
> the possible cause. Thanks in advance.
Even though you may have the latest Vista compatible drivers for your card,
they appear to still be in beta. They have a bug reporting site: http://www.nvidia.com/vistaqualityassurance.
These issues are not likely to be resolved until nVidia is able to produce
fully stable drivers and get them out of past the beta test stage. Your
best bet for help is probably from them.
VISTA BSOD - Please Help!!!!! 
Linear Mode
