PC Locks up - Error Event ID 8003

[dalangley]

Since my last post i have started WoW and so far no lockups at 3 PM. So far so good.

[cluberti]

Neither of those events are run on synch or blocking threads, it's all async. Therefore, neither event should "lock up" your PC. If it really *is* hanging up when this happens, it's very much more likely that there's a driver problem, below explorer.exe (kernel-mode driver, LSP on the network stack, etc) that is misbehaving. Again, these operations are done on async threads that simply report back to the caller after a time, so these would not have any way to block the OS (in fact, unless someone or something blocks the waiting thread, it's impossible).

[dalangley]

Neither of those events are run on synch or blocking threads, it's all async. Therefore, neither event should "lock up" your PC. If it really *is* hanging up when this happens, it's very much more likely that there's a driver problem, below explorer.exe (kernel-mode driver, LSP on the network stack, etc) that is misbehaving. Again, these operations are done on async threads that simply report back to the caller after a time, so these would not have any way to block the OS (in fact, unless someone or something blocks the waiting thread, it's impossible).

Where would I check for these?

UPDATE: Since 1:45 CST the Event Log has reported no errors. No 15016 or 8003. So far so good.

Edited November 10, 2008 by dalangley

[Nerwin]

I agree with Cluberti (and he knows his stuff ) My first thought was it's a drive problem, Windows could say the driver is fine. Like I thought I had a good Nivida Graphics driver and windows said it was good, but it was causing all sorts of problems.. Did windows update any drivers by it self? or did you update any drivers recently? or Installed some peice of hardware? External or Internal?

Hey i'm just narrowing it down, Nothing wrong with that!

[dalangley]

No new hardware has been installed. And no new drivers have been installed.

[Nerwin]

Hmmm... Interesting! Just for giggles, Download Ccleaner (Crap Cleaner) and she how many registry problems and other crap it found. I dunnoi if it would help any, but when I am having problems with my system, I just run that and it seems to go away.

[dalangley]

I ran CCleaner and it found alot! Luckily its free and cleared everything. Still no crash.

[Nerwin]

Well good!

[PfrancoIT]

Hello Im new here.. =D

Im an I/T director Server Admin Network Admin =D you name it.

Anyway, Ive noticed on a lot of workstations areound our networks running Vista Business and Ultimate that if you disable the Desktop Window Manager service and manually stop it, it resolves this problem on most of our machines.

My only simple explanation I can come up with is this.

I Beleive the DWM actually eats up a lot of memory and resource on the processor. In fact if you have ever noticed your computer running and the Processor Fan going nonstop that is an indicator that your chip is heating up (NOT OVERHEATING BUT HEATING UP AS IT SHOULD) and the fan is cooling it. This will only happen when the processor starts doing some actual work. 98.9 percent of the time its the DWM. And the DWM is just running away and heating that Chip up constantly while you are using the workstations. But funny the computer is silent when no one is on it but it is still on. (No Windows to manage no need to run =D) Any way I belevei that this resource Hogging and the fact that windows is generating a error to the log reporting service etc, think just casues a cache or memory conflict. I dont think there is any relevance in the DWM to the actual 15016 Error but I do believe the resource utalization on both the Kerberos Auth Error and the DWM is too much.. I have also noticed that this is not so much of an issue on all of the Dual Core Machines we run. Usually happens more on the Prescott P4's and AMD X64 Chips.. And Im pretty sure that it becasue the Dual Core processor's disperse the resources evenly as opposed to the single core.

But i can tell you that on every machine this happens on, I go in and disable the DWM and no more crashes and freezes. The error is still in the log but the spuratic freezes cease. Therefore i believe it is not the actuall error or the Kerb. Auth Service causing this but it is the DWM.

Hope this helps

Good luck.

Paul

Good Luck hope this helps....

Edited November 11, 2008 by PfrancoIT