F
FuzzyCritter
Tried posting this about 4 hours ago, however, I don't see it here.
MS please read the text file.
MS please read the text file.
R
Ron Martell
FuzzyCritter <snowbunny@msn.com> wrote:
>Tried posting this about 4 hours ago, however, I don't see it here.
>MS please read the text file.
Microsoft does not respond to questions posted on these newsgroups,
although some Microsoft employess do so on occasion. But there is no
guarantee.
Now to your problem
Your text file says: Stop: 0x000000c4 (0x00000081, 0x85197a93, blah
blah blah)
There is no known instance of a STOP error with parameter values of
blah blah blah.
However the specific error that you are dealing with is
DRIVER_VERIFIER_DETECTED_VIOLATION, and for your specific instance the
value in parameter 1 is sufficient to identify the cause. The value
you reported is 0x00000081 which, according to
http://msdn2.microsoft.com/en-us/library/ms796113.aspx, means the
culprit is "the driver called MmMapLockedPages. (You should use
MmMapLockedPagesSpecifyCache instead, with the BugCheckOnFailure
parameter set to FALSE.)"
Why are you running VERIFIER? Is there an additional problem that you
are trying to track down with this utility? Does VERIFIER provide any
reports of suspect drivers?
Good luck
Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair
"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
>Tried posting this about 4 hours ago, however, I don't see it here.
>MS please read the text file.
Microsoft does not respond to questions posted on these newsgroups,
although some Microsoft employess do so on occasion. But there is no
guarantee.
Now to your problem
Your text file says: Stop: 0x000000c4 (0x00000081, 0x85197a93, blah
blah blah)
There is no known instance of a STOP error with parameter values of
blah blah blah.
However the specific error that you are dealing with is
DRIVER_VERIFIER_DETECTED_VIOLATION, and for your specific instance the
value in parameter 1 is sufficient to identify the cause. The value
you reported is 0x00000081 which, according to
http://msdn2.microsoft.com/en-us/library/ms796113.aspx, means the
culprit is "the driver called MmMapLockedPages. (You should use
MmMapLockedPagesSpecifyCache instead, with the BugCheckOnFailure
parameter set to FALSE.)"
Why are you running VERIFIER? Is there an additional problem that you
are trying to track down with this utility? Does VERIFIER provide any
reports of suspect drivers?
Good luck
Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair
"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."