Re: Bugcheck 101

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

This is stack of an idle processor, doing nothing. intelpp is
processor-specific driver providing, besides from other thing, a
power-saving idle loop.

Your problem is on a differrent proc.

"alberto" <amoreira@xxxxxxxx> wrote in message
news:74926d8c-808e-4d7f-baca-fb2709c5f3b7@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
This is what the stack in the hung processor looks like:

fffffa60`00b92685 : 00000000`dfe5f0a2 00000000`00000008
fffffa60`017d8180 fffff800`02055979 : intelppm!C1Halt+0x2
fffff800`0208f7f8 : fffffa60`017db580 fffffa60`017e1d40
fffffa60`0000040e fffffa60`017ffd40 : intelppm!C1Idle+0x9
fffff800`0207eb21 : fffffa60`017d8180 00000000`00061c82
00000000`00000000 00000000`00000000 : nt!PoIdle+0x148
fffff800`0224c5c0 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x21

I was assuming that the problem was created by the other processor,
but, thanks! This gives me new food for thought. I'll disable
intelppm.sys and see what happens!

Alberto.



On Dec 5, 4:07 pm, "Scott Noone" <sno...@xxxxxxx> wrote:
I've never actually hit this bugcheck, but I'll bite.

The bugcheck information should show the hung processor. Have you looked
at
the call stack on that processor to see why it's locked up?

-scott

--
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.http://www.osronline.com

"Alberto" <more...@xxxxxxxxxxxxx> wrote in message

news:38960766-493e-4629-8459-02f4e82d662f@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



Hi, All,

I bumped into a nasty, hard to debug crash. It's a Bugcheck 101. It
happens when we run one of our products on our Vp2000 volume rendering
board: after we play with images for ten or fifteen minutes, the
machine gets unresponsive and after a few more seconds we get the blue
screen. This is a 4-processor Dell 5400 with hyperthreading on and
running 64-bit Vista. There's a lot going on in there at the time of
the crash, and all 8 virtual processors are busy at that time.

By the time the dump gets taken, the system's long gone into la-la
land, and there isn't much in the dump that's useful to diagnose
what's going on. The crash is supposed to be a processor timeout
waiting for a timer interrupt, and while processor 3 is the timed out
processor, a thread in processor 0 seems to be at IRQL 13, which is
the level for the Amd64 timer interrupt. If that's a sustained
situation, that might explain what's going on, although actually
tracking it requires more work.

There isn't much on the web about this Bugcheck, except the normal
"make sure your hw is not overheating or this or that" or "download
your latest bios and video drivers". No indication of what in those
new versions might actually have fixed the problem!

My user has Daemon Tools installed, and I hear that they install a
hard-to-get-rid-of driver called sptd.sys. People on the web say that
sptd.sys sometimes interacts with the rest of the system in ways that
end up generating a Bugcheck 101. My user uninstalled Daemon Tools but
the crash is still there, and I'm pretty sure that sptd.sys has not
been disabled.

My question is, do any of you have any experience with this Bugcheck
you might be willing to share ? At this point, any information,
however minor, will be highly appreciated!

Thanks,

Alberto.- Hide quoted text -

- Show quoted text -




.

Relevant Pages

  • Re: a dozen cpus on a chip
    ... It is still possible to write something that will crash, ... memory, or write to memory it doesn't own should be terminated with a ... I think that hardware designers could do a lot to improve matters. ... Having a call-return stack, a parameter stack, return value area, and ...
    (sci.electronics.design)
  • Re: boot failure, "DWARF2 unwinder stuck at 0xc0100199"
    ... The way that code reads the stack is just ... this unwinder change has been quite problematic. ... add new crashes and the fallback always gives an useful backtrace (that is why I ... Has anyone even tried to reproduce Bruce's crash? ...
    (Linux-Kernel)
  • Re: wuauclt.exe has encountered a problem...
    ... That is the full extent of the message and pop-up detail. ... Have you disabled the Error Reporting Tool? ... to extract from it a list of the modules involved in the call stack at the time ... I'm suggesting only that you find the one entry which represents your crash event. ...
    (microsoft.public.windowsupdate)
  • Win32 DLL project randomly crashes after moving to VS2005
    ... the first step was to take care of the compilation ... The problem is that when I run my DLL it crashes in apparently random places ... I had a crash within a dialog's window procedure and another ... image library were generating a "stack overflow" message. ...
    (microsoft.public.vc.ide_general)
  • Re: Bugcheck 101
    ... This is what the stack in the hung processor looks like: ... The bugcheck information should show the hung processor. ... the crash, and all 8 virtual processors are busy at that time. ... waiting for a timer interrupt, and while processor 3 is the timed out ...
    (microsoft.public.development.device.drivers)