Getting a blue screen of death!

I've been getting a blue screen of death. It started pretty recently and seemingly randomly. Here's the minidump.

crashdump

Some extra details:

We tested the ram, there was nothing wrong with it (as of yesterday anyway). The problem had occurred with updated video drivers, following advice saying that Dragon Age was crashing with the latest nVidia drivers and to roll back, we rolled back to 90 drivers as opposed to the 95 drivers.

Starting to think it's the HD dying. I've since gotten a Page Fault BSOD and a memory management error. Gonna try ghosting to a new HD and see if that solves it. The HD in there is one salvaged from a computer that was hit by lightning.

Coridan said:

I've been getting a blue screen of death. It started pretty recently and seemingly randomly. Here's the minidump.

crashdump

Hi and welcome.

I took a quick look at your dmp while we are waiting for an expert at this I noticed a couple of things
First, several drivers are more than 3 years old and need to be updated. Second this dump probably was caused bu indexing, and it took ntkrnl with it.

I would update the drivers

Since a system file was involved I would run a system file check to verify and repair system files
to run type cmd in search>right click and run as admin>sfc /scannow.

As usual
If you are overclocking stop
if you have a raid update its driver

downloading memtestx86 might be called for and should be run for several hours

If you have any more bsod upload the dmp

Hope this helps


Ken J+








ASACPI.sys fffff880`02be5000 fffff880`02bed000 0x00008000 0x42476c4c 3/27/2005 9:30:36 PM
secdrv.SYS fffff880`08731000 fffff880`0873c000 0x0000b000 0x4508052e 9/13/2006 8:18:38 AM
speedfan.sys fffff880`01883000 fffff880`0188a000 0x00007000 0x45168798 9/24/2006 8:26:48 AM
x10ufx2.sys fffff880`04087000 fffff880`04093000 0x0000c000 0x456f66db 11/30/2006 6:18:51 PM



Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\120109-25084-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`01a57000 PsLoadedModuleList = 0xfffff800`01c94e50
Debug session time: Tue Dec 1 09:11:52.430 2009 (GMT-5)
System Uptime: 0 days 0:05:38.242
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8000000028, 2, 1, fffff80001adfd79}

Probably caused by : ntkrnlmp.exe ( nt!KeReleaseSemaphore+329 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000008000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80001adfd79, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001cff0e0
0000008000000028

CURRENT_IRQL: 2

FAULTING_IP:
nt!KeReleaseSemaphore+329
fffff800`01adfd79 f083402801 lock add dword ptr [rax+28h],1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: SearchIndexer.

TRAP_FRAME: fffff8800a803790 -- (.trap 0xfffff8800a803790)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000008000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001adfd79 rsp=fffff8800a803920 rbp=fffffa8006038f28
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffff8a00601ee00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KeReleaseSemaphore+0x329:
fffff800`01adfd79 f083402801 lock add dword ptr [rax+28h],1 ds:00000080`00000028=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001ac8469 to fffff80001ac8f00

STACK_TEXT:
fffff880`0a803648 fffff800`01ac8469 : 00000000`0000000a 00000080`00000028 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a803650 fffff800`01ac70e0 : 00000000`00000000 fffffa80`06038f20 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0a803790 fffff800`01adfd79 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0a803920 fffff800`01dc74d4 : fffffa80`00000000 fffff8a0`00000001 00000000`00000000 fffff8a0`0601ed00 : nt!KeReleaseSemaphore+0x329
fffff880`0a8039a0 fffff800`01dc593e : 00000000`00000000 00000000`00000000 89800000`0010001b fffff880`0a803a10 : nt!AlpcpCompleteDispatchMessage+0x9a4
fffff880`0a803a30 fffff800`01dc5f4f : fffffa80`00010000 fffff8a0`01669118 00000000`00000001 fffff880`00000000 : nt!AlpcpDispatchNewMessage+0x24e
fffff880`0a803a90 fffff800`01db2de7 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000001 : nt!AlpcpSendMessage+0x4ad
fffff880`0a803b90 fffff800`01ac8153 : fffffa80`04fd9b60 fffff880`0a803ca0 fffffa80`05fc65f0 00000000`00000000 : nt!NtRequestPort+0x9f
fffff880`0a803c20 00000000`770012ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`04c4f628 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770012ea


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KeReleaseSemaphore+329
fffff800`01adfd79 f083402801 lock add dword ptr [rax+28h],1

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KeReleaseSemaphore+329

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

FAILURE_BUCKET_ID: X64_0xA_nt!KeReleaseSemaphore+329

BUCKET_ID: X64_0xA_nt!KeReleaseSemaphore+329

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

Here is all the mini dumps from today

Minidump

As for the 3 year old drivers, those are all accounted for and irrelevant drivers (one is for ATI Remote wonder for example) There were no driver changes before the crashes started to occur (we have since updated some to try and solve it, to no avail.)

Hi Coridan.

This is your problem:

ASACPI ASACPI.sys Sun Mar 27 22:30:36 2005
speedfan speedfan.sys Sun Sep 24 09:26:48 2006

Update to a 2009 driver for those or uninstall the apps that installed them. The first one is a motherboard utility driver, ATK0110.