Various BSOD errors during normal use and sleep

Welcome to SevenForums..

Is the firmware of your SSD up to date?

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80002000000, 8, fffff80002000000, 2}

*** 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+9f3bb )

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: fffff80002000000, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff80002000000, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036c6100
GetUlongFromAddress: unable to read from fffff800036c61c0
 fffff80002000000 Nonpaged pool

FAULTING_IP: 
+0
fffff800`02000000 ??              ???

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

LAST_CONTROL_TRANSFER:  from fffff8000343d8e0 to fffff80003496fc0

FAILED_INSTRUCTION_ADDRESS: 
+0
fffff800`02000000 ??              ???

STACK_TEXT:  
fffff880`02b63738 fffff800`0343d8e0 : 00000000`00000050 fffff800`02000000 00000000`00000008 fffff880`02b638a0 : nt!KeBugCheckEx
fffff880`02b63740 fffff800`034950ee : 00000000`00000008 fffff800`02000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x437f6
fffff880`02b638a0 fffff800`02000000 : fffffa80`40820089 fffff880`038af3bb fffffa80`00000000 fffff880`00004048 : nt!KiPageFault+0x16e
fffff880`02b63a30 fffffa80`40820089 : fffff880`038af3bb fffffa80`00000000 fffff880`00004048 fffff800`00000000 : 0xfffff800`02000000
fffff880`02b63a38 fffff880`038af3bb : fffffa80`00000000 fffff880`00004048 fffff800`00000000 00000000`00000000 : 0xfffffa80`40820089
fffff880`02b63a40 fffffa80`00000000 : fffff880`00004048 fffff800`00000000 00000000`00000000 00000000`00000000 : athurx+0x9f3bb
fffff880`02b63a48 fffff880`00004048 : fffff800`00000000 00000000`00000000 00000000`00000000 fffffa80`08636030 : 0xfffffa80`00000000
fffff880`02b63a50 fffff800`00000000 : 00000000`00000000 00000000`00000000 fffffa80`08636030 fffff880`02b63bdc : 0xfffff880`00004048
fffff880`02b63a58 00000000`00000000 : 00000000`00000000 fffffa80`08636030 fffff880`02b63bdc fffffa80`0667c840 : 0xfffff800`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athurx+9f3bb
fffff880`038af3bb ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  athurx+9f3bb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athurx

IMAGE_NAME:  athurx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4daeb071

FAILURE_BUCKET_ID:  X64_0x50_BAD_IP_athurx+9f3bb

BUCKET_ID:  X64_0x50_BAD_IP_athurx+9f3bb

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

1: kd> lmvm athurx
start             end                 module name
fffff880`03810000 fffff880`039ee000   athurx   T (no symbols)           
    Loaded symbol image file: athurx.sys
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
    Image name: athurx.sys
    Timestamp:        Wed Apr 20 16:07:45 2011 (4DAEB071)
    CheckSum:         001E1C78
    ImageSize:        001DE000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Perform a clean install of the above Atheros driver.

METHOD:

Click on the Start ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; ATHEROS & restart the computer. Delete remnants of its drivers/older drivers using Driver Fusion/Sweeper

Atheros Driver:

If its wireless, match your device from here:

• ATHEROS Wireless drivers for Windows

If its not a wireless, match your device from here:

• ATHEROS Network drivers for Windows

Perform a System File Check:

• Click on the start
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

Disk Check on your hard drive for file system errors and bad sectors on it:

• Disk Check

If this does not bring stability, test the RAM.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

Let us know your results.

There are no .dmp files after the 26th of last month

I will check the files again.

Do let us know the results from memtest.

OK, and after that we'll enable driver verifier.

Do you get BSOD-s in safe mode?

Upload a screenshot of your hard disk using CrystalDiskInfo:

• CrystalDiskInfo - Software - Crystal Dew World
• Screenshots and Files - Upload and Post in Seven Forums

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• Disk Check

Hard drive test both short and long with:

• SeaTools for Windows

Also the DOS version of:

• SeaTools for DOS
• SeaTools for DOS tutorial