UVK forums

It does that for custom build computers. If that is the case, then it is normal.

So that's normal

virtualnetwork, reggaemanu

If you guys still have those machines in your possession and don't mind to try out the new beta release I just uploaded in there, it's appreciated.

http://www.carifred.com/uvk/beta/

Thanks

I'll try it tomorrow (if he don't come at the store opening) I still have the machine.

I don't know if it's the issue or not but I have seen this with 9.6.0 and 9.6.1. As you can see in the images it's an HP.

Fred wrote:The problem with these machines, and I'm starting to believe they are all HP, is that they have no BaseBoard with 0Ah at offset 13, so Motherborad info is retrieved through WMI. I would surely like to know how many baseboard tables they have, and what is the value of the BYTE at offset 13.

This is all the baseboard information I could get using dmidecode:
I'll try to get more information from a firmware memory dump, though it would help to know which memory locations or strings to look for.


The new beta, v.9.6.1.0, seems to be working well. Thank you. I will let you know if I find any bugs.

Thanks, guys. I'm really proud of having such helpful members in this forum. But I still feel I'm taking too much of your time, so I decided to take a new approach to these issues.

virtualnetwork, reggaemanu, Charger440, please download this file: http://www.carifred.com/system_files/SMBIOS_dump.exe

It is a small program I created that dumps the SMBIOS data to a binary file in your desktop folder named SMBIOS_dump.

Once the file is created, please send it to me via private message (it may contain serial numbers you don't want in the public domain). You can see the contents of the file with a hex editor such as HXD or a special text editor such as Notepad2.

This way I can load the SMBIOS data from the file, and won't need to bother you guys again.

Thanks again.

I am experiencing this issue.
Click on system info it starts doing its thing, then it errors out.
thanks for any help you can give.
I hope the system info below helps.
antivirus and and malwarebytes are all turned off.
---------------
[ Basic System Info ]

Application version: Ultra Virus Killer 10.2.3.0
Operating system: Microsoft Windows 10 Pro 64-bit Build 14393
OS install date: 2016/08/08 17:36:51
I.E. version: 0.0.0.0
Time & date: 2017/01/05 20:24:20:091
System drive: C: 1.10 TB free of 1.81 TB
__________
here is some info from siw
Bios - Intel Corp
Firmware Version [unknown]
BIOS Date 10/28/2009
BIOS Size 2048 KB
BIOS Starting Segment F000h
BIOS Release Version [unknown]
DMI Version 2.5
--------------
mother board
Manufacturer Intel Corporation
Model DP55WG
Version AAE57269-405
Name Intel(R) Core(TM) i5 CPU 661 @ 3.33GHz
CPU Socket Socket 1156 LGA
Max CPU Speed 4000 MHz
Memory Summary Reported by BIOS
Memory Type DDR3
Installed Memory 16.0 GB
---------------
I am going to go see if there is a new bios firmware out there and update to see if it helps any.
I want to buy your software but I need the system info to work.
I plan to use it with pcrt.

thanks
Robert

I updated the bios, it did not help.
thanks
Robert

Hi Robert.

Please download our smbios dump utility ant launch it. It will create a file named SMBIOS_dump in your desktop folder. Please compress that file into a ZIP (compressed folder), and attach it in your next reply.

Thanks for your cooperation.

here is the attached file

thanks
Robert

Hi Fred, did you find a solution?
I noticed when the system info is run, behind the error you can see it was at 10% done when it crashes.

I went ahead and bought the branded version of your software.
thanks in advance for your help.
Robert

Hi Robert. Thanks for the extra info. That surely narrows down the number of code lines to search in. I imported your SMBios dump, bu it didn't crash on my PC.

Sorry for not replying earlier, been hill with Influenza and bronchitis. Couldn't come up in a worst time, I have tons of work ahead right now.

Anyway, let's debug this thing. Please download the zipped debug build from the link below. Go to UVK's install directory, and rename the current UVK_en64.exe so you can restore it when this is all over.
Extract UVK_en64.exe from the zip to UVK's install directory.
Launch the new EXE file and go to the System Info section. The application may crash again.
A text file will be created in your desktop folder named "UVK_debug.txt". Please post it in your reply.

Thanks.