IRQL_NOT_LESS_OR_EQUAL and Blue Screen of Death

First post to major geeks but been reading awhile


I recently started getting this when I go to shut down this pops up and computer just restarts. Only way to turn off is manually.

Says IRQL_NOT_LESS_OR_EQUAL

STOP: 0x0000000A (0x0000FFDF,0x00000002,0x00000001,0x806E6A8E)

and then something about a physical memory dump


And thats it where do I start to fix this?

Thanks for any help

 

Did you upgrade the amount of RAM recently?

 

Had a couple memory dumps can you help me analyze this

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


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

Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.080814-1236
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Nov 3 22:02:22.843 2008 (GMT-5)
System Uptime: 0 days 0:01:53.574
Loading Kernel Symbols
....................................................................................................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {bab3, 2, 1, 806e6a8e}

Probably caused by : ntkrpamp.exe ( nt!IoAcquireCancelSpinLock+e )

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

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: 0000bab3, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 806e6a8e, address which referenced memory

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


WRITE_ADDRESS: 0000bab3

CURRENT_IRQL: 2

FAULTING_IP:
hal!KeAcquireQueuedSpinLock+42
806e6a8e 8902 mov dword ptr [edx],eax

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: nSvcLog.exe

LAST_CONTROL_TRANSFER: from 804eee9e to 806e6a8e

STACK_TEXT:
a279fc0c 804eee9e a279fc28 804f15cf a279fc24 hal!KeAcquireQueuedSpinLock+0x42
a279fc14 804f15cf a279fc24 89e7e018 00000041 nt!IoAcquireCancelSpinLock+0xe
a279fc28 80575715 89e7e008 8a800880 8a5cf310 nt!IoCancelIrp+0x2f
a279fc50 805d24ba 8a5cf310 8a54c768 00000005 nt!IoCancelThreadIo+0x33
a279fcf0 805d27f5 00000005 a279fd4c 804ff94f nt!PspExitThread+0x428
a279fcfc 804ff94f 8a54c768 a279fd48 a279fd3c nt!PsExitSpecialApc+0x23
a279fd4c 80541697 00000001 00000000 a279fd64 nt!KiDeliverApc+0x1af
a279fd4c 7c90e4f4 00000001 00000000 a279fd64 nt!KiServiceExit+0x59
WARNING: Frame IP not in any known module. Following frames may be wrong.
0083ff48 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!IoAcquireCancelSpinLock+e
804eee9e 8b4d08 mov ecx,dword ptr [ebp+8]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!IoAcquireCancelSpinLock+e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48a3fbd9

FAILURE_BUCKET_ID: 0xA_W_nt!IoAcquireCancelSpinLock+e

BUCKET_ID: 0xA_W_nt!IoAcquireCancelSpinLock+e

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

1: kd> lmvm nt
start end module name
804d7000 806e4000 nt # (pdb symbols) DownstreamStore\ntkrpamp.pdb\D82F3C0407BA4AB09C7831D423622B691\ntkrpamp.pdb
Loaded symbol image file: ntkrpamp.exe
Mapped memory image file: DownstreamStore\ntkrpamp.exe\48A3FBD920d000\ntkrpamp.exe
Image path: ntkrpamp.exe
Image name: ntkrpamp.exe
Timestamp: Thu Aug 14 05:33:13 2008 (48A3FBD9)
CheckSum: 001FBC56
ImageSize: 0020D000
File version: 5.1.2600.5657
Product version: 5.1.2600.5657
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0401.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrpamp.exe
OriginalFilename: ntkrpamp.exe
ProductVersion: 5.1.2600.5657
FileVersion: 5.1.2600.5657 (xpsp_sp3_gdr.080814-1236)
FileDescription: ‎‎NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.

 

Here is a debugging log can you help me understand this

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


Loading Dump File [C:\WINDOWS\Minidump\Mini110308-02.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) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.080814-1236
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Nov 3 22:05:53.187 2008 (GMT-5)
System Uptime: 0 days 0:02:25.777
Loading Kernel Symbols
...................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {ffdf, 2, 1, 806e6a8e}

Probably caused by : ntkrpamp.exe ( nt!IoAcquireCancelSpinLock+e )

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: 0000ffdf, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 806e6a8e, address which referenced memory

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


WRITE_ADDRESS: 0000ffdf

CURRENT_IRQL: 2

FAULTING_IP:
hal!KeAcquireQueuedSpinLock+42
806e6a8e 8902 mov dword ptr [edx],eax

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: nSvcLog.exe

LAST_CONTROL_TRANSFER: from 804eee9e to 806e6a8e

STACK_TEXT:
a36fcc0c 804eee9e a36fcc28 804f15cf a36fcc24 hal!KeAcquireQueuedSpinLock+0x42
a36fcc14 804f15cf a36fcc24 89eae848 00000041 nt!IoAcquireCancelSpinLock+0xe
a36fcc28 80575715 89eae838 89e58bc0 89e3bda8 nt!IoCancelIrp+0x2f
a36fcc50 805d24ba 89e3bda8 8a103680 00000005 nt!IoCancelThreadIo+0x33
a36fccf0 805d27f5 00000005 a36fcd4c 804ff94f nt!PspExitThread+0x428
a36fccfc 804ff94f 8a103680 a36fcd48 a36fcd3c nt!PsExitSpecialApc+0x23
a36fcd4c 80541697 00000001 00000000 a36fcd64 nt!KiDeliverApc+0x1af
a36fcd4c 7c90e4f4 00000001 00000000 a36fcd64 nt!KiServiceExit+0x59
WARNING: Frame IP not in any known module. Following frames may be wrong.
0083ff48 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!IoAcquireCancelSpinLock+e
804eee9e 8b4d08 mov ecx,dword ptr [ebp+8]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!IoAcquireCancelSpinLock+e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48a3fbd9

FAILURE_BUCKET_ID: 0xA_W_nt!IoAcquireCancelSpinLock+e

BUCKET_ID: 0xA_W_nt!IoAcquireCancelSpinLock+e

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: 0000ffdf, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 806e6a8e, address which referenced memory

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


WRITE_ADDRESS: 0000ffdf

CURRENT_IRQL: 2

FAULTING_IP:
hal!KeAcquireQueuedSpinLock+42
806e6a8e 8902 mov dword ptr [edx],eax

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: nSvcLog.exe

LAST_CONTROL_TRANSFER: from 804eee9e to 806e6a8e

STACK_TEXT:
a36fcc0c 804eee9e a36fcc28 804f15cf a36fcc24 hal!KeAcquireQueuedSpinLock+0x42
a36fcc14 804f15cf a36fcc24 89eae848 00000041 nt!IoAcquireCancelSpinLock+0xe
a36fcc28 80575715 89eae838 89e58bc0 89e3bda8 nt!IoCancelIrp+0x2f
a36fcc50 805d24ba 89e3bda8 8a103680 00000005 nt!IoCancelThreadIo+0x33
a36fccf0 805d27f5 00000005 a36fcd4c 804ff94f nt!PspExitThread+0x428
a36fccfc 804ff94f 8a103680 a36fcd48 a36fcd3c nt!PsExitSpecialApc+0x23
a36fcd4c 80541697 00000001 00000000 a36fcd64 nt!KiDeliverApc+0x1af
a36fcd4c 7c90e4f4 00000001 00000000 a36fcd64 nt!KiServiceExit+0x59
WARNING: Frame IP not in any known module. Following frames may be wrong.
0083ff48 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!IoAcquireCancelSpinLock+e
804eee9e 8b4d08 mov ecx,dword ptr [ebp+8]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!IoAcquireCancelSpinLock+e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48a3fbd9

 

No I haven't upgraded the ram still original froma year ago. 3 posted my memory dump from Microsoft debugger program but can't make heads or tails of it lol =) so any is help is welcome

thanks

 

Any ideas where to start thank you?

 

This may be helpful some general system specs

Intel Core Duo 2.6ghz
BFG Nvidia 8800 GT OCX
Asus P5N E SLI Motherboard
2 gigs of ram
Windows XP

I just did an update of graphic card driver and went to Asus and downloaded latest Nvidia chipset drivers, when it got done with chipset drivers and asked to restart it didnt blue screen it restarted normally when I restarted again got BSOD and same error. So where should I start looking next ?


Thanks

 

Well I am at a loss as what to do now and this post had was slowly moving towards page 5 lol. So any suggestions would be greatly appreciated

 

It's the nVidia network service. If your board is an nForce board, then try updating the board drivers and it should update the network drivers as well.