Re: Stop 0x50 w/ Verifier & WinDBG loaded
- From: "Chris Swinney" <swin@xxxxxxxxxxxxx>
- Date: Wed, 13 Jul 2005 12:34:50 +0100
Did you manage to resolve this issue. We have a similar error with a
PAGE_FAULT_IN_NONPAGED_AREA blue screen.
Ours seems to be profile related not hardware related. The stops appear to
be random but we can force the issue by simply searching the registry for a
text string that would not exist (eg "Testest"). This WILL ALWAYS cause a
blue screen stop 50 error at the end of the registry search in certain
profiles, yet in others, the error will not happen. However, we have run
certain stress tests and mrmory test with no problems.
Chris
"Kelly" <kelly@xxxxxxxx> wrote in message
news:%23Y$SPAmZFHA.1088@xxxxxxxxxxxxxxxxxxxxxxx
> It showed fine.
>
> Suggestions:
>
> Using an NNTP Newsreader
> http://www.microsoft.com/communities/guide/nntpnews.mspx
>
> For a better way to access these newsgroups look here:
> http://michaelstevenstech.com/outlookexpressnewreader.htm
> http://www.microsoft.com/windowsxp/pro/using/newsgroups/setup.asp
> http://support.microsoft.com/default.aspx?scid=fh;[ln];newswhelp
>
> --
>
> All the Best,
> Kelly (MS-MVP)
>
> Troubleshooting Windows XP
> http://www.kellys-korner-xp.com
>
>
>
> "Ron Garnett" <RonGarnett@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:0428AF15-BC3F-47F3-8445-14C1F8CFBB7D@xxxxxxxxxxxxxxxx
> > My last reply seemed to go away, so I apologize if this is a dupe.
> >
> > Thanks for the links. The viral things didn't pan out. I had seen
those
> > and tried already, but no signatures appeared.
> >
> > I actually crashed while trying to get to the first link, but it was
> > before
> > I had finished the cut and paste operation. OCA told me that the video
> > driver was hung, but the crash dump was the old stop 0x50 with no
details
> > on
> > which driver failed. I turned off acceleration anyway, just in case.
> >
> > Ron
> >
> >
> > --
> > Ron Garnett
> >
> >
> > "Unrepper" wrote:
> >
> >>
> >>
> >> "Unrepper" wrote:
> >>
> >> >
> >> >
> >> > "Ron Garnett" wrote:
> >> >
> >> > > Dell D600 M Laptop
> >> > > 512 MB RAM
> >> > > 1.7 GHz Centrino
> >> > > BugCheck 50, {ff909000, 0, 804e422b, 0}
> >> > >
> >> > > I have been fighting a stop 0x50 error for several months now.
> >> > > Dell has
> >> > > replaced motherboard, memory, processor, and HD. 2 other people in
> >> > > my area
> >> > > with the exact same configuration have the same problem, and it
> >> > > started
> >> > > happening for all of us around March. I went to SP2 to hopefully
fix
> >> > > this,
> >> > > but it didn't help and possibly made it worse. I am in SP1 right
> >> > > now.
> >> > >
> >> > > I have multiple mini and kernel dump files. The first set was
> >> > > prior to
> >> > > turning on the verifier. It shows a random mem address in upper
> >> > > memory, but
> >> > > always the same source address which shows up in the NT kernel
itself
> >> > > 804e422b.
> >> > >
> >> > > Turning on the verifier switched all of the blue screens to
> >> > > 0xC4_090
> >> > > errors instead. I used SiSoft Sandra to exercise the system, and
got
> >> > > consistent failures during the HD test with verifier on. I could
not
> >> > > even
> >> > > run that test without crashinng.
> >> > >
> >> > > The first post-verifier dump identified SAVRT.SYS, so I disabled
> >> > > all
> >> > > Symantec Antivirus services (9.0 Corporate) and processes and tried
> >> > > again.
> >> > > Next, it reported a fault back in ntoskrnl.exe. I backed out one
of
> >> > > the
> >> > > following hotfixes to put NTOSKRNL.EXE back prior to March 2005
> >> > > (890859,826939, 885835). These hotfixes werre pushed down by a
> >> > > corporate
> >> > > auto-update tool, which I suspect is the reason why this started
> >> > > happening
> >> > > all of a sudden.
> >> > >
> >> > > With an October 2004 version of NTOSKRNL.EXE resinstalled, I ran
> >> > > the
> >> > > SiSoft disk test twice in a row with no problems. I don't have
> >> > > enough run
> >> > > time to prove this 100%, but if this fixes it then I can't upgrade
to
> >> > > SP2 or
> >> > > accept further security updates on these three Dell systems.
> >> > >
> >> > > Dell is trying to troubleshoot this, as is our IT department.
> >> > > But, we
> >> > > clearly need Microsoft's help in taking it to the next level.
WinDBG
> >> > > is
> >> > > helpful, but I am a novice in using it. I am a firmware programmer
> >> > > by trade,
> >> > > but am not skilled in Windows kernel troubleshooting.
> >> > >
> >> > > I can forward whichever dumps and logs you want.
> >> > >
> >> > > Regards,
> >> > > Ron Garnett
> >> > >
> >> > Here's one referal to the 0x50
> >> >
> >> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/
> >> > ddtools/hh/ddtools/BCCodes_afaf4889-08de-40ea-b335-729d8213f3b5
> >> > .xml.asp
> >> >
> >> > also take a look here
> >> > http://support.microsoft.com/?kbid=894278&sd=RMVP#kb1
> >> >
> >> > the search will go on.
> >>
> >> We might be getting closer
> >>
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;897079
> >>
> >> If I'm off the mark just say so.
>
>
.
- Prev by Date: Re: dual boot!!!!!
- Next by Date: Re: Laptop?
- Previous by thread: Installing Fax Services
- Next by thread: Loading New Softwear
- Index(es):
Relevant Pages
|
