New
#1
BSOD Analysis Needed
Hey, title says it all. Was gone for about a week, when I came home, my computer ran for about 2-3 hours and then the blue screens started. Have been getting them upon reboot and within 5-10 min of reboot. Here is my analysis...
All help is greatly appreciated, in a time pinch! Thanks everyone.Code:******************************************************************************* * * * 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: 00000000000600dd, 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: fffff80002efe0c5, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fd100 00000000000600dd CURRENT_IRQL: 2 FAULTING_IP: nt!KeStackAttachProcess+115 fffff800`02efe0c5 f00fc186dc000000 lock xadd dword ptr [rsi+0DCh],eax CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff88008992770 -- (.trap 0xfffff88008992770) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000008 rbx=0000000000000000 rcx=fffffa800c36c0a0 rdx=fffff88008992a58 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002efe0c5 rsp=fffff88008992900 rbp=fffff88008992a58 r8=fffffa800c36c090 r9=0000000000000130 r10=fffff880033d80c0 r11=fffffa800c36c040 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KeStackAttachProcess+0x115: fffff800`02efe0c5 f00fc186dc000000 lock xadd dword ptr [rsi+0DCh],eax ds:3e30:00000000`000000dc=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ecd569 to fffff80002ecdfc0 STACK_TEXT: fffff880`08992628 fffff800`02ecd569 : 00000000`0000000a 00000000`000600dd 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`08992630 fffff800`02ecc1e0 : fffff880`089927b0 fffff8a0`0cef3e30 00000000`00000039 fffffa80`0c36c040 : nt!KiBugCheckDispatch+0x69 fffff880`08992770 fffff800`02efe0c5 : 00000000`00000000 fffffa80`0c36c040 fffffa80`0c36c040 fffff800`0319c8e3 : nt!KiPageFault+0x260 fffff880`08992900 fffffa80`0a2f49c8 : fffff880`08992a80 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeStackAttachProcess+0x115 fffff880`08992980 fffff880`08992a80 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0a2f49c8 fffff880`08992988 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`08992a80 STACK_COMMAND: kb FOLLOWUP_IP: nt!KeStackAttachProcess+115 fffff800`02efe0c5 f00fc186dc000000 lock xadd dword ptr [rsi+0DCh],eax SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KeStackAttachProcess+115 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be FAILURE_BUCKET_ID: X64_0xA_nt!KeStackAttachProcess+115 BUCKET_ID: X64_0xA_nt!KeStackAttachProcess+115 Followup: MachineOwner ---------
Rob
Last edited by Rmont11b; 28 Nov 2012 at 20:12. Reason: Adding the Zip file.