SysnativeBSODApp.exe app crash

U

usasma

Retired Admin
Joined
Feb 20, 2012
Posts
2,126
From this topic: https://www.sysnative.com/forums/bs...opped-responding-has-recovered.html#post47524

App crashes when running the full memory dump that the OP uploaded
Worked around by generating a minidump in WinDbg - and it opens w/o problems
EDIT: now it crashes whenever I try to run a minidump. Still looks like the same errors in Event Viewer.

Repaired my .NET 4.5 installation and app still crashes

Event Viewer shows this error:
Log Name: Application
Source: .NET Runtime
Date: 5/30/2013 05:21:14
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Owner-PC
Description:
Application: _SysnativeBSODApps.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
Stack:
at System.Text.StringBuilder.ToString()
at System.IO.StreamReader.ReadToEnd()
at System.IO.File.InternalReadAllText(System.String, System.Text.Encoding, Boolean)
at System.IO.File.ReadAllText(System.String)
at <Module>.MyCheckDir.DmpCheck(MyCheckDir*, std.vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > >*, std.basic_string<char,std::char_traits<char>,std::allocator<char> >*)
at <Module>.InputData.getDmpsList(InputData*)
at <Module>.OutputDmps.getInputData(OutputDmps*)
at <Module>.OutputDmps.outputAnalysisFiles(OutputDmps*)
at <Module>.main(System.String[])

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-05-30T09:21:14.000000000Z" />
<EventRecordID>11419</EventRecordID>
<Channel>Application</Channel>
<Computer>Owner-PC</Computer>
<Security />
</System>
<EventData>
<Data>Application: _SysnativeBSODApps.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
Stack:
at System.Text.StringBuilder.ToString()
at System.IO.StreamReader.ReadToEnd()
at System.IO.File.InternalReadAllText(System.String, System.Text.Encoding, Boolean)
at System.IO.File.ReadAllText(System.String)
at <Module>.MyCheckDir.DmpCheck(MyCheckDir*, std.vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > >*, std.basic_string<char,std::char_traits<char>,std::allocator<char> >*)
at <Module>.InputData.getDmpsList(InputData*)
at <Module>.OutputDmps.getInputData(OutputDmps*)
at <Module>.OutputDmps.outputAnalysisFiles(OutputDmps*)
at <Module>.main(System.String[])
</Data>
</EventData>
</Event>
Click to expand...
Immediately followed by this error:
Log Name: Application
Source: Application Error
Date: 5/30/2013 05:21:14
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Owner-PC
Description:
Faulting application name: _SysnativeBSODApps.exe, version: 2.15.3.0, time stamp: 0x518723a0
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16451, time stamp: 0x50988950
Exception code: 0xe0434352
Fault offset: 0x00014b32
Faulting process id: 0x2aa8
Faulting application start time: 0x01ce5d17018f9bcc
Faulting application path: C:\Users\Owner\SysnativeBSODApps\_SysnativeBSODApps.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: 463bab64-c90a-11e2-beb8-485b3901d3fe
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="2013-05-30T09:21:14.000000000Z" />
<EventRecordID>11420</EventRecordID>
<Channel>Application</Channel>
<Computer>Owner-PC</Computer>
<Security />
</System>
<EventData>
<Data>_SysnativeBSODApps.exe</Data>
<Data>2.15.3.0</Data>
<Data>518723a0</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.2.9200.16451</Data>
<Data>50988950</Data>
<Data>e0434352</Data>
<Data>00014b32</Data>
<Data>2aa8</Data>
<Data>01ce5d17018f9bcc</Data>
<Data>C:\Users\Owner\SysnativeBSODApps\_SysnativeBSODApps.exe</Data>
<Data>C:\Windows\SYSTEM32\KERNELBASE.dll</Data>
<Data>463bab64-c90a-11e2-beb8-485b3901d3fe</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
Click to expand...
 
Last edited:
Re: SysnativeBSODApp.exe app crash w/Full memory dump

Mike -- I am experiencing this same issue too. It seems to crash when determining which files are dumps.

Stephen
 
I would greatly appreciate a folder of files (all files, not just .dmps) with which the problem occurs so I can test.

I am extremely sick at the moment with fever, cough, and severe soar throat, so it may be a while before I'm well enough to track down the bugs. I have to get the bugs out of my body first. ;-}
 
I'm using v6.2.9200.165384 of the debugger (Win8)
Anyone have a newer version? (kemical at Windows8Forums may have one - am waiting on a reply back from a PM)
 
Exception Info: System.OutOfMemoryException
Click to expand...

Too many running threads? If this has to do with the output otherwise, then perhaps you could fix the issue by writing things in buffered chunks to an output and then read it back in chunks when you need the data. Or you should dispose of some instantiated objects that you may not need at the time. :)
 
Last edited:
It was actually a result of reading full files into memory. Fine for most minidumps, but a full MEMORY.DMP is 500MB - 10GB, so the buffer exceeds what is allotted by the system. All I really need is the first line to determine whether it is a .DMP, .mdmp, .kdmp, .dmp, .hdmp, etc. so I just read the first line now.
 
writhziden said:
It was actually a result of reading full files into memory. Fine for most minidumps, but a full MEMORY.DMP is 500MB - 10GB, so the buffer exceeds what is allotted by the system.
Click to expand...

When I seen the StringBuilder in there I assumed as much, or you just had too many running threads and something else with strings set it off. If you needed the full dump then I would read this in chunks as mentioned.

All I really need is the first line to determine whether it is a .DMP, .mdmp, .kdmp, .dmp, .hdmp, etc. so I just read the first line now
Click to expand...

This is what I was doing too. :thumbsup2: It's either PAGE or PAGE64? If I can remember correctly? It's in my project, but from the large collection of test dumps you sent me this is the commonality I've found in the file header. Past that, I've also found a new way to test dump validity (which would be more reliable), but I haven't implemented it yet.
 
Another question, please.

The latest version doesn't delete the dump files from the directory that they're run out of (in my case I use the SysnativeBSODApps directory to run the dumps from). Previous versions did delete them. Is this by design now?
 
The latest version should still move the .dmps you analyze to the output directory, and the .dmps that are not analyzed should be moved to the %TEMP% directory under SysnativeBSODApps\%RandomNumber%\oldDmps. I'll double check functionality tomorrow morning, but everything was working correctly for me when I tested the other night.
 
You were correct. File handles were left open by the .dmp checking for some files. I believe I have now fixed it along with a couple other bugs.

Code: 
[B]2.15.6[/B]
[LIST=1]
[*][B][COLOR=RED]FIXED[/COLOR][/B] Out of Memory exception no longer occurs with large files.
[*][B][COLOR=RED]FIXED[/COLOR][/B] Problem with empty files causing a memory leak exception
[*][B][COLOR=RED]FIXED[/COLOR][/B] File handles being left open after scanning for dumps which sometimes led to files not being moved or deleted properly after processing
[/LIST]
 

Attachments

No problem. :-}

And yes, I'm feeling much better, thanks. I'll try to catch up on the other fixes and added functionality for the apps over the next few days.
 
Interesting "non-bug" on install.

As you may recall, I had problems with the install. I finally had to rename the SysnativeBSODApps directory in order to get the previous new versions to install correctly.
With this iteration (v2.15.6), I no longer have to do that! It installs over the old version and keeps my settings intact!

Also, the installer runs much faster now (for me).

Thanks Mike!

PS - renaming SysnativeBSODApps to xxxSysnativeBSODApps and then running installer results in a clean installation of the app with no settings transferred (and it didn't accept it when I tried to import my saved settings!).
 
Last edited:
During installation, the installer now only backs up and restores the settings saved in your SysnativeBSODApps folder. It will not back up other files in that folder (since this was causing slow installation on some people's systems due to using the SysnativeBSODApps directory for storage of downloaded files), so if you install to a new location, you will want to manually back up any files you need that are not related to the apps settings.

Directories included in backup are: backup, dmpOptions, download, driverStatistics, forumSettings, and parms.

usasma said:
and it didn't accept it when I tried to import my saved settings!.
Click to expand...

Not sure what this means. Is this a bug I need to look into, or can you open a .zdn file to load your settings on a fresh install of the apps?
 
Last edited:
Not sure what this means. Is this a bug I need to look into, or can you open a .zdn file to load your settings on a fresh install of the apps?
Click to expand...
I'm not sure either, but it was when I was messing around with the way that I install the app, so it's very likely that it's my fault (and it didn't occur in my successful installation). Please ignore it for now. I'll post back should it come up again.
 

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

Back
Top