Hi
I just got a BSOD and I would like to know if anyone can help me about this.
I replaced a faulty GPU one week ago so it may be linked.
Update: I forgot to mention that this happened while is was browsing on firefox.
Please help!!
I analyzed it with WinDbg and got the following:
Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*
http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02e1e000 PsLoadedModuleList = 0xfffff800`03061890
Debug session time: Sun Oct 12 13:47:51.736 2014 (UTC - 4:00)
System Uptime: 0 days 3:30:38.011
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd4018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {10060000a, 2, 1, fffff80002ec4622}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
Followup: MachineOwner
---------
6: 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: 000000010060000a, 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: fffff80002ec4622, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 000000010060000a
CURRENT_IRQL: 2
FAULTING_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`02ec4622 48890a mov qword ptr [rdx],rcx
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: services.exe
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
TRAP_FRAME: fffff88006fc7820 -- (.trap 0xfffff88006fc7820)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88006fc7a28
rdx=000000010060000a rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ec4622 rsp=fffff88006fc79b0 rbp=fffff88006fc7b60
r8=fffffa800e441218 r9=0000000000000000 r10=ffffffffffffffbf
r11=fffffa800ecd2601 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KxWaitForLockOwnerShip+0x12:
fffff800`02ec4622 48890a mov qword ptr [rdx],rcx ds:00000001`0060000a=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e93169 to fffff80002e93bc0
STACK_TEXT:
fffff880`06fc76d8 fffff800`02e93169 : 00000000`0000000a 00000001`0060000a 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`06fc76e0 fffff800`02e91de0 : fffffa80`0e3f4b50 fffff880`06fc7a90 00000000`ffff0000 fffffa80`0e430a00 : nt!KiBugCheckDispatch+0x69
fffff880`06fc7820 fffff800`02ec4622 : 00000000`00000000 fffffa80`0e420ad0 00000000`0233fcb0 fffff880`06fc7aa0 : nt!KiPageFault+0x260
fffff880`06fc79b0 fffff800`02e7ef9c : fffffa80`0e430a00 fffff880`06fc7a68 fffff880`06fc7a88 00000000`00000001 : nt!KxWaitForLockOwnerShip+0x12
fffff880`06fc79e0 fffff800`02e92e53 : fffffa80`0f375060 00000000`770145c0 fffff880`00000102 00000000`00000000 : nt!NtWaitForWorkViaWorkerFactory+0x41b
fffff880`06fc7ae0 00000000`76f62bba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0233fac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f62bba
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`02ec4622 48890a mov qword ptr [rdx],rcx
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KxWaitForLockOwnerShip+12
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb
IMAGE_VERSION: 6.1.7601.18409
FAILURE_BUCKET_ID: X64_0xA_nt!KxWaitForLockOwnerShip+12
BUCKET_ID: X64_0xA_nt!KxWaitForLockOwnerShip+12
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xa_nt!kxwaitforlockownership+12
FAILURE_ID_HASH: {69f619cc-5abb-1c14-4270-8e17efbcd182}
Followup: MachineOwner
---------