Programs crashing on launch under one account only

D

doveman

Well-known member
Joined
Sep 22, 2012
Posts
58
I hope this is OK here as I'm not experiencing BSOD, just programs crashing on being launched. Please move it if there's a more appropriate section.

I have my Main account under which everything is working fine and I decided to set up a separate Gaming account that would auto-launch certain apps when logging in and not load some others that my Main account uses.

When using this Gaming account, I get multiple crashes when programs load (not just, or necessarily even, the ones that autolaunch at login). I'll just get "This program has stopped working" and then if I try it again or a bit later it loads OK.

The same programs work fine under the Main account so I can't make any sense of this whatsoever. Both accounts are Administrator. Here's some extracts from the Application log showing the crashes.

Code: 
Faulting application name: HWMonitor_x64.exe, version: 1.2.1.0, time stamp: 0x509b8388
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001b901c1
Faulting process id: 0x379c
Faulting application start time: 0x01cded409886f7c5
Faulting application path: E:\Portable Apps\HwMonitor\HWMonitor_x64.exe
Faulting module path: unknown
 Report Id: d656ab32-5933-11e2-9a8e-8c89a563ffda

Faulting application name: taskmgr.exe, version: 6.1.7601.17514, time stamp: 0x4ce79737
Faulting module name: USER32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c9f1
Exception code: 0xc0000409
Fault offset: 0x000000000008100b
Faulting process id: 0x1e50
Faulting application start time: 0x01cded4039300de5
Faulting application path: C:\Windows\system32\taskmgr.exe
Faulting module path: C:\Windows\system32\USER32.dll
 Report Id: 76e64582-5933-11e2-9a8e-8c89a563ffda

Faulting application name: mmc.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc808
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000041d
Fault offset: 0x00000000021001c1
Faulting process id: 0x2e80
Faulting application start time: 0x01cded403436a2b0
Faulting application path: C:\Windows\system32\mmc.exe
Faulting module path: unknown
 Report Id: 73c5e6fa-5933-11e2-9a8e-8c89a563ffda

Faulting application name: ActualMultipleMonitorsShellCenter64.exe, version: 5.0.2.0, time stamp: 0x50e508ee
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000034c01c1
Faulting process id: 0x1190
Faulting application start time: 0x01cded275cf9b190
Faulting application path: C:\Program Files (x86)\Actual Multiple Monitors\ActualMultipleMonitorsShellCenter64.exe
Faulting module path: unknown
 Report Id: 563199aa-5933-11e2-9a8e-8c89a563ffda

Faulting application name: calc.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc9d4
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000026801c1
Faulting process id: 0x1e4c
Faulting application start time: 0x01cded2c4c9b4929
Faulting application path: C:\Windows\system32\calc.exe
Faulting module path: unknown
Report Id: 8eae0d6f-591f-11e2-9a8e-8c89a563ffda
 
Hi -

Are either of the user accounts the Hidden Admin account?

To check - bring up CMD, run -
Code: 
whoami /user

What are the last digits of the SID?
Code: 
User Name      SID
============== ==============================================
pc1\USER1      S-1-5-21-1477948808-2898045070-2393627958-[COLOR=#ff0000]1001[/COLOR]

- 100x = user admin
- 500 = hidden admin

Task Manager, MS Management Console, calculator - all listed as crashing.

Also -
Code: 
[B]ActualMultipleMonitorsShellCenter64.exe[/B]
version: 5.0.2.0
[B]time stamp[/B]: [COLOR=#ff0000]0x50e508ee[/COLOR]
0x50e508ee = Thu Jan 3 04:28:30 2013

Others reporting problems - http://www.actualtools.com/forum/read.php?PAGEN_1=2&FID=10&TID=2459#nav_start

Also crashing from drive e:
Code: 
E:\Portable Apps\HwMonitor\HWMonitor_x64.exe

Does the other user account have those 2?

Regards. . .

jcgriff2
 
Hi

I need to login to the other account to check but the main one is 1007, so user admin.

Thanks for the link to the AMM forum, it seems that problem was a memory leak and appears (hopefully) to have been fixed by v5.02 which I'm running.

AMM does load at login for my working Main account and HwMonitor doesn't have any problems under that account either.

I'll post again once I've checked whether the other account is hidden admin or not.
 
The crashed included a few exception codes (most "unknown"); one in particular seen a few times -

0xc0000005 = memory access violation

Given only the one user account experiences it, it is likely a driver attempting to access memory it should not.

A memory leak could do it.

Regards. . .

jcgriff2
 
Hmm, interesting.

It would seem strange for AMM to cause these problems under one account but not the other but I'll try killing it under the troublesome account and see if that fixes it.
 
I do agree, but there may be something in one & not the other.

Could be perms, too. 0xc00000005 can also = "access denied". I've seen that scenario with 3rd party firewalls in crashes (not saying a firewall is the cause here).

Given the name of the app, are shells involved? They could be at fault here.

http://www.nirsoft.net/utils/shexview.html

http://www.nirsoft.net/utils/shell_menu_view.html



Also - have you tried to create another user account & transfer files over. Often works if user profile/ registry of the account is corrupted.

Can you test in safemode - see if it crashes there?

Regards. . .

jcgriff2
 
I've checked the other account's SID and that's 1009, so user admin as well.

I tried killing AMM but still had apps crashing after that (AMM was using very little memory just after logging in anyway).

As both accounts are in the Administrators groups, there shouldn't be any issue with one not having sufficient perms to access any required files.

I tried killing the firewall (Comodo) just in case some component of that was blocking something but still got crashes after.

I'm not using any shell replacement if that's what you were asking. I actually got a crash running shexview the first time and it does seem that programs/components that crash the first time work OK on subsequent attempts, although I can't say for sure. Certainly when trying to reproduce the crashing I find that running the same program that caused it a minute ago doesn't anymore and I have to try a different program, which generally succeeds in crashing.

I actually only just created this account the other day so it shouldn't be corrupted but it's possible of course. I'll try testing with another account and see if that has the same problem.

Here's some of the crashes/errors I've just had:

Code: 
Faulting application name: shmnview.exe, version: 1.2.0.0, time stamp: 0x4fef7db7Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001e601a0
Faulting process id: 0x141c
Faulting application start time: 0x01cdeeb53fcdc7f6
Faulting application path: C:\Users\Gaming\AppData\Local\Temp\Rar$EX00.467\shmnview.exe
Faulting module path: unknown
Report Id: 7d99f8e6-5aa8-11e2-8fe1-8c89a563ffda

Faulting application name: Defraggler64.exe, version: 2.9.0.391, time stamp: 0x4f0ef824
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000026b01a0
Faulting process id: 0xba0
Faulting application start time: 0x01cdeeb5076234b9
Faulting application path: C:\Program Files\Defraggler\Defraggler64.exe
Faulting module path: unknown
Report Id: 45c550ae-5aa8-11e2-8fe1-8c89a563ffda

Faulting application name: systempropertiesadvanced.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc9a0
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000021201c1
Faulting process id: 0x14c8
Faulting application start time: 0x01cdeeb4469633f9
Faulting application path: C:\Windows\system32\systempropertiesadvanced.exe
Faulting module path: unknown
Report Id: 87970f0d-5aa7-11e2-8fe1-8c89a563ffda

Faulting application name: FreeFileSync_x64.exe, version: 5.5.0.0, time stamp: 0x4ff0a7bc
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001f201a0
Faulting process id: 0xd70
Faulting application start time: 0x01cdeeb3ccde4758
Faulting application path: E:\Portable Apps\FreeFileSync\Bin\FreeFileSync_x64.exe
Faulting module path: unknown
Report Id: 0d6f20e8-5aa7-11e2-8fe1-8c89a563ffda

Windows cannot access the file  for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program IType.exe because of this error.


Program: IType.exe
File: 


The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
    - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
    - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.


Additional Data
Error value: 00000000
Disk type: 0

Faulting application name: itype.exe, version: 8.20.469.0, time stamp: 0x4e41c954
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17965, time stamp: 0x506dcae6
Exception code: 0xc0000096
Fault offset: 0x000000000000b7b6
Faulting process id: 0x18c4
Faulting application start time: 0x01cdeeb26c97f928
Faulting application path: C:\Program Files\Microsoft IntelliType Pro\itype.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: dead2b69-5aa5-11e2-8fe1-8c89a563ffda
 
I actually found there was another account already setup back when I installed Windows so I tested with that and had no problems.

I'll have to create another new account and test with that. If that has the problem, I guess it shows that something is happening when creating new accounts now that causes them to have this problem.
 
If the other 2 work and 1 does not, it's that account.

One crash had exception 0xc141 = invalid memory address

Most others - 0xc5 again.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top