Intel Directory on Start Up 1

[w7zr]

I have a box with an Intel 945PVS motherboard and configured for a RAID 1 system. Sometime recently I started getting an explorer window to the c:\program files\intel directory opening on boot. The only things in this directory are two sub directories:INFInst and Intel Matrix Manager. I have to manually close the window every time the system boots. It does however seem to be functioning normally in all other respects.

 

[bcastner]

You are right, and I thought we had re-enabled it.

I have to say I am completely stumped.

I will start looking for a solution on the net.

 

[bcastner]

A guess:

Change in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Symantec NetDriver Monitor
"C:\PROGRA~1\SYMNET~1\SNDMon.exe /Consumer"

-to-

Symantec NetDriver Monitor
"C:\PROGRA~1\SYMNET~1\SNDMon.exe" /Consumer

 

[w7zr]

That appeared to have done nothing. Here are excerpts from Event Viewer

SYSTEM

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1015
Date: 8/8/2006
Time: 12:13:37 PM
User: RICHARD1\User
Computer: RICHARD1
Description:
Failed to connect to server. Error: 0x800401F0

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

APPLICATION

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1015
Date: 8/8/2006
Time: 12:13:37 PM
User: RICHARD1\User
Computer: RICHARD1
Description:
Failed to connect to server. Error: 0x800401F0

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

 

[bcastner]

Then restore the entry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Symantec NetDriver Monitor
"C:\PROGRA~1\SYMNET~1\SNDMon.exe /Consumer"

 

[w7zr]

I have tried that entry i HKLM both ways and the problem has not been solved. Right now from Event Viewer I only get a caution in application:

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1015
Date: 8/8/2006
Time: 12:49:09 PM
User: RICHARD1\User
Computer: RICHARD1
Description:
Failed to connect to server. Error: 0x800401F0

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

 

[bcastner]

Copy/paste the below into a notepad session and save as netmon_fix.reg Then double click and merge the contents into the registry. Reboot and test:

------ begin copy/paste below this line
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"Symantec NetDriver Monitor"="C:\\PROGRA~1\\SYMNET~1\\SNDMon.exe /Consumer"

------- end copy/paste above this line

 

[w7zr]

No change

 

[bcastner]

Then if all is okay, use AutoRuns and disable the startup line for Symantec NetDriver Monitor. This is part of Live Update.

What bothers me is that this entry is not appearing in your process list, only SNDSrvc.exe appears and that is an unrelated service that deals with malware.

 

[w7zr]

No go. Same.

 

[linney]

If you change the name of the opening folder to something else (just a temporary setting for a reboot and check), it may cause some error to occur that you can trace back from?

 

[bcastner]

There are at least three pieces of software at startup being taken from that folder, so there should be some errors if you rename it!

What makes it hard is that it is unlikely any command line or registry entry dealing with the Intel folder that is at fault; the error is likely for some other unrelated command string that fails, leaving the OS to fault to its last used directory.

If you Google, both Web and Groups, on "xp folder opens at startup" you will see what I mean. The malfunctioning entry usually has nothing to do with the folder that opens at startup.

 

[linney]

There are at least three pieces of software at startup being taken from that folder, so there should be some errors if you rename it!"

At least it might stop the damn folder from opening (lol).

Software might be able to be suspended from running via MsConfig. Maybe that might be worth a check anyway?

310353 - How to Perform a Clean Boot in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;310353&FR=1&PA=1&SD=HSCH

316434 - HOW TO: Perform Advanced Clean-Boot Troubleshooting in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;316434&FR=1&PA=1&SD=HSCH

310560 - How to Troubleshoot By Using the Msconfig Utility in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;310560&FR=1&PA=1&SD=HSCH

 

[w7zr]

Results of running various start ups from MSCONFIG General Tab

Diagnostic Startup- Did not get the window
System.INI- Did not get the window
Win.ini- Did not get the window
System Services- Did not get the window
Startup Items- Got the Intel Window

Conclusion: Got to be something in the startup items

 

[bcastner]

Lets divide and conquer. You can use either AutoRuns or MSConfigur for this.

Start with the 15 entries in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Disable the first 8. Reboot. Does the Intel folder appear?
If it does, re-enable the first 8 and disable the last 7 entries. Reboot. Does the Intel folder appear? If it does, re-enable the last 7 entries and now head to the 8 entries in
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

Again, split the entries in half. When the Intel folder stops showing up after a reboot, you know you have the subset containing the problematic entry. Try disabling them by halves further, or one-by-one to find the bad entry.

 

[w7zr]

The culprit has been found. The Boolean approach was a good one. The guilty entry was:
Sigmatel Sys Tray App
HKLM Microsoft\windows\current version\run
c:\program files\intel desktop board\disk 1\stacgui\sstray.exe

Now----what's wrong with that? I can execute the program manually from the directory. I probably do not need the program to be running.

 

[bcastner]

You probably do not need the program.

Disable it using AutoRuns.

You could try an update to the Sigmatel drivers used by Intel for your motherboard. A new driver set was released by Intel in June, 2006.

Note too the BIOS for that system was upgraded last week.

Expand the section on the left "Desktop Boards":

http://downloadfinder.intel.com/scripts-df-external/Support_Intel.aspx

And good job on the divide and conquer method of finding the bum driver.

Best wishes,
Bill Castner

 

[w7zr]

Bill, Thanks for all of your help and support. You certainly went way beyond to help.

Dick

 

[bcastner]

You are very welcome.

Best wishes,
Bill Castner

 

[dac72]

Hey guys just wanted to let you know I had the very same problem. However due to your excellent work, I was quickly able to troubleshoot and fix it. Thanks very much!!

David

 

[bcastner]

You are very welcome.

Best,
Bill Castner