Overclock.net › Forums › Graphics Cards › NVIDIA › EVGA GTX 670 BF3 BSOD
New Posts  All Forums:Forum Nav:

EVGA GTX 670 BF3 BSOD - Page 2

post #11 of 36
5/18/12 at 9:35am
Quote:
Originally Posted by jojorockets52 View Post

I have the stock EVGA 670 (http://www.newegg.com/Product/Product.aspx?Item=N82E16814130782)

EVGA's cards seem to be having many problems, the SC edition in particular (Referencing their mini-recall and upping SC buyers to FTW).

Though the fact you're not crashing in others games is peculiar. Have you tried lowering settings in BF (Mainly AA and SSAO)?
Beast
(19 items)
  		  
CPUMotherboardGraphicsGraphics
i7 930 ASUS Rampage III Extreme EVGA GTX670 SC 4GB EVGA GTX670 SC 4GB 
RAMHard DriveHard DriveOptical Drive
Corsair Dominator GT OCZ Vertex 2 Wester Digital Caviar Black ASUS 24x  
CoolingOSMonitorMonitor
Corsair H50 Windows 7 Professional 64bit ASUS 25" LED-Backlit 1920x1080 ASUS 25" LED-Backlit 1920x1080 
MonitorKeyboardPowerCase
ASUS 25" LED-Backlit 1920x1080 Microsoft Sidewinder X4 Silverstone P-1000 Cooler Master ATCS840 
MouseAudioAudio
Razer Lechesis 4200DPi ASUS DGXonar 5.1 Beyerdynamic MMX 300 Headset 
View all
  hide details  
Reply
Beast
(19 items)
  		  
CPUMotherboardGraphicsGraphics
i7 930 ASUS Rampage III Extreme EVGA GTX670 SC 4GB EVGA GTX670 SC 4GB 
RAMHard DriveHard DriveOptical Drive
Corsair Dominator GT OCZ Vertex 2 Wester Digital Caviar Black ASUS 24x  
CoolingOSMonitorMonitor
Corsair H50 Windows 7 Professional 64bit ASUS 25" LED-Backlit 1920x1080 ASUS 25" LED-Backlit 1920x1080 
MonitorKeyboardPowerCase
ASUS 25" LED-Backlit 1920x1080 Microsoft Sidewinder X4 Silverstone P-1000 Cooler Master ATCS840 
MouseAudioAudio
Razer Lechesis 4200DPi ASUS DGXonar 5.1 Beyerdynamic MMX 300 Headset 
View all
  hide details  
Reply
post #12 of 36
5/18/12 at 11:04am
Would running FurMark at stock settings be a good choice to test if his card is unstable?

(Hoping someone more knowledgeable than me can answer that question)
Venom (Reborn)
(15 items)
  		  
CPUMotherboardGraphicsRAM
Core i7-2600K @ 4.6 GHz [1.33 vCore] [HT ON] ASUS P8P67 PRO (REV 3.1) EVGA GTX470 8 GB [2x4 GB] G.Skill Ripjaws X Series 1600 CL 9 
Hard DriveHard DriveHard DriveOptical Drive
Crucial C300 64 GB Western Digital 640 GB Samsung 2 TB Lite-On DVD Burner 
OSMonitorPowerCase
Windows 7 x64 Ultimate, Ubuntu 10.04, Arch Acer 22" 1680x1050, Dell 19" Corsair TX650 NZXT Tempest 
MouseMouse Pad
Logitech G500 Some random cloth thing 
View all
  hide details  
Reply
Venom (Reborn)
(15 items)
  		  
CPUMotherboardGraphicsRAM
Core i7-2600K @ 4.6 GHz [1.33 vCore] [HT ON] ASUS P8P67 PRO (REV 3.1) EVGA GTX470 8 GB [2x4 GB] G.Skill Ripjaws X Series 1600 CL 9 
Hard DriveHard DriveHard DriveOptical Drive
Crucial C300 64 GB Western Digital 640 GB Samsung 2 TB Lite-On DVD Burner 
OSMonitorPowerCase
Windows 7 x64 Ultimate, Ubuntu 10.04, Arch Acer 22" 1680x1050, Dell 19" Corsair TX650 NZXT Tempest 
MouseMouse Pad
Logitech G500 Some random cloth thing 
View all
  hide details  
Reply
post #13 of 36
5/18/12 at 12:21pm
Thread Starter 
What's weird is that I can completely use 100% GPU on Crysis 2 without crashing, but as soon as I start gameplay in BF3 it crashes.
Reply
Reply
post #14 of 36
5/18/12 at 1:11pm
Hi smile.gif

Four dumps, 2 dumps have the same culprit, the other two have different culprits. All driver culprits.

First off, SP1 is not installed. Do that right away: http://windows.microsoft.com/en-US/windows7/install-windows-7-service-pack-1

1st dump: 1e bugcheck with culprit as danew.sys (New DeathAdder Mouse driver). Update here. If after updating you're still having issues with this driver, uninstall Razer's drivers, unplug the mouse, and then replug it so it installs the generic Windows drivers.

2nd dump: 116 TDR bugcheck with VirtuWDDM.sys as the culprit (VIRTU LucidInterop WDDM Driver by LucidLogix). Update here. If you're having issue after updating the driver, removing the device using this driver / software.

3rd dump:
2nd dump: 116 TDR bugcheck with VirtuWDDM.sys as the culprit (VIRTU LucidInterop WDDM Driver by LucidLogix). Update here. If you're having issue after updating the driver, removing the device using this driver / software.

4th dump: d1 IRQL bugcheck pointing to the culprit tdx.sys (core windows driver, likely wasn't the actual cause, but what crashed).

After looking at your loaded drivers list:

1. dtsoftbus01.sys is listed, this is the Daemon Tools driver. Daemon Tools is notorious for causing BSODs in the W7 environment, so please fully uninstall Daemon Tools. Optional programs that do the same thing are PowerISO, ImgBurn, etc.

Looks like that's it for now, keep me updated when you've done everything I've recommended smile.gif

Dump(s) for reference:

Warning: Spoiler! (Click to show)
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Cardbox\Downloads\Debugging\051612-20077-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0345c000 PsLoadedModuleList = 0xfffff800`03699e50
Debug session time: Wed May 16 17:48:33.069 2012 (UTC - 4:00)
System Uptime: 1 days 13:54:35.975
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 \SystemRoot\system32\drivers\danew.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for danew.sys
*** ERROR: Module load completed but symbols could not be loaded for danew.sys
Probably caused by : danew.sys ( danew+6da )

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

0: 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: 
+3231323165653330
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800034c5c2e to fffff800034cded0

STACK_TEXT:  
fffff800`00b9bc58 fffff800`034c5c2e : 00000000`00000000 00000000`00000014 fffff800`00b9c460 fffff800`034fae28 : nt!KeBugCheck
fffff800`00b9bc60 fffff800`034f3bed : fffff800`036dac24 fffff800`03613a3c fffff800`0345c000 fffff800`00b9c3c0 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9bc90 fffff800`034fb250 : fffff800`0361bb5c fffff800`00b9bd08 fffff800`00b9c3c0 fffff800`0345c000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9bcc0 fffff800`034fc82e : fffff800`00b9c3c0 fffff800`00b9c460 fffffa80`00000001 fffff800`00b9cc18 : nt!RtlDispatchException+0x410
fffff800`00b9c3a0 fffff800`0352a7c2 : fffffa80`0d2c72e0 00000000`00000000 00000000`00000000 fffff880`08006f3d : nt!RtlRaiseStatus+0x4e
fffff800`00b9c940 fffff880`101576da : fffffa80`0e690590 fffff800`00000000 fffffa80`0a829c50 fffff880`0802dd00 : nt! ?? ::FNODOBFM::`string'+0xf63c
fffff800`00b9c9c0 fffffa80`0e690590 : fffff800`00000000 fffffa80`0a829c50 fffff880`0802dd00 fffffa80`0a829ee0 : danew+0x6da
fffff800`00b9c9c8 fffff800`00000000 : fffffa80`0a829c50 fffff880`0802dd00 fffffa80`0a829ee0 fffff880`0802d0d8 : 0xfffffa80`0e690590
fffff800`00b9c9d0 fffffa80`0a829c50 : fffff880`0802dd00 fffffa80`0a829ee0 fffff880`0802d0d8 fffffa80`0a932c60 : 0xfffff800`00000000
fffff800`00b9c9d8 fffff880`0802dd00 : fffffa80`0a829ee0 fffff880`0802d0d8 fffffa80`0a932c60 fffff800`034d0516 : 0xfffffa80`0a829c50
fffff800`00b9c9e0 fffff880`099d0300 : 00000000`000007ff 00000000`00000050 fffffa80`0e6905e0 00000000`00000000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x3c
fffff800`00b9ca20 fffffa80`0a829a10 : fffffa80`0a8379f0 fffffa80`0d146010 00000000`00000002 fffffa80`0d2c72e0 : usbehci!EHCI_sMode_PollEndpointSlot+0x388
fffff800`00b9cab0 fffffa80`0a8379f0 : fffffa80`0d146010 00000000`00000002 fffffa80`0d2c72e0 fffffa80`09edd050 : 0xfffffa80`0a829a10
fffff800`00b9cab8 fffffa80`0d146010 : 00000000`00000002 fffffa80`0d2c72e0 fffffa80`09edd050 fffff880`080135d9 : 0xfffffa80`0a8379f0
fffff800`00b9cac0 00000000`00000002 : fffffa80`0d2c72e0 fffffa80`09edd050 fffff880`080135d9 fffffa80`09edd050 : 0xfffffa80`0d146010
fffff800`00b9cac8 fffffa80`0d2c72e0 : fffffa80`09edd050 fffff880`080135d9 fffffa80`09edd050 fffffa80`0a7ab200 : 0x2
fffff800`00b9cad0 fffffa80`09edd050 : fffff880`080135d9 fffffa80`09edd050 fffffa80`0a7ab200 00000000`00000000 : 0xfffffa80`0d2c72e0
fffff800`00b9cad8 fffff880`080135d9 : fffffa80`09edd050 fffffa80`0a7ab200 00000000`00000000 00000000`00000000 : 0xfffffa80`09edd050
fffff800`00b9cae0 fffff880`08013ab7 : fffffa80`0d2c7202 fffffa80`0a932c60 00000000`ffffffff fffffa80`09eddea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff800`00b9cbc0 fffff880`0801164f : fffffa80`09eddea8 fffffa80`09edd1a0 fffffa80`09ede040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`00b9cc20 fffff880`08002f89 : fffffa80`09edd050 00000000`00000000 fffffa80`09edde02 fffffa80`09eddea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`00b9cc60 fffff800`034d95dc : fffff800`03646e80 fffffa80`09eddea8 fffffa80`09eddec0 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00b9cc90 fffff800`034d66fa : fffff800`03646e80 fffff800`03654c40 00000000`00000000 fffff880`08002db0 : nt!KiRetireDpcList+0x1bc
fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
danew+6da
fffff880`101576da ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  danew+6da

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: danew

IMAGE_NAME:  danew.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ba87dcd

FAILURE_BUCKET_ID:  X64_0x1E_0_danew+6da

BUCKET_ID:  X64_0x1E_0_danew+6da

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


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Cardbox\Downloads\Debugging\051612-16489-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03853000 PsLoadedModuleList = 0xfffff800`03a90e50
Debug session time: Wed May 16 23:46:44.240 2012 (UTC - 4:00)
System Uptime: 0 days 0:06:24.552
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800ceb5010, fffff8800762e51c, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\VirtuWDDM.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VirtuWDDM.sys
*** ERROR: Module load completed but symbols could not be loaded for VirtuWDDM.sys
Probably caused by : VirtuWDDM.sys ( VirtuWDDM+851c )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800ceb5010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800762e51c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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


FAULTING_IP: 
VirtuWDDM+851c
fffff880`0762e51c 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`061feb48 fffff880`078ebcbc : 00000000`00000116 fffffa80`0ceb5010 fffff880`0762e51c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`061feb50 fffff880`078bf867 : fffff880`0762e51c fffffa80`0a834000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`061feb90 fffff880`078ebacb : 00000000`ffffd87b ffffffff`fffe7960 fffffa80`0ceb5010 fffff880`079badc0 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`061fec40 fffff880`079baec1 : fffffa80`0b118c10 00000000`00000080 00000000`00000000 fffffa80`0a82c410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`061fecc0 fffff800`03b68166 : 00000000`02cf147b fffffa80`090c1b60 fffffa80`06d1e5f0 fffffa80`090c1b60 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`061fed00 fffff800`038a3486 : fffff800`03a3de80 fffffa80`090c1b60 fffff800`03a4bc40 fffff880`0124d534 : nt!PspSystemThreadStartup+0x5a
fffff880`061fed40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
VirtuWDDM+851c
fffff880`0762e51c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  VirtuWDDM+851c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: VirtuWDDM

IMAGE_NAME:  VirtuWDDM.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dfe17bc

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_VirtuWDDM.sys

BUCKET_ID:  X64_0x116_IMAGE_VirtuWDDM.sys

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


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Cardbox\Downloads\Debugging\042112-18766-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0341c000 PsLoadedModuleList = 0xfffff800`03659e50
Debug session time: Sat Apr 21 04:45:23.574 2012 (UTC - 4:00)
System Uptime: 1 days 10:52:07.916
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {28, 2, 0, fffff88002da3245}

Probably caused by : tdx.sys ( tdx!TdxEventReceiveMessagesTransportAddress+235 )

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

3: 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: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88002da3245, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036c40e0
 0000000000000028 

CURRENT_IRQL:  2

FAULTING_IP: 
tdx!TdxEventReceiveMessagesTransportAddress+235
fffff880`02da3245 8b4628          mov     eax,dword ptr [rsi+28h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880250ae710 -- (.trap 0xfffff880250ae710)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880250ae9b8 rbx=0000000000000000 rcx=fffff880250ae9c6
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002da3245 rsp=fffff880250ae8a0 rbp=fffffa8008058100
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000002
r11=fffff880250ae9b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
tdx!TdxEventReceiveMessagesTransportAddress+0x235:
fffff880`02da3245 8b4628          mov     eax,dword ptr [rsi+28h] ds:00000000`00000028=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000348d469 to fffff8000348df00

STACK_TEXT:  
fffff880`250ae5c8 fffff800`0348d469 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`250ae5d0 fffff800`0348c0e0 : 00000000`00000000 fffffa80`0b38b130 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`250ae710 fffff880`02da3245 : fffffa80`0b38b130 fffff880`01825571 fffff880`250aeb08 fffffa80`07acfd70 : nt!KiPageFault+0x260
fffff880`250ae8a0 fffff880`018413c5 : fffffa80`07acfd70 fffffa80`0b377780 fffffa80`07acfd70 fffffa80`07acfd70 : tdx!TdxEventReceiveMessagesTransportAddress+0x235
fffff880`250aea90 fffff880`0184179d : fffffa80`00000018 fffffa80`07acfd70 fffffa80`00000000 fffffa80`0a4fbc2c : tcpip!UdpDeliverDatagrams+0x155
fffff880`250aec20 fffff880`0185d427 : fffffa80`09a6ee30 ffff0000`249c9ba7 00000000`00000002 00060000`08000000 : tcpip!UdpReceiveDatagrams+0x1ed
fffff880`250aed10 fffff880`0185d499 : fffff880`250aee90 fffff880`0196d9a0 fffff880`250aeea0 fffff880`01967101 : tcpip!IppDeliverListToProtocol+0xf7
fffff880`250aedd0 fffff880`0185d990 : fffff880`0196d9a0 fffffa80`09da54a0 00000000`00000011 fffff880`250aee90 : tcpip!IppProcessDeliverList+0x59
fffff880`250aee40 fffff880`0185c821 : 00000000`00000001 fffffa80`09a6a000 fffff880`0196d9a0 00000000`0a3f0001 : tcpip!IppReceiveHeaderBatch+0x231
fffff880`250aef20 fffff880`0187ce94 : fffffa80`09ef9870 00000000`00000000 fffffa80`0a3f0001 00000000`00000001 : tcpip!IpFlcReceivePackets+0x651
fffff880`250af120 fffff880`01874682 : fffffa80`09ef9870 fffffa80`09e75bb0 fffffa80`0b330011 00000000`00000000 : tcpip!IpFlcReceivePreValidatedPackets+0x944
fffff880`250af280 fffff800`0349d64a : 00000000`00000000 fffff880`250aa000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xa2
fffff880`250af2d0 fffff880`018740e2 : fffff880`018745e0 fffff880`250af3e0 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`250af3b0 fffff880`0157a0eb : fffffa80`09e75470 00000000`00000000 fffffa80`09dfb1a0 fffff880`0157a11e : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`250af420 fffff880`01543fc6 : 000a0100`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`250af490 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tdx!TdxEventReceiveMessagesTransportAddress+235
fffff880`02da3245 8b4628          mov     eax,dword ptr [rsi+28h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  tdx!TdxEventReceiveMessagesTransportAddress+235

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tdx

IMAGE_NAME:  tdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc16b

FAILURE_BUCKET_ID:  X64_0xD1_tdx!TdxEventReceiveMessagesTransportAddress+235

BUCKET_ID:  X64_0xD1_tdx!TdxEventReceiveMessagesTransportAddress+235

Followup: MachineOwner
--------

Edited by pjBSOD - 5/18/12 at 1:53pm
Reply
Reply
post #15 of 36
5/18/12 at 1:42pm
Holy wall of text batman. Any way you could put that in spoilers? Nice work.
Venom (Reborn)
(15 items)
  		  
CPUMotherboardGraphicsRAM
Core i7-2600K @ 4.6 GHz [1.33 vCore] [HT ON] ASUS P8P67 PRO (REV 3.1) EVGA GTX470 8 GB [2x4 GB] G.Skill Ripjaws X Series 1600 CL 9 
Hard DriveHard DriveHard DriveOptical Drive
Crucial C300 64 GB Western Digital 640 GB Samsung 2 TB Lite-On DVD Burner 
OSMonitorPowerCase
Windows 7 x64 Ultimate, Ubuntu 10.04, Arch Acer 22" 1680x1050, Dell 19" Corsair TX650 NZXT Tempest 
MouseMouse Pad
Logitech G500 Some random cloth thing 
View all
  hide details  
Reply
Venom (Reborn)
(15 items)
  		  
CPUMotherboardGraphicsRAM
Core i7-2600K @ 4.6 GHz [1.33 vCore] [HT ON] ASUS P8P67 PRO (REV 3.1) EVGA GTX470 8 GB [2x4 GB] G.Skill Ripjaws X Series 1600 CL 9 
Hard DriveHard DriveHard DriveOptical Drive
Crucial C300 64 GB Western Digital 640 GB Samsung 2 TB Lite-On DVD Burner 
OSMonitorPowerCase
Windows 7 x64 Ultimate, Ubuntu 10.04, Arch Acer 22" 1680x1050, Dell 19" Corsair TX650 NZXT Tempest 
MouseMouse Pad
Logitech G500 Some random cloth thing 
View all
  hide details  
Reply
post #16 of 36
5/18/12 at 1:45pm
Not a bad idea, actually... I'll use spoiler tags for dump references instead of code tags now, nice suggestion thumb.gif
Reply
Reply
post #17 of 36
5/18/12 at 1:48pm
Possible to embed code in spoilers? That way you get the color, without looking like a dictionary threw up on my screen
Venom (Reborn)
(15 items)
  		  
CPUMotherboardGraphicsRAM
Core i7-2600K @ 4.6 GHz [1.33 vCore] [HT ON] ASUS P8P67 PRO (REV 3.1) EVGA GTX470 8 GB [2x4 GB] G.Skill Ripjaws X Series 1600 CL 9 
Hard DriveHard DriveHard DriveOptical Drive
Crucial C300 64 GB Western Digital 640 GB Samsung 2 TB Lite-On DVD Burner 
OSMonitorPowerCase
Windows 7 x64 Ultimate, Ubuntu 10.04, Arch Acer 22" 1680x1050, Dell 19" Corsair TX650 NZXT Tempest 
MouseMouse Pad
Logitech G500 Some random cloth thing 
View all
  hide details  
Reply
Venom (Reborn)
(15 items)
  		  
CPUMotherboardGraphicsRAM
Core i7-2600K @ 4.6 GHz [1.33 vCore] [HT ON] ASUS P8P67 PRO (REV 3.1) EVGA GTX470 8 GB [2x4 GB] G.Skill Ripjaws X Series 1600 CL 9 
Hard DriveHard DriveHard DriveOptical Drive
Crucial C300 64 GB Western Digital 640 GB Samsung 2 TB Lite-On DVD Burner 
OSMonitorPowerCase
Windows 7 x64 Ultimate, Ubuntu 10.04, Arch Acer 22" 1680x1050, Dell 19" Corsair TX650 NZXT Tempest 
MouseMouse Pad
Logitech G500 Some random cloth thing 
View all
  hide details  
Reply
post #18 of 36
5/18/12 at 1:50pm
Thread Starter 
Thanks man I really appreciate it. I'll update all those drivers and post back with the results. Is there any place to learn how to read the dumps. It seems like it is a good skill to have.
Reply
Reply
post #19 of 36
5/18/12 at 1:52pm
Quote:
Originally Posted by jojorockets52 View Post

Thanks man I really appreciate it. I'll update all those drivers and post back with the results. Is there any place to learn how to read the dumps. It seems like it is a good skill to have.

I've written a guide for basic analysis skills, the link is in my signature smile.gif

If you'd like to really get good at it and learn how to extensively read memory stacks and other things, look into a book called Windows Internals. I read it every night before bed, great read! Part 2 is coming soon, it will contain much more crash dump analysis information.
Quote:
Originally Posted by Raptor_Jesus View Post

Possible to embed code in spoilers? That way you get the color, without looking like a dictionary threw up on my screen

Just added code tags inside spoiler and it worked thumb.gif
Edited by pjBSOD - 5/18/12 at 1:54pm
Reply
Reply
post #20 of 36
5/18/12 at 10:54pm
Thread Starter 
Well I downloaded/installed all the windows updates and downloaded the new Virtu drivers and got this error:


338
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: NVIDIA
Overclock.net › Forums › Graphics Cards › NVIDIA › EVGA GTX 670 BF3 BSOD