[coLinux-devel] Re: BSOD, kd> !analyze -v

[ePAc <ep...@ko...>]

> I have some output from the kernel debugger, but i don't have the symbols
> files (gotta hunt those suckers down on the MS website), and no linux.pdb
> to trace either.

this is the output (minus the big useless boxes).
it loads in the windbg, and gives me some "disassembly". Dan, is you want
to have a look at it, i'd be more than happy to give you more info.. :o)

--------------------------------------------------------------------------

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: eea5e000, Virtual address for the attempted write.
Arg2: 81ec1b38, PTE contents.
Arg3: eebe0aa8, (reserved)
Arg4: 0000000e, (reserved)

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.


DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xBE

LAST_CONTROL_TRANSFER:  from 80511b47 to 804f4103

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be
wrong.
eebe0a44 80511b47 000000be eea5e000 81ec1b38 nt!KeBugCheckEx+0x19
eebe0a90 80530140 00000001 eea5e000 00000000 nt!MmTrimAllSystemPagableMemory+0x50f1
eebe0aa8 00000000 c03ba778 eebe0ad4 eeda621d nt!Kei386EoiHelper+0x2388


FOLLOWUP_IP:
nt!MmTrimAllSystemPagableMemory+50f1
80511b47 833dbc30548000 cmp dword ptr [nt!LpcPortObjectType+0x114
(805430bc)],0x0

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  nt!MmTrimAllSystemPagableMemory+50f1

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  kb

BUCKET_ID:  WRONG_SYMBOLS

MODULE_NAME:  Unknown_Module

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

I hope this makes more sense to some of you than to me...

this the the bugcheck i got after a clean boot, running it once, and got a
error -15 (as mentioned in other posts), and on the second try, a couple
of minutes later, this BSOD.

---
Nothing is foolproof to a sufficiently talented fool...
  oo
,(..)\
  ~~