GlassWire Computer Idle Monitor has stopped working v1.0.30b

MORBiD · November 25, 2014, 9:02pm

I am using GlassWire Version 1.0.30b.

Problem signature:
Problem Event Name: APPCRASH
Application Name: GWIdlMon.exe
Application Version: 1.0.19.699
Application Timestamp: 5459bb2d
Fault Module Name: MSVCR110.dll
Fault Module Version: 11.0.51106.1
Fault Module Timestamp: 5098858e
Exception Code: 40000015
Exception Offset: 000a327c
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 5cb4
Additional Information 2: 5cb42b1d79921a0194b53b6576253585
Additional Information 3: b611
Additional Information 4: b611839d07e715bbc87390cc2887fb5b

Read our privacy statement online:
htp://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I hope this helps with the development of GlassWire. I absolutley love the product and keep up the good work. Looking forward to the next GlassWire version release.
Thank you for your time and consideration,
MORBiD

Servo_GlassWire · November 26, 2014, 3:09am

Thanks! We’ll try to reproduce this problem and fix it ASAP.

MuLy · December 19, 2014, 12:06pm

I not sure of what i’m saying, but the time of the computer seems to be the problem.

I was 1 minutes away from the good time and the service didn’t stopped running, now i updated my time; the service work perfectly, it should be the reason why glasswire work fine a time, then the service cant run and after he run perfectly (The system should have updated his time)

well, that’s my opinion and it’s work fine for me

Servo_GlassWire · December 19, 2014, 12:48pm

What time was it? We received another report like this once but I can’t remember if we could reproduce the problem or not. What operating system?

MuLy · December 20, 2014, 11:23pm

the real time was 12h02 (on my time zone) on my pc if i remember well but the internet time was 12h03 or 04, before the update it didn’t work, after a time update of my pc by the server “time.a.nist.gov” everything work fine.

I’m on windows 7 pro 64 bits

phocks · April 23, 2015, 11:45pm

Yes, I am having this issue as well. I believe it is the same as here: forum.)glasswire. com/t/glasswire-computer-idle-monitor-eats-up-cpu/530

I am on a Surface Pro 3 i7 and every time I wake from sleep it seems like GlassWire Idle Monitor process spawns multiple times and then crashes using up a lot of CPU.

Faulting application name: GWIdlMon.exe, version: 1.0.19.699, time stamp: 0x5500634a
Faulting module name: MSVCR110.dll, version: 11.0.51106.1, time stamp: 0x5098858e
Exception code: 0xc0000409
Fault offset: 0x000a326c
Faulting process ID: 0xea8
Faulting application start time: 0x01d07e0975dd9957
Faulting application path: C:\Program Files (x86)\GlassWire\GWIdlMon.exe
Faulting module path: C:\Program Files (x86)\GlassWire\MSVCR110.dll
Report ID: b348ab10-ea11-11e4-8284-c0335e0dc702
Faulting package full name: 
Faulting package-relative application ID:

00Dubbo · June 4, 2015, 10:16am

Same issue as @phocks. I’m on the Surface Pro 3 i5 and when my computer wakes up it’s supper slow and occasionally unresponsive for a few minutes. When I have been able to get the the task manager there were 6 or 7 instances of GlassWire related apps running. I’m uninstalling again until fixed so please post up when a patch is applied. Thanks.

Servo_GlassWire · June 4, 2015, 12:03pm

We just released an update a few days ago. What was the last version you were using? Please try the update.

lowgman · December 12, 2015, 7:19pm

Hello.

Just wanted to note that I’m experiencing this issue with Glasswire 1.1.36b on a fully patched (as of 12/12/15) Windows 8.1 Pro install running in a Dell Latitude E7350. Same symptoms as described above, other than it appears to happen any time the computer sleeps, not associated with a specific time of day.

No idea if the Windows error report is useful?

Version=1
EventType=BEX
EventTime=130944210277678674
ReportType=2
Consent=1
ReportIdentifier=009ac0c0-a104-11e5-825f-c739aea238f8
IntegratorReportIdentifier=009ac0bf-a104-11e5-825f-c739aea238f8
WOW64=1
NsAppName=GWIdlMon.exe
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=GWIdlMon.exe
Sig[1].Name=Application Version
Sig[1].Value=1.1.36.0
Sig[2].Name=Application Timestamp
Sig[2].Value=565fd429
Sig[3].Name=Fault Module Name
Sig[3].Value=MSVCR120.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=12.0.21005.1
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=524f7ce6
Sig[6].Name=Exception Offset
Sig[6].Value=000a7666
Sig[7].Name=Exception Code
Sig[7].Value=c0000409
Sig[8].Name=Exception Data
Sig[8].Value=00000007
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a81
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a81048bf1356bd42eb05945d5b261a6
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=936b
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=936b809b454d6ce4d7cec558a54f7fba
UI[2]=C:\Program Files (x86)\GlassWire\GWIdlMon.exe
UI[3]=GlassWire Computer Idle Monitor has stopped working
UI[4]=Windows can check online for a solution to the problem the next time you go online.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\GlassWire\GWIdlMon.exe
LoadedModule[1]=C:\windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\windows\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\windows\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\windows\SYSTEM32\USER32.dll
LoadedModule[5]=C:\windows\SYSTEM32\ADVAPI32.dll
LoadedModule[6]=C:\Program Files (x86)\GlassWire\MSVCP120.dll
LoadedModule[7]=C:\windows\SYSTEM32\WS2_32.dll
LoadedModule[8]=C:\windows\SYSTEM32\WTSAPI32.dll
LoadedModule[9]=C:\Program Files (x86)\GlassWire\MSVCR120.dll
LoadedModule[10]=C:\windows\SYSTEM32\SHELL32.dll
LoadedModule[11]=C:\windows\SYSTEM32\MSWSOCK.dll
LoadedModule[12]=C:\windows\SYSTEM32\GDI32.dll
LoadedModule[13]=C:\windows\SYSTEM32\msvcrt.dll
LoadedModule[14]=C:\windows\SYSTEM32\sechost.dll
LoadedModule[15]=C:\windows\SYSTEM32\RPCRT4.dll
LoadedModule[16]=C:\windows\SYSTEM32\NSI.dll
LoadedModule[17]=C:\windows\SYSTEM32\combase.dll
LoadedModule[18]=C:\windows\SYSTEM32\SHLWAPI.dll
LoadedModule[19]=C:\windows\SYSTEM32\SspiCli.dll
LoadedModule[20]=C:\windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[21]=C:\windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[22]=C:\windows\system32\IMM32.DLL
LoadedModule[23]=C:\windows\SYSTEM32\MSCTF.dll
LoadedModule[24]=C:\windows\system32\uxtheme.dll
LoadedModule[25]=C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll
LoadedModule[26]=C:\windows\SYSTEM32\OLEAUT32.dll
LoadedModule[27]=C:\windows\system32\dwmapi.dll
LoadedModule[28]=C:\windows\SYSTEM32\WINSTA.dll
LoadedModule[29]=C:\windows\SYSTEM32\SHCORE.dll
LoadedModule[30]=C:\windows\SYSTEM32\profapi.dll
LoadedModule[31]=C:\windows\SYSTEM32\kernel.appcore.dll
LoadedModule[32]=C:\windows\SYSTEM32\CRYPTSP.dll
LoadedModule[33]=C:\windows\system32\rsaenh.dll
LoadedModule[34]=C:\windows\SYSTEM32\bcrypt.dll
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=GlassWire Computer Idle Monitor
AppPath=C:\Program Files (x86)\GlassWire\GWIdlMon.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=293879913041E85E47746938EBCB8AC3

If you need any additional information, please just let me know.
G

Ken_GlassWire · December 13, 2015, 7:40pm

Thanks for your report. We’ll try to reproduce this on our end so we can fix it.

Martijn_ · December 19, 2015, 1:01pm

Surface Pro 3 i5, machine is unresponsive and my windows event log is filled with these every time I wake it up from sleep or hibernate:

Faulting application name: GWIdlMon.exe, version: 1.1.36.0, time stamp: 0x565fd429
Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f7ce6
Exception code: 0xc0000409
Fault offset: 0x000a7666
Faulting process ID: 0x1500
Faulting application start time: 0x01d13a53930be113
Faulting application path: C:\Program Files (x86)\GlassWire\GWIdlMon.exe
Faulting module path: C:\Program Files (x86)\GlassWire\MSVCR120.dll
Report ID: 54e2d746-a64e-11e5-844b-6002923c32c9
Faulting package full name:
Faulting package-relative application ID:

Details:

System

Provider

[
Name]
Application
Error

EventID
1000

[
Qualifiers]
0

Level
2

Task
100

Keywords
0x80000000000000

TimeCreated

[
SystemTime]
2015-12-19T12:45:07.000000000Z

EventRecordID
56013

Channel
Application

Computer
Surface

Security

EventData

GWIdlMon.exe

1.1.36.0

565fd429

MSVCR120.dll

12.0.21005.1

524f7ce6

c0000409

000a7666

1500

01d13a53930be113

C:\Program Files
(x86)\GlassWire\GWIdlMon.exe

C:\Program Files
(x86)\GlassWire\MSVCR120.dll

54e2d746-a64e-11e5-844b-6002923c32c9

LorenAmelang · December 20, 2015, 4:32am

Have 1.1.32b. (Just noticed there is 1.1.36, but sounds like lowgman sees similar issues with that newer version.) Maybe my info will help find them.

I’m setting up a new Microsoft Surface Book i7 with the graphics chip and Win 10 (latest updates after November version update.)

I was digging for other errors, and noticed lots of these:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_GWIdlMon.exe_b1441b55cd359a8f5e796330eadd4fe0d2514bdb_da2d90e4_29948fdf\Report.wer

They seem to come in groups of three or four at a time, identical except for the internal timestamps. But occasionally there is a single one.

Interesting how many of the reports here are from Surface machines… Maybe other people ended up with GlassWire to help find and stop all the chatter Win 10 and Surface send home to Microsoft? The default would cost me $60 per month in data overage…

I dug into this error because when I woke the computer just now it acted very strangely, stopped in the middle of sliding the splash screen up to reveal the login, then slowly slid it back down. I had to slide it up manually again, and it still seemed sluggish. Earlier today I chose sleep. Apparently the system timed out of sleep to hibernation. Looks like when the power state changes while in “connected standby”, Windows discovers it step-by-step during wakeup.

The times below are the times on the GWI errors…

151219-18:07:
Pressed power button.
“The system is exiting connected standby Reason: Resume from Hibernate.”
“The system is entering connected standby Reason: Idle Timeout.”

There were lots of these… Not sure they are connected to GWI…
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
to the user DESKTOP-OMMHHCL\loren SID (S-1-5-21-2642381790-255542418-257213659-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.WindowsStore_2015.23.23.0_x64__8wekyb3d8bbwe SID (S-1-15-2-1609473798-1231923017-684268153-4268514328-882773646-2760585773-1760938157). This security permission can be modified using the Component Services administrative tool.

“The system is exiting connected standby Reason: Power Button.”

Previous instance:

"The system is entering connected standby Reason: Screen Off Request."
151218-11:40:
“The system is exiting connected standby Reason: Power Button.”

Previous instance:

“The system is entering connected standby Reason: Screen Off Request.”
“The system is exiting connected standby Reason: AC/DC Display Burst.”
"The system is entering connected standby Reason: AC/DC Display Burst."
151217-23:10:
“The system is exiting connected standby Reason: Power Button.”

Here’s a typical Report.wer:

Version=1
EventType=BEX
EventTime=130950508267539408
ReportType=2
Consent=1
UploadTime=130950508303876022
ReportIdentifier=5de4a153-a6be-11e5-9bd5-b4ae2bd1665f
IntegratorReportIdentifier=5de24955-0ffd-4491-95b8-2f874e6a44c8
WOW64=1
NsAppName=GWIdlMon.exe
Response.BucketId=b44f61a48f70b30559669d6e0ee53089
Response.BucketTable=5
Response.LegacyBucketId=116035246605
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=GWIdlMon.exe
Sig[1].Name=Application Version
Sig[1].Value=1.1.32.0
Sig[2].Name=Application Timestamp
Sig[2].Value=561d1614
Sig[3].Name=Fault Module Name
Sig[3].Value=MSVCR120.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=12.0.21005.1
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=524f7ce6
Sig[6].Name=Exception Offset
Sig[6].Value=000a7666
Sig[7].Name=Exception Code
Sig[7].Value=c0000409
Sig[8].Name=Exception Data
Sig[8].Value=00000007
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.10586.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a81
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a81048bf1356bd42eb05945d5b261a6
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=ebcf
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=ebcf362df25853e41210db68c52fab46
UI[2]=C:\Program Files (x86)\GlassWire\GWIdlMon.exe
UI[3]=GlassWire Computer Idle Monitor has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\GlassWire\GWIdlMon.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\SYSTEM32\USER32.dll
LoadedModule[5]=C:\WINDOWS\SYSTEM32\GDI32.dll
LoadedModule[6]=C:\WINDOWS\SYSTEM32\ADVAPI32.dll
LoadedModule[7]=C:\WINDOWS\SYSTEM32\msvcrt.dll
LoadedModule[8]=C:\WINDOWS\SYSTEM32\sechost.dll
LoadedModule[9]=C:\WINDOWS\SYSTEM32\RPCRT4.dll
LoadedModule[10]=C:\WINDOWS\SYSTEM32\SspiCli.dll
LoadedModule[11]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
LoadedModule[12]=C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll
LoadedModule[13]=C:\WINDOWS\SYSTEM32\WS2_32.dll
LoadedModule[14]=C:\WINDOWS\SYSTEM32\SHELL32.dll
LoadedModule[15]=C:\WINDOWS\SYSTEM32\cfgmgr32.dll
LoadedModule[16]=C:\WINDOWS\SYSTEM32\windows.storage.dll
LoadedModule[17]=C:\WINDOWS\SYSTEM32\combase.dll
LoadedModule[18]=C:\WINDOWS\SYSTEM32\shlwapi.dll
LoadedModule[19]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[20]=C:\WINDOWS\SYSTEM32\shcore.dll
LoadedModule[21]=C:\WINDOWS\SYSTEM32\powrprof.dll
LoadedModule[22]=C:\WINDOWS\SYSTEM32\profapi.dll
LoadedModule[23]=C:\Program Files (x86)\GlassWire\MSVCP120.dll
LoadedModule[24]=C:\WINDOWS\SYSTEM32\WTSAPI32.dll
LoadedModule[25]=C:\Program Files (x86)\GlassWire\MSVCR120.dll
LoadedModule[26]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll
LoadedModule[27]=C:\WINDOWS\SYSTEM32\IMM32.DLL
LoadedModule[28]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[29]=C:\WINDOWS\SYSTEM32\MSCTF.dll
LoadedModule[30]=C:\Program Files (x86)\Common Files\Microsoft Shared\Ink\tiptsf.dll
LoadedModule[31]=C:\WINDOWS\SYSTEM32\OLEAUT32.dll
LoadedModule[32]=C:\Program Files (x86)\MessagEase\MEOKHOOK.DLL
LoadedModule[33]=C:\WINDOWS\SYSTEM32\comdlg32.dll
LoadedModule[34]=C:\WINDOWS\SYSTEM32\FirewallAPI.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\NETAPI32.dll
LoadedModule[36]=C:\WINDOWS\SYSTEM32\ole32.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[38]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.10586.0_none_811bc0006c44242b\COMCTL32.dll
LoadedModule[39]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
LoadedModule[40]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[42]=C:\WINDOWS\SYSTEM32\DAVHLPR.DLL
LoadedModule[43]=C:\WINDOWS\SYSTEM32\fwbase.dll
LoadedModule[44]=C:\WINDOWS\system32\dwmapi.dll
LoadedModule[45]=C:\WINDOWS\SYSTEM32\WINSTA.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\NETUTILS.DLL
LoadedModule[47]=C:\WINDOWS\SYSTEM32\wkscli.dll
LoadedModule[48]=C:\WINDOWS\SYSTEM32\srvcli.dll
LoadedModule[49]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[50]=C:\WINDOWS\system32\rsaenh.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=GlassWire Computer Idle Monitor
AppPath=C:\Program Files (x86)\GlassWire\GWIdlMon.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=20DFF0540B62AAECD23503B91D1874DB

Ken_GlassWire · December 21, 2015, 2:10am

Thanks. We recently got a Surface so we can crack down on these problems.

LorenAmelang · December 22, 2015, 12:11am

Possibly another clue… I happened to have Win 10 Resource Monitor showing when I woke the Surface Book earlier today, and it was showing an entire screenfull of Terminated GWIdlMon.exe processes! By the time I realized they were disappearing and hit PrintScreen, only the top five were left. Seems odd to me - the live PID 9456 is still the one running hours later. Why would there be so many others during sleep?

Was going to post the screenshot so you could see the process list, but I’m not seeing a way to attach a picture… Oh - that little Upload icon…

LorenAmelang · December 22, 2015, 12:12am

And the normal state, later:

Ken_GlassWire · December 22, 2015, 1:42am

We were able to reproduce this also and we’re working on fixing it. Thanks for your report!

fred-firewall · February 7, 2016, 12:37pm

Same problem on a Surface Pro 3 i5 with latest Glasswire 1.1.41 beta.

Multiple Glasswire Computer Idle Monitor entries with crashes on all of them.
Windows error log created 15-20 entries. Surface is extremly slow and unresponsive. TaskManager takes about 5min to start. Thereafter shut down of the faulty GWIdlMon.exe (15-20 of them) is possible.

Glasswire still works after that, but the same happens again and again after waking up from sleep mode.

Ken_GlassWire · February 8, 2016, 1:06pm

Everyone who has this problem (besides Fred) please email our helpdesk and we’ll send you a test version. https://www.glasswire.com/contact/ I’ll message Fred directly here. Thanks!

fred-firewall · February 8, 2016, 8:02pm

Hi Ken,

thank you for the above mentioned download.
I installed it and the problem still exists. After waking up from sleep 30 crashed Glasswire Computer Idle Monitor warnings occurred.After closing this 30 windows everything worked fine until the next wake from sleep.
The only difference is the cpu utilization. The surface was still responsive and the cpu never went above 40%.

So the problem still isn`t solved…

Ken_GlassWire · February 8, 2016, 9:26pm

I’ll report your results to the dev team. Thanks for testing and hopefully we can figure this out soon.