BSOD even after reformatting computer.

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

- Uninstall Norton. They are known to cause BSODs

Code:

Start Menu\Programs\Norton Online Backup	Public:Start Menu\Programs\Norton Online Backup	Public

Recommended to use Microsoft Security Essential from BSOD perspective, and Malwarebytes
Microsoft Security Essentials - Microsoft Windows
Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer

- Do a series of testing using memtest86+. Bad RAM chip could be one of the cause here
RAM - Test with Memtest86+
Pay attention to #3, do the test for at least 8 passes

- Update these drivers as they are pretty old. Outdated driver sometimes cause crashes which is fixed thru update

Code:

Image path: \SystemRoot\system32\DRIVERS\mwlPSDVDisk.sys
    Image name: mwlPSDVDisk.sys
    Timestamp:        Tue Jun 02 17:15:29 2009 (4A24FBC1)

mwlPSDVDisk.sys Driver Download Page

Code:

Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
    Image name: iaStor.sys
    Timestamp:        Thu Dec 10 08:39:43 2009 (4B20515F)

iaStor.sys Driver Download Page

You can find the rest of the info here: Driver Reference Table (DRT)

Code:

Image path: \SystemRoot\system32\DRIVERS\mwlPSDNServ.sys
    Image name: mwlPSDNServ.sys
    Timestamp:        Tue Jun 02 17:07:39 2009 (4A24F9EB)

Code:

Image path: \SystemRoot\system32\DRIVERS\intelppm.sys
    Image name: intelppm.sys
    Timestamp:        Tue Jul 14 06:19:25 2009 (4A5BC0FD)

Code:

Image path: \SystemRoot\system32\DRIVERS\mfenlfk.sys
    Image name: mfenlfk.sys
    Timestamp:        Thu Dec 10 04:05:24 2009 (4B201114)

Code:

Image path: \SystemRoot\system32\DRIVERS\ks.sys
    Image name: ks.sys
    Timestamp:        Thu Mar 04 11:32:25 2010 (4B8F37D9)

there's too many I can't point them out at once
so...

- Run Driver Verifier. This will help to get us the driver that is causing the failure
Driver Verifier - Enable and Disable

- Better run these commands from the Elevated Command Prompt too:
SFC /scannow
chkdsk /r /f

in your dump files, we can get many information that was collected right when the BSOD happened.
Some of them are list of drivers that are loaded in your PC when it occurred.
for more info about the drivers I listed on my post, and other drivers you might be interested, along with their Home Page, you can read here:
Driver Reference Table (DRT)

Because there are so many drivers that are out-of-date and your dump file is not specifically point on the failing driver, I suggest to run Driver Verifier to find out the one.

Hope it helps