[tdevill]

Hello all,

I have finally decided to come ask for help after trying to sort this myself, and scouring tech forums for hours.

I have gone back to using my old Dell Inspiron 8200 after my desktop fried. Will have to stick with it for a few months before upgrading my desktop.

The thing is the Dell works fine and does everything i need it to do, but with one horrible problem. At least 2-3 times per day i get the dreaded IRQL_NOT_LESS_OR_EQUAL error most often pointing to ntoskrnl.exe as the problem.

I have been using Nirsoft's Bluescreen view to look over the Minidump files. I have attatched a few of the more recent files to this message.

Now - I have gathered that this could be caused by several issues, some of which i have eliminated:

RAM - but I ran Memtest several times for a few hours with 0 errors.

A corrupt windows install - I doubt it because I have done a full windows reinstall and the error still crops up.

So that leaves

Drivers/Hardware - well I have checked and made sure most of my drivers are up to date. I really suspected it was an old Buffalo WIFI (airstation MIMO WLI-CB-G108) card causing the problem, but i just bought and installed a new card today and the error still crops up.

I don't really know now what the issue could be.

I have tried using the windows driver checker utility, but that just seemed to slow the system down loads and the blue screens still cropped up with the same error pointing to ntoskrnl.exe.

Maybe I should try it again...

Perhaps by looking at the Minidump files, you guys might be able to shine a little light on the issue?

(one of these minidumps points to the driver for my old Airstation Wifi card, which is why i bought a new one today, but to no avail...)

here is my system info:
OS Version: Microsoft Windows XP Professional, Service Pack 3, 32 bit
Processor: Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz, x86 Family 15 Model 2 Stepping 7
Processor Count: 1
RAM: 1023 Mb
Graphics Card: ATI MOBILITY/RADEON 9000 (Omega 3.8.252), 64 Mb
Hard Drives: C: Total - 38107 MB, Free - 12523 MB;
Motherboard: Dell Computer Corporation, Inspiron 8200 , ,
Antivirus: AVG Anti-Virus Free, Updated: Yes, On-Demand Scanner: Enabled

I have a few external hard drives, but this error occurs without them plugged in.

The new WIFI card i have plugged is a D-LINK DWA-645

Otherwise all that is plugged is a microsoft USB mouse, tho errors occur without this plugged in too.

Look forward to your help.

Take care,

Tam

[TekTime]

What's the make and model of your PSU (power supply)? That could be causing your issue.

Your motherboard could also be an issue (bad memory controller...etc...etc)

[tdevill]

Well, the INSPIRON 8200 is a laptop, so the PSU is the DELL one it came with.

I downloaded and installed all the motherboard related drivers i could find from the DELL support website.

Here is a little more info too:

The computer crashes most often when I shut down windows. It blue screens just before windows finishes closing.

However, it also randomly BSODs at other times - when browsing, using itunes, etc...

Did u get a chance to look at the minidump files attatched?

Last night it gave me a KERNEL_MODE_EXCEPTION_NOT_HANDLED - I guess just to vary things a little.

0x1000008e (0xc0000005, 0x80565e1f, 0xf01fbbe0, 0x00000000), again on Nirsoft BlueScreenView it points to the famous ntoskrnl.exe as the problem. But that means little as its a system file - which i doubt is corrupt since I reinstalled windows.

[tdevill]

Here is the most recent crash report:


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


Loading Dump File [C:\WINDOWS\Minidump\Mini083110-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
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Tue Aug 31 00:45:10.671 2010 (GMT+2)
System Uptime: 0 days 2:36:57.269
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
..............
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 80565e1f, f01fbbe0, 0}

Probably caused by : ntoskrnl.exe ( nt!ObDereferenceSecurityDescriptor+13 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 80565e1f, The address that the exception occurred at
Arg3: f01fbbe0, Trap Frame
Arg4: 00000000

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!ObDereferenceSecurityDescriptor+13
80565e1f 8b33 mov esi,dword ptr [ebx]

TRAP_FRAME: f01fbbe0 -- (.trap 0xfffffffff01fbbe0)
ErrCode = 00000000
eax=00000040 ebx=00000038 ecx=00000001 edx=82dbb058 esi=82dbb068 edi=00000030
eip=80565e1f esp=f01fbc54 ebp=f01fbc68 iopl=0 nv up ei pl nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010207
nt!ObDereferenceSecurityDescriptor+0x13:
80565e1f 8b33 mov esi,dword ptr [ebx] ds:0023:00000038=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: winlogon.exe

LAST_CONTROL_TRANSFER: from 8056b8cc to 80565e1f

STACK_TEXT:
f01fbc68 8056b8cc 00000040 00000001 f01fbc84 nt!ObDereferenceSecurityDescriptor+0x13
f01fbc78 8056b8a8 82dbb07c f01fbcc0 8056b89b nt!ObDeassignSecurity+0x1d
f01fbc84 8056b89b 82dbb080 00000002 00000000 nt!SeDefaultObjectMethod+0x40
f01fbcc0 804e36d5 82dbb080 00000000 00000200 nt!ObpRemoveObjectRoutine+0xc4
f01fbce4 80567847 82b9b790 e16d3b78 82bf7da8 nt!ObfDereferenceObject+0x5f
f01fbcfc 805678b0 e16d3b78 82dbb080 00000200 nt!ObpCloseHandleTableEntry+0x155
f01fbd44 805678fa 00000200 00000001 00000000 nt!ObpCloseHandle+0x87
f01fbd58 804de7ec 00000200 015aff74 7c90e4f4 nt!NtClose+0x1d
f01fbd58 7c90e4f4 00000200 015aff74 7c90e4f4 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
015aff74 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ObDereferenceSecurityDescriptor+13
80565e1f 8b33 mov esi,dword ptr [ebx]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ObDereferenceSecurityDescriptor+13

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48025eab

FAILURE_BUCKET_ID: 0x8E_nt!ObDereferenceSecurityDescriptor+13

BUCKET_ID: 0x8E_nt!ObDereferenceSecurityDescriptor+13

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

[tdevill]

bump

[TekTime]

This is a tough one. I have heard of people having issues with SP3. Did your BSODs start after a Windows update?

[tdevill]

Actually no, the same errors cropped up under SP2... :-(

Any ideas of what i could do, besifes live with it or buy a new PC?

[TekTime]

Try running your computer in "Safe Mode With Networking." See if the same problem occurs....