Page 2 of 2 First 12
  1. #21
    Sysnative Staff
    BSOD Kernel Dump Analyst
    Contributor

    Join Date
    May 2015
    Location
    The Netherlands
    Age
    21
    Posts
    467
    • specs System Specs
      • Manufacturer:
        Custom build
      • Motherboard:
        Gigabyte B150-HD3P-CF
      • CPU:
        Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
      • Memory:
        16GB DDR4 Crucial Ballistix Sport LT BLS8G4D240F
      • Graphics:
        Intel(R) HD Graphics 530
      • Sound Card:
        (1) Intel(R) Display Audio (2) Realtek HD Audio
      • Hard Drives:
        Crucial MX200 500GB & 2x Toshiba DT01ACA300
      • Power Supply:
        Corsair RM550x
      • Case:
        Fractal Design Define S
      • Cooling:
        Cooler Master TX3 i
      • Display:
        24" Liyama ProLite XB2483HSU-B2 & 24" Dell Ultrasharp U2414H
      • Operating System:
        Windows 10 Pro

    Re: Crash .net runtime

    Problem has been resolved
    Thanks a lot writhziden for taking a look at it
    Attached Thumbnails Attached Thumbnails Crash .net runtime-cdb25d1379-png  
    writhziden says thanks for this.


    • Ad Bot

      advertising
      Beep.

        
       

  2. #22
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    15,955
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    Re: Crash .net runtime

    Quote Originally Posted by writhziden View Post
    Empty .txt files are always 0 KB on my system.
    Same here.
    writhziden says thanks for this.

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015

  3. #23
    niemiro's Avatar
    Join Date
    Mar 2012
    Location
    District 12
    Posts
    7,837

    Re: Crash .net runtime

    Quote Originally Posted by writhziden View Post
    Quote Originally Posted by axe0 View Post
    That I have the Dutch language installed would be an odd cause, half of the crash dumps are from when I only had the english language installed.

    I have attached a new zip file from a user on EF where I experience this problem.
    Ah, it's not crashing due to the .dmps; it is crashing due to ProcessList.txt, a seemingly empty file that is mysteriously 1KB in size. If I open it in any text editor, the file is empty, so why is it taking up 1 KB?

    At any rate, I'll look into why the apps crash when opening that file. I will try to roll out an update in the next couple weeks. I am still in the process of getting the apps compatible with Windows 8.1 and Windows 10 for old driver list functionality on those OSes. That is quite an endeavor since that information is deeply embedded in so much of how the apps analyze .dmps
    That's because a text editor is inherently a text editor. They do not show every piece of data a file holds. You need to use a hex editor or raw read for that.

    Read up about Byte Order Marks (BOM): https://en.wikipedia.org/wiki/Byte_order_mark

    This file contains just two bytes 0xFF 0xFE. They signify that this is a UTF-16 LE file, and that text editors should read the rest of the file in this format (BOMs alleviate ambiguity between all of the various Unicodes).

    In essence this is a perfectly normal, perfectly healthy empty file. But it's UTF-16 LE rather than ASCII/"ANSI" encoded. It's a good idea to use some form of Unicode anyway though since they support lots of different character sets much better [Windows natively used UTF16-LE most of the time, although arguably UTF8 is a much better format, and is also what *nix systems tend to use].

    Overall though they're a bit of a pain to code with in C/C++ languages and I've run into every problem under the sun over the years with development versions of SFCFix & trying to make it support lots of languages. But it's worth it in the end :)
    writhziden and jcgriff2 say thanks for this.

  4. #24
    writhziden's Avatar
    Join Date
    May 2012
    Location
    Colorado
    Posts
    2,328
    • specs System Specs
      • Manufacturer:
        Sony
      • Model Number:
        VPCF232FX/B
      • Motherboard:
        Sony Corporation VAIO
      • CPU:
      • Memory:
        8.00 GB Crucial CT2KIT51264BF1339 DDR3 1333
      • Graphics:
      • Sound Card:
        Realtek High Definition Audio/nVidia High Definition Audio
      • Hard Drives:
        TOSHIBA MK5061GSY 500 GB (465 GB actual)
      • Case:
        Laptop black matte case with backlit keyboard
      • Cooling:
        Air cooling via fan and heat exchanger heatsink
      • Display:
        Laptop display
      • Operating System:
        Windows 7 Home Premium 64 Bit

    Re: Crash .net runtime

    Quote Originally Posted by niemiro View Post
    Read More:


    That's because a text editor is inherently a text editor. They do not show every piece of data a file holds. You need to use a hex editor or raw read for that.

    Read up about Byte Order Marks (BOM): https://en.wikipedia.org/wiki/Byte_order_mark

    This file contains just two bytes 0xFF 0xFE. They signify that this is a UTF-16 LE file, and that text editors should read the rest of the file in this format (BOMs alleviate ambiguity between all of the various Unicodes).

    In essence this is a perfectly normal, perfectly healthy empty file. But it's UTF-16 LE rather than ASCII/"ANSI" encoded. It's a good idea to use some form of Unicode anyway though since they support lots of different character sets much better [Windows natively used UTF16-LE most of the time, although arguably UTF8 is a much better format, and is also what *nix systems tend to use].

    Overall though they're a bit of a pain to code with in C/C++ languages and I've run into every problem under the sun over the years with development versions of SFCFix & trying to make it support lots of languages. But it's worth it in the end :)
    Yeah, I figured there might be some other language formatting in that file. A purely empty .txt file has always shown up at 0 KB on my systems. It makes sense that it would be Hex format, but I've never been very comfortable working in Hex and tend to avoid it. Maybe someday when I can find time, I will try to learn how it works.
    I am only a volunteer helping users on the forums. Please wait 72 hours before double posting or PMing for help. I appreciate your patience. :-}

Page 2 of 2 First 12

Similar Threads

  1. [SOLVED] Explorer.EXE runtime error/Issues with SFC
    By mbrenner in forum Windows Update
    Replies: 2
    Last Post: 06-04-2015, 02:04 PM
  2. Error runtime visual C++ libarry in windows 8
    By mks001 in forum Windows Update
    Replies: 0
    Last Post: 01-23-2014, 12:40 PM
  3. [SOLVED] atikmpag.sys crash
    By mnmsvista in forum BSOD, Crashes, Kernel Debugging
    Replies: 32
    Last Post: 09-18-2013, 12:31 PM
  4. SysnativeBSODApp.exe app crash
    By usasma in forum BSOD Processing Apps Download | Information | Discussions
    Replies: 18
    Last Post: 06-13-2013, 05:38 AM

Log in

Log in