Shutdown woes

The last week or so, After being on for 2 or 3 days, when I try to shutdwn nothing happens. No saving settings, windows is shutting dwn. After 3 minutes I hit the button. & today I came in & was hung on screen saver. A clue please. Temp. is ok, did scan dsk. virus scan.
But I'm baffled. just updated the 2k, ones I thought I needed & will not restart, have to reset. Forgot how to run sfc. sfc/scannow? yes.
Ok. Here's where I'm (at). I have ran spy-bots., sfc, JV16, reg.1st aid. Will try shutdown again. Same ****! Clueless in Ms. Thanks Bb

 

Yup. start~run~sfc /scannow (and note the space after sfc).

After that I'd also check the event logs for clues. Easiest to clear the current contents, crash the server (2K doesn't really mind if you shut down via the button or pulling the power cord once in a while), restart, try a normal shutdown, and after a restart, look at the logs. If you see anything that looks iffy but doesn't make sense, post it (them) here. Easiest is to open an event, click the icon under the up/down arrows (sends a text copy to the clipboard) and paste that here. Less typing and gives us the exact, complete entry.

And before you reboot, start~run~cmd and chkdsk /r on each of your drives. That way they'll get checked while the PC restarts. Could take a while but well worth doing.

 

Event viewer

TKS, Newt. Here's 1st event when I rebooted while ago.
Event Type: Error
Event Source: Mouclass
Event Category: None
Event ID: 9
Date: 5/20/2003
Time: 6:59:03 PM
User: N/A
Computer: PERSONAL-MLABQU
Description:
Could not enable interrupts on connected port device \Device\PointerClass0.
Data:
0000: 00 00 00 00 01 00 5a 00 ......Z.
0008: 00 00 00 00 09 00 05 c0 .......À
0010: 98 4e 00 00 03 01 00 c0 ˜N.....À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

The other is
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 5/20/2003
Time: 2:17:17 PM
User: N/A
Computer: PERSONAL-MLABQU
Description:
The ASPI32 service failed to start due to the following error:
The system cannot find the file specified.

The service control error has been around for months. Thanks BB

 

App log

This's from the app. log . Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 5/20/2003
Time: 7:01:18 PM
User: NT AUTHORITY\SYSTEM
Computer: PERSONAL-MLABQU
Description:
Windows cannot unload your registry file. If you have a roaming profile, your settings are not replicated. Contact your administrator.

DETAIL - Access is denied. , Build number ((2195)).

 

The app log userenv error should be fixed by SP3. It might well fix some other issues for you as well.

Have to research the other two. And the first one does ring some alarm bells. It points to a setup problem with your mouse but not sure exactly what effect that might have. Q164403 deals with a problem that sounds almost like yours but it is event 10 and the error is a failure to disable interrupts rather than your failure to enable them.

I think that in the meantime, you should look for a BIOS update and if you find one, install it.

 

App. log

I just ran SP-3 again. Now I see this in App. log
Event Type: Error
Event Source: True Vector Engine
Event Category: None
Event ID: 1
Date: 5/21/2003
Time: 3:54:27 PM
User: N/A
Computer: PERSONAL-MLABQU
Description:
The description for Event ID ( 1 ) in Source ( True Vector Engine ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: .
Data:
0000: 44 61 74 61 62 61 73 65 Database
0008: 20 66 69 6c 65 20 43 3a file C:
0010: 5c 57 49 4e 4e 54 5c 49 \WINNT\I
0018: 6e 74 65 72 6e 65 74 20 nternet
0020: 4c 6f 67 73 5c 49 41 4d Logs\IAM
0028: 44 42 2e 52 44 42 20 77 DB.RDB w
0030: 61 73 20 69 6d 70 72 6f as impro
0038: 70 65 72 6c 79 20 73 68 perly sh
0040: 75 74 20 64 6f 77 6e 2e ut down.
0048: 20 20 52 65 73 74 6f 72 Restor
0050: 69 6e 67 20 62 61 63 6b ing back
0058: 75 70 20 72 75 6c 65 73 up rules
0060: 20 64 61 74 61 62 61 73 databas
0068: 65 3a 20 43 3a 5c 57 49 e: C:\WI
0070: 4e 4e 54 5c 49 6e 74 65 NNT\Inte
0078: 72 6e 65 74 20 4c 6f 67 rnet Log
0080: 73 5c 42 41 43 4b 55 50 s\BACKUP
0088: 2e 52 44 42 00 .RDB.


BB

 

I finally found the problem. The Logitech, Itouch software is buggy.

I started in safe mode, checked what was running. Then used enditall to work on the list, might know Itouch was next to last thing I tried.
Thanks for all the help all. BB
The service control error is still in event viewer.

 

I found this about Logitech tonight, but can't find in the Reg. Anyone help?

"When I did stumble upon the shutdown refusal, I removed NewsGator and OneNote, seeing no improvement. Those were easy enough to wax, without having to mess with drivers. With those checked off, on to the keyboard software. Within the startup portions of the registry, Logitech buries two items named iTouch.exe and zBrowser.exe. The iTouch.exe file is the main keyboard driver, while the zBrowser seems to have more to do with the system tray icon operation, though I can't confirm it's entire scope. I decided to kill zBrowser since it didn't seem much like a driver type of thing, but I left iTouch.exe alone for the time being. After the next reboot, things were back to normal. Best of all, the iTouch.exe portion still loads normally, and all keyboard functions appear to be unaffected in any way, including the on-screen feedback as buttons with assigned functions are pressed. Logitech weighs in with very little detail, simply stating that the iTouch software fails to unload during system shutdown. Duh.

Further, support document #6801, published 4/3/2003 states: This issue has been addressed in the next release of software, which is expected to be available shortly. Now, I don't know about you, but this is a show-stopper sort of bug, and the term "shortly" obviously varies depending on which side of the keyboard you happen to find yourself. Nearly two full months and nothing to show for it. In fact, the latest version of the iTouch software available was published 11/27/2002, so this has been a 6 month issue with a promise that it will be fixed "shortly ". Such usable hardware and such horrible developers. It only took 3+ years to finally address the scrolling issues in their mouseware package, so I'm beginning to wonder if another 2 1/2 years will result in the repaired driver. No worries, though... just wax that zBrowser thing and I'm guessing you'll be rid of the shutdown hassles ".