Random BSODs ... whether desktop is active or idle

[lance713]

Is Windows 7 . . . - x86 (32-bit) or x64 ?
x64

- the original installed OS on the system?
Yes

- an OEM or full retail version? Full retail - What is the age of system (hardware)?
All parts bought and built in February 2011, except graphics card purchased March 2012, installed last week.

- What is the age of OS installation (have you re-installed the OS?)
February 2011, have not reformatted since being built.

-------------------------------
BSOD/crashing has started since installing a new gfx card. before card I was using onboard graphics, AMD ATI 4200. Upgraded to AMD ATI Radeon 5570. Since then I've been getting random bsods/crashing.

The graphics card was purchased by my brother as a temporary card until he could afford a more expensive one. When he bought the new one he gave the old one to me. It ran perfectly fine in his machine, no crashing or BSODs.

Sometimes can happen immediately upon boot, idling, or heavy load. Nothing specific seems to trigger it.

I've already tried uninstalling gfx drivers and re-installing. Also tried re-seating the graphics card itself. Aside from that I've made no other hardware/software changes since the BSODs started.

Help would be greatly appreciated!

 

[lance713]

I've ran memtest, it seems like I have a bad stick.

2 sticks = 100+ errors before first past even finishes.
1 stick (stick a, bank a) = errors
1 stick (stick b, bank b) = no errors after a couple passes
1 stick (stick b, bank a) = no errors after a couple passes

I've removed the stick for now and seeing if I still crash.

--------------------

Have also done the driver verifier thing, it BSODs before windows can boot. Had to boot into safe mode to turn it off. Is there anyway I can check which driver is causing it... or do I have to be able to boot for it to tell me which driver it is?

 

[lance713]

Well I haven't crashed since removing that 1 stick of RAM but I feel like I'm not out of the woods yet. I still feel like I have a driver issue somewhere. Can anybody check the dumps and help me out?

 

[writhziden]

Loading Dump File [D:\Kingston\BSODDmpFiles\lance713\Windows_NT6_BSOD_jcgriff2\040712-24398-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0384b000 PsLoadedModuleList = 0xfffff800`03a90670
Debug session time: Sat Apr  7 02:11:46.692 2012 (UTC - 6:00)
System Uptime: 0 days 0:57:27.972
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffea80042f44a4, 2, 0, fffff88003e443f3}

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

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

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003afa100
 ffffea80042f44a4 

CURRENT_IRQL:  2

FAULTING_IP: 
networx+33f3
fffff880`03e443f3 4c390f          cmp     qword ptr [rdi],r9

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880031a87b0 -- (.trap 0xfffff880031a87b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0015b53535ad64c8 rbx=0000000000000000 rcx=0000000000000bcb
rdx=00000000000007f8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003e443f3 rsp=fffff880031a8940 rbp=0000000000000000
 r8=fffffa8005252000  r9=fffffa8003d38a90 r10=0000000000000003
r11=fffff880031a8a58 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
networx+0x33f3:
fffff880`03e443f3 4c390f          cmp     qword ptr [rdi],r9 ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800038c71e9 to fffff800038c7c40

STACK_TEXT:  
fffff880`031a8668 fffff800`038c71e9 : 00000000`0000000a ffffea80`042f44a4 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`031a8670 fffff800`038c5e60 : fffffa80`05716880 00000000`00000000 fffffa80`053711a0 fffffa80`066afdd8 : nt!KiBugCheckDispatch+0x69
fffff880`031a87b0 fffff880`03e443f3 : fffffa80`066afcc0 fffff880`03e139c0 fffffa80`066afcc0 fffffa80`066afdd8 : nt!KiPageFault+0x260
fffff880`031a8940 fffffa80`066afcc0 : fffff880`03e139c0 fffffa80`066afcc0 fffffa80`066afdd8 fffffa80`066afcc0 : networx+0x33f3
fffff880`031a8948 fffff880`03e139c0 : fffffa80`066afcc0 fffffa80`066afdd8 fffffa80`066afcc0 fffff800`038cb021 : 0xfffffa80`066afcc0
fffff880`031a8950 fffffa80`066afcc0 : fffffa80`066afdd8 fffffa80`066afcc0 fffff800`038cb021 fffffa80`066afd93 : tdx! ?? ::FNODOBFM::`string'
fffff880`031a8958 fffffa80`066afdd8 : fffffa80`066afcc0 fffff800`038cb021 fffffa80`066afd93 00000000`00000002 : 0xfffffa80`066afcc0
fffff880`031a8960 fffffa80`066afcc0 : fffff800`038cb021 fffffa80`066afd93 00000000`00000002 fffffa80`05245060 : 0xfffffa80`066afdd8
fffff880`031a8968 fffff800`038cb021 : fffffa80`066afd93 00000000`00000002 fffffa80`05245060 fffffa80`05456590 : 0xfffffa80`066afcc0
fffff880`031a8970 fffff880`03e15bdd : fffffa80`066afd90 fffffa80`05456502 fffffa80`05244e30 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`031a8a60 fffff880`03e42758 : 00000000`00000000 fffffa80`07063410 00000000`00000000 fffff800`03a682d0 : tdx!TdxTdiDispatchInternalDeviceControl+0x36d
fffff880`031a8ae0 00000000`00000000 : fffffa80`07063410 00000000`00000000 fffff800`03a682d0 fffffa80`066afcc0 : networx+0x1758


STACK_COMMAND:  kb

FOLLOWUP_IP: 
networx+33f3
fffff880`03e443f3 4c390f          cmp     qword ptr [rdi],r9

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  networx+33f3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: networx

IMAGE_NAME:  networx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8374cb

FAILURE_BUCKET_ID:  X64_0xD1_networx+33f3

BUCKET_ID:  X64_0xD1_networx+33f3

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

Crash caused by networx.sys: NetWorx – Free Bandwidth Monitoring and Usage Reporting

Recommend uninstalling the software that is causing crashes.


You do also have some memory related crashes: Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA and Bug Check 0x1A: MEMORY_MANAGEMENT, so that may very well be why removing one module helped.