Benzoate's Profile User Rating: -----

Reputation: 51 Whiz
Group:
Active Members
Active Posts:
229 (0.26 per day)
Joined:
29-February 12
Profile Views:
3,910
Last Active:
User is offline Jul 16 2014 07:23 PM
Currently:
Offline

Previous Fields

Country:
US
OS Preference:
Windows
Favorite Browser:
Chrome
Favorite Processor:
Intel
Favorite Gaming Platform:
XBox
Your Car:
Chevrolet
Dream Kudos:
0
Icon   Benzoate o.O

Posts I've Made

  1. In Topic: Saving Image Exits Browser Without Prompt

    Posted 30 Oct 2013

    I tried all the Windows repair tools then just decided to go ahead and do this thing I found on my computer called an Alien Respawn (I have an AlienWare m17x so it came pre-installed) which essentially completely re-installed Windows 7 but allowed me to keep any files I wanted. So it is all good now
  2. In Topic: Saving Image Exits Browser Without Prompt

    Posted 29 Oct 2013

    View Postmodi123_1, on 29 October 2013 - 02:14 PM, said:

    Start searching some of those errors out.. it looks like something got jacked up. It may be worth doing a 'repair' from your install media.



    I've looked around on the Microsoft site and haven't really found anything.. but I'm going to keep searching, and might contact tech support and see what they say. But in the mean time, how would I go about doing a 'repair' from the install media?
  3. In Topic: Saving Image Exits Browser Without Prompt

    Posted 29 Oct 2013

    Could this be the problem? I'm not really sure what it is..

    Faulting application name: MsiExec.exe, version: 5.0.7601.17514, time stamp: 0x4ce792c4
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x74e0e384
    Faulting process id: 0x17d0
    Faulting application start time: 0x01ced4a26a857d8b
    Faulting application path: C:\Windows\syswow64\MsiExec.exe
    Faulting module path: unknown
    Report Id: a8e95260-4095-11e3-b745-74de2b9a644d
    


    or maybe this?

    Faulting application name: DllHost.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc6b7
    Faulting module name: ieframe.dll, version: 9.0.8112.16514, time stamp: 0x523ec4a5
    Exception code: 0xc0000096
    Fault offset: 0x0017105a
    Faulting process id: 0x1460
    Faulting application start time: 0x01ced4a0587202b7
    Faulting application path: C:\Windows\SysWOW64\DllHost.exe
    Faulting module path: C:\Windows\SysWOW64\ieframe.dll
    Report Id: 964e291d-4093-11e3-b745-74de2b9a644d
    


    edit: I found an issues for COM surrogate and DistributedCOM. Not sure what either is but here it sounds like it could be it. Here is the event logs:

    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 COM Surrogate because of this error.
    
    Program: COM Surrogate
    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
    


    The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID 
    {C97FCC79-E628-407D-AE68-A06AD6D8B4D1}
     and APPID 
    {344ED43D-D086-4961-86A6-1106F4ACAD9B}
     to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
    
  4. In Topic: Saving Image Exits Browser Without Prompt

    Posted 28 Oct 2013

    complete the error checking.. still no dice.
  5. In Topic: Saving Image Exits Browser Without Prompt

    Posted 28 Oct 2013

    View Postmodi123_1, on 28 October 2013 - 02:13 PM, said:

    What's the event viewer saying?

    (start -> control panel -> admin tools -> event viewer)


    stuff about errors with a kernel-power error, ntfs, dhcp-client, application, msiInstaller, nginx, event log, service control manager, load perf, kernel-event, kernel-general, wmi, acpi, windows update.. all kinds of stuff.

    I have no idea what's going wrong. I haven't installed anything different with my core files and haven't played with any paths, plus I've constantly scanned for viruses...

    edit: I do remember accidently almost uninstalling something from windows, though I canceled it before it finished... maybe it is something to do with that? I think I had miss-clicked onto windows essentials or something like that. Should I try to do a system restore?

    edit 2: attempted a system restore and received an error stating "Windows has detected file system corruption on OS (C:). You must check the disk for errors before it can be restored."... Checking for errors now.

My Information

Member Title:
D.I.C Head
Age:
17 years old
Birthday:
November 20, 1996
Gender:
Interests:
food
programming
gaming
Full Name:
Nolan Canady
Years Programming:
2
Programming Languages:
Know Decently:
Java
HTML

Working on Learning:
Android
XML

Going to Learn:
C++
C#

Contact Information

E-mail:
Click here to e-mail me

Comments

Benzoate has no profile comments yet. Why not say hello?