BSOD IRQL_NOT_EQUAL

yoonyuljjang said:

so i have been getting random bsods lately.... and its driving me crazy.
can anyone help me?
windows 7 ultimate
NVIDIA 460
4GB RAM
32bit

memory corruption. We cant tell from only one dmp ifit is the memory or a driver so I would run memtest.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Code:

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


Loading Dump File [C:\Users\K\Desktop\040411-20139-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82e4d000 PsLoadedModuleList = 0x82f97850
Debug session time: Mon Apr  4 00:45:34.623 2011 (GMT-4)
System Uptime: 0 days 15:53:09.387
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {839f22e0, 2, 0, 82eefe73}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+1cf )

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: 839f22e0, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 82eefe73, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82fb7718
Unable to read MiSystemVaType memory at 82f971a0
 839f22e0 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiIdentifyPfn+1cf
82eefe73 8b38            mov     edi,dword ptr [eax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  9dc036f4 -- (.trap 0xffffffff9dc036f4)
ErrCode = 00000000
eax=839f22e0 ebx=87cf2ec0 ecx=00000000 edx=08054cfc esi=06000000 edi=9dc037a0
eip=82eefe73 esp=9dc03768 ebp=9dc037a0 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!MiIdentifyPfn+0x1cf:
82eefe73 8b38            mov     edi,dword ptr [eax]  ds:0023:839f22e0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82eefe73 to 82e8e5cb

STACK_TEXT:  
9dc036f4 82eefe73 badb0d00 08054cfc 00000002 nt!KiTrap0E+0x2cf
9dc037a0 82e7f551 87cf2ec0 87cf2000 9dc03844 nt!MiIdentifyPfn+0x1cf
9dc037c8 830cdeff 00cf2060 ae7def93 9dc03858 nt!MmQueryPfnList+0xa6
9dc03810 830838fb 00000001 ae7def13 00000000 nt!PfpPfnPrioRequest+0xde
9dc03890 8306f5ff 00000000 00000001 9dc03cd0 nt!PfQuerySuperfetchInformation+0xea
9dc03d00 8307ed4a 0000004f 00000000 00000000 nt!ExpQuerySystemInformation+0x2477
9dc03d1c 82e8b1ea 0000004f 0135edd0 00000014 nt!NtQuerySystemInformation+0x76
9dc03d1c 77d970b4 0000004f 0135edd0 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0135cc90 00000000 00000000 00000000 00000000 0x77d970b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiIdentifyPfn+1cf
82eefe73 8b38            mov     edi,dword ptr [eax]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiIdentifyPfn+1cf

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce78a09

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiIdentifyPfn+1cf

BUCKET_ID:  0xA_nt!MiIdentifyPfn+1cf

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

yea i did the memtest... i got about 5800 errors. is that bad? and also another bsod dmp file attached