Re: SP 2 compatibility problem

Tech-Archive recommends: Fix windows errors by optimizing your registry

Cool, David you obviously know your stuff and I appreciate the list of error
codes!!

I'm assuming by what Kerry said...I'm to be concerned by this one...

0x781 The PTEs mapping the argument system cache view have been corrupted.

Would someone be interested in translating that into something a novice
would understand?? Perhaps and hopefully pinpointing the problem!!

Thanks
Roger

"David Candy" wrote:

> Parameter 1 Cause of Error
> 0x1 The fork clone block reference count is corrupt. (This only occurs on checked builds of Windows.)
> 0x777 The caller is unlocking a system cache address that is not currently locked. (This address was either never mapped or is being unlocked twice.)
> 0x778 The system is using the very last system cache view address, instead of preserving it.
> 0x780
> 0x781 The PTEs mapping the argument system cache view have been corrupted.
> 0x1000 A caller of MmGetSystemAddressForMdl* tried to map a fully-cached physical page as non-cached. This action would cause a conflicting hardware translation buffer entry, and so it was refused by the operating system. Since the caller specified "bugcheck on failure" in the requesting MDL, the system had no choice but to bugcheck in this instance.
> 0x1010 The caller is unlocking a pageable section that is not currently locked. (This section was either never locked or is being unlocked twice.)
> 0x1234 The caller is trying lock a nonexistent pageable section.
> 0x1235 The caller is trying to protect an MDL with an invalid mapping.
> 0x3451 The PTEs of an outswapped kernel thread stack are corrupt.
> 0x8888
> 0x8889 Internal memory management structures are corrupt.
> 0x41283 The working set index encoded in the PTE is corrupt.
> 0x41284 A PTE or the working set list is corrupt.
> 0x41286 The caller is trying to free an invalid pool address.
> 0x41785 The working set list is corrupt.
> 0x61940 A PDE has been unexpectedly invalidated.
> Other An unknown memory management error occurred.
>
>
> --
> ----------------------------------------------------------
>
> "Kerry Brown" <kerry@xxxxxxxxxxxxxxxxxx*o*m> wrote in message news:uRSY2eIOFHA.2728@xxxxxxxxxxxxxxxxxxxxxxx
> > "rogval" <rogval@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:CDBFE255-24A7-4226-B6C4-B80CA91C43D5@xxxxxxxxxxxxxxxx
> >> Ok...how about this.....
> >> memory_management
> >> Stop error 0x0000001a (0x0000781, 0xc0306100, 0x8111b8c0, 0x8111b8d0)
> >>
> >> My uppercase doesn't work on some of my keys on this laptop...so if you
> >> need
> >> some of those letters in specific form, let me know, I will do some
> >> pasting
> >> and copying!!
> >>
> >> Roger
> >>
> >
> > Roger
> >
> > Thanks for posting the error message. The key parameter is the first one
> > 0x0000781. Unfortunately I can't find any info on this error. Maybe someone
> > else will be able to help.
> >
> > Kerry
> >
> >
.

Relevant Pages

  • Re: Is it possible to use the value of the PROGRAM ID within the source code?
    ... Every called program has a way of returning to its caller. ... >information about calling history in some sort of hardware stack? ... True but discordant with the culture of operating systems and other languages. ... premise is that called programs may irrationally corrupt parameter values. ...
    (comp.lang.cobol)
  • Re: [9fans] quantity vs. quality
    ... As long as the stack isn't corrupt, it _can_ still return to the ... The argument is really whether the caller can be trusted to ... he won't test his recovery code, but that is not an acceptable ... under error conditions. ...
    (comp.os.plan9)