View Single Post
27 Dec 2010  
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Your latest four dumps are all error code A, IRQL_NOT_LESS_OR_EQUAL. Usual causes are Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility. All of your drivers appear to be up to date. The dumps blame the Windows system core file, which is highly unlikely to be the real cause.

You ran Memtest and it found no errors. This indicates your RAM is probably OK. Memtest nor any other test is 100% accurate. Did you run Memtest from a cold boot after your computer had been off for a while? Most of your crashes are occurring shortly after booting up. This can indicate a power problem. Do you get the same BSOD's on battery as well as plugged in? Try booting in the safe mode. Do you get BSOD's?

Try enabling Driver Verifier following the instructions in this tutorial: Driver Verifier - Enable and Disable. If Driver Verifier encounters a faulty driver, it will trigger a BSOD. Upload any and all Verifier enabled dumps.
Code:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02057000 PsLoadedModuleList = 0xfffff800`0228beb0
Debug session time: Mon Dec 27 02:18:51.916 2010 (GMT-5)
System Uptime: 0 days 0:00:33.416
Loading Kernel Symbols
...............................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff800020e0998}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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: 0000000000000000, 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: fffff800020e0998, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800022f60e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!IopCompleteRequest+c85
fffff800`020e0998 488908          mov     qword ptr [rax],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  WerFault.exe

IRP_ADDRESS:  ffffffffffffff88

TRAP_FRAME:  fffff88003893600 -- (.trap 0xfffff88003893600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80055673c0
rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000200 rsp=fffff88003893790 rbp=fffff88003893c20
 r8=0000000000000000  r9=0000000000007e00 r10=000000000000000e
r11=fffffa8003cab1f6 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
0090:00000000`00000200 ??              ???
Resetting default scope

EXCEPTION_RECORD:  fffff88003893558 -- (.exr 0xfffff88003893558)
ExceptionAddress: 0000000000000000
   ExceptionCode: 10000004
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 0000000000000000

LAST_CONTROL_TRANSFER:  from fffff800020bcae9 to fffff800020bd580

STACK_TEXT:  
fffff880`03892798 fffff800`020bcae9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`038927a0 fffff800`020bb760 : 00000000`00000001 00000000`00000000 00000000`001fff00 fffffa80`05bc4650 : nt!KiBugCheckDispatch+0x69
fffff880`038928e0 fffff800`020e0998 : fffffa80`05ad7b60 00000000`00000001 00000000`00000001 fffff800`021b2596 : nt!KiPageFault+0x260
fffff880`03892a70 fffff800`0209858f : 00000000`00000000 fffff800`0209a544 fffffa80`05ad0500 00000000`00000000 : nt!IopCompleteRequest+0xc85
fffff880`03892b40 fffff800`02098957 : fffff880`03892dc0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`03892bc0 fffff800`020fe558 : 00000000`00000000 fffff800`020fcb41 fffff880`038930c0 fffff880`038935d0 : nt!KiApcInterrupt+0xd7
fffff880`03892d50 fffff800`020fe6d5 : fffff880`03893558 fffff880`038932c0 fffff880`03893600 fffffa80`055673c0 : nt!KeContextFromKframes+0x398
fffff880`03892d90 fffff800`020bcbc2 : fffff880`03893558 00000000`00000000 fffff880`03893600 fffff8a0`01aac030 : nt!KiDispatchException+0x105
fffff880`03893420 fffff800`020bb73a : 00000000`00000008 00000000`00000000 00000000`00010000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`03893600 00000000`00000200 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
fffff880`03893790 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x200


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`020bb760 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c42e3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260

BUCKET_ID:  X64_0xA_nt!KiPageFault+260

Followup: MachineOwner
---------
My System SpecsSystem Spec