BSOD 1E, 0D, different everytime

Toshiba: Follow it:
Troubleshooting Windows 7 Failure to Start

Or, run Startup Repair for three separate times, with restarts after every single run.
Startup Repair: Run three separate times.

BUT, after running WDO. If there is any virus, it will never boot normally I guess.

HP: If it is fine now, Good news. Observe that one, how it works. And pay the attention to the Toshiba one. :)

Both of the network drivers are very old.

Atheros network adapter driver

Code:

 lmvm athrx
start             end                 module name
fffff880`04441000 fffff880`045ca000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Wed Mar 03 06:15:21 2010 (4B8DB121)
    CheckSum:         00186AC4
    ImageSize:        00189000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from ATHEROS drivers for Microsoft Windows (Atheros?????)

Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC

Code:

lmvm rt64win7
start             end                 module name
fffff880`05845000 fffff880`05891000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Fri Nov 27 15:15:07 2009 (4B0F9FA3)
    CheckSum:         00056663
    ImageSize:        0004C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Realtek

A preferred way to update the network drivers.
First, download the network card driver from manufactuer's website.
Then reinstall the driver:

1. Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
2. Double click to expand "Network adaptors".
3. Right click your network card and click Uninstall.
4. Check "Delete driver software for this device" check box, click OK.
5. Restart the computer
6. If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually.

► Scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

► Perform some Disc Check

1. Update your SSD's Firmware
2. Reseat the sata and power.
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
4. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

► Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.


Let us know. If not worked, it may be that you need to change your network adapter.

Within the last month, you haven't let me know if you worked with my last suggestions or not. OK, good.

But I am seeing that you may not have followed it, coz it is still crashing on the same Atheros network adapter driver.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff3000b7e0dcd, 2, 0, fffff88002d989f2}

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

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ccc100
 fffff3000b7e0dcd 

CURRENT_IRQL:  2

FAULTING_IP: 
athrx+12d9f2
fffff880`02d989f2 3a040a          cmp     al,byte ptr [rdx+rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002f1b630 -- (.trap 0xfffff88002f1b630)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80078d3700 rbx=0000000000000000 rcx=fffffa80078d3dc3
rdx=fffff88003f0d00a rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002d989f2 rsp=fffff88002f1b7c8 rbp=0000000000000000
 r8=0000000000000006  r9=0000000000000000 r10=fffffa8005368c90
r11=fffff88003f0d000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
athrx+0x12d9f2:
fffff880`02d989f2 3a040a          cmp     al,byte ptr [rdx+rcx] ds:fffff300`0b7e0dcd=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a9c569 to fffff80002a9cfc0

STACK_TEXT:  
fffff880`02f1b4e8 fffff800`02a9c569 : 00000000`0000000a fffff300`0b7e0dcd 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f1b4f0 fffff800`02a9b1e0 : fffffa80`04bf55e0 fffff880`033fd000 00000000`00000000 fffffa80`05572010 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b630 fffff880`02d989f2 : fffff880`02cb9cc0 fffff880`02f1b848 fffff880`014a9207 00000000`00000002 : nt!KiPageFault+0x260
fffff880`02f1b7c8 fffff880`02cb9cc0 : fffff880`02f1b848 fffff880`014a9207 00000000`00000002 00000011`ad13f638 : athrx+0x12d9f2
fffff880`02f1b7d0 fffff880`02f1b848 : fffff880`014a9207 00000000`00000002 00000011`ad13f638 fffffa80`00000010 : athrx+0x4ecc0
fffff880`02f1b7d8 fffff880`014a9207 : 00000000`00000002 00000011`ad13f638 fffffa80`00000010 fffffa80`078d3770 : 0xfffff880`02f1b848
fffff880`02f1b7e0 00000000`00000002 : 00000011`ad13f638 fffffa80`00000010 fffffa80`078d3770 00000000`00000000 : ndis+0x43207
fffff880`02f1b7e8 00000011`ad13f638 : fffffa80`00000010 fffffa80`078d3770 00000000`00000000 fffff880`02c6c9c0 : 0x2
fffff880`02f1b7f0 fffffa80`00000010 : fffffa80`078d3770 00000000`00000000 fffff880`02c6c9c0 00000000`00000000 : 0x11`ad13f638
fffff880`02f1b7f8 fffffa80`078d3770 : 00000000`00000000 fffff880`02c6c9c0 00000000`00000000 fffff880`02cb9ec3 : 0xfffffa80`00000010
fffff880`02f1b800 00000000`00000000 : fffff880`02c6c9c0 00000000`00000000 fffff880`02cb9ec3 fffffa80`04bf4778 : 0xfffffa80`078d3770


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrx+12d9f2
fffff880`02d989f2 3a040a          cmp     al,byte ptr [rdx+rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  athrx+12d9f2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrx

IMAGE_NAME:  athrx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b8db121

FAILURE_BUCKET_ID:  X64_0xD1_athrx+12d9f2

BUCKET_ID:  X64_0xD1_athrx+12d9f2

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

1: kd> lmvm athrx
start             end                 module name
fffff880`02c6b000 fffff880`02df4000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Wed Mar 03 06:15:21 2010 (4B8DB121)
    CheckSum:         00186AC4
    ImageSize:        00189000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Link to update it is given in my earlier post, see it there.

Code:

lmvm athrx
start             end                 module name
fffff880`02c6b000 fffff880`02df4000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Wed Mar 03 06:15:21 2010 (4B8DB121)
    CheckSum:         00186AC4
    ImageSize:        00189000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

According to it, the driver is not updated. Follow it: Driver Install - Device Manager

I will go an see if there is a newer one, but i went on the website you told me to and download the latest one from there.

From the website you gave it say this for the date of the driver:

Release: 2012-08-01 [August '12]

Let us know what is the situation after replacing the driver.