BSOD App 2.2.9.3 Unhandled Exception

Shintaro

Shintaro

Well-known member
Joined
Jun 12, 2012
Posts
206
Location
Brisbane, Australia
Mate,

I'm getting an unhandled exception (See below) after the "Update Available" form. Which is a bit strange in its self as I am using 2.2.9.3.

Code: 
See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
   at _CxxThrowException(Void* , _s__ThrowInfo* )
   at std._Xout_of_range(SByte* _Message)
   at std.basic_string<char,std::char_traits<char>,std::allocator<char> >.assign(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* , basic_string<char\,std::char_traits<char>\,std::allocator<char> >* _Right, UInt32 _Roff, UInt32 _Count)
   at std.basic_string<char,std::char_traits<char>,std::allocator<char> >.{ctor}(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* , basic_string<char\,std::char_traits<char>\,std::allocator<char> >* _Right, UInt32 _Roff, UInt32 _Count, allocator<char>* _Al)
   at std.basic_string<char,std::char_traits<char>,std::allocator<char> >.substr(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* , basic_string<char\,std::char_traits<char>\,std::allocator<char> >* , UInt32 _Off, UInt32 _Count)
   at SysnativeBSODApps.Form1.loadForm1(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.269 (RTMGDR.030319-2600)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
SysnativeBSODApps
    Assembly Version: 1.0.4698.16813
    Win32 Version: 2,2,9,3
    CodeBase: file:///C:/Documents%20and%20Settings/Andrew/_jcgriff2_/dbug/__Kernel__/SysnativeBSODApps.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.278 built by: RTMGDR
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.282 built by: RTMGDR
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.269 built by: RTMGDR
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.



  • I then click continue, "Driver Reference Table Update Info" form is shown.
  • Add my user name and Originating Post.
  • Unhandled Exception.


Code: 
See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
   at _CxxThrowException(Void* , _s__ThrowInfo* )
   at std._Xout_of_range(SByte* _Message)
   at std.basic_string<char,std::char_traits<char>,std::allocator<char> >.assign(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* , basic_string<char\,std::char_traits<char>\,std::allocator<char> >* _Right, UInt32 _Roff, UInt32 _Count)
   at std.basic_string<char,std::char_traits<char>,std::allocator<char> >.{ctor}(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* , basic_string<char\,std::char_traits<char>\,std::allocator<char> >* _Right, UInt32 _Roff, UInt32 _Count, allocator<char>* _Al)
   at std.basic_string<char,std::char_traits<char>,std::allocator<char> >.substr(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* , basic_string<char\,std::char_traits<char>\,std::allocator<char> >* , UInt32 _Off, UInt32 _Count)
   at SysnativeBSODApps.Form1.button2_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.269 (RTMGDR.030319-2600)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
SysnativeBSODApps
    Assembly Version: 1.0.4698.16813
    Win32 Version: 2,2,9,3
    CodeBase: file:///C:/Documents%20and%20Settings/Andrew/_jcgriff2_/dbug/__Kernel__/SysnativeBSODApps.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.278 built by: RTMGDR
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.282 built by: RTMGDR
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.269 built by: RTMGDR
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.233 built by: RTMGDR
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


  1. If I check the box "Full GUI Version, then click Process BSOD's.
  2. Unhandled Exception.
  3. Click Continue
  4. Back to "Driver Reference Table update Info".
  5. Button "Process BSODs" always leads to Unhandled Exception and "Continue" back to the "Driver Reference..." form.



  1. Click "Change Settings" also shows the Unhandled Exception.
  2. Click Continue
  3. Everything is Greyed out (Disabled), Tabs do not respond.
  4. Try "Save and Run"
  5. App closes

My old Laptop:
Dell 505
2Gb RAM
5Gb Free space
Win XP SP3 (All MS patches applied.)

I hope that my explanation is ok.


The only version that works is 2.2.5.0

Cheers
Andrew
 
Do you have the Windows Server 2003 Resource Kit Tools installed? It sounds like linkd is not working right on your system.

Run the following command in a command prompt:

Code: 
linkd tmp %temp%\\SysnativeBSODApps


Let me know what the output is.


EDIT:

I just removed the resource kit tools on my own XP system and was able to reproduce the problems you are having. I am fairly sure now that is the problem. Let me know if you face the problem with the Windows Server 2003 Resource Kit Tools installed.​
 
Last edited:
Mate,

Thanks, that fixed the problem.

Did you publish a per-requisite / requirements list?
I'm going to upgrade my main machine to Win 8 next week, so I might as well try to get all the required software now.

Also, due to lack of caffeine this morning, I clicked on "Process BSODs", but forgot to add dump files to the directory first. It complained, "There are currently no .dmps to analyze.......".
I clicked on the "OK" button.
It then went ahead and created empty files.

May I be so bold and make some suggestions.
- Move the check of .dmp files to the first thing that is checked, rather than "Getting Driver Reference Table", because there is no point doing anything unless there are .dmp files there to analyze.
- If there are no .dmp files the program loops back to the first form "Sysnative BSOD Apps 2.2.9.6"

I hope that I am not sounding rude or anything. I greatly appreciate the massive amount of work that you have put in to this app.

Kind regards,
Andrew.
 
I will look into implementing your suggestions tonight.

All info about the apps and installation can be found here: OFFICIAL UPDATE: Sysnative BSOD Apps 2.2.5.0

The required programs to allow the apps to work smoothly are at the bottom of that first post. I have quoted the requirements below for convenience.

writhziden said:
You will need:
  1. Microsoft .NET Framework 4 (Web Installer)
  2. Visual C++ 2010 Redistributable (x86)

If you are running XP, you will also need:
  1. Windows Server 2003 Resource Kit Tools

    Info

    If you are running the apps in Windows XP and need the apps to find the kd.exe path for you, you will have to run the apps as an administrator either by logging in with an administrator account or by using the run as option



While you are at it, you may also want to install:
  1. Visual C++ 2005 Redistributable (x86)
    Visual C++ 2005 Redistributable (x64)
  2. Visual C++ 2008 Redistributable (x86)
    Visual C++ 2008 Redistributable (x64)
  3. Visual C++ 2010 Redistributable (x64)
to help with compatibility for programs, games, and other apps on your system. Make sure to install both the x86 and x64 versions for 64-bit Windows. Then install their updates through Windows Update.
Click to expand...
 
BETA: Sysnative BSOD Apps 2.3.0.1 <--- Link to latest update.

  1. FIXED .dmps now checked for prior to downloading any DRT info to save time downloading DRT info if .dmps are not present
  2. FIXED Missing .dmps message now reverts back to the first screen of the apps
  3. CHANGED Missing .dmps message now only has an OK option to revert back to the first screen and let the user add .dmps to the directory
  4. CHANGED Missing .dmps message to reflect the changes to the apps behavior when .dmps are not found
  5. ADDED More status updates for setting up the directory structure, getting user options, determining whether .dmps reside in the directory with the apps, and getting Driver Reference Table info
 

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

Back
Top