BSOD While Playing LA Noire

Update the drivers for all those devices.

It is reported as a USB related fault, and in such a situation it is the better to update the drivers for the USB devices.

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Alright, I have enabled driver verifier and encountered another error.

EDIT: I had another error that I think is different occur while playing Mass Effect 2

You are having lots of NTFS and Volmgr errors. In this situation, better you dont use any HDD monitoring program, speially a demanding one like Acronis. As a try, uninstall DiscDirector.

You are having a few ataport error, too. For them, you need to scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

As another try, place the SATA to another port on the motherboard.

Update Marvell 91xx Confige Device Driver for 6G SATA Controller, ar it is really very old. Search in Marvell ... http://www.marvell.com/support/downloads/search.do

C-Media USB Audio Driver (WDM) (PLTGC.sys) is failing there ..... try to get some updates from C-Media Electronics, Inc..

After doing there, continue with verifier .... it might catch something more.

Information found in your crash dump: 022713-21528-01 of 27-02-2013 PM 07:44 (256 KB)

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff800035aa9cc, 2, 8, fffff800035aa9cc}

*** WARNING: Unable to verify timestamp for PLTGC.sys
*** ERROR: Module load completed but symbols could not be loaded for PLTGC.sys
Probably caused by : PLTGC.sys ( PLTGC+168c89 )

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

Description here: Driver Reference Table - PLTGC.sys
And here: What is pltgc.sys ? | System Explorer
And here: PLTGC.sys - C-Media Audio WDM Driver File Information
Yes, it is C-Media USB Audio Driver (WDM), which caused the last BSOD.

It is your computer ..... wherter it will be fixed or not depends totally on your action, but if you dont want to do it .... dont do. I cannot say anything other than the information obtained in the data supplied by you.

And, here is your marvell ....

Code:

fffff880`00e81000 fffff880`00e8b000   mv91cons   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\mv91cons.sys
    Image name: mv91cons.sys
    Timestamp:        Wed Sep 23 03:06:37 2009 (4AB94365)
    CheckSum:         00005993
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Older than the official release of Windows 7.

Arc,

Your reference to Marvel in that post made me remember a post that LaybackBear made: https://www.sevenforums.com/windows-updates-activation/276851-windows-update-error-code-80080005-windows-7-64-bit-3.html#post2304355

It has to do with updates and SSD's, but LB mentions that Marvel doesn't work well with certain ports, and since the OP's machine is self-built s/he may want to check those connections.

Marvel is picky about what SATA connections it uses.