bsod irql_not_less_or_equal DELL XPS 1340

[knitsuj]

XPS M1340, P7350 (2.0GHZ) CORE 2 DUO
6GB, DDR3, 1066 MHZ (4gb + 2gb dual channel)
Nvidia Geforce 9500m

Windows 7 64bit Home Premium

Could someone please help me diagnose the minidumps?

I've spend countless hours and days trying to fix this stupid machine. I usually get 2 BSODS a day, when I updated all my drivers and updated fully through windows update I got all sorts of BSOD (irql, memory_management, win32k), but when I reformat the laptop fresh and install the newest drivers from the manufacturer the most common BSOD is IRQL_NOT_LESS_OR_EQUAL.

Thanks a ton in advance! This stupid dell has caused me many sleepless nights, and I'm in the middle of my exams

P.S. I've already done memtest86 and /chkdisk, 6 passes with memtest with no errors, and no errors found with /chkdisk

 

[Pauly]

Both dumps report error 0xA and blame memory management, this could be page file as well as ram i would run memtest again overnight and try a full HDD diagnostic thats a bit more comprehensive that chkdsk
HD Diagnostic

 

[knitsuj]

hi pauly,

thanks for the prompt response. i've done several extensive memtests overnight with 6 or 7 passes and each time i find no errors.

i will try your full hd check tonight.

 

[knitsuj]

is it possible that my ram setup might be an issue?

4gb hyundai ddr3 1066mhz stick

2gb samsung ddr3 1066mhz stick

timing on both sticks = 7 7 7 20 1.5V

just did some googling and one person said that his problem was from different brands of ram :huh:?

 

[Pauly]

Sorry to be so long

It could well be the issue, i would also check your mobo homepage for the qvl list of compatible ram

Easiest way to check is to remove the 2GB and try for a few days or remove the 4GB and try

 

[knitsuj]

Pauly I did the extensive hd scan and came up with nothing again.

In the last day I've gotten two more minidumps.

One of them is a nlvd driver crash that I forced with a verifier scan. The other was a regular one out of the blue (can you check to see if it's memory_management again Pauly?)

Much appreciated

Will be playing with ram after I get back from my exam.

 

[zigzag3143]

Pauly I did the extensive hd scan and came up with nothing again.

In the last day I've gotten two more minidumps.

One of them is a nlvd driver crash that I forced with a verifier scan. The other was a regular one out of the blue (can you check to see if it's memory_management again Pauly?)

Much appreciated

Will be playing with ram after I get back from my exam.

Well you hit the nail on the head. Memory corruption for both.

Again
memtestx86 for 5 passes
sysem file check
type cmd in search>right click and run as admin>sfc /scannow

If you are overclocking STOP.

Ken

020910-16941-01.dmp    2/9/2010 6:31:30 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    ffffffff`c0000005    fffff800`02cf84a8    00000000`00000000    ffffffff`ffffffff    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\020910-16941-01.dmp    2    15    7600    
020810-24897-01.dmp    2/8/2010 8:06:46 PM    DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL    0x000000d5    fffff980`16fd2e08    00000000`00000000    fffff880`0fe9ea0e    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\020810-24897-01.dmp    2    15    7600

OLD DRIVERS

SSPORT.sys        fffff880`0ae48000    fffff880`0ae50000    0x00008000    0x42fbda34    8/11/2005 6:07:32 PM                        
secdrv.SYS        fffff880`0ae10000    fffff880`0ae1b000    0x0000b000    0x4508052e    9/13/2006 8:18:38 AM                        
bcmwl664.sys        fffff880`0426d000    fffff880`043e5000    0x00178000    0x48ffc83b    10/22/2008 7:41:31 PM                        
BCM42RLY.sys        fffff880`0b68c000    fffff880`0b695000    0x00009000    0x491a486c    11/11/2008 10:07:24 PM

ANALYSIS

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


Loading Dump File [C:\Users\K\Desktop\020910-16941-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c65000 PsLoadedModuleList = 0xfffff800`02ea2e50
Debug session time: Tue Feb  9 18:30:21.748 2010 (GMT-5)
System Uptime: 0 days 6:21:25.698
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002cf84a8, 0, ffffffffffffffff}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+6a8 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002cf84a8, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MiUnlinkPageFromLockedList+6a8
fffff800`02cf84a8 49890cc1        mov     qword ptr [r9+rax*8],rcx

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0d0e0
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d16a17 to fffff80002cd6f00

STACK_TEXT:  
fffff880`0b40ce38 fffff800`02d16a17 : 00000000`0000001e ffffffff`c0000005 fffff800`02cf84a8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0b40ce40 fffff800`02cd6542 : fffff880`0b40d618 fffffa80`04155420 fffff880`0b40d6c0 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x460da
fffff880`0b40d4e0 fffff800`02cd4e4a : 00000001`00000001 00000000`00000011 00000000`80000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0b40d6c0 fffff800`02cf84a8 : fffffa80`05afcf30 fffffa80`079f10b0 7ff00000`00000000 00000000`01d4c238 : nt!KiGeneralProtectionFault+0x10a
fffff880`0b40d850 fffff800`02d08d57 : 00000000`01d4b7b8 fffff680`00000000 0000007f`00000000 fffff680`0000ea58 : nt!MiUnlinkPageFromLockedList+0x6a8
fffff880`0b40d8e0 fffff800`02cf3506 : 00000000`00000000 00000000`01d4b7b8 fffff880`0b40d990 fffffa80`05da9d88 : nt!MiResolveTransitionFault+0x167
fffff880`0b40d970 fffff800`02cf0f23 : ffffffff`ffffffff 00000000`00052a00 00000000`00000020 00020bea`00020410 : nt!MiDispatchFault+0x946
fffff880`0b40da80 fffff800`02cd4fee : 00000000`00000000 00000000`01d4ad50 fffffa80`0ad41a01 00000000`00000000 : nt!MmAccessFault+0x343
fffff880`0b40dbe0 00000000`6af828d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0430e070 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6af828d7


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiUnlinkPageFromLockedList+6a8
fffff800`02cf84a8 49890cc1        mov     qword ptr [r9+rax*8],rcx

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiUnlinkPageFromLockedList+6a8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1E_nt!MiUnlinkPageFromLockedList+6a8

BUCKET_ID:  X64_0x1E_nt!MiUnlinkPageFromLockedList+6a8

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

 

[knitsuj]

okay, took out the 2gb of samsung, will run memtest for 6passes tonight with just the 4gb of hyunda (hynix) ram. thanks for the help guys, i'll keep you posted.

oh and p.s. i don't overclock, never wanted to, not for desktops nor laptops

 

[knitsuj]

hey guys,

sorry for the wait, i tested both single strips of ram and was still getting bsods. memtest came up with no errors on either strip of ram. i didn't post earlier because i was occupied with midterms sorry

today i got a different bsod though, non_page_failed or something like that (my usual one is service_exception or IRQL_NOT_LESS_OR_EQUAL). could anyone read my minidumps real quick and tell me if it points to ram again?

much appreciated