debug info from .dmp. I was able to move the dmp to a usb drive and on
another computer install windbg. I extracted the stack info but I dont see
any driver names there, unless I dont see it. Heres the stack:
kd> kb
ChildEBP RetAddr Args to Child
9bdb3c20 81cad9bb badb0d00 00001d50 00000004 nt!KiTrap0E+0x2ac
9bdb3cb0 81cac462 00000000 0012fc34 81e90b59 nt!KiInsertTimerTable+0x2f
9bdb3d08 81e90bf1 00000101 00000000 9bdb3d2c nt!KeDelayExecutionThread+0x36b
9bdb3d54 81c8caaa 00000000 0012fc68 0012fc8c nt!NtDelayExecution+0x8d
9bdb3d54 77340f34 00000000 0012fc68 0012fc8c nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fc8c 00000000 00000000 00000000 00000000 0x77340f34
Thanks for your help.
"Mark L. Ferguson" wrote:
> If you are saying safe mode runs, you can run the command:
> perfmon /rel
>
> to get a better idea of the problem.
> --
> Was this helpful? Then click the Ratings button. Voting helps the web
> interface.
> http://www.microsoft.com/wn3/locales...eAPostAsAnswer
> Mark L. Ferguson
> .
>
> "microsvc" <(E-Mail Removed)> wrote in message
> news:C0FEBF37-47FA-4110-BD98-(E-Mail Removed)...
> > When I boot, the desktop displays then a few seconds later I get a Blue
> > Screen 0x0000000a followed by some numbers. Booting into
> > safe mode, I can get more info about this:
> >
> > Problem signature:
> > Problem Event Name: BlueScreen
> > OS Version: 6.0.6000.2.0.0.768.3
> > Locale ID: 1033
> >
> > Additional information about the problem:
> > BCCode: a
> > BCP1: 006C0065
> > BCP2: 0000001B
> > BCP3: 00000000
> > BCP4: 81CAD9BB
> > OS Version: 6_0_6000
> > Service Pack: 0_0
> > Product: 768_1
> >
> > Files that help describe the problem:
> > C:\Windows\Minidump\Mini040908-01.dmp
> > C:\Windows\System32\config\systemprofile\AppData\Local\Temp\WER-69843-0.sysdata.xml
> > C:\Windows\System32\config\systemprofile\AppData\Local\Temp\WERBADF.tmp.version.txt
> >
> > I have already backed up on the restore points by several levels. I
> > remember one of the last windows updates included Audio drivers, and other
> > drivers. From safe mode, can I see what was installed? I have "rolled
> > back"
> > the audio already and unchecked several things in msconfig. ntbtlog.txt
> > has
> > the last driver installed as cdfs.sys.
> >
> > *** I have reviewed the .dmp and .xml file. What can the contents of
> > these
> > files do to help me see whats exactly causing this problem? ***
> >
> > Ideas? I'm desperate. Thanks!
> > ~Bob
> >
> >