From: garwil on
Hi,
XP PRo seems to work fine and then all of a sudden it reboots. The sytem
event viewer says "The computer has rebooted from a bugcheck. The bugcheck
was: 0x1000000a (0x00000004, 0x00000002, 0x00000000, 0x804e6d3f). A dump was
saved in: C:\WINDOWS\Minidump\Mini022005-02.dmp."
What could have caused a bug check to start? Trying to view the content of
the minidump reveals nothign but lines and lines of letters and numbers and
does not help one trying to solve problems of this nature.
Can anyone give me an idea what could be at fault?
Many thanks
From: "Rick "Nutcase" Rogers" on
Hi,

You need to use a debugger to read the .dmp file. You can send it to me if
you wish, I might be able to point out where the problem is. Use the email
address used here (rick(a)mvps.org) and make the subject line "per req"
(without the quotes) or it won't get past my filters.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Associate Expert - WindowsXP Expert Zone
www.microsoft.com/windowsxp/expertzone
Windows help - www.rickrogers.org

"garwil" <garwil(a)discussions.microsoft.com> wrote in message
news:60B22C85-6512-42EA-AF49-98B3F948C6B4(a)microsoft.com...
> Hi,
> XP PRo seems to work fine and then all of a sudden it reboots. The sytem
> event viewer says "The computer has rebooted from a bugcheck. The
> bugcheck
> was: 0x1000000a (0x00000004, 0x00000002, 0x00000000, 0x804e6d3f). A dump
> was
> saved in: C:\WINDOWS\Minidump\Mini022005-02.dmp."
> What could have caused a bug check to start? Trying to view the content of
> the minidump reveals nothign but lines and lines of letters and numbers
> and
> does not help one trying to solve problems of this nature.
> Can anyone give me an idea what could be at fault?
> Many thanks


From: garwil on
Hi Rick,

Email sent..Many thanks and gratefule for your help


"garwil" wrote:

> Hi,
> XP PRo seems to work fine and then all of a sudden it reboots. The sytem
> event viewer says "The computer has rebooted from a bugcheck. The bugcheck
> was: 0x1000000a (0x00000004, 0x00000002, 0x00000000, 0x804e6d3f). A dump was
> saved in: C:\WINDOWS\Minidump\Mini022005-02.dmp."
> What could have caused a bug check to start? Trying to view the content of
> the minidump reveals nothign but lines and lines of letters and numbers and
> does not help one trying to solve problems of this nature.
> Can anyone give me an idea what could be at fault?
> Many thanks
From: "Rick "Nutcase" Rogers" on
Additional information for those following the thread:

An !Analyze -v of the .dmp gives the following report, seems to be related
to having wampserver installed at one point. Any additional thoughts would
be welcome, as I am not familiar with that server application:

***************************************************
* 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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804e6d3f, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: 00000004
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiRemovePageByColor+6a
804e6d3f 8b4804 mov ecx,[eax+0x4]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from 80500a9d to 804e6d3f
STACK_TEXT:
ebf21cec 80500a9d c0300044 c0011d38 84e0d020 nt!MiRemovePageByColor+0x6a
ebf21d04 804e9c35 0474e000 c0011d38 84e0d020
nt!MiResolveDemandZeroFault+0xa5
ebf21d4c 804e1ff1 00000001 0474e000 00000001 nt!MmAccessFault+0x7e8
ebf21d64 7c910c71 badb0d00 00018000 00000000 nt!KiTrap0E+0xcc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0456e578 00000000 00000000 00000000 00000000 0x7c910c71

FOLLOWUP_IP:
nt!MiRemovePageByColor+6a
804e6d3f 8b4804 mov ecx,[eax+0x4]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!MiRemovePageByColor+6a
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 41108004
STACK_COMMAND: kb
IMAGE_NAME: memory_corruption
BUCKET_ID: 0xA_nt!MiRemovePageByColor+6a
Followup: MachineOwner

***end analysis***

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Associate Expert - WindowsXP Expert Zone
www.microsoft.com/windowsxp/expertzone
Windows help - www.rickrogers.org

"Rick "Nutcase" Rogers" <rick(a)mvps.org> wrote in message
news:%230PXBd0FFHA.1456(a)TK2MSFTNGP09.phx.gbl...
> Hi,
>
> You need to use a debugger to read the .dmp file. You can send it to me if
> you wish, I might be able to point out where the problem is. Use the email
> address used here (rick(a)mvps.org) and make the subject line "per req"
> (without the quotes) or it won't get past my filters.
>
> --
> Best of Luck,
>
> Rick Rogers, aka "Nutcase" - Microsoft MVP
> http://mvp.support.microsoft.com/
> Associate Expert - WindowsXP Expert Zone
> www.microsoft.com/windowsxp/expertzone
> Windows help - www.rickrogers.org
>
> "garwil" <garwil(a)discussions.microsoft.com> wrote in message
> news:60B22C85-6512-42EA-AF49-98B3F948C6B4(a)microsoft.com...
>> Hi,
>> XP PRo seems to work fine and then all of a sudden it reboots. The sytem
>> event viewer says "The computer has rebooted from a bugcheck. The
>> bugcheck
>> was: 0x1000000a (0x00000004, 0x00000002, 0x00000000, 0x804e6d3f). A dump
>> was
>> saved in: C:\WINDOWS\Minidump\Mini022005-02.dmp."
>> What could have caused a bug check to start? Trying to view the content
>> of
>> the minidump reveals nothign but lines and lines of letters and numbers
>> and
>> does not help one trying to solve problems of this nature.
>> Can anyone give me an idea what could be at fault?
>> Many thanks
>
>


From: BBUNNY on
garwil wrote:
| Hi,
| XP PRo seems to work fine and then all of a sudden it reboots. The
| sytem event viewer says "The computer has rebooted from a bugcheck.
| The bugcheck was: 0x1000000a (0x00000004, 0x00000002, 0x00000000,
| 0x804e6d3f). A dump was saved in:
| C:\WINDOWS\Minidump\Mini022005-02.dmp."
| What could have caused a bug check to start? Trying to view the
| content of the minidump reveals nothign but lines and lines of
| letters and numbers and does not help one trying to solve problems of
| this nature.
| Can anyone give me an idea what could be at fault?
| Many thanks

Go to CPL>>Internet Options>>Advanced>>
[ ] Disable script Debugging (internet explorer)
[ ] Disable script Debugging (other)

These were checked by default on both XPH and XPP SP2.