Lemur, thanks for the suggestion re: memtest86+, this might sound like a basic question but how do I run memtest86+? Ive downloaded a file and it wants me to make a boot cd from it and use that. Is there a thread or youtube video that can show me how to use this program?
Lucien
Hi and welcome
I know you are having quite a time of it but BSOD's are difficult to diagnose. the one you uploaded was probably caused by something other than the ntkrnlmp listed but it is fairly ambiguous. Keep uploading the dumps as each new one gives us more info.
What service pack are you running?
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Mini101109-02.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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18295.amd64fre.vistasp1_gdr.090721-0152
Machine Name:
Kernel base = 0xfffff800`02056000 PsLoadedModuleList = 0xfffff800`0221bdb0
Debug session time: Sat Oct 10 20:37:50.593 2009 (GMT-4)
System Uptime: 0 days 1:39:54.637
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {493, c, 0, fffff800020c77af}
Probably caused by : ntkrnlmp.exe ( nt!KeReleaseSemaphore+4f )
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: 0000000000000493, memory referenced
Arg2: 000000000000000c, IRQL
Arg3: 0000000000000000, 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: fffff800020c77af, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000227f080
0000000000000493
CURRENT_IRQL: c
FAULTING_IP:
nt!KeReleaseSemaphore+4f
fffff800`020c77af 8b7b04 mov edi,dword ptr [rbx+4]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: WinService.exe
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KeReleaseSemaphore+4f
fffff800`020c77af 8b7b04 mov edi,dword ptr [rbx+4]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KeReleaseSemaphore+4f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a65b149
FAILURE_BUCKET_ID: X64_0xA_nt!KeReleaseSemaphore+4f
BUCKET_ID: X64_0xA_nt!KeReleaseSemaphore+4f
Followup: MachineOwner
---------