BSOD on certain games

[Shintaro]

Could you also please get a screen capture of the following registry key: HKLM\System\CurrentControlSet\Control\CrashControl

 

[SquireJames]

Verifier was off when that dump was created. It's been on since my post indicating I turned it on (the "broken glass" screen occurred when it was turned on) As far as I am aware I have the latest version of Thunderbird. I'll update just in case.

 

[SquireJames]

 

[Shintaro]

You can check if verifier is on by typing in a command window:

verifier /querysettings

The attached image shows that verifier is OFF.

 

[SquireJames]

 

[Shintaro]

Mate,
How are things going? Any further crashes with verifier running?

 

[SquireJames]

Sorry for the late reply. My family came to visit so I was off my PC for a few days.

That same "broken glass" effect occurs on Napoleon Total War, but the PC seems to be behaving itself otherwise (plays Skyrim and so forth with no issues, further indicating that the graphics card seems to be fine)

I guess, for now, we can close this. If I have any further issues on any other games I will make a new thread. At the moment I'll just put it down to NTW being based on a slightly dodgy engine (its predecessor, Empire Total War, was notorious for crashing when first released)

 

[SquireJames]

Right, update time.

I cleared off my ATI Drivers using their driver cleaner tool and reinstalled the latest, as XCOM Enemy Within was choppier than the Bay of Biscay. This solved the choppy performance and everything has been working fine for about 48 hrs. (I had to turn driver verifier off when clearing off the drivers as it kept triggering a bluescreen elsewise)

Now, I just got that broken glass effect again. Pressed and held right CTRL then pressed Scroll Lock twice as per the instructions before (enabled it in my registry some time back). Upon restarting, it bluescreened twice before it successfully rebooted. Here are the two log files from those crashes. I am unsure where the scroll lock triggered log would be stored, if indeed it worked.

 

[Shintaro]

Mate,

The problem appears to be Steam.exe (See below)
However, in your case I would suggest that you try an older video driver, maybe 13.1 HERE is the link.

Get the AMD ATI Clean Uninstall Utility HERE.


_________________________
Composed/Posted with WYSIWYG BBCode Editor

*******************************************************************************
*  *
*  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: fffff800038c7ac5, Address of the instruction which caused the bugcheck
Arg3: fffff8800958cff0, 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!ExpInterlockedPopEntrySListFault16+0
fffff800`038c7ac5 498b08  mov  rcx,qword ptr [r8]

CONTEXT:  fffff8800958cff0 -- (.cxr 0xfffff8800958cff0;r)
rax=0000000005ad0001 rbx=fffff900c47ea538 rcx=fffffa8008d73a60
rdx=ff7ff900c35ba261 rsi=fffffa8008d73a60 rdi=fffff900c47ea290
rip=fffff800038c7ac5 rsp=fffff8800958d9d0 rbp=fffff8800958dca0
 r8=ff7ff900c35ba260  r9=fffff900c47ea648 r10=fffffa8008d73a60
r11=fffff900c0c059f0 r12=0000000000000001 r13=fffff8800958dbd8
r14=00000000000025ff r15=0000000000000000
iopl=0  nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b  efl=00010286
nt!ExpInterlockedPopEntrySListFault16:
fffff800`038c7ac5 498b08  mov  rcx,qword ptr [r8] ds:002b:ff7ff900`c35ba260=????????????????
Last set context:
rax=0000000005ad0001 rbx=fffff900c47ea538 rcx=fffffa8008d73a60
rdx=ff7ff900c35ba261 rsi=fffffa8008d73a60 rdi=fffff900c47ea290
rip=fffff800038c7ac5 rsp=fffff8800958d9d0 rbp=fffff8800958dca0
 r8=ff7ff900c35ba260  r9=fffff900c47ea648 r10=fffffa8008d73a60
r11=fffff900c0c059f0 r12=0000000000000001 r13=fffff8800958dbd8
r14=00000000000025ff r15=0000000000000000
iopl=0  nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b  efl=00010286
nt!ExpInterlockedPopEntrySListFault16:
fffff800`038c7ac5 498b08  mov  rcx,qword ptr [r8] ds:002b:ff7ff900`c35ba260=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800038c7ac5

STACK_TEXT:  
fffff880`0958d9d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16


FOLLOWUP_IP:
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`038c7ac5 498b08  mov  rcx,qword ptr [r8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExpInterlockedPopEntrySListFault16+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb

IMAGE_VERSION:  6.1.7601.18409

STACK_COMMAND:  .cxr 0xfffff8800958cff0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0

BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_nt!expinterlockedpopentryslistfault16+0

FAILURE_ID_HASH:  {b390bf2a-9c11-079f-34b0-5dffcabffe4b}

 

[SquireJames]

Not much I can do about Steam unfortunately. If that is the same source of the crash with Napoleon Total War, I'm a bit snookered. These things only run with Steam in the background.

I will try an older driver if it continues, but out of interest, why do you think an older driver (especially that one) will solve the problem? Is my card incompatible with more modern drivers?

 

[Shintaro]

Mate,

Sometimes there are changes in the drivers but not in the game software. For example a game might test their software against a particular driver version prior to shipping. But a short time later the video card manufacturer will release a driver that the game testers haven't vetted.
So it *might* work for one game but not another. So we are trying to find a happy medium.