BSOD While Playing LA Noire

As there is a BIOS update available, apply it.

Also, try to update the device drivers those uses any third party driver. Probably the keyboard and mouse need third party drivers to run.

Jm, the .dmp's still point to PLTGC. Reference this link to my post #34: BSOD While Playing LA Noire
There is one new one, new to me concerning your video

Your saying this happened while playing MC, but the .dmp says Borderlands

Still have the headphones plugged in? Even if you don't, and you haven't tried this yet is, remove/uninstall everything related to those gamecon780's, and make sure you have all the fractal audio stuff removed too.

Its getting to a point where you should start thinking about doing a systematic check like done when trying to solve a browser add-on or start program problem. Uninstall everything related to games or gaming, get back to bare bones and stability then start adding one at a time to see what will BSOD your machine.


Use CCleaner or Revouninstaller

Code:

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  Borderlands2.e

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000ba21c8 -- (.exr 0xfffff80000ba21c8)
ExceptionAddress: fffff88006485bd6 (PLTGC+0x0000000000031bd6)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000ba2270 -- (.trap 0xfffff80000ba2270)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=f7fffa800b5955c0 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88006485bd6 rsp=fffff80000ba2408 rbp=fffffa800acf2000
 r8=0000000000000008  r9=fffffa800b561474 r10=0000000000000000
r11=fffffa800ad432a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
PLTGC+0x31bd6:
fffff880`06485bd6 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ab756e to fffff80002abf810

STACK_TEXT:  
fffff800`00ba12b8 fffff800`02ab756e : 00000000`00000000 fffff880`04802d02 fffff800`00ba1a30 fffff800`02aec0b8 : nt!KeBugCheck
fffff800`00ba12c0 fffff800`02ae4e6d : fffff800`02ccda80 fffff800`02c07d3c fffff800`02a50000 fffff800`00ba21c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00ba12f0 fffff800`02aec4e0 : fffff800`02c0e988 fffff800`00ba1368 fffff800`00ba21c8 fffff800`02a50000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00ba1320 fffff800`02af952f : fffff800`00ba21c8 fffff800`00ba1a30 fffff800`00000000 fffffa80`00000003 : nt!RtlDispatchException+0x410
fffff800`00ba1a00 fffff800`02abee82 : fffff800`00ba21c8 fffffa80`0aca0030 fffff800`00ba2270 00000000`00002000 : nt!KiDispatchException+0x16f
fffff800`00ba2090 fffff800`02abd78a : 00000000`00000080 00000000`00200202 407dccbf`42082616 fffff880`06491cf8 : nt!KiExceptionDispatch+0xc2
fffff800`00ba2270 fffff880`06485bd6 : fffff880`064c2e11 fffffa80`0aca0030 fffff880`064a0ddb fffffa80`0aca0030 : nt!KiGeneralProtectionFault+0x10a
fffff800`00ba2408 fffff880`064c2e11 : fffffa80`0aca0030 fffff880`064a0ddb fffffa80`0aca0030 00000000`00000000 : PLTGC+0x31bd6
fffff800`00ba2410 fffffa80`0aca0030 : fffff880`064a0ddb fffffa80`0aca0030 00000000`00000000 00000000`0000000f : PLTGC+0x6ee11
fffff800`00ba2418 fffff880`064a0ddb : fffffa80`0aca0030 00000000`00000000 00000000`0000000f 00000000`000000f0 : 0xfffffa80`0aca0030
fffff800`00ba2420 fffffa80`0aca0030 : 00000000`00000000 00000000`0000000f 00000000`000000f0 fffff800`00000080 : PLTGC+0x4cddb
fffff800`00ba2428 00000000`00000000 : 00000000`0000000f 00000000`000000f0 fffff800`00000080 fffff880`064d6b95 : 0xfffffa80`0aca0030


STACK_COMMAND:  kb

FOLLOWUP_IP: 
PLTGC+31bd6
fffff880`06485bd6 ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  PLTGC+31bd6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: PLTGC

IMAGE_NAME:  PLTGC.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4eb3a6bd

FAILURE_BUCKET_ID:  X64_0x1E_PLTGC+31bd6

BUCKET_ID:  X64_0x1E_PLTGC+31bd6

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

There is one new one, new to me, concerning your video:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880053d405b, fffff88006cc6698, fffff88006cc5ef0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880053d405b, The address that the exception occurred at
Arg3: fffff88006cc6698, Exception Record Address
Arg4: fffff88006cc5ef0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b
fffff880`053d405b 48392cf0        cmp     qword ptr [rax+rsi*8],rbp

EXCEPTION_RECORD:  fffff88006cc6698 -- (.exr 0xfffff88006cc6698)
ExceptionAddress: fffff880053d405b (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x000000000000010b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88006cc5ef0 -- (.cxr 0xfffff88006cc5ef0)
rax=f7fff8a00c47f930 rbx=fffff8a0028d25c0 rcx=fffff8a00c47f970
rdx=0000000000000007 rsi=0000000000000000 rdi=fffffa800c8d7000
rip=fffff880053d405b rsp=fffff88006cc68d0 rbp=0000000000916995
 r8=0000000000000008  r9=0000000000000008 r10=0000000000000040
r11=fffffa800c8d83e8 r12=00000000000000ad r13=0000000000000000
r14=fffffa800a3e6430 r15=00000000000000c8
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210246
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x10b:
fffff880`053d405b 48392cf0        cmp     qword ptr [rax+rsi*8],rbp ds:002b:f7fff8a0`0c47f930=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bc100
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b
fffff880`053d405b 48392cf0        cmp     qword ptr [rax+rsi*8],rbp

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880053d18af to fffff880053d405b

STACK_TEXT:  
fffff880`06cc68d0 fffff880`053d18af : 00000000`00000000 fffffa80`0a5fc568 00000000`000000b2 fffffa80`0a612040 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x10b
fffff880`06cc6910 fffff880`053eb65d : 00000000`00000000 fffff8a0`0b24daa0 fffffa80`00000000 fffffa80`0a3e6430 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`06cc6ae0 fffff880`053eb398 : fffff880`030a8fc0 fffff880`053ead00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`06cc6cd0 fffff880`053eae96 : 00000000`00000000 fffffa80`0a35b7d0 00000000`00000080 fffffa80`0c7bf410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`06cc6d00 fffff800`0312434a : 00000000`02ef79ff fffffa80`0c789760 fffffa80`09a5f040 fffffa80`0c789760 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`06cc6d40 fffff800`02e74946 : fffff880`030a4180 fffffa80`0c789760 fffff880`030af040 00000007`dffa8000 : nt!PspSystemThreadStartup+0x5a
fffff880`06cc6d80 00000000`00000000 : fffff880`06cc7000 fffff880`06cc1000 fffff880`06cc6680 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff88006cc5ef0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b

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

Jm, going over your event logs I'm noticing a few problem signatures:

Code:

 Problem signature:
 P1: x64
 P2: HID\VID_046D&PID_C22A&REV_0100&MI_01&Col02
  Problem signature:
 P1: x64
 P2: USB\VID_046D&PID_C22B&REV_0101&MI_00
  Problem signature:
 P1: x64
 P2: USB\VID_1532&PID_0017&REV_0200&MI_01
  Problem signature:
 P1: x64
 P2: USB\VID_047F&PID_C010&REV_0100&MI_03
  
There are others.

Please run the DxDiag tool, instructions are at the link.

The program will be listed first, at the top under Programs.
Attachment 259265

• When you click on it, it will open and run the 32bit side first.
• When finished click on "Save all Information". Save to Desktop as DxDiag32.txt

• Go back to the tool only this time click on "Run 64bit DxDiag" button.

• When finished click on "Save all Information". Save to Desktop as DxDiag64.txt
• Zip and upload both files with your next reply.

Although Nvidia says your latest drivers are WHQL certified the dxdiag report says otherwise, the 32bit side is okay, but the 64bit is not.

I'm not sure whether or not this poses a problem. I posted this question in this thread: Latest NVIDIA ForceWare Video Drivers Windows 7 Did you follow the note in that tutorial to update your WEI? If you didn't that can throw things off.
I'll see if Brink can reply here, if there I'll post a link.

You can check if the Steam cache files are okay: Verifying Game Cache Files (GCF)
This brings me to possible corrupt user profiles in L.A.Noire, Borderlands, and Minecraft.

I found out about a possible virus floating in one of those games profiles: PSA: How to Avoid Borderlands 2 'Graveyard.sav' Virus [Updated] - Xbox 360 News At Xbox360Achievements.org now, you may not use Xbox, but that's not to say it couldn't infect your profiles. You will have to check them yourself, you may have to use something like Eset online scanner, and upload each individual games folder to scan.
Here's one on a BL2 site: Graveyard.sav "Viral Infections" [FAQ] [Video] - The Gearbox Software Forums

And, when I say corrupted it can also mean the Social Club in L.A.Noire, see this thread for more: Green Man Gaming Forums / Technical Talk / L.A Noire - Licence Corrupted, and other files, for example .pfil, .tfil, .mfil as described in this thread: Error Help. Game Crashing - Forums - World of Warcraft

My problem is I am not used to gaming and I don't know, but realize these games will in all probability have different files for user profiles and you would have to do some research to understand the steps needed to rebuild each one.

Questions; Have you tried Gumbyjunior1's suggestion? And, most importantly other than playing these games, does your machine run okay?


32bit:

Code:

------------------
System Information
------------------
Time of this report: 3/14/2013, 12:40:34
       Machine name: JEEPMASH
   Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130104-1431)
           Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
       System Model: GA-770TA-UD3
               BIOS: Award Modular BIOS v6.00PG
          Processor: AMD Phenom(tm) II X6 1090T Processor (6 CPUs), ~3.2GHz
             Memory: 12288MB RAM
Available OS Memory: 12286MB RAM
          Page File: 2034MB used, 22536MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: Using System DPI
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
     DxDiag Version: 6.01.7601.17514 32bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
      Display Tab 2: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
        Sound Tab 3: No problems found.
        Sound Tab 4: No problems found.
        Sound Tab 5: No problems found.
        Sound Tab 6: No problems found.
          Input Tab: No problems found.

64bit:

Code:

------------------
System Information
------------------
Time of this report: 3/14/2013, 12:41:30
       Machine name: JEEPMASH
   Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130104-1431)
           Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
       System Model: GA-770TA-UD3
               BIOS: Award Modular BIOS v6.00PG
          Processor: AMD Phenom(tm) II X6 1090T Processor (6 CPUs), ~3.2GHz
             Memory: 12288MB RAM
Available OS Memory: 12286MB RAM
          Page File: 2077MB used, 22494MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: Using System DPI
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
     DxDiag Version: 6.01.7601.17514 64bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: The file nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL).  You may be able to get a WHQL logo'd driver from the hardware manufacturer.
      Display Tab 2: The file nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL).  You may be able to get a WHQL logo'd driver from the hardware manufacturer.
        Sound Tab 1: The file pae_avs_x64.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL).  You may be able to get a WHQL logo'd driver from the hardware manufacturer.
        Sound Tab 2: The file pae_avs_x64.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL).  You may be able to get a WHQL logo'd driver from the hardware manufacturer.
        Sound Tab 3: No problems found.
        Sound Tab 4: No problems found.
        Sound Tab 5: The file pae_avs_x64.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL).  You may be able to get a WHQL logo'd driver from the hardware manufacturer.
        Sound Tab 6: The file pae_avs_x64.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL).  You may be able to get a WHQL logo'd driver from the hardware manufacturer.
          Input Tab: No problems found.