New
#1
BSOD from nowhere
Hey,
My Win 7 64 crushed
I had two BSODs in the last week. Checked the dump file from the first time just now.
Here are the results.
Any clue...?
=====================
This is from today:
Loading Dump File [C:\Windows\Minidump\Subfolder\122710-44444-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e1d000 PsLoadedModuleList = 0xfffff800`0305ae50
Debug session time: Mon Dec 27 22:08:02.842 2010 (UTC + 2:00)
System Uptime: 1 days 18:17:19.680
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {9a, 3880, 2, 0}
Unable to load image \SystemRoot\system32\DRIVERS\iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : iaStor.sys ( iaStor+2d990 )
Followup: MachineOwner
---------
2: kd> !analyza -v
No export analyza found
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 000000000000009a,
Arg2: 0000000000003880
Arg3: 0000000000000002
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_9a
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002f1d32f to fffff80002e8d740
STACK_TEXT:
fffff880`03393a38 fffff800`02f1d32f : 00000000`0000004e 00000000`0000009a 00000000`00003880 00000000`00000002 : nt!KeBugCheckEx
fffff880`03393a40 fffff800`02f01eb5 : fffffa80`0763e1a0 fffffa80`0785ade8 fffff880`03e40200 00000000`00000000 : nt!MiBadRefCount+0x4f
fffff880`03393a80 fffff800`02e8fae8 : 00000000`00008043 00000000`00000000 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34910
fffff880`03393b10 fffff880`01237990 : fffffa80`0daa53c0 fffffa80`0d63d600 fffffa80`044c5cf0 00000000`00000000 : nt!IopfCompleteRequest+0x168
fffff880`03393bf0 fffffa80`0daa53c0 : fffffa80`0d63d600 fffffa80`044c5cf0 00000000`00000000 fffff880`03393ef8 : iaStor+0x2d990
fffff880`03393bf8 fffffa80`0d63d600 : fffffa80`044c5cf0 00000000`00000000 fffff880`03393ef8 fffff880`01213e7d : 0xfffffa80`0daa53c0
fffff880`03393c00 fffffa80`044c5cf0 : 00000000`00000000 fffff880`03393ef8 fffff880`01213e7d fffffa80`04de4dc0 : 0xfffffa80`0d63d600
fffff880`03393c08 00000000`00000000 : fffff880`03393ef8 fffff880`01213e7d fffffa80`04de4dc0 fffff880`03393cd0 : 0xfffffa80`044c5cf0
STACK_COMMAND: kb
FOLLOWUP_IP:
iaStor+2d990
fffff880`01237990 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: iaStor+2d990
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: iaStor
IMAGE_NAME: iaStor.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b2a7b77
FAILURE_BUCKET_ID: X64_0x4E_9a_iaStor+2d990
BUCKET_ID: X64_0x4E_9a_iaStor+2d990
Followup: MachineOwner
---------
===========================================================
===========================================================
This is the first one
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: 0000000000000088, 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: fffff80002e9afae, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f30e0
0000000000000088
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeInsertQueueApc+42
fffff800`02e9afae f0480fbaab8800000000 lock bts qword ptr [rbx+88h],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
TRAP_FRAME: fffff88003393920 -- (.trap 0xfffff88003393920)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa80100db318
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e9afae rsp=fffff88003393ab0 rbp=0000000000000002
r8=0000000000000000 r9=0000000000000000 r10=fffffa8006e7bb30
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KeInsertQueueApc+0x42:
fffff800`02e9afae f0480fbaab8800000000 lock bts qword ptr [rbx+88h],0 ds:00000000`00000088=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ebaca9 to fffff80002ebb740
STACK_TEXT:
fffff880`033937d8 fffff800`02ebaca9 : 00000000`0000000a 00000000`00000088 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`033937e0 fffff800`02eb9920 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffeb64`363b1d64 : nt!KiBugCheckDispatch+0x69
fffff880`03393920 fffff800`02e9afae : fffffa80`04dbf200 00000002`00000046 fffffa80`04db8c80 00000000`00000000 : nt!KiPageFault+0x260
fffff880`03393ab0 fffff800`02ebe55b : 00000000`00000000 00000000`a000000c 00000000`00000000 00000000`00000000 : nt!KeInsertQueueApc+0x42
fffff880`03393b10 fffff880`0122e990 : fffffa80`0ba6bee0 fffffa80`100db200 fffffa80`08e04010 00000000`00000000 : nt!IopfCompleteRequest+0xbdb
fffff880`03393bf0 fffffa80`0ba6bee0 : fffffa80`100db200 fffffa80`08e04010 00000000`00000000 fffff880`03393ef8 : iaStor+0x2d990
fffff880`03393bf8 fffffa80`100db200 : fffffa80`08e04010 00000000`00000000 fffff880`03393ef8 fffff880`0120ae7d : 0xfffffa80`0ba6bee0
fffff880`03393c00 fffffa80`08e04010 : 00000000`00000000 fffff880`03393ef8 fffff880`0120ae7d fffffa80`04db8dc0 : 0xfffffa80`100db200
fffff880`03393c08 00000000`00000000 : fffff880`03393ef8 fffff880`0120ae7d fffffa80`04db8dc0 fffff880`03393cd0 : 0xfffffa80`08e04010
STACK_COMMAND: kb
FOLLOWUP_IP:
iaStor+2d990
fffff880`0122e990 ?? ???
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: iaStor+2d990
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: iaStor
IMAGE_NAME: iaStor.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b2a7b77
FAILURE_BUCKET_ID: X64_0xA_iaStor+2d990
BUCKET_ID: X64_0xA_iaStor+2d990
Followup: MachineOwner
---------