Look at this blue screen dump and tell me what you think

[Nebor]

So I've had a persistent, totally random blue screen problem ever since going from Vista 32 to Vista 64-bit. I read the dump file and found this:
*******************************************************************************
* *
* 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: fffff80001ee28a4, Address of the exception record for the exception that caused the bugcheck
Arg3: fffffa600c729990, 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!CmpCacheLookup+3d6
fffff800`01ee28a4 488b02 mov rax,qword ptr [rdx]

CONTEXT: fffffa600c729990 -- (.cxr 0xfffffa600c729990)
rax=f08b44ffdde78be8 rbx=0000000000000000 rcx=0000000000000ad1
rdx=f08b44ffdde7e270 rsi=fffffa600c72a840 rdi=fffff88000908808
rip=fffff80001ee28a4 rsp=fffffa600c72a1f0 rbp=000000000000039b
r8=000000003c4c5da2 r9=0000000000000006 r10=0000000000000000
r11=000000003c4c5da2 r12=0000000000000003 r13=fffffa600c72a320
r14=fffff88000031108 r15=fffff88000031108
iopl=0 nv up ei pl nz ac pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010212
nt!CmpCacheLookup+0x3d6:
fffff800`01ee28a4 488b02 mov rax,qword ptr [rdx] ds:002b:f08b44ff`dde7e270=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: SearchIndexer.e

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80001ee3295 to fffff80001ee28a4

STACK_TEXT:
fffffa60`0c72a1f0 fffff800`01ee3295 : fffffa60`0c72a330 fffffa60`00000005 fffffa60`0c72a770 fffffa60`0c72a750 : nt!CmpCacheLookup+0x3d6
fffffa60`0c72a2d0 fffff800`01ee3c6a : fffffa60`0c72ab70 fffffa60`0c72a750 fffffa60`0c72a740 fffffa60`0c72a758 : nt!CmpBuildHashStackAndLookupCache+0x276
fffffa60`0c72a670 fffff800`01ef4c4e : 00000000`00000040 00000000`00000000 fffffa80`07fb0b10 fffffa80`05bc0001 : nt!CmpParseKey+0x20a
fffffa60`0c72a910 fffff800`01ef8e54 : 00000000`00000018 fffffa80`075f9a01 00000000`00000040 fffffa80`0189b140 : nt!ObpLookupObjectName+0x2ce
fffffa60`0c72aa20 fffff800`01edee3f : 00023149`00000001 00000000`00000000 0008859c`00034a01 00000000`14853bc2 : nt!ObOpenObjectByName+0x2f4
fffffa60`0c72aaf0 fffff800`01c72e33 : 00000000`063fecf0 00000000`00000001 00000000`063feb70 00000000`00000000 : nt!CmOpenKey+0x25d
fffffa60`0c72ac20 00000000`77845b9a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`063feb28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77845b9a


FOLLOWUP_IP:
nt!CmpCacheLookup+3d6
fffff800`01ee28a4 488b02 mov rax,qword ptr [rdx]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!CmpCacheLookup+3d6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4812c3f7

STACK_COMMAND: .cxr 0xfffffa600c729990 ; kb

FAILURE_BUCKET_ID: X64_0x3B_nt!CmpCacheLookup+3d6

BUCKET_ID: X64_0x3B_nt!CmpCacheLookup+3d6



Now it seems to me that Windows Searchindexer.exe is at fault. Is that what you guys are seeing?

 

[Nebor]

Ok so I looked at several of the other dump files, and it looks like the process name is different for every one, Ex:

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80001c47d25

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: audiodg.exe

CURRENT_IRQL: 0

EXCEPTION_RECORD: fffffa600ad23428 -- (.exr 0xfffffa600ad23428)
ExceptionAddress: fffff80001c832ed (nt!RtlVirtualUnwind+0x000000000000025d)
ExceptionCode: 10000004
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000002e1

TRAP_FRAME: fffffa600ad234d0 -- (.trap 0xfffffa600ad234d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000050 rbx=01030279015d0225 rcx=0000000000000004
rdx=00000000000002e1 rsi=004c04ba00680421 rdi=0091038a00c202f1
rip=fffff80001c832ed rsp=fffffa600ad23660 rbp=0000000000000233
r8=0000000000000006 r9=fffff80001c1b000 r10=0000000000000191
r11=fffff80001e1a000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!RtlVirtualUnwind+0x25d:
fffff800`01c832ed 488b02 mov rax,qword ptr [rdx] ds:025e:00000000`000002e1=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001c7012e to fffff80001c70390

STACK_TEXT:
fffff800`02f84d28 fffff800`01c7012e : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`02f84d30 fffff800`01c6e978 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffff800`02f84e70 fffff800`01c47d25 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb8
fffffa60`0ad22cf0 fffff800`01c701e9 : fffffa60`0ad23428 00000000`00000001 fffffa60`0ad234d0 fffffa60`0ad238a0 : nt!KiDispatchException+0x35
fffffa60`0ad232f0 fffff800`01c6efe5 : 00000000`00000000 00d4048e`fffe03d2 022b0553`01950500 00000000`00000001 : nt!KiExceptionDispatch+0xa9
fffffa60`0ad234d0 fffff800`01c832ed : fffffa60`0ad244f8 fffffa60`0ad23ed0 fffff800`01d667e0 fffff800`01c1b000 : nt!KiPageFault+0x1e5
fffffa60`0ad23660 fffff800`01c8abd8 : fffffa60`00000001 00000000`00000000 fed6f7f4`00000000 00000000`00000191 : nt!RtlVirtualUnwind+0x25d
fffffa60`0ad236d0 fffff800`01c47db3 : fffffa60`0ad244f8 fffffa60`0ad23ed0 00000000`00000000 fffffa60`0ad245a0 : nt!RtlDispatchException+0x118
fffffa60`0ad23dc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0xc3


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b8
fffff800`01c6e978 90 nop

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiDoubleFaultAbort+b8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 479192b7

FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b8

BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b8



--------------------------------------------------'



But they all say VISTA_DRIVER_FAULT. Anybody have any ideas?

 

[Markbnj]

If these are random crashes then I think it points to either: a BIOS incompatibility; a processor error; or overheating/electrical problems.

Do you overclock? Is it a dual core machine?

 

[Nebor]

Originally posted by: Markbnj
If these are random crashes then I think it points to either: a BIOS incompatibility; a processor error; or overheating/electrical problems.

Do you overclock? Is it a dual core machine?

It is a dual core machine, an e6600 processor. I do not overclock. BIOS incompatibility sounds possible. Temperatures are fine, and voltages from the Antec 500w PS look solid.

 

[Markbnj]

I'd check the BIOS version then, and see if there's an update for Vista. All the results I was able to find searching for this pointed to Microsoft saying it was a hardware issue.

 

[Nebor]

Originally posted by: Markbnj
I'd check the BIOS version then, and see if there's an update for Vista. All the results I was able to find searching for this pointed to Microsoft saying it was a hardware issue.

Are there Vista specific BIOS versions? The motherboard is an Abit AW9D MAX. Pretty sure the box said "Made for Windows Vista" or some such non-sense.

I updated the bios a couple months ago, possibly around the time I started having these problems.

 

[Markbnj]

Originally posted by: Nebor

Originally posted by: Markbnj
I'd check the BIOS version then, and see if there's an update for Vista. All the results I was able to find searching for this pointed to Microsoft saying it was a hardware issue.

Are there Vista specific BIOS versions? The motherboard is an Abit AW9D MAX. Pretty sure the box said "Made for Windows Vista" or some such non-sense.

I updated the bios a couple months ago, possibly around the time I started having these problems.

I don't know, but I wouldn't be surprised. There used to be issues with some BIOS's and multiple cores too, as well as timing issues between cores in the app layer, but if you updated the BIOS not long ago I'm sure you're past all that. About all I can say from what I could find is that it's likely a hardware issue. You might try running memtest overnight to make sure everything is good there.