[Consolidated reply to multiple posts from the same person] On Thu, Jun 18, 2009 at 8:55 PM, Brian Desmond <[email protected]> wrote: > Lm will list all loaded modules so you'll see every driver on your box.
Ah. Makes sense, then. As I said, I was cookbooking. One of the recipes said to run that command, so I did. :) > What you're looking for here when casually browsing is 3rd party > drivers which are old. Well, they'll all be at least a year and a half old, since that's when the laptop was installed. We generally don't update drivers unless there is a problem, and the ones in our standard RIS image are generally stable. These laptops have both been stable for over a year. Then they started bluescreening a few weeks ago. With the exact same codes. So it doesn't seem like a hardware problem. Since it's recent, that suggests a Windows Update broke something. I'm trying to figure out what broke. (It could be an update from something else, of course, but we haven't updated anything else on those computers recently.) > Note the F1 help in Windbg has excellent docs for > every command as well as every bugcheck. Tried it. It seems more reference than guidance. In other words, if I already know *what* to do, it will tell me *how* to do it. I don't know what to do. On Thu, Jun 18, 2009 at 8:58 PM, Brian Desmond <[email protected]> wrote: > I'd start as a simple task with updating the audio driver and then > if that doesn't help, SP3. Yah, I'm considering that. I just really hate to resort to shotgun debugging. (Shotgun debugging: "the making of relatively undirected changes to software in the hope that a bug will be perturbed out of existence". http://www.catb.org/jargon/html/S/shotgun-debugging.html) On Thu, Jun 18, 2009 at 8:53 PM, Brian Desmond <[email protected]> wrote: > _NT_SYMBOL_PATH=srv*c:\symbols\public*http://msdl.microsoft.com/download/symbols > > That is what mine looks like... Mine looks like that, plus it has all the subdirectories from C:\WINDOWS\SYMBOLS\ as well. (Since I took the time to download and install that entire package.) In full: C:\WINDOWS\Symbols\sys;C:\WINDOWS\Symbols\tsp;C:\WINDOWS\Symbols\wpc;C:\WINDOWS\Symbols\scr;C:\WINDOWS\Symbols\ocx;C:\WINDOWS\Symbols\ime;C:\WINDOWS\Symbols\iec;C:\WINDOWS\Symbols\exe;C:\WINDOWS\Symbols\ds;C:\WINDOWS\Symbols\drv;C:\WINDOWS\Symbols\dll;C:\WINDOWS\Symbols\dic;C:\WINDOWS\Symbols\cpl;C:\WINDOWS\Symbols\com;C:\WINDOWS\Symbols\cnv;C:\WINDOWS\Symbols\ax;C:\WINDOWS\Symbols\acm;srv*c:\symbols*http://msdl.microsoft.com/download/symbols > .symfix c:\symbols Completed silently. > .reload Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols Unable to load image portcls.sys, Win32 error 0n2 *** ERROR: Module load completed but symbols could not be loaded for portcls.sys Loading User Symbols Loading unloaded module list > .sympath Symbol search path is: srv* Expanded Symbol search path is: cache*c:\symbols;SRV*http://msdl.microsoft.com/download/symbols > .exepath <paste> So I did: .exepath cache*c:\symbols;SRV*http://msdl.microsoft.com/download/symbols Which said: Executable image search path is: cache*c:\symbols;SRV*http://msdl.microsoft.com/download/symbols Expanded Executable image search path is: cache*c:\symbols;srv*http://msdl.microsoft.com/download/symbols > .reload Same as before. The "kb" command is the same as before, also. So, thanks (seriously), but I'm still stuck in the mud. :-( -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
