On Going PC Issue

Hi guys, I'm having some serious issues with my PC and I'm at the end of my rope as far as repairing it. I've been fixing my own PCs for over 15 years and I've never run up against something I can't fix but this thing is confusing me at every turn.

The Windows 7 64 bit installation in this thing is brand new. The hard drive is new, there is a new USB hub PCI card recently installed. I've replaced and upgraded the power supply, replaced the heat sync gel twice (Heat is not an issue at this point) The graphics card is also brand new.

Only recently I've had this issue come up with the audio of the PC, and now it has been to effect the video as well, and has progressed to a serious BSOD where the computer says there is a pagefault, an attempt to access paged memory in an unpaged area (Has happened 3 times now)

When I play any game, video, music regardless of the output (Speakers, headphones, HDMI Cable) I get studdering and choppy music, with crackling and buzzing. Video games studder and freeze for a few seconds, even ones I was previously able to play at max settings now run like garbage from time to time. Another troubling issue is that all the USB ports in the back went out at he same time and 2 in the front cut out constantly so I Can't use them for anything. To compound the issue the RJ-45 port for Ethernet connection is messed up and burns out any router it is hooked up to (Went through 2 between we realized it was this computer burning them out) So I couldn't connect to the internet with normal ethernet cables, couldn't connect with a wireless USB dongle because the USB ports didn't work. This is why I installed the USB PCI card which seems to work (Have the internet and a wireless USB key/boarder and mouse hooked up to it atm) Even still the USB ports in the PCI card shut off and I have to take the dongles out and place them back in to get them to work again.

On resource manager none of my resources are being stressed. Even with the CPU is at 10-20 % and ram is around the same area I Get this stutter and crackling sound. I'm starting to believe that maybe the ram itself is damaged, or the mobo is damaged. The fact that it is shorting out stuff through the Ethernet port is something I've never seen before. Any help you guys can offer would be much appreciated, tell me what info you'd like me to post first and I will do.


I have attached my DxDiag.txt to this post, thanks!

 

I ran memtest86 and found no errors or faults, not sure if that means my ram is fine or not.

 

Could you go to C:\Windows\Minidump folder and attach the minidump file(s) as ZIP archive? That would give the experts more to go on. The fact that you're shorting things out could mean a bad ground connection though.

 

Reads like a hardware issue to me, 'board or PSU would be my first suspects. A stripdown test followed by a careful rebuild might eliminate the short but it won't fix any damage already done.

Run MSInfo32 and Save as the default .nfo type, wait 10 minutes or so for it to complete data collection before zipping it and attaching it to a reply. The WER (Windows Error Reporting) and other info contained might furnish some clues.

 

Attached as requested. Much thanks for any help you can give. The documents.zip file contains the .dmp files. The PSU is less than a year old, that doesn't mean anything I guess but it is possible something is wrong with it.

 

2 of the dumps flag the Netgear/Atheros driver as being corrupted (this could also mean 'is being interfered with'), try updating it here: http://downloadcenter.netgear.com/en/product/WNA1100#searchResults

The 3rd dump is old and possibly corrupt, I'll ignore it.

The Connexant modem is loading Vista-era drivers, better to disable it in the BIOS and uninstall the software/drivers for it.

The Daemon Tools driver, dtsoftbus01.sys, has been implicated with causing BSODs in W7, uninstall DT.

It's an Emachines, I can see why you replaced the PSU What make/model# is the replacement?

Deal with the above and get rid of SnapDo ('c:\users\valosar\appdata\local\smartbar\application\snapdo.exe startup', try this first: http://malwaretips.com/blogs/remove-snapdo-virus/ - if that fails, or for a checkup, see here: http://forums.majorgeeks.com/showthread.php?t=35407).

 

The netgear device on my pc is the wireless USB dongle and the BSODs only started after I started using it (But to be fair they also started after I installed the PCI card with extra USB ports)

I will do everything you've instructed and get back with results. I believe the PSU is a coolmaster not sure exactly what the model # is but I will get back with that as well.

Thank you!

 

New BSOD while reading your post, new minidump file uploaded to see if it was caused by the same thing. Nothing has been done yet about to try again now.

 

I'm having trouble with this step, the modem does not appear in my device manager (I removed the PCI card with the modem and installed the USB card instead) Is there a manual way to remove these drivers from my computer?

 

Theoretically, Windows shouldn't load drivers for a device that isn't installed, if, however, the device is virtual/software, as most modems have been for 15+ years now, that's probably not going to happen. If the software doesn't appear in Add/Remove, you could try uninstalling them after enabling the hidden devices in Device Manager (under Non Plug and play?) but be prepared for a crash or the need to use Last known good or System Restore

These are the driver details I see, they may be ok to leave on W7x86 but I don't trust anything of that age to play well on x64:
mdmxsdk.sys Mon Jun 19 22:27:26 2006 (449716BE)
Conexant Modem Diagnostic Interface x86 Driver
http://www.carrona.org/drivers/driver.php?id=mdmxsdk.sys

xaudio64.sys Sat Jun 30 01:11:22 2007 (46859FAA)
Conexant Modem Audio
http://www.carrona.org/drivers/driver.php?id=xaudio64.sys

The latest crash looks much the same, athurx.sys being the most recent 3rd party driver in the call stack:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff800ff7fff4f, 8, fffff800ff7fff4f, 5}

Unable to load image \SystemRoot\system32\DRIVERS\athurx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athurx.sys
*** ERROR: Module load completed but symbols could not be loaded for athurx.sys

Could not read faulting driver name
Probably caused by : athurx.sys ( athurx+9efab )

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

1: kd> !analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff800ff7fff4f, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff800ff7fff4f, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f14100
 fffff800ff7fff4f 

FAULTING_IP: 
+656e952f000dda00
fffff800`ff7fff4f ??              ???

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800a0919e0 -- (.trap 0xfffff8800a0919e0)
.trap 0xfffff8800a0919e0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0001360900000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800ff7fff4f rsp=fffff8800a091b70 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000f44 r10=fffff80002c67000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffff800`ff7fff4f ??              ???
.trap
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d595b3 to fffff80002cdcbc0

STACK_TEXT:  
fffff880`0a091878 fffff800`02d595b3 : 00000000`00000050 fffff800`ff7fff4f 00000000`00000008 fffff880`0a0919e0 : nt!KeBugCheckEx
fffff880`0a091880 fffff800`02cdacee : 00000000`00000008 fffff800`ff7fff4f 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`0a0919e0 fffff800`ff7fff4f : 00000000`40bd0089 fffff880`028b9fab fffffa80`00000000 00000000`00004048 : nt!KiPageFault+0x16e
fffff880`0a091b70 00000000`40bd0089 : fffff880`028b9fab fffffa80`00000000 00000000`00004048 fffff880`00000000 : 0xfffff800`ff7fff4f
fffff880`0a091b78 fffff880`028b9fab : fffffa80`00000000 00000000`00004048 fffff880`00000000 00000000`00000000 : 0x40bd0089
fffff880`0a091b80 fffffa80`00000000 : 00000000`00004048 fffff880`00000000 00000000`00000000 00000000`00000000 : [b]athurx[/b]+0x9efab
fffff880`0a091b88 00000000`00004048 : fffff880`00000000 00000000`00000000 00000000`00000000 fffffa80`04592030 : 0xfffffa80`00000000
fffff880`0a091b90 fffff880`00000000 : 00000000`00000000 00000000`00000000 fffffa80`04592030 00000000`00000001 : 0x4048
fffff880`0a091b98 00000000`00000000 : 00000000`00000000 fffffa80`04592030 00000000`00000001 fffffa80`036ccb30 : 0xfffff880`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athurx+9efab
fffff880`028b9fab ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  athurx+9efab

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athurx

IMAGE_NAME:  athurx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cb2d4a1

FAILURE_BUCKET_ID:  X64_0x50_athurx+9efab

BUCKET_ID:  X64_0x50_athurx+9efab

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

 

I've gone everything you've asked, updated the drivers for my wireless network card, removed the Daemon tools, scanned my computer with malware bytes and another program it looks like it removed that pesky malware (I thought I got it right away when it installed but I guess I missed a bit. I misclicked while installing something else and knew right away I was boned) IS there anything else I can do to reduce the chance of this BSOD happening again?

 

So far, so good, eh? You could try forcing the issue by stress-testing the 3rd party drivers with Driver Verifier turned on for 24-48 hours. Read this very carefully, don't ignore the System Restore creation, you might need it: http://www.sysnative.com/forums/bso...river-verifier-blue-screen-death-related.html

 

New BSOD earlier today. If I were to stop using this wireless dongle and remove the drivers would it resolve my issues?