Bsod after startup and after sleepmode, 0x00000070E

Filip, Welcome to SF :) .

Your bugchecks show a lot of issues but the most prominent one is with your storage configuration
Specifically the Marvell controller [Two SATA 6Gb/s ports (navy blue)], on your motherboard.

Code:

fffff800`00b9bdc8  fffff800`030cd510 nt!KiDispatchException+0x164
fffff800`00b9bde8  fffff800`0308e490 nt!KiChainedDispatch
fffff800`00b9bdf0  fffff880`01166f50 mv91xx+0x2ff50
fffff800`00b9bdf8  fffff880`01137000 mv91xx
fffff800`00b9be00  fffff880`011b9680 mv91xx+0x82680
fffff800`00b9be08  fffff880`01137000 mv91xx
fffff800`00b9be10  fffff880`011b92b4 mv91xx+0x822b4
fffff800`00b9be18  fffff880`01137000 mv91xx
fffff800`00b9be20  fffff880`011b9308 mv91xx+0x82308
fffff800`00b9be28  fffff880`01137000 mv91xx
fffff800`00b9be30  fffff880`011b8054 mv91xx+0x81054
fffff800`00b9be38  fffff880`010b0000 SCSIPORT!SpIsAdapterControlTypeSupported <PERF> (SCSIPORT+0x0)
fffff800`00b9be40  fffff880`010c42f4 SCSIPORT!__PchSym_ <PERF> (SCSIPORT+0x142f4)
fffff800`00b9be48  fffff800`0301d000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff800`00b9be50  fffff800`032a0978 nt!BBTBuffer <PERF> (nt+0x283978)
fffff800`00b9be58  fffff800`0301d000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff800`00b9be60  fffff800`032a096c nt!BBTBuffer <PERF> (nt+0x28396c)
fffff800`00b9bea0  fffff880`011b6b80 mv91xx+0x7fb80
fffff800`00b9bea8  fffff880`011b7900 mv91xx+0x80900
fffff800`00b9bf08  fffff800`030cd4e1 nt!KiDispatchException+0x135
fffff800`00b9c038  fffff880`01166ee1 mv91xx+0x2fee1

Code:

lmvm mv91xx
start             end                 module name
fffff880`01137000 fffff880`011c3000   mv91xx   T (no symbols)           
    Loaded symbol image file: mv91xx.sys
    Image path: \SystemRoot\system32\DRIVERS\mv91xx.sys
    Image name: mv91xx.sys
    Timestamp:        Fri Aug 27 12:49:22 2010

• Driver Reference Table - mv91xx.sys

Seeing that Marvell doesn't offer an official update I believe its time to switch
to the Intel ports, (2 x SATA 6Gb/s port(s), gray).

Other storage issues;

Code:

BugCheck 7A, {fffff6fc806007a0, ffffffffc000009d, b8f0d880, fffff900c00f4e7c}
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.

Code:

ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000009d

Code:

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.

Code:

BugCheck 77, {1, ba8b7, 0, fffff8800c592e80}

Code:

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in.  Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found.  Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED)  normally indicates
the data could not be read from the disk due to a bad
block.  Upon reboot autocheck will run and attempt to map out the bad
sector.  If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked.  See the knowledge base article on SCSI termination.

Code:

ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1

Code:

lmvm jraid
start             end                 module name
fffff880`00fc2000 fffff880`00fe3000   jraid    T (no symbols)           
    Loaded symbol image file: jraid.sys
    Image path: \SystemRoot\system32\DRIVERS\jraid.sys
    Image name: jraid.sys
    Timestamp:        Tue Aug 10 12:28:44 2010

• Driver Reference Table - jraid.sys
• Please Update :: Download ::

Upload a screenshot of Disk Management:

• Disk Management - Post a Screen Capture Image

Test the HDD:

   Warning

The Following Method Should NOT Be Performed On An SSD!

Testing the HDD:

1. Perform a Disk Check | Disk Check
2. Then Post the results following | THIS METHOD
3. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
4. If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

If SeaTools For DOS does not recognize the drive;
Boot into the BIOS using the *Fxkey.
Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
Set it to IDE then save and exit usually by pressing the F10 key.
Now boot into SeaTools and it should detect the drives.
Start the Long Test and let it run.
Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
and change the SATA setting back to what it was in the first place.

• *Popular BIOS access keys.

• Upload a Screenshot of Crystal Disk Info
• Update your SSD Firmware
• And upload a screenshot of the SMART Status

Code:

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


Unable to load image \SystemRoot\System32\cdd.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll

• Download Speccy and upload a Screenshot of the summary tab.
• Download TDSS-Killer and scan for rootkits.
• Download Windows Defender Offline and scan for other types of infections.
• Follow this tutorial on how to use the SFC/ SCANNOW tool in Windows.

Running two Anti-Virus software only makes things worst:

Code:

Start Menu\Programs\McAfee Security Scan Plus

Code:

Start Menu\Programs\avast! Free Antivirus

Uninstall both programs using each respective removal tool.

• Avast Removal Tool
• Mcafee Removal Tool
• Follow the bottom mentioned quote;
  

Arc said:

Use Microsoft Security Essentials as your antivirus with windows
inbuilt firewall and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Remove MSI Afterburner, it's a know BSOD in Windows 7;

Code:

Start Menu\Programs\MSI Afterburner

   Note

Stop! overclocking, if any component is overclocked revert back to stock speeds.

Cleanup your startup by following this tutorial;

• Troubleshoot Application Conflicts by Performing a Clean Startup

Update your USB 3.0 Drivers:

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff88008e71716, fffff8800b41e708, fffff8800b41df60}

Probably caused by : asmtxhci.sys ( asmtxhci+1b716 )

Code:

fffff880`0b41e918  fffff880`08e71716 asmtxhci+0x1b716
fffff880`0b41e978  fffff880`0893cc77 asmthub3+0x8c77
fffff880`0b41e998  fffff880`08935c2b asmthub3+0x1c2b
fffff880`0b41e9b8  fffff880`08938390 asmthub3+0x4390
fffff880`0b41e9d8  fffff880`0893c809 asmthub3+0x8809
fffff880`0b41ea08  fffff880`0893b285 asmthub3+0x7285
fffff880`0b41ea38  fffff880`0893aed1 asmthub3+0x6ed1
fffff880`0b41eaa0  fffff880`0893fd28 asmthub3+0xbd28
fffff880`0b41eab0  fffff880`0893e060 asmthub3+0xa060
fffff880`0b41ead8  fffff880`0893fd28 asmthub3+0xbd28
fffff880`0b41eae8  fffff880`0893ec00 asmthub3+0xac00
fffff880`0b41eb10  fffff880`0893fd28 asmthub3+0xbd28
fffff880`0b41eb20  fffff880`0893f37c asmthub3+0xb37c
fffff880`0b41eba0  fffff880`08941780 asmthub3+0xd780
fffff880`0b41ebc8  fffff880`08941789 asmthub3+0xd789

Code:

lmvm asmtxhci
start             end                 module name
fffff880`08e56000 fffff880`08eba000   asmtxhci T (no symbols)           
    Loaded symbol image file: asmtxhci.sys
    Image path: \SystemRoot\system32\DRIVERS\asmtxhci.sys
    Image name: asmtxhci.sys
    Timestamp:        Wed Sep 14 10:36:09 2011

Code:

lmvm asmthub3
start             end                 module name
fffff880`08934000 fffff880`08958000   asmthub3 T (no symbols)           
    Loaded symbol image file: asmthub3.sys
    Image path: \SystemRoot\system32\DRIVERS\asmthub3.sys
    Image name: asmthub3.sys
    Timestamp:        Wed Sep 14 10:36:19 2011

• Driver Reference Table - asmthub3.sys
• Driver Reference Table - asmtxhci.sys
• Please update :: Download ::
  

Testing the RAM:

koolkat77 said:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• Pay close attention to part 3 of the tutorial "If you have errors"
• Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

When done with the testing procedure take a picture and upload it here.


Post back with the results!

Thanks, keep us posted.
How many passes did you allow Memtest to run through?

Hello :) .
Thank you for the feed back :) .
The screenshots you uploaded look good, with fingers crossed I look forward to your update.

Good news to jump-start the day off :) !
Happy I could be an assistance.

You can find it here;
https://www.facebook.com/sevenforums

Now please mark the topic as solved.
Enjoy your stay!