Getting "Faulting application"s - why?

Norton Security | Norton Internet Security
1

I just bought a new Win7/64 and when I look at the event viewer, I am seeing these two entries occur over and over again.

 

Why?

 

1) Faulting application name: WSCStub.exe, version: 21.2.0.38, time stamp: 0x531faac9

Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2be1e

Exception code: 0xc0000005

Fault offset: 0x0001025b

Faulting process id: 0x4ec

Faulting application start time: 0x01cf63a351cddbdf

Faulting application path: C:\Program Files (x86)\Norton AntiVirus\Engine\21.2.0.38\WSCStub.exe

Faulting module path: C:\Program Files (x86)\Norton AntiVirus\Engine\21.2.0.38\MSVCR100.dll

Report Id: 92a0bcea-cf96-11e3-80cb-3c77e6804a22

 

2) Faulting application name: WSCStub.exe, version: 21.2.0.38, time stamp: 0x531faac9

Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521ea8e7

Exception code: 0xc0000005

Fault offset: 0x0002e04e

Faulting process id: 0xea0

Faulting application start time: 0x01cf63ae9311201b

Faulting application path: C:\Program Files (x86)\Norton AntiVirus\Engine\21.2.0.38\WSCStub.exe

Faulting module path: C:\Windows\SysWOW64\ntdll.dll

Report Id: d417e26a-cfa1-11e3-80cb-3c77e6804a22

2

I just bought a new Win7/64 and when I look at the event viewer, I am seeing these two entries occur over and over again.

 

Why?

 

1) Faulting application name: WSCStub.exe, version: 21.2.0.38, time stamp: 0x531faac9

Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2be1e

Exception code: 0xc0000005

Fault offset: 0x0001025b

Faulting process id: 0x4ec

Faulting application start time: 0x01cf63a351cddbdf

Faulting application path: C:\Program Files (x86)\Norton AntiVirus\Engine\21.2.0.38\WSCStub.exe

Faulting module path: C:\Program Files (x86)\Norton AntiVirus\Engine\21.2.0.38\MSVCR100.dll

Report Id: 92a0bcea-cf96-11e3-80cb-3c77e6804a22

 

2) Faulting application name: WSCStub.exe, version: 21.2.0.38, time stamp: 0x531faac9

Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521ea8e7

Exception code: 0xc0000005

Fault offset: 0x0002e04e

Faulting process id: 0xea0

Faulting application start time: 0x01cf63ae9311201b

Faulting application path: C:\Program Files (x86)\Norton AntiVirus\Engine\21.2.0.38\WSCStub.exe

Faulting module path: C:\Windows\SysWOW64\ntdll.dll

Report Id: d417e26a-cfa1-11e3-80cb-3c77e6804a22

3

It was a clean install from a ISO directly from Microsoft, so no bloatware at all.

 

Besides, all the files mentioned in the error log belong to NAV, so what made you think it might be an external app causing this?

4

Hello

 

I Googled one of the .dll files mentioned.

 

What is ntdll.dll?

The ntdll.dll file is a file created by Microsoft that has a description of "NT Layer DLL" and is the file that contains NT kernel functions.

This file is located in the c:\windows\system32 or c:\winnt\system32 directory and can also be found in the c:\i386 directory.

taken from

 

http://www.computerhope.com/issues/ch000960.htm

 

I'm another User like you are, so I am just trying to be a help.

5

ntdll.dll along with ntoskrnl.exe is Windows.  Basically it's the windows operating system kernel.

 

msvcr100.dll is a Microsoft Visual C++ runtime file.

 

But thats not saying anything is wrong with the Norton file, the windows kernal or visual C++, something else is causing the problem because for the most part Norton and Windows work fine.

 

I this is a fresh install of Windows, it has to be a driver problem.

My crystal ball says video driver.

 

Flo's original question was because the most common reason for problems we see here is conflicts between Norton and other products.  It's also follows the same reasons I'm trying to get at above.  Files don't crash on there own, it's almost always a conflict between more than one file and the real culprit may or not be listed in the event console or crash log.

 

Best of luck,

Dave

 

6

But the file that is mentioned 3 out of the 4 files is the "WSCStub.exe" and this appears to be from Symantec.

 

I am a programmer, so it would help me to understand exactly (detailed) what the WSCStub.exe file does?

7

Hi,

 

Try this:

 

Click the Start button, and then click All Programs > Accessories > Run.

2. In the Run dialog box, type the following text:

regsvr32 /u WMIUTILS.DLL

3. Click OK.

4. Restart the computer.

5. Click the Start button, and then click All Programs > Accessories > Run.

6. In the Run dialog box, type the following text:

regsvr32 WMIUTILS.DLL

7. Click OK.

8. Restart the computer.

 

Post back if the issue is gone.

 

Regards,

8

Hi, John. This is information on what WSCtub.exe does.

 

It runs as a scheduled task under the Windows Task Scheduler, triggered to execute when the computer performs a specific event.

 

 I think that the WSC part is for Windows Security Center Connector or something like that...

This part of the product informs your Windows OS about the status of the Norton product (active and protecting you, or turned off, etc.).

9
Apostolos wrote:

Click the Start button, and then click All Programs > Accessories > Run.

2. In the Run dialog box, type the following text:

regsvr32 /u WMIUTILS.DLL

3. Click OK.

4. Restart the computer.

5. Click the Start button, and then click All Programs > Accessories > Run.

6. In the Run dialog box, type the following text:

regsvr32 WMIUTILS.DLL

7. Click OK.

8. Restart the computer.

I tried the above and still get the errors :(

10
F4E wrote:

Hi, John. This is information on what WSCtub.exe does.

 

It runs as a scheduled task under the Windows Task Scheduler, triggered to execute when the computer performs a specific event.

 

 I think that the WSC part is for Windows Security Center Connector or something like that...

This part of the product informs your Windows OS about the status of the Norton product (active and protecting you, or turned off, etc.).

I am now REAL interested in why this is happening. If this "scheduled" event is failing EVERY time it runs, then that concerns me that the task has NEVER run. Or has this task ran OK all-along, but just errors every once in a while.

 

I went into the task scheduler, and into the NAV section, but didn't see anything that directly launched WSCtub.exe so I dont know whats causing this app to run.

11

Hi,

 

I suggest that you remove/reinstall NAV.

See if the issue persists and then we could try extra things.

Maybe it's just a faulty installation of NAV, it happens.

Post back...

 

Regards,

12
JohnC123 wrote:

But the file that is mentioned 3 out of the 4 files is the "WSCStub.exe" and this appears to be from Symantec.

 

I am a programmer, so it would help me to understand exactly (detailed) what the WSCStub.exe file does?

From your logs, it is wscstub.exe as the faulting application, but it is Microsoft dlls that are the faulting module that is being called by wscstub.

 

Have you run a Windows system file check?  As in    sfc /scannow

 

1) Faulting application name: WSCStub.exe, version: 21.2.0.38, time stamp: 0x531faac9

Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2be1e

Exception code: 0xc0000005

Fault offset: 0x0001025b

Faulting process id: 0x4ec

Faulting application start time: 0x01cf63a351cddbdf

Faulting application path: C:\Program Files (x86)\Norton AntiVirus\Engine\21.2.0.38\WSCStub.exe

Faulting module path: C:\Program Files (x86)\Norton AntiVirus\Engine\21.2.0.38\MSVCR100.dll

Report Id: 92a0bcea-cf96-11e3-80cb-3c77e6804a22

 

2) Faulting application name: WSCStub.exe, version: 21.2.0.38, time stamp: 0x531faac9

Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521ea8e7

Exception code: 0xc0000005

Fault offset: 0x0002e04e

Faulting process id: 0xea0

Faulting application start time: 0x01cf63ae9311201b

Faulting application path: C:\Program Files (x86)\Norton AntiVirus\Engine\21.2.0.38\WSCStub.exe

Faulting module path: C:\Windows\SysWOW64\ntdll.dll

Report Id: d417e26a-cfa1-11e3-80cb-3c77e6804a22

 

 

 

13

I did the check as you suggested and it reportes no integrity violations.

 

Windows "system" files are pretty rock solid, so any crash related to them was probably caused by a bad paramiter passed to it by the parent application.

 

I wish I knew specifically what WSCtub.exe does so I know if it not running is a big concern or not.

14

Hi,

 

2 questions:

 

1. Did you try uninstall/reinstall of NAV??

2. Do you have MSE or any other AV installed on your system with a real-time component enabled??

 

Regards,

15

Where can I download this "Norton Remove" tool so I can once and for all say that "I uninstalled NAV, then double-uninstalled it (by using the tool), then installed it" ;) ?

16

Hi,

 

You did not reply to both my questions.

Also, you can download NRT here: https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us

 

Be sure to first uninstall NAV via Control panel, then after reboot use NRT and reboot again.

 

P.S. If you have other AV's running on your pc or you didn't uninstall them properly, I can tell you in advance that even the NRT solution will not work.

Post back.

 

Regards,

17

I originally had NIS 2013 installed, but decided to go with NAV. So I did do the Control panel uninstall of NIS, then installed NAV.

 

But I will do the CP uninstall nav, reboot, NRT, roobot, install NAV and see what happens.

18

Hi,

 

When you will reinstall NAV, please open Task Scheduler and check the status of Norton tasks, if they are all enabled and scheduled to run at specific intervals.

Also, for the Norton tasks already ran in TS, see if the message is "operation completed successfully".

 

Regards,

19

Hello John

 

For a description of what that file does, please see this site for information reasons only.

 

http://www.shouldiblockit.com/wscstub.exe-2244.aspx

 

 

 

20

Will the NRT also uninstall my PCanywhere app and it's setting?

 

I am looking in my current install of NAV and I into "settings....system tab" and I dont see anywhere where it says "operation completed successfully". Where specifically is this task log?