Solved BSOD While Playing LA Noire

[Anak]

For the 04-08 file you had two BL2's and that PLTGC
For the 04-09 you had a new one called GameOverlayUI.

If you don't chat while playing or even if you do, to test go into Services | Option One and stop the GameOverlayUI. service. Then see if your games crash.

Your temps look okay, but ambient heat below and around the GPU and the ram modules could exceed 80°C, can you open up your case and try to run an extra fan or two to test? Even if you use a floor model type.

Next, you can try using older driver versions from nvidia for the geforce 660 ti to see if an older one would work.

This link: GIGABYTE - Support & Downloads - Downloads - Graphics Card Might help matching up the gforce with your gigabyte MB.

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003013147, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800a9eef90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
nt!ExAllocatePoolWithTag+537
fffff800`03013147 48895808        mov     qword ptr [rax+8],rbx

CONTEXT:  fffff8800a9eef90 -- (.cxr 0xfffff8800a9eef90)
rax=f7fffa800b4f41e0 rbx=fffff8000306e730 rcx=fffffa800aed4430
rdx=0000000000000000 rsi=0000000000000008 rdi=0000000000000000
rip=fffff80003013147 rsp=fffff8800a9ef970 rbp=0000000000001000
 r8=0000000000000000  r9=fffff8000306e730 r10=fffff8000306e588
r11=fffff8800a9efaa0 r12=fffff8000306e580 r13=0000000000000000
r14=0000000000000000 r15=00000000ee657645
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!ExAllocatePoolWithTag+0x537:
fffff800`03013147 48895808        mov     qword ptr [rax+8],rbx ds:002b:f7fffa80`0b4f41e8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  GameOverlayUI.

 

[Jeepmash]

I've run a few GPU logs (GPU-Z and MSI Afterburner), HWmonitor before I started gameplay, and CoreTemp. I have tried older GPU drivers to no avail. GameOverLayUI is a part of Steam and is not really possible to stop if I start a game...

 

[Anak]

jm, I'm at a loss, Your last .dmp points to SearchFilterHo A system file:

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002e8cfe4, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88009e1fce0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
nt!KiDeferredReadyThread+e4
fffff800`02e8cfe4 80bd1e04000002  cmp     byte ptr [rbp+41Eh],2

CONTEXT:  fffff88009e1fce0 -- (.cxr 0xfffff88009e1fce0)
rax=00000000000000e0 rbx=0000000000000004 rcx=0000000000000004
rdx=0000000000000004 rsi=fffff80003002e80 rdi=fffffa800d81db50
rip=fffff80002e8cfe4 rsp=fffff88009e206c0 rbp=f7fffa800a614a60
 r8=0000000000000004  r9=0000000000000000 r10=fffff80002e12000
r11=0000000000000000 r12=0000000000000000 r13=0000000002254dfe
r14=fffff88002f64101 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!KiDeferredReadyThread+0xe4:
fffff800`02e8cfe4 80bd1e04000002  cmp     byte ptr [rbp+41Eh],2 ss:0018:f7fffa80`0a614e7e=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  [COLOR=DarkRed][COLOR=Red]SearchFilterHo[/COLOR]
[/COLOR]
CURRENT_IRQL:  2

But I'm leaning towards this:

Vladimir Zografski

C0000005 Error is a Windows System error, not a VFP Error. It is an Exception Error that occurs when a process (application, driver, etc.) tries to execute a processor command that references memory outside the space allocated to that process by the Operating System. It is what used to be known as a "General Protection Fault" or GPF. There is no generic "solution" to this type of error.
There are many possible causes ranging from corrupt data tables, to a bad network connection, ActiveX controls, or Printer or Video driver errors. WIthout knowing what type of error you are seeing, it is impossible to guess what the cause may be.
The one thing it is very unlikely to be is some particular line of application code (whether VFP or any other language).

Systems Analyst

Source: C00005 error at program startup

I'm thinking someway to rule out your hardware like,

• Can you try different/spare memory?
• Look over those cables/connections.
• Looking at the CPU or GPU especially the CPU is up to you.
• Do you have/can you replace the CPU or GPU?
• Try a new coat of thermal paste on the present CPU?
• ?????

Have you considered a Repair Install?


I'm going to see if Arc can take another look.

 

[Arc]

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.

 

[Jeepmash]

I seemed to have fixed the issue. For whatever reason, having two different RAM sizes (though they matched in speed) was causing the problem. Removing one of the sets (it didn't matter which) let me play any game that would normally crash for hours without difficulty. I've tried running both sets of RAM in and out of dual channel to no avail, so I will just stick with the larger set, leaving out the other. I am not entirely certain yet that I won't run into a problem again with BSOD crashes but everything seems to be in the clear so far. Thank you so much Arc and Anak for the help over the months! I will certainly give you two reputation any time I can

 

[Arc]

You are welcome mate. We tried, but you have done a real good job

 

[Anak]

Your welcome jm.

Two different sizes? You only have one listed in your system specs, was one a 2GB stick and the other a 1 or 4GB?

When using more than one RAM stick, the rule is to run "matched pairs", and with your board if you only have two you should run both in either the two Beige or two Blue slots.

Refer back to your Gigabyte GA-770TA-UD3 manual and Chapter 1-4-1 Dual Channel Memory Configuration.


In any event it's good to hear you resolved the issue, and thank you for posting back.