Support Forum

Registration is not required to ask a question. If you're a Pro Club member, please use our Priority Support page for a faster response.

Junk Cleaner +Windows10

Home Forums Product Support Junk Cleaner +Windows10

Viewing 10 posts - 1 through 10 (of 21 total)
  • Author
    Posts
  • #14065
    Phobos
    Moderator

    Run the program as an administrator. Activate the debug mode in the settings. Reproduce the problem. Download here “debug-errors-***.log” from the program folder.

    #14098
    Poppa Mintin
    Participant

    Exception encountered in module [System Ninja]
    Message: Object reference not set to an instance of an object.
    at System_Ninja.routine_startup_data.read_x64_registry_startups()

    Exception encountered in module [System Ninja]
    Message: Object reference not set to an instance of an object.
    at System_Ninja.routine_startup_data.read_x64_registry_startups()

    #14103
    Shane Gowland
    Keymaster

    [quote quote=14098]Exception encountered in module [System Ninja]
    Message: Object reference not set to an instance of an object.
    at System_Ninja.routine_startup_data.read_x64_registry_startups()

    Exception encountered in module [System Ninja]
    Message: Object reference not set to an instance of an object.
    at System_Ninja.routine_startup_data.read_x64_registry_startups()[/quote]

    These don’t cause any issues. They’re leftovers from when Windows first implemented the Wow6432Node redirects.

    #14106
    Poppa Mintin
    Participant

    OK…

    So, I uninstalled System Ninja, then using RegEdit, I removed all references to System Ninja from the registry.

    Then re-booted the laptop, re-installed from “ninja-setup-3.2.5.exe” running as administrator.

    Than ran System Ninja, ‘ as administrator’, went to the ‘Options’ tab and selected ‘Debug Mode’, and tried using ‘Junk Remover’, the problem is still just the same.

    I opened the System Ninja folder but this time ‘ debug-errors-***.log’ is absent.

     

    #14107
    Poppa Mintin
    Participant

    I find that there is a ‘Dump’ file in ‘AppData\Local\CrashDumps’.

    herewith in case it helps.

     

     

     

     

    #14108
    Poppa Mintin
    Participant

    Ah…  too big, zipped is smaller.

    Try again.

     

     

    #14112
    Poppa Mintin
    Participant

    Still trying to find an answer to my problem.

    Usually when I start Junk Scanner, I’m offered a choice of which drives to scan, and usually I choose just C:\ and click Scan, today out of curiosity I chose D:\ and clicked Scan…  Junk Scanner worked correctly, finding and deleting over a gigabyte of junk !

    Then I tried scanning C:\again and the application failed in the usual way.  I tried de-selecting all but ‘Temporary’ files and tried again, and sadly the application failed again.  I then tried de-selecting just ‘Temporary’ files, and again the application failed.

    Logically there must be something somewhere ‘Protecting’ the C:\drive…  I’m not keen on the idea of closing my AV program to test that, and anyway, why would that protect the C:\ drive but not the D:\ ?

     

     

    #14113
    Shane Gowland
    Keymaster

    C:\ is typically the system drive and would be protected more than others.

    What A/V are you using? We can spin up a VM and test whether there’s a conflict happening.

    #14114
    Phobos
    Moderator

    I think we need to look into Windows journal through the event viewer.

    #14115
    Poppa Mintin
    Participant

    OK,   I ran Junk Scanner, then looked up the log, I think this is what you’re asking for: –

     

    Log Name: Application
    Source: Application Error
    Date: 24/02/19 16:17:32
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: MSI
    Description:
    Faulting application name: System Ninja.exe, version: 3.2.5.0, time stamp: 0x5c4840c6
    Faulting module name: clr.dll, version: 4.7.3324.0, time stamp: 0x5c09b330
    Exception code: 0xc00000fd
    Fault offset: 0x00000000000bda54
    Faulting process id: 0x2554
    Faulting application start time: 0x01d4cc5c63fd5cb2
    Faulting application path: C:\Program Files (x86)\System Ninja\System Ninja.exe
    Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
    Report Id: ba52988d-e32b-4a5a-b5b6-bbfa0c489ce4
    Faulting package full name:
    Faulting package-relative application ID:
    Event Xml:
    <Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”&gt;
    <System>
    <Provider Name=”Application Error” />
    <EventID Qualifiers=”0″>1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=”2019-02-24T16:17:32.857389400Z” />
    <EventRecordID>7630</EventRecordID>
    <Channel>Application</Channel>
    <Computer>MSI</Computer>
    <Security />
    </System>
    <EventData>
    <Data>System Ninja.exe</Data>
    <Data>3.2.5.0</Data>
    <Data>5c4840c6</Data>
    <Data>clr.dll</Data>
    <Data>4.7.3324.0</Data>
    <Data>5c09b330</Data>
    <Data>c00000fd</Data>
    <Data>00000000000bda54</Data>
    <Data>2554</Data>
    <Data>01d4cc5c63fd5cb2</Data>
    <Data>C:\Program Files (x86)\System Ninja\System Ninja.exe</Data>
    <Data>C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll</Data>
    <Data>ba52988d-e32b-4a5a-b5b6-bbfa0c489ce4</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    </EventData>
    </Event>

     

Viewing 10 posts - 1 through 10 (of 21 total)
  • You must be logged in to reply to this topic.