Random BSOD

[Dancer]

I seem to get a BSOD every now and then and it seems to happen more often when I use dual displays or extend my desktop across the HDMI. Each time it has happened while watching a video, but only after a long while and then replaying the same video it is fine again.

I've run hd scans and will try memtest now. I've tried looking at the memory dump, but I'm no expert and not sure what to make of it. Seems ntkrnlmp.exe
is the culprit, but I've got a feeling it is the symptom and not the cause. Anyone spot anything?

Short version:

BugCheck 1E, {ffffffffc0000005, fffff80002a89037, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!SepAccessCheck+127 )

Details:

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

FAULTING_IP:
nt!SepAccessCheck+127
fffff800`02a89037 66837b0400 cmp word ptr [rbx+4],0

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: ffffffffffffffff

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: System

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff80000b9af18 -- (.exr 0xfffff80000b9af18)
ExceptionAddress: fffff80002a89037 (nt!SepAccessCheck+0x0000000000000127)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff80000b9afc0 -- (.trap 0xfffff80000b9afc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000004 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a89037 rsp=fffff80000b9b158 rbp=fffff80000b9b398
r8=0000000000000001 r9=0000000b00040001 r10=0000000000000002
r11=fffff80002bfde80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!SepAccessCheck+0x127:
fffff800`02a89037 66837b0400 cmp word ptr [rbx+4],0 ds:00000000`00000004=????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002abd929 to fffff80002a83600

STACK_TEXT:
fffff800`00b9a748 fffff800`02abd929 : 00000000`0000001e ffffffff`c0000005 fffff800`02a89037 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9a750 fffff800`02a82c42 : fffff800`00b9af18 3f3f3f3f`3f3f3f3f fffff800`00b9afc0 00000000`00026930 : nt!KiDispatchException+0x1b9
fffff800`00b9ade0 fffff800`02a8154a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00b9afc0 fffff800`02a89037 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9b158 fffff800`02a88b10 : fffff800`02bd11c0 fffff800`00b9c4a0 fffff800`00b9c4a0 fffff800`00b9c1d8 : nt!SepAccessCheck+0x127
fffff800`00b9b288 fffff800`02bd1194 : fffff800`00b9b3a8 fffff800`00b9c208 fffff800`02a13000 fffff800`02bd1194 : nt!SeAccessCheckWithHint+0x180
fffff800`00b9b368 fffff800`00b9b3a8 : fffff800`00b9c208 fffff800`02a13000 fffff800`02bd1194 fffff800`00b9b8e0 : nt!_imp_NtOpenSymbolicLinkObject+0x6cac
fffff800`00b9b370 fffff800`00b9c208 : fffff800`02a13000 fffff800`02bd1194 fffff800`00b9b8e0 00000000`00000000 : 0xfffff800`00b9b3a8
fffff800`00b9b378 fffff800`02a13000 : fffff800`02bd1194 fffff800`00b9b8e0 00000000`00000000 fffff800`02c8ccc8 : 0xfffff800`00b9c208
fffff800`00b9b380 fffff800`02bd1194 : fffff800`00b9b8e0 00000000`00000000 fffff800`02c8ccc8 fffff800`00b9c4a0 : nt!MmIsSessionAddress <PERF> (nt+0x0)
fffff800`00b9b388 fffff800`00b9b8e0 : 00000000`00000000 fffff800`02c8ccc8 fffff800`00b9c4a0 fffff800`02a13000 : nt!_imp_NtOpenSymbolicLinkObject+0x6cac
fffff800`00b9b390 00000000`00000000 : fffff800`02c8ccc8 fffff800`00b9c4a0 fffff800`02a13000 fffff800`02bd1194 : 0xfffff800`00b9b8e0


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!SepAccessCheck+127
fffff800`02a89037 66837b0400 cmp word ptr [rbx+4],0

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!SepAccessCheck+127

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x1E_nt!SepAccessCheck+127

BUCKET_ID: X64_0x1E_nt!SepAccessCheck+127

 

[mattyfez]

You could try a windows repair by booting from a windows disk, a scandisk /r and an SFC command in CMD.

Thats kinda stabbing in the dark though but will rule out a lot of things, any window files that are corrupt/overwritten will be replaced with new ones.
Obvioulsly update your graphics drivers and memtest may may come up with something.

Have you googled/looked in MS KB for that stopcode, may give you more of a clue as to what the issue is.

 

[mattyfez]

A quick google, as always with stopcodes throws up all sorts of potential answers, but I would updates all drivers motherboard etc, , run the above repairs, and if it comes to it, then a BIOS flash to the latest version has been mentioned on some posts ive seen..

I would suspect a driver issue or a corrupt windows file(s) to be the culprit

 

[Dancer]

I agree that driver issue seems most likely. Just ran one pass of memtest with no errors (will do overnight test, but don't expect to find anything).

I have catalyst 10.3 and although there is 10.4 now I am hesitant as I had to tweak my overdrive settings to stop freeze crashes while playing (like a lot of people) and I'm just worried upgrading could re-introduce those problems.

Windows 7 is up-to-date and my bios is upgraded to F2. I see there is a brand new F4 version for the bios, but in the notes all it mentions is "added support for 6 core AMD processors" which is not something I need, so again don't know if its worth it...

 

[mattyfez]

In that case, I would run the above mentioned scans if you are inclined, and that should purge any issues with the OS, otherwise it looks like graphics drivers.