[SOLVED] SysnativeBSODProcessingApps Missing BaseBoard Manufacturer

[blueelvis]

Hello Everyone ^_^,

I was analysing the dump files and found that in WinDBG, the dump file gave the output -

3: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.5, DMIVersion 0, Size=2414]
BiosMajorRelease = 8
BiosMinorRelease = 15
BiosVendor = American Megatrends Inc.
BiosVersion = 2104   
BiosReleaseDate = 08/13/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
SystemFamily = To Be Filled By O.E.M.
SystemVersion = System Version
SystemSKU = To Be Filled By O.E.M.
[B][U]BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = M4A785TD-M EVO
BaseBoardVersion = Rev X.0x
[/U][/B]

This is the output of the SysnativeBSODProcessingApps when that dump was analysed using the app -

**************************Thu Jan 22 00:02:45.123 2015 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\012115-42406-01.dmp]
 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
 
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
 
System Uptime: 0 days 0:08:41.935
 
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_UsbMapDpc_Worker+1e672 )
 
BugCheck 139, {3, ffffd000208e3870, ffffd000208e37c8, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]KERNEL_SECURITY_CHECK_FAILURE (139)[/url]
 
Arguments: 
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd000208e3870, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd000208e37c8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
BUGCHECK_STR:  0x139
 
DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  0x139_3_USBPORT!USBPORT_Core_UsbMapDpc_Worker
 
  BIOS Version                  2104   
 
  BIOS Release Date             08/13/2010
 
 [B][U] Manufacturer                  System manufacturer
 
  Product Name                  System Product Name
 [/U][/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

As you can see, if only the importantinfo.txt was checked, it was not revealed who the motherboard manufacturer was. But, when using WinDBG (This information was also present in the MSINFO32 partially) the manufacturer of the motherboard was revealed which helped in the identification of the system. I have attached the dump file as well.

View attachment 012115-42406-01.zip

So, Mike could you please add the BaseBoard manufacturer part as well to the SysnativeBSODProcessingApps output (importantinfo.txt) ?


Thanks :hug:
-Pranav

 

[writhziden]

I'll look into it. I have an idea of how to tie the two together so both are shown if one is requested. Would that work?

For example, if the settings in the apps have SystemManufacturer, SystemProductName, and SystemVersion enabled, the apps will also include the listings for BaseBoardManufacturer, BaseboardProductName, and BaseBoardVersion.

 

[blueelvis]

I'll look into it. I have an idea of how to tie the two together so both are shown if one is requested. Would that work?

For example, if the settings in the apps have SystemManufacturer, SystemProductName, and SystemVersion enabled, the apps will also include the listings for BaseBoardManufacturer, BaseboardProductName, and BaseBoardVersion.

Yea sure that would work. Would you be having all the options enabled by default so that the BaseBoardManufacturer, BaseboardProductName, and BaseBoardVersion are displayed in the output?

Also, any chance you could add an option (Like a checkbox?) on the default screen to automatically close the output window once the apps are finished working with the dump files?

Thanks a lot Mike ^_^

-Pranav

 

[writhziden]

I'll look into it. I have an idea of how to tie the two together so both are shown if one is requested. Would that work?

For example, if the settings in the apps have SystemManufacturer, SystemProductName, and SystemVersion enabled, the apps will also include the listings for BaseBoardManufacturer, BaseboardProductName, and BaseBoardVersion.

Yea sure that would work. Would you be having all the options enabled by default so that the BaseBoardManufacturer, BaseboardProductName, and BaseBoardVersion are displayed in the output?

Also, any chance you could add an option (Like a checkbox?) on the default screen to automatically close the output window once the apps are finished working with the dump files?

Thanks a lot Mike ^_^

-Pranav

I'll have to look into the default settings to answer your question about the defaults for the baseboard info. I also do not understand the request to close the output screen: Do you mean the screen that provides the options to open as HTML/txt output? How do you currently view the results?

 

[blueelvis]

I'll have to look into the default settings to answer your question about the defaults for the baseboard info. I also do not understand the request to close the output screen: Do you mean the screen that provides the options to open as HTML/txt output? How do you currently view the results?

Hi Mike ^_^,

Yes, I meant that screen only where we get the option to open the files as TXT/HTML output. Clicking on any button (TXT/HTML) opens up a lot of windows/browsers which are not required. In most of the cases, the only files I need to open and check are the 95_Debug, importantinfo.txt and 3rdPartyDriversDate.txt . I have enabled the option to have stacks and other information in separate text files as well in case they are needed (For example - when I want to take a look at the stacks of the dump files all together in a nice manner).

I currently close the output window and then manually open up the SysnativeBSODProcessingApps folder and then find the folder and check the files in there.

 

[writhziden]

I'll have to look into the default settings to answer your question about the defaults for the baseboard info. I also do not understand the request to close the output screen: Do you mean the screen that provides the options to open as HTML/txt output? How do you currently view the results?

Hi Mike ^_^,

Yes, I meant that screen only where we get the option to open the files as TXT/HTML output. Clicking on any button (TXT/HTML) opens up a lot of windows/browsers which are not required. In most of the cases, the only files I need to open and check are the 95_Debug, importantinfo.txt and 3rdPartyDriversDate.txt . I have enabled the option to have stacks and other information in separate text files as well in case they are needed (For example - when I want to take a look at the stacks of the dump files all together in a nice manner).

I currently close the output window and then manually open up the SysnativeBSODProcessingApps folder and then find the folder and check the files in there.

I've attached a new version of the executable with the option to close the apps when finished. It also grabs the BaseBoard info if it differs from the System info (it will grab both if both are different from each other). See how it works for you. I'll release an official update once I get some feedback from you and Usasma. :-}


I am also still working on adding support for driver dates on Windows 8.1 and Windows 10/release preview.

 

[blueelvis]

Thanks a lot Mike for the new version :)
I will provide feedback once I have analysed a couple of dumps using this :)

 

[blueelvis]

Hey Mike ^_^,

I just analysed a couple of dump files and everything is working smoothly. I have enabled the Option to close the output window and it is working flawlessly :) . Once again thanks! Below is one output of the importantinfo.txt -

**************************Sat Jan 31 11:35:07.183 2015 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\013115-5218-01.dmp]
 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
 
Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
 
System Uptime: 0 days 13:50:57.924
 
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
 
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
 
Arguments: 
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
 component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  ZEROED_STACK
 
CPUID:        "Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz"
 
MaxSpeed:     1600
 
CurrentSpeed: 1600
 
  BIOS Version                  R1044V7
 
  BIOS Release Date             03/24/2014
 
  Manufacturer                  Sony Corporation
 
  Product Name                  SVP1321M2EB
 
  Baseboard Product             VAIO
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Thread marked as solved.

-Pranav