BSOD Errors - Idling Computer

Do not maintain two running threadsin the same section. Go mark BSOD Various Errors as solved and continue here.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall the program at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

You have 32 startup items!!!! Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Update the driver to ASUS Xonar DGX Audio Device from ASUSTeK Computer Inc. -Support- Drivers and Download Xonar DGX.

Let us know the results.
_______________________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88059a356d0, 0, fffff880043bdf4c, 5}

*** WARNING: Unable to verify timestamp for cmudaxp.sys
*** ERROR: Module load completed but symbols could not be loaded for cmudaxp.sys

Could not read faulting driver name
Probably caused by : cmudaxp.sys ( cmudaxp+1baf4c )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff88059a356d0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880043bdf4c, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f7100
GetUlongFromAddress: unable to read from fffff800032f71c0
 fffff88059a356d0 Nonpaged pool

FAULTING_IP: 
cmudaxp+1baf4c
fffff880`043bdf4c 0fb7ac4180d12d00 movzx   ebp,word ptr [rcx+rax*2+2DD180h]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  PathOfExile.ex

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800e56d200 -- (.trap 0xfffff8800e56d200)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000002aaaaaa8 rbx=0000000000000000 rcx=fffff88004203000
rdx=000000002aaaaaa8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880043bdf4c rsp=fffff8800e56d390 rbp=fffffa800aa70000
 r8=000000000000b975  r9=0000000000000000 r10=000000007ffffff8
r11=fffffa8009c92110 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cmudaxp+0x1baf4c:
fffff880`043bdf4c 0fb7ac4180d12d00 movzx   ebp,word ptr [rcx+rax*2+2DD180h] ds:fffff880`59a356d0=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000313c5a3 to fffff800030bfc00

STACK_TEXT:  
fffff880`0e56d098 fffff800`0313c5a3 : 00000000`00000050 fffff880`59a356d0 00000000`00000000 fffff880`0e56d200 : nt!KeBugCheckEx
fffff880`0e56d0a0 fffff800`030bdd2e : 00000000`00000000 fffff880`59a356d0 00000000`00000000 fffffa80`0aa771d0 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`0e56d200 fffff880`043bdf4c : fffffa80`0aa77218 00000000`00000000 fffffa80`0aa77218 fffff880`043be4ac : nt!KiPageFault+0x16e
fffff880`0e56d390 fffffa80`0aa77218 : 00000000`00000000 fffffa80`0aa77218 fffff880`043be4ac fffffa80`0aa77218 : cmudaxp+0x1baf4c
fffff880`0e56d398 00000000`00000000 : fffffa80`0aa77218 fffff880`043be4ac fffffa80`0aa77218 fffffa80`0aa771e0 : 0xfffffa80`0aa77218


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cmudaxp+1baf4c
fffff880`043bdf4c 0fb7ac4180d12d00 movzx   ebp,word ptr [rcx+rax*2+2DD180h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  cmudaxp+1baf4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cmudaxp

IMAGE_NAME:  cmudaxp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4eefffab

FAILURE_BUCKET_ID:  X64_0x50_cmudaxp+1baf4c

BUCKET_ID:  X64_0x50_cmudaxp+1baf4c

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

1: kd> lmvm cmudaxp
start             end                 module name
fffff880`04203000 fffff880`0452f000   cmudaxp  T (no symbols)           
    Loaded symbol image file: cmudaxp.sys
    Image path: cmudaxp.sys
    Image name: cmudaxp.sys
    Timestamp:        Tue Dec 20 08:53:23 2011 (4EEFFFAB)
    CheckSum:         0029B62C
    ImageSize:        0032C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

No startup item anyhow affect the network connection at all. Either Wired or wireless, the connection is done with the network adapter, that is a hardware. No software controls it.

It is either something else with your connection, or uninstall Networx.