Home › Forums › Product Support › Junk Cleaner +Windows10
- This topic has 21 replies, 3 voices, and was last updated 6 years, 1 month ago by
Poppa Mintin.
-
AuthorPosts
-
February 3, 2019 at 1:49 am #14065
Phobos
ModeratorRun the program as an administrator. Activate the debug mode in the settings. Reproduce the problem. Download here “debug-errors-***.log” from the program folder.
February 22, 2019 at 9:47 am #14098Poppa Mintin
ParticipantException 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()February 22, 2019 at 12:07 pm #14103Shane 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.
February 23, 2019 at 3:34 am #14106Poppa Mintin
ParticipantOK…
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.
February 23, 2019 at 3:53 am #14107Poppa Mintin
ParticipantI find that there is a ‘Dump’ file in ‘AppData\Local\CrashDumps’.
herewith in case it helps.
February 23, 2019 at 4:05 am #14108Poppa Mintin
ParticipantFebruary 24, 2019 at 11:03 pm #14112Poppa Mintin
ParticipantStill 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:\ ?
February 24, 2019 at 11:05 pm #14113Shane Gowland
KeymasterC:\ 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.
February 25, 2019 at 1:17 am #14114Phobos
ModeratorI think we need to look into Windows journal through the event viewer.
February 25, 2019 at 2:51 am #14115Poppa Mintin
ParticipantOK, 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”>
<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> -
AuthorPosts
- You must be logged in to reply to this topic.