Windows Vista Repeated IRQL Problem In Vista 64..posting logs

I am repeatedly getting an IRQL Not less or equal BSOD. I have checked my memory over night using memtest86+ and then again with mem test built into vista. This is driving me crazy. Here is as much info as I have at this time. Any ideas would be greatly appreciated.

BSOD Error

IRQL Not Less or Equal
*** Stop: 0x0000000A (0xFFFFFA7FFFFFF3EA, 0x0000000000000002, 0x0000000000000000, 0xFFFFF80001887988)

System Specs

Alienware Area 51 7500
Asus P5N32 Sli Deluxe "Nforce 4 Sli Intel Chipset "
Core 2 Duo 2.67 E6700
4 GB Patriot DD2 6400
2 WD Raptors 150GB Raid 0
Nvidia Geforce 7950GX2
750 Power Supply
Windows Vista Ultimate 64


Microsoft (R) Windows Debugger Version 6.7.0005.0
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Theodore Tomita III\Desktop\Mini050607-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: set _NT_SYMBOL_PATH=srv*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16386.amd64fre.vista_rtm.061101-2205
Kernel base = 0xfffff800`01800000 PsLoadedModuleList = 0xfffff800`01999e90
Debug session time: Sun May 6 17:54:51.556 2007 (GMT-4)
System Uptime: 0 days 0:14:22.495
Loading Kernel Symbols
........................................................................................................................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa7ffffff3ea, 2, 0, fffff80001887988}

Probably caused by : memory_corruption ( nt!MiRemovePageByColor+48 )

Followup: MachineOwner
---------

0: 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: fffffa7ffffff3ea, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80001887988, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800019f90b0
fffffa7ffffff3ea

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRemovePageByColor+48
fffff800`01887988 8a431a mov al,byte ptr [rbx+1Ah]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: ehshell.exe

TRAP_FRAME: fffff980156f5740 -- (.trap 0xfffff980156f5740)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000058000000000 rbx=fffff6fb00000000 rcx=ffffffffffffffbf
rdx=0000000000000023 rsi=0000000000000000 rdi=fffff980156f58b8
rip=fffff80001887988 rsp=fffff980156f58d0 rbp=0000000000000000
r8=000000000000003f r9=0000000000000001 r10=0000000000000006
r11=000000000000a204 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nt!MiRemovePageByColor+0x48:
fffff800`01887988 8a431a mov al,byte ptr [rbx+1Ah] ds:5790:fffff6fb`0000001a=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000184dff3 to fffff8000184e250

STACK_TEXT:
fffff980`156f55f8 fffff800`0184dff3 : 00000000`0000000a fffffa7f`fffff3ea 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff980`156f5600 fffff800`0184cecb : 00000000`00000000 00000000`00000023 fffff6fb`41ffad00 00000000`0000000c : nt!KiBugCheckDispatch+0x73
fffff980`156f5740 fffff800`01887988 : fffff700`00081000 fffff800`01893d4f cd7bfa80`04ce9420 fffffa80`08acfe20 : nt!KiPageFault+0x20b
fffff980`156f58d0 fffff800`01872484 : 00000000`00000023 00000000`00000000 fffffa80`03c00600 00000001`179a6000 : nt!MiRemovePageByColor+0x48
fffff980`156f5900 fffff800`01856c6d : 00000000`00000005 fffff980`0009e000 fffff6fb`41ff9f38 00000000`003ff3e7 : nt!MiRemovePageZeroPreferred+0x114
fffff980`156f5940 fffff800`01863688 : 00000000`00000001 fffff683`ff3e7d00 fffff980`0009e000 00000000`00003000 : nt!MiResolveDemandZeroFault+0x3cd
fffff980`156f59d0 fffff800`01855564 : 00000580`00000000 fffff683`ff3e7d00 00000000`00000000 fffff980`00000000 : nt!MiDispatchFault+0xb51
fffff980`156f5b20 fffff800`0184cdd9 : 00000000`00000001 00000000`00000063 000007fe`99c00001 fffffa80`00008000 : nt!MmAccessFault+0x1ac8
fffff980`156f5c20 000007fe`f0b3d98c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x119
00000000`0b30ebd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f0b3d98c


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRemovePageByColor+48
fffff800`01887988 8a431a mov al,byte ptr [rbx+1Ah]

SYMBOL_STACK_INDEX: 3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4549b6c6

SYMBOL_NAME: nt!MiRemovePageByColor+48

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiRemovePageByColor+48

BUCKET_ID: X64_0xA_nt!MiRemovePageByColor+48

Followup: MachineOwner
---------

Can anyone make heads or tails of this. I am losing my mind here trying to find a fix..

Thanks in advance for any help you may be able to offer.

 

While waiting for someone with more knowledge than I have, I'd suggest updating your video drivers to the latest version due to this portion of the error:

 

System crash at the following instruction is usually related to faulty ram.
nt!MiRemovePageByColor+48
fffff800`01887988 8a431a mov al,byte ptr [rbx+1Ah]

Reseat the memory module to another memory slot. If it still crashes, run memtest to stress test the ram.

 

I currently have 4 GB of mem "4 1 GB" filling every bank. I ran memtest86+ for 12 hours without an error. I also ran mem test that is in vista for another 4 hours and no errors. I only get the error in vista 64. If i run a 32 bit version i get no errors at all. I have also run winxp for about 9 months and have never recieved one bluescreen in all that time. I loves alienware..lol Any thoughts?

 

One minidump is insufficient to determine the root cause. Your analysis report is incomplete (ie no module list (lmtn) and thread information (!thread)). Post more debug reports here. If all the debug reports have different symptoms and it is hardware problem. If the debug reports have the same symptom and it is software error. Your windows is crashed and the running process is eshell.exe (windows media centre). Does your windows always crashes when the media centre is active.

 

Back again

Well here is the story. After trying to figure out this problem i gave up for a bit and went back to XP. Ran XP for about 3 weeks and had not one BSOD during that time or any other errors at all. I power use my system so i would think it would come out preaty soon again. I desided to go back to Vista now that some new drivers were out.

I started with Vista 32 " this is getting expensive" thinking maybe it would be a 64 problem. Blue screen within the first hour. So...back to 64...figure if i am going to have a problem might as well be a 64 one..lol

Ok. So I am back on X64 Vista now. Recently got my first bluescreen "about 2 hours in. Before I installed I ran MEMTEST 86+ 1 stick at a time " I have 4 1 GB sticks" Ran them about 4 hours each. Flawless results.

And here is the latest BSOD


*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {1f, 2, 1, fffff8000188f125}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+381 )

Followup: Pool_corruption
---------

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: 000000000000001f, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8000188f125, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800019f90b0
000000000000001f

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiInsertPageInFreeList+195
fffff800`0188f125 49897020 mov qword ptr [r8+20h],rsi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffff9800d3a42b0 -- (.trap 0xfffff9800d3a42b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000fffffffffffff rbx=000000000000003c rcx=0000057fffffffff
rdx=0000001d554713d2 rsi=fffff9800d3a4990 rdi=fffff800018c6d4f
rip=fffff8000188f125 rsp=fffff9800d3a4440 rbp=0000058000000000
r8=ffffffffffffffff r9=0000000000000081 r10=fffffa8003c00600
r11=fffff78000001488 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!MiInsertPageInFreeList+0x195:
fffff800`0188f125 49897020 mov qword ptr [r8+20h],rsi ds:4440:00000000`0000001f=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000184dff3 to fffff8000184e250

STACK_TEXT:
fffff980`0d3a4168 fffff800`0184dff3 : 00000000`0000000a 00000000`0000001f 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff980`0d3a4170 fffff800`0184cecb : 00000000`00000001 00000000`000449ab 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x73
fffff980`0d3a42b0 fffff800`0188f125 : fffff880`00000001 fffffa80`07446ca8 00000000`00000001 00000000`00000001 : nt!KiPageFault+0x20b
fffff980`0d3a4440 fffff800`0188e496 : 1c000000`449ab963 fffffa80`00cdd010 fffffa80`07446bb0 00000000`00000000 : nt!MiInsertPageInFreeList+0x195
fffff980`0d3a4470 fffff800`0186bff1 : 00000000`00000000 ffffffff`ffffffff ffffffff`ffffffff fffff800`00000000 : nt!MiPfnShareCountIsZero+0x166
fffff980`0d3a44f0 fffff800`0189c917 : fffff6fc`40017a38 00000000`00000001 00000000`00000000 00000000`00000000 : nt!MiDeleteSystemPagableVm+0x555
fffff980`0d3a4660 fffff800`0194090a : fffff6fc`40017a38 00000000`00000000 00000000`00002f47 fffffa80`03c57120 : nt!MiFreePagedPoolPages+0x387
fffff980`0d3a4770 fffff800`0193d727 : fffff880`02f47000 fffff800`01889cc8 fffff880`04bef414 fffff880`04cf3060 : nt!MiFreePoolPages+0x944
fffff980`0d3a4890 fffff800`0193c640 : fffffa80`03c57120 00000000`00000000 00000000`00000001 fffff980`0d3a4ac0 : nt!ExDeferredFreePool+0x381
fffff980`0d3a4900 fffff800`018a497d : 00000000`1bfb2801 fffff880`04cf3060 fffffa80`03c57120 fffff980`63536553 : nt!ExFreePoolWithTag+0x840
fffff980`0d3a49c0 fffff800`01834eb7 : 00000000`1bf66be0 00000000`00000000 00000000`000003e8 00000002`00000001 : nt!SeAccessCheckByType+0x79c
fffff980`0d3a4b40 fffff800`0184dcf3 : 00000000`00000002 00000000`00000000 000007fe`f3a79fb0 00000000`1bf66bb0 : nt!NtAccessCheck+0x57
fffff980`0d3a4bb0 00000000`76fd08ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`1b62e058 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fd08ba


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+381
fffff800`0193d727 4885db test rbx,rbx

SYMBOL_STACK_INDEX: 8

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

SYMBOL_NAME: nt!ExDeferredFreePool+381

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID: X64_0xA_W_nt!ExDeferredFreePool+381

BUCKET_ID: X64_0xA_W_nt!ExDeferredFreePool+381

Followup: Pool_corruption
---------

1: kd> lmvm Pool_Corruption
start end module name