BSOD issues

[iceshooter161]

Hey, I have been having problems with my computer for the past week or so ever since I reformated my hard drive. I have been getting a lot of IRQL_NOT_LESS_OR_EQUAL errors. Now I know everyone is gonna jump and say that it is a memory issue but I am not too sure of it. I ran memtest86 for numerous hours with having both of my sticks in dual channel, single channel together, and each stick independently. Each time I get no errors at all in memtest86. The thing that I dont understand though is if I have both sticks of memory installed in dual channel I get the bsod however If I have them in single channel together it works perfectly fine. I have completely removed my nvidia drivers and reinstalled them in safe mode but that still didn't help. Anyone have any suggestions?

 

[iceshooter161]

Bump. Does anyone have any clue why I can't get my memory to run in dual channel? I started to also get a pfn_list_corrupt bsod. Any help would be great.

 

[Celegorm]

Not memory, drivers. Get all updates for your motherboard, video, and audio drivers. If you are using the latest, try the version right before.

 

[iceshooter161]

Ok thanks. I'll give that a try when I am able to get back to my computer and Ill let you know. Thanks!

 

[iceshooter161]

Ok so I have tried everything with all of the drivers on my computer but I am still getting a BSOD. Here is a memory dump from windbg. Hopefully someone can help with it.

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


Loading Dump File [C:\WINDOWS\Minidump\Mini090208-11.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0
Debug session time: Tue Sep 2 15:13:41.281 2008 (GMT-5)
System Uptime: 0 days 0:00:28.906
Loading Kernel Symbols
..........................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {1138, 2, 0, 80533923}

Probably caused by : ntkrnlpa.exe ( nt!ExpScanGeneralLookasideList+1b )

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

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: 00001138, 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: 80533923, address which referenced memory

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


READ_ADDRESS: 00001138

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExpScanGeneralLookasideList+1b
80533923 8b56e0 mov edx,dword ptr [esi-20h]

CUSTOMER_CRASH_COUNT: 11

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

TRAP_FRAME: f78f2ca8 -- (.trap 0xfffffffff78f2ca8)
ErrCode = 00000000
eax=0000001e ebx=0000006b ecx=000007d0 edx=00000547 esi=00001158 edi=0000006b
eip=80533923 esp=f78f2d1c ebp=f78f2d2c iopl=0 vif nv up ei pl nz na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00090203
nt!ExpScanGeneralLookasideList+0x1b:
80533923 8b56e0 mov edx,dword ptr [esi-20h] ds:0023:00001138=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 80533923 to 80540683

STACK_TEXT:
f78f2ca8 80533923 badb0d00 00000547 ffffffff nt!KiTrap0E+0x233
f78f2d2c 80533e88 8055b4f0 8055b4e8 8053c298 nt!ExpScanGeneralLookasideList+0x1b
f78f2d38 8053c298 00000000 86590da8 00000000 nt!ExAdjustLookasideDepth+0x32
f78f2dac 805c6160 00000000 00000000 00000000 nt!KeBalanceSetManager+0x88
f78f2ddc 80541dd2 8053c210 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExpScanGeneralLookasideList+1b
80533923 8b56e0 mov edx,dword ptr [esi-20h]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!ExpScanGeneralLookasideList+1b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlpa.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a

FAILURE_BUCKET_ID: 0xA_nt!ExpScanGeneralLookasideList+1b

BUCKET_ID: 0xA_nt!ExpScanGeneralLookasideList+1b

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

 

[J03]

Hmm... I would try resetting your BIOS, as IRQ issues are somtimes cause by impropper configuration.

 

[iceshooter161]

I have tried resetting it back to defaults and also upgrading to the latest bios version and it still gives me the same errors.