You don't have symbols in that stack. Please do this:
.symfix c:\symbols .reload .sympath <copy and paste the stuff it prints .exepath <paste> .reload _NT_SYMBOL_PATH=srv*c:\symbols\public*http://msdl.microsoft.com/download/symbols That is what mine looks like... Thanks, Brian Desmond [email protected] c - 312.731.3132 -----Original Message----- From: Ben Scott [mailto:[email protected]] Sent: Thursday, June 18, 2009 7:27 PM To: NT System Admin Issues Subject: Re: STOP 0xD1 in PORTCLS.SYS recently? On Tue, Jun 16, 2009 at 9:50 PM, Ken Schaefer <[email protected]> wrote: > This is what an IRQL is, and why IRQL_NOT_LESS_OR_EQUAL bugchecks your > machine: > http://www.adopenstatic.com/cs/blogs/... Okay, I followed to the second page and tried some of your debugging advice. (Excellent write-ups, BTW!) The "kb" command says: WARNING: Stack unwind information not available. Following frames may be wrong. baccffa0 80501833 ed1f189c ffdff9c0 ffdff000 portcls+0xf21 baccffcc 805450df 8055b4a0 00000000 00071970 nt+0x2a833 baccffd0 8055b4a0 00000000 00071970 00000000 nt+0x6e0df baccffd4 00000000 00071970 00000000 00000000 nt+0x844a0 The "lmv" command lists what looks like every driver used by the system. I see SATA, IDE, NDIS, serial, USB, and other stuff. Am I doing something wrong? Well, okay, obviously, I am. Any idea what it is? :) -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
