spintt2002
asked on
stop error 0x000000d1 (0x00000000, 0x00000002, 0x00000000, 0x00000000) DRIVER_IRQL_NOT_LESS_OR_EQUAL
So i have been getting this error for sometime now on a windows 2000 server, i have analyzed the minidump but had to transfer the minidumps onto another windows 2000 server becuase i could not get the windows debugging tools to load on the server that is generating the errors. Here is the dump log, it is saying memory corruption but i just replaced out the 2gbs of ram in there with 4gigs and still got the error. Here is the analyzed file, if u need me to post a few of the mini dumps up please let me know i have a few of them. Here is the windows debugging tool analysis let me know if there are any other steps i need to do thank you! and like i said this was analyzed on a different win 2000 server.
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Minidump\Mini081006-02 .dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\Symbols\symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: symbols timestamp is wrong 0x44925809 0x427b58bb for ntoskrnl.exe
Windows 2000 Kernel Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x80485b80
Debug session time: Thu Aug 10 16:27:28.031 2006 (GMT-4)
System Uptime: not available
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: symbols timestamp is wrong 0x44925809 0x427b58bb for ntoskrnl.exe
Loading Kernel Symbols
.......................... .......... .......... .......... .......... .......... .......... .......... .
Loading User Symbols
Loading unloaded module list
......
************************** ********** ********** ********** ********** ********** ***
* *
* Bugcheck Analysis *
* *
************************** ********** ********** ********** ********** ********** ***
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 0, 0}
Probably caused by : memory_corruption ( nt!MiAllocatePoolPages+2ac )
Followup: MachineOwner
---------
0: kd> !analyze -v
************************** ********** ********** ********** ********** ********** ***
* *
* Bugcheck Analysis *
* *
************************** ********** ********** ********** ********** ********** ***
DRIVER_IRQL_NOT_LESS_OR_EQ UAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: unable to read from 80481518
unable to read from 804811c8
unable to read from 804810a8
unable to read from 80472de0
unable to read from 804810c0
unable to read from 804811c4
unable to read from 80472de4
unable to read from 80481284
unable to read from 804814b8
00000000
CURRENT_IRQL: 2
FAULTING_IP:
+0
00000000 ?? ???
PROCESS_NAME: System
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from 00000000 to 8046b1ac
FAILED_INSTRUCTION_ADDRESS :
+0
00000000 ?? ???
STACK_TEXT:
eb4239a4 00000000 00000000 00000002 00000000 nt!MiAllocatePoolPages+0x2 ac
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiAllocatePoolPages+2ac
8046b1ac ?? ???
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 44925809
SYMBOL_NAME: nt!MiAllocatePoolPages+2ac
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!Mi AllocatePo olPages+2a c
BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!Mi AllocatePo olPages+2a c
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Minidump\Mini081006-02
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\Symbols\symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: symbols timestamp is wrong 0x44925809 0x427b58bb for ntoskrnl.exe
Windows 2000 Kernel Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x80485b80
Debug session time: Thu Aug 10 16:27:28.031 2006 (GMT-4)
System Uptime: not available
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: symbols timestamp is wrong 0x44925809 0x427b58bb for ntoskrnl.exe
Loading Kernel Symbols
..........................
Loading User Symbols
Loading unloaded module list
......
**************************
* *
* Bugcheck Analysis *
* *
**************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 0, 0}
Probably caused by : memory_corruption ( nt!MiAllocatePoolPages+2ac
Followup: MachineOwner
---------
0: kd> !analyze -v
**************************
* *
* Bugcheck Analysis *
* *
**************************
DRIVER_IRQL_NOT_LESS_OR_EQ
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: unable to read from 80481518
unable to read from 804811c8
unable to read from 804810a8
unable to read from 80472de0
unable to read from 804810c0
unable to read from 804811c4
unable to read from 80472de4
unable to read from 80481284
unable to read from 804814b8
00000000
CURRENT_IRQL: 2
FAULTING_IP:
+0
00000000 ?? ???
PROCESS_NAME: System
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from 00000000 to 8046b1ac
FAILED_INSTRUCTION_ADDRESS
+0
00000000 ?? ???
STACK_TEXT:
eb4239a4 00000000 00000000 00000002 00000000 nt!MiAllocatePoolPages+0x2
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiAllocatePoolPages+2ac
8046b1ac ?? ???
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:
SYMBOL_NAME: nt!MiAllocatePoolPages+2ac
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!Mi
BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!Mi
Followup: MachineOwner
---------
You got a bad driver somewhere on that system thats where the problem lies. Memory corruption can be caused by a bad RAM stick or it can be cause by a bad driver IRQ not less or equal definetly means its a driver issue look in the event viewer see if you can get a pin point on it probably not though. Another process of elimination is to run the server up in safe mode and see if it reproduces if not then you know it is either in your video card network card or sound card. being as its a server i would be pointing toward the network card.
ASKER
Venom thanks for the help, sorry it has taken so long for me to post, this is our customers server and they have an outsoucered company that takes care of their IT needs. They havent been able to fix the problem in a month and just told our customer it is SQL 2005 causing the BSOD, but i am running windows drivier verifier tonight to see if anything stands out also do u think the page file could have anything to do with this?
ASKER
One more thing just to ask, the Nvidia is using IRQ 16 and so is NEC USB enhanced controller.....any issues with that?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes, you are so right one with this Tech because, well in short, they were getting multiple blue screens, never saved those errors or anything, called Microsoft about it, they told him to reload the server..........so he did......but in doing so he made a backup of the registry and restored it after the reload because this is their domain controller and he did not want to have to reconfigure everything which would have taken him a week but now he has spent almost a montha nd a half .......after that i believe the only thing that was replaced was the motherboard, the video card is a agp GEforce4 mX 4000 and the USB is a pci NEC with 4 slots. Network card is brand new, 3com pci, i updated the drivers on that and still nothing, unfortunatly, they are hard headed and they are in the south and i am up north trying to trouble shoot this on my off time, just to prove it is not SQL. And like you said i have told my superiors to let me uninstall all of are program make backups of the database and get rid of sql.......no one likes to listen to me. The way i look at it is that i am not the one losing money everyday. I will test out 2 drivers at a time tongiht and post the results. Thanks venom, when we get this hashed out ill up the points.