BSOD: 0x000000D1 Message

N

Nicm15

I'm so confused. I have a dell Dimension 5100 it's running on Windows XP
Professional SP2 Media Center Edition, we've never had any problems with this
computer before. We started having problems when we installed a DivX package
that came with the Divx player and codec and etc. and we upgraded our Adobe
from 7.0 to 9.0. That was when the BSOD made it's debut. Once the problem
started, we went into safe mode uninstalled these programs. We left DivX off
and put the original Adobe that we had back on the computer. The blue screen
still came up. I searched this forum and went to the recommended site that
had the various suggestions for this matter, I downloaded the appropriate Hot
Fixes, still no result. Finally, I attempted to do a system restore, but our
system restore refuses to work, it gets to the confirm page and I click the
next button and absolutely nothing happens. We even left it running
overnight thinking it needed a while to restore and still no result. I'm out
of ideas at this point and totally lost. Does anybody have an idea why this
might be happening?
 
G

Gerry

Please post a complete Stop Error report.

Disable automatic restart on system failure. This should help by
allowing time to write down the STOP code properly. Keep pressing the F8
key during Start-Up and select option - Disable automatic restart on
system failure. Do not re-enable automatic restart on system failure.

What "recommended site"?

What "hot fixes"?

What anti-virus software is installed?


--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
N

Nicm15

Hello Randem and Gerry, I appreciate you guys taking the time to assist me.
I addressed each of you separately in this post so there wouldn't be any
confusion.

Randem: I ran a search on the LogiTech program you mentioned and I found
the following notepad located in C:\i386\CompData it states:

The currently installed driver for Logitech MouseWare or Logitech iTouch is
not compatible with Microsoft Windows XP and will be disabled during the
upgrade. You should uninstall the Logitech drivers and software before
continuing with the upgrade.

For more information about this driver, visit the manufacturer's Web site at
http://go.microsoft.com/fwlink/?linkid=383. Web addresses can change, so you
might be unable to connect to this Web site.
For a list of software supported by this version of Microsoft Windows, see
the Microsoft Windows XP Compatibility List at
http://www.microsoft.com/isapi/redir.dll?prd=whistler&ar=help&sba=compatible.

I'm a little confused by this because I haven't done any updates or changes,
so should I go the site you previously mentioned and do an update?

Gerry: Here is the entire stop message, I did it word for word I didn't
want to miss anything important.

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

DRIVER_IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this Stop error screen restart your
computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If
this is a new installation, ask your hardware or software manufacturer for
any Windows updates you might need.

If problems continue disable or remove any newly installed hardware or
software. Disable BIOS memory options such as caching or shadowing. If you
need to use Safe mode to remove or disable components, restart your computer,
press F8 to Select Advanced Startup Options, and then Select Safe Mode.

Technical information:

***STOP: 0x000000D1 (0xE1BB300, 0x00000002, 0x00000000, 0xF555CE85)

Beginning dump of physical memory
Physical memory dump complete
Contact your system administrator or technical support group for further
assistance.

I haven't tried doing that disable caching or shadowing suggestion because I
don't know how to do it. Should I try doing that?

When I did a search on this forum regarding this issue, I noticed this site
was recommended.
http://aumha.org/a/stop.htm
I went to this site and clicked on the D1: Driver IRQL_NOT_LESS_OR_EQUAL
issue on the right hand side. I attempted to install these two fixes that
were recommended on the site.

http://support.microsoft.com/?kbid=839876&sd=RMVP
When I installed this one I got a message stating the service pack I was
running was newer than the fix so it didn't need to be installed.

http://support.microsoft.com/?kbid=916595&sd=RMVP
I didn't have any problems installing this one but I'm still having the same
problem with the blue screen.

I use AVG Free 8.5 Anti-Virus as well as Malwarebytes because I heard the
latter of the two tends to notice viruses that other anti-virus programs
don't pick up on. I ran a full scan using both of these programs and nothing
turned up. Sorry for such a long post but I wanted to be as detailed as
possible. Thanks again guys!
 
N

Nicm15

*Sighs* This situation keeps getting weirder and weirder. I went to
LogiTech's site and there was no mention of the mouse we're using. The mouse
says Dell on it but after some research I found out that LogiTech made the
mouse for Dell it's model number M-UK DEL3 but I couldn't find any driver
information on Dell's website or LogiTech could our mouse be obsolete?
 
N

Nicm15

I went to dell's site and tried to do it by putting in my Service Tag number
which Dell didn't recognize, go figure. So I just looked up the model name
and number Dimension 5100. I looked up to see if they had any drivers for
mice or keyboards and it came back with nothing. Thanks for your help, I'm
going to see what Gerry suggests if he's out of ideas then I'll try the
uninstall. Should I try to find my recovery disc that came with the computer
and just reinstall everything?
http://support.dell.com/support/dow...DIMENSION+5100&hidos=WW1&hidlang=UK&TabIndex=
 
G

Gerry

Nicm

Have you read the Dell Owners Manual?

You never answered these questions?

What "recommended site"?

What "hot fixes"?

What anti-virus software is installed?

Did you uninstall the Logitech drivers and software?

Is the mouse wired or wirelesss?

Have you Dell Diagnostics?


--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
N

Nicm15

UPDATE:

I ran Windows Debugger and it's coming back and stating that
I probably have memory corruption. How in the world do I go about fixing
such a thing? I've never encountered such a problem before.

Gerry in response to your questions, here's the site I went to before
finding out about this memory corruption issue.

http://aumha.org/a/stop.htm
I went to this site and clicked on the D1: Driver IRQL_NOT_LESS_OR_EQUAL
issue on the right hand side. I attempted to install these two fixes that
were recommended on the site.

http://support.microsoft.com/?kbid=839876&sd=RMVP
When I installed this one I got a message stating the service pack I was
running was newer than the fix so it didn't need to be installed.

http://support.microsoft.com/?kbid=916595&sd=RMVP
I didn't have any problems installing this one but I'm still having the same
problem with the blue screen.

I use AVG Free 8.5 Anti-Virus as well as Malwarebytes because I heard the
latter of the two tends to notice viruses that other anti-virus programs
don't pick up on. I ran a full scan using both of these programs and nothing
turned up.

The mouse we use is wired.

So how do I go about repairing memory corruption?
 
G

Gerry

Nic

Please post the complete copy of the Debugger Report. It may be long but
once it has been posted it can be snipped in later posts.

The general advice in the Aumha is helpful but the KB Articles are from
a number of years ago so they are not usually relevant to current
errors. To a certain extent many Microsoft KB Articles cease to be
relevant not too long after they have been published. Those relating to
specific Stop error codes often mislead to the extent that users think
they have a solution when all they have found is one published solution
when there are countless similar Stop Errors where there is no published
solution.

--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
N

Nicm15

Gerry, thanks for explaining that to me about the knowledge base. Here's the
one the reports. I've checked just about all of them and they're all saying
possible memory corruption.

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


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

Symbol search path is: C:\WINDOWS\symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Jun 24 13:15:31.000 2009 (GMT-4)
System Uptime: 0 days 0:00:18.703
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {e1bb3000, 2, 0, f555ce85}

Probably caused by : memory_corruption ( nt!MiInsertPageFileInList+db )

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

1: 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: e1bb3000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f555ce85, address which referenced memory

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


READ_ADDRESS: e1bb3000

CURRENT_IRQL: 2

FAULTING_IP:
+2ab
f555ce85 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from f555e9f9 to f555ce85

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f8942d54 f555e9f9 80503960 8295f1d0 8056375c 0xf555ce85
f8942d7c 805379dd 8295f1d0 00000000 82bc63c8 0xf555e9f9
f8942dac 805ce858 8295f1d0 00000000 00000000 nt!MiInsertPageFileInList+0xdb
f8942ddc 8054534e 805378ee 00000001 00000000 nt!`string'+0x20
f8942e64 00000000 00000000 da5c6000 fffdb83f nt!WmiTraceMessageVa+0x2ab


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiInsertPageFileInList+db
805379dd ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!MiInsertPageFileInList+db

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 498c69f0

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xD1_nt!MiInsertPageFileInList+db

BUCKET_ID: 0xD1_nt!MiInsertPageFileInList+db

Followup: MachineOwner
 
G

Gerry

Nic

Have posted all the report as it looks truncated?


--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Gerry, thanks for explaining that to me about the knowledge base.
Here's the one the reports. I've checked just about all of them and
they're all saying possible memory corruption.

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


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

Symbol search path is: C:\WINDOWS\symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Jun 24 13:15:31.000 2009 (GMT-4)
System Uptime: 0 days 0:00:18.703
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {e1bb3000, 2, 0, f555ce85}

Probably caused by : memory_corruption ( nt!MiInsertPageFileInList+db
)

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

1: 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: e1bb3000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f555ce85, address which referenced memory

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


READ_ADDRESS: e1bb3000

CURRENT_IRQL: 2

FAULTING_IP:
+2ab
f555ce85 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from f555e9f9 to f555ce85

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be
wrong. f8942d54 f555e9f9 80503960 8295f1d0 8056375c 0xf555ce85
f8942d7c 805379dd 8295f1d0 00000000 82bc63c8 0xf555e9f9
f8942dac 805ce858 8295f1d0 00000000 00000000
nt!MiInsertPageFileInList+0xdb f8942ddc 8054534e 805378ee 00000001
00000000 nt!`string'+0x20
f8942e64 00000000 00000000 da5c6000 fffdb83f
nt!WmiTraceMessageVa+0x2ab


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiInsertPageFileInList+db
805379dd ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!MiInsertPageFileInList+db

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 498c69f0

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xD1_nt!MiInsertPageFileInList+db

BUCKET_ID: 0xD1_nt!MiInsertPageFileInList+db

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





Gerry said:
Nic

Please post the complete copy of the Debugger Report. It may be long
but once it has been posted it can be snipped in later posts.

The general advice in the Aumha is helpful but the KB Articles are
from a number of years ago so they are not usually relevant to
current errors. To a certain extent many Microsoft KB Articles cease
to be relevant not too long after they have been published. Those
relating to specific Stop error codes often mislead to the extent
that users think they have a solution when all they have found is
one published solution when there are countless similar Stop Errors
where there is no published solution.

--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to expand...
 
N

Nicm15

Yes, I double checked, that's the whole thing. I ran a diagnostics test via
pressing F12 upon my dell screen at startup. Selected Hard Drive Diagnostics
and got the following information:

Drive 0: Maxtor 64080M0---Pass
Drive 1: No device
Drive 2: Philips DVD +/-RW DVD8631--Diagnostics not supported
Drive 3: No device

Does that information help any? Should I do a driver rollback of my DVD
drive?

Gerry said:
Nic

Have posted all the report as it looks truncated?


--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Gerry, thanks for explaining that to me about the knowledge base.
Here's the one the reports. I've checked just about all of them and
they're all saying possible memory corruption.

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


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

Symbol search path is: C:\WINDOWS\symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Jun 24 13:15:31.000 2009 (GMT-4)
System Uptime: 0 days 0:00:18.703
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {e1bb3000, 2, 0, f555ce85}

Probably caused by : memory_corruption ( nt!MiInsertPageFileInList+db
)

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

1: 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: e1bb3000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f555ce85, address which referenced memory

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


READ_ADDRESS: e1bb3000

CURRENT_IRQL: 2

FAULTING_IP:
+2ab
f555ce85 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from f555e9f9 to f555ce85

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be
wrong. f8942d54 f555e9f9 80503960 8295f1d0 8056375c 0xf555ce85
f8942d7c 805379dd 8295f1d0 00000000 82bc63c8 0xf555e9f9
f8942dac 805ce858 8295f1d0 00000000 00000000
nt!MiInsertPageFileInList+0xdb f8942ddc 8054534e 805378ee 00000001
00000000 nt!`string'+0x20
f8942e64 00000000 00000000 da5c6000 fffdb83f
nt!WmiTraceMessageVa+0x2ab


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiInsertPageFileInList+db
805379dd ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!MiInsertPageFileInList+db

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 498c69f0

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xD1_nt!MiInsertPageFileInList+db

BUCKET_ID: 0xD1_nt!MiInsertPageFileInList+db

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





Gerry said:
Nic

Please post the complete copy of the Debugger Report. It may be long
but once it has been posted it can be snipped in later posts.

The general advice in the Aumha is helpful but the KB Articles are
from a number of years ago so they are not usually relevant to
current errors. To a certain extent many Microsoft KB Articles cease
to be relevant not too long after they have been published. Those
relating to specific Stop error codes often mislead to the extent
that users think they have a solution when all they have found is
one published solution when there are countless similar Stop Errors
where there is no published solution.

--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Nicm15 wrote:
UPDATE:

I ran Windows Debugger and it's coming back and stating that
I probably have memory corruption. How in the world do I go about
fixing such a thing? I've never encountered such a problem before.

Gerry in response to your questions, here's the site I went to
before finding out about this memory corruption issue.

http://aumha.org/a/stop.htm
I went to this site and clicked on the D1: Driver
IRQL_NOT_LESS_OR_EQUAL issue on the right hand side. I attempted to
install these two fixes that were recommended on the site.

http://support.microsoft.com/?kbid=839876&sd=RMVP
When I installed this one I got a message stating the service pack I
was running was newer than the fix so it didn't need to be
installed.

http://support.microsoft.com/?kbid=916595&sd=RMVP
I didn't have any problems installing this one but I'm still having
the same problem with the blue screen.

I use AVG Free 8.5 Anti-Virus as well as Malwarebytes because I
heard the latter of the two tends to notice viruses that other
anti-virus programs don't pick up on. I ran a full scan using both
of these programs and nothing turned up.

The mouse we use is wired.

So how do I go about repairing memory corruption?

:

I'm so confused. I have a dell Dimension 5100 it's running on
Windows XP Professional SP2 Media Center Edition, we've never had
any problems with this computer before. We started having problems
when we installed a DivX package that came with the Divx player and
codec and etc. and we upgraded our Adobe from 7.0 to 9.0. That was
when the BSOD made it's debut. Once the problem started, we went
into safe mode uninstalled these programs. We left DivX off and
put the original Adobe that we had back on the computer. The blue
screen still came up. I searched this forum and went to the
recommended site that had the various suggestions for this matter,
I downloaded the appropriate Hot Fixes, still no result. Finally,
I attempted to do a system restore, but our system restore refuses
to work, it gets to the confirm page and I click the next button
and absolutely nothing happens. We even left it running overnight
thinking it needed a while to restore and still no result. I'm out
of ideas at this point and totally lost. Does anybody have an idea
why this might be happening?
Click to expand...
Click to expand...
Click to expand...
 
G

Gerry

Nicm

Were you using the DVD drive when the Stop Error occurred?

Has the original firmware been updated?
http://support.dell.com/support/dow...ID=DIMENSION 5100&os=WW1&osl=en&catid=&impid=

http://snurl.com/kvqrw [support_dell_com]

Try some ther diagnostic tests.


--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Yes, I double checked, that's the whole thing. I ran a diagnostics
test via pressing F12 upon my dell screen at startup. Selected Hard
Drive Diagnostics and got the following information:

Drive 0: Maxtor 64080M0---Pass
Drive 1: No device
Drive 2: Philips DVD +/-RW DVD8631--Diagnostics not supported
Drive 3: No device

Does that information help any? Should I do a driver rollback of my
DVD drive?

Gerry said:
Nic

Have posted all the report as it looks truncated?


--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Gerry, thanks for explaining that to me about the knowledge base.
Here's the one the reports. I've checked just about all of them and
they're all saying possible memory corruption.

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


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

Symbol search path is: C:\WINDOWS\symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free
x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Jun 24 13:15:31.000 2009 (GMT-4)
System Uptime: 0 days 0:00:18.703
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {e1bb3000, 2, 0, f555ce85}

Probably caused by : memory_corruption (
nt!MiInsertPageFileInList+db )

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

1: 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: e1bb3000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f555ce85, address which referenced memory

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


READ_ADDRESS: e1bb3000

CURRENT_IRQL: 2

FAULTING_IP:
+2ab
f555ce85 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from f555e9f9 to f555ce85

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be
wrong. f8942d54 f555e9f9 80503960 8295f1d0 8056375c 0xf555ce85
f8942d7c 805379dd 8295f1d0 00000000 82bc63c8 0xf555e9f9
f8942dac 805ce858 8295f1d0 00000000 00000000
nt!MiInsertPageFileInList+0xdb f8942ddc 8054534e 805378ee 00000001
00000000 nt!`string'+0x20
f8942e64 00000000 00000000 da5c6000 fffdb83f
nt!WmiTraceMessageVa+0x2ab


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiInsertPageFileInList+db
805379dd ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!MiInsertPageFileInList+db

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 498c69f0

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xD1_nt!MiInsertPageFileInList+db

BUCKET_ID: 0xD1_nt!MiInsertPageFileInList+db

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





:

Nic

Please post the complete copy of the Debugger Report. It may be
long but once it has been posted it can be snipped in later posts.

The general advice in the Aumha is helpful but the KB Articles are
from a number of years ago so they are not usually relevant to
current errors. To a certain extent many Microsoft KB Articles
cease to be relevant not too long after they have been published.
Those relating to specific Stop error codes often mislead to the
extent that users think they have a solution when all they have
found is one published solution when there are countless similar
Stop Errors where there is no published solution.

--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Nicm15 wrote:
UPDATE:

I ran Windows Debugger and it's coming back and stating that
I probably have memory corruption. How in the world do I go about
fixing such a thing? I've never encountered such a problem
before.

Gerry in response to your questions, here's the site I went to
before finding out about this memory corruption issue.

http://aumha.org/a/stop.htm
I went to this site and clicked on the D1: Driver
IRQL_NOT_LESS_OR_EQUAL issue on the right hand side. I attempted
to install these two fixes that were recommended on the site.

http://support.microsoft.com/?kbid=839876&sd=RMVP
When I installed this one I got a message stating the service
pack I was running was newer than the fix so it didn't need to be
installed.

http://support.microsoft.com/?kbid=916595&sd=RMVP
I didn't have any problems installing this one but I'm still
having the same problem with the blue screen.

I use AVG Free 8.5 Anti-Virus as well as Malwarebytes because I
heard the latter of the two tends to notice viruses that other
anti-virus programs don't pick up on. I ran a full scan using
both of these programs and nothing turned up.

The mouse we use is wired.

So how do I go about repairing memory corruption?

:

I'm so confused. I have a dell Dimension 5100 it's running on
Windows XP Professional SP2 Media Center Edition, we've never had
any problems with this computer before. We started having
problems when we installed a DivX package that came with the
Divx player and codec and etc. and we upgraded our Adobe from
7.0 to 9.0. That was when the BSOD made it's debut. Once the
problem started, we went into safe mode uninstalled these
programs. We left DivX off and put the original Adobe that we
had back on the computer. The blue screen still came up. I
searched this forum and went to the recommended site that had
the various suggestions for this matter, I downloaded the
appropriate Hot Fixes, still no result. Finally, I attempted to
do a system restore, but our system restore refuses to work, it
gets to the confirm page and I click the next button and
absolutely nothing happens. We even left it running overnight
thinking it needed a while to restore and still no result. I'm
out of ideas at this point and totally lost. Does anybody have
an idea why this might be happening?
Click to expand...
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

BSOD 4
BSOD-Unmountable & others 25
BSOD/Error Message 6
Please Help! with my Documents Folder 1
Important message from Dixons Carphone 1
BSOD After WinXP Install 4
SP2 BSOD Problems 6
BSOD 0xBE 1

Top