Nvidia 680i Mobo BSOD Crash Dumps - Can't seem to track it down!!

I'd REALLY appreciate any help determinin if this is a hardware issue or not. Due to the random nature and the fact they just started coming out of the blue, I have a feeling it might be. Here's my dumps...

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 805452b0, The address that the exception occurred at
Arg3: afeeb548, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

FAULTING_IP:
nt!WmiTraceMessageVa+217
805452b0 f3ab rep stos dword ptr es:[edi]

TRAP_FRAME: afeeb548 -- (.trap ffffffffafeeb548)
ErrCode = 00000002
eax=00ffffff ebx=00000456 ecx=0000029c edx=00000640 esi=069f0000 edi=06c11000
eip=805452b0 esp=afeeb5bc ebp=afeeb5f0 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!WmiTraceMessageVa+0x217:
805452b0 f3ab rep stos dword ptr es:[edi] es:0023:06c11000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: firefox.exe

LAST_CONTROL_TRANSFER: from bf835331 to 805452b0

STACK_TEXT:
afeeb5f0 bf835331 afeeb864 00000640 069f0000 nt!WmiTraceMessageVa+0x217
afeeb770 bf82f6fe bf8353f3 afeeb864 00000000 win32k!NtUserfnINLPCREATESTRUCT+0xcd
afeeb7dc bf805393 e20c4008 00000000 00000000 win32k!xxxClientWOWGetProcModule+0x38
afeeb7e4 00000000 00000000 00000000 00000000 win32k!DC::vReleaseRao+0x1f


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!NtUserfnINLPCREATESTRUCT+cd
bf835331 ?? ???

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43446a58

SYMBOL_NAME: win32k!NtUserfnINLPCREATESTRUCT+cd

FAILURE_BUCKET_ID: 0x8E_win32k!NtUserfnINLPCREATESTRUCT+cd

BUCKET_ID: 0x8E_win32k!NtUserfnINLPCREATESTRUCT+cd

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

 

Here is another dump, this is the crash I get most frequently

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USB Bugcheck Code:
Arg2: 8ab230e0
Arg3: 10de036d
Arg4: 8a4d7c58

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


CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xFE

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 8ab230e0 to 804f9c37

STACK_TEXT:
80550244 8ab230e0 10de036d 8a4d7c58 00000000 nt!PspReaper+0x25
WARNING: Frame IP not in any known module. Following frames may be wrong.
80550258 b9d30cc3 000000fe 00000005 8ab230e0 0x8ab230e0
80550278 b9d3d516 8ab23028 00000fd0 89cc2000 USBPORT!USBPORT_BugCheck+0x2d
805502b4 bac4b3dd 08ff92a0 8ab239dc 8a4d7c58 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x126
805502d8 bac4b8a6 8ab239dc 8a4d7c58 8a4d7c58 usbehci!EHCI_PollActiveAsyncEndpoint+0x37
80550334 bac4d3d3 8ab239dc 8a4d7c58 80550364 usbehci!EHCI_PollAsyncEndpoint+0x98
80550344 b9d2a2ba 8ab239dc 8a4d7c58 80545aac usbehci!EHCI_PollEndpoint+0x1f
80550364 b9d2b578 026c6f50 8ab230e0 8a4d7ae0 USBPORT!USBPORT_PollEndpoint+0xe8
8055038c b9d2eed0 8ab23028 50457270 80545aac USBPORT!USBPORT_CoreEndpointWorker+0x2be
805503bc b9d3cfb0 8ab23028 80545aac 8ab23028 USBPORT!USBPORT_DpcWorker+0x18a
805503f8 b9d3d128 8ab23028 00000001 8055b0a0 USBPORT!USBPORT_IsrDpcWorker+0x37e
80550414 8aadbea3 8ab2364c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
80550428 80544e5f 8ab2364c 8ab23028 00000000 0x8aadbea3
8ab230ec 00000000 8aae1000 8aae8ff0 00000000 nt!WmiTraceEvent+0x3e8


STACK_COMMAND: kb

FOLLOWUP_IP:
usbehci!EHCI_PollActiveAsyncEndpoint+37
bac4b3dd ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: usbehci!EHCI_PollActiveAsyncEndpoint+37

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME: usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62

FAILURE_BUCKET_ID: 0xFE_usbehci!EHCI_PollActiveAsyncEndpoint+37

BUCKET_ID: 0xFE_usbehci!EHCI_PollActiveAsyncEndpoint+37

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

 

Here is another, I'm hoping this is the right kind of info...

Please let me know if anything else would be helpful...

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USB Bugcheck Code:
Arg2: 8a7550e0
Arg3: 10de036d
Arg4: 894bc870

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


CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xFE

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 8a7550e0 to 804f9c37

STACK_TEXT:
80550244 8a7550e0 10de036d 894bc870 00000000 nt!PspReaper+0x25
WARNING: Frame IP not in any known module. Following frames may be wrong.
80550258 b985bcc3 000000fe 00000005 8a7550e0 0x8a7550e0
80550278 b9868516 8a755028 00000fd0 88c87000 USBPORT!USBPORT_BugCheck+0x2d
805502b4 bac533dd 0707e2a0 8a7559dc 894bc870 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x126
805502d8 bac538a6 8a7559dc 894bc870 894bc870 usbehci!EHCI_PollActiveAsyncEndpoint+0x37
80550334 bac553d3 8a7559dc 894bc870 80550364 usbehci!EHCI_PollAsyncEndpoint+0x98
80550344 b98552ba 8a7559dc 894bc870 80545aac usbehci!EHCI_PollEndpoint+0x1f
80550364 b9856578 026c6f50 8a7550e0 894bc6f8 USBPORT!USBPORT_PollEndpoint+0xe8
8055038c b9859ed0 8a755028 50457270 80545aac USBPORT!USBPORT_CoreEndpointWorker+0x2be
805503bc b9867fb0 8a755028 80545aac 8a755028 USBPORT!USBPORT_DpcWorker+0x18a
805503f8 b9868128 8a755028 00000001 8055b0a0 USBPORT!USBPORT_IsrDpcWorker+0x37e
80550414 8a6d6ea3 8a75564c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
80550428 80544e5f 8a75564c 8a755028 00000000 0x8a6d6ea3
8a7550ec 00000000 8a687000 8a68eff0 00000000 nt!WmiTraceEvent+0x3e8


STACK_COMMAND: kb

FOLLOWUP_IP:
usbehci!EHCI_PollActiveAsyncEndpoint+37
bac533dd ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: usbehci!EHCI_PollActiveAsyncEndpoint+37

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME: usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62

FAILURE_BUCKET_ID: 0xFE_usbehci!EHCI_PollActiveAsyncEndpoint+37

BUCKET_ID: 0xFE_usbehci!EHCI_PollActiveAsyncEndpoint+37

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

 

Probably the culprit is ram. Run memtest to stress test the ram. If you hjave a huge Dr Watson log, it is the also the symptom of faulty ram and you can find the DrWatson log at C:\Documents and Settings\All Users\Documents\DrWatson\drwtsn32.log

 

Thanks!

Thanks for the input, I appreciate the reply. Unfortuneately, and I mean unfortuneately I don't think it's the memory. I've tested all the memory I have with memtest 86 and It's good. I've basically determined my motherboard was faulty The worst possible component to go bad. I had to RMA my board and am currently waiting for a new one.

For those that have EVGA 680i motherboard problems - Search the EVGA forums for posts on re-applying thermal compound to the North and South bridge chips. aparently they used really crappy thermal compound and they get REALLY hot with the stock putty - 65 degrees C! Using Arctic Silver 5 should drop it down to around 40C. All the instructions are in a sticky in the EVGA community forum. I beleve this is a solution to ALL 680i chipset motherboards.

Cheers...

 

Memtest is not 100% accurate

Hi,

If memtest reports the ram is faulty, it is faulty. However some faulty ram can pass memtest. BTW do you have a huge DrWatson log (ie size is bigger than 5MB).