|
Question : stop error 0x000000d1 (0x00000000, 0x00000002, 0x00000000, 0x00000000) DRIVER_IRQL_NOT_LESS_OR_EQ<wbr />UAL
|
|
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_EQUAL (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+0x2ac
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!MiAllocatePoolPages+2ac
BUCKET_ID: 0xD1_CODE_AV_NULL_IP_nt!MiAllocatePoolPages+2ac
Followup: MachineOwner
---------
|
|
|
Answer : stop error 0x000000d1 (0x00000000, 0x00000002, 0x00000000, 0x00000000) DRIVER_IRQL_NOT_LESS_OR_EQ<wbr />UAL
|
|
Not really i dont see a problem with them sharing that unless perhaps the video card was going south but you would be getting a hardware bsod. i would check the driver verifier see whats going on with that did the problem start directly after the sql was installed if the techs are outsourced he should probably outsource someone else if they cant get a server back up and going in a month. Back to the problem though if you want to check to see if the techs are correct in their assuption shut down sql and see if the problem reproduces if it does they are obviously wrong. Was anything else replaced in the server?
|
|
|
|
|
