SysnativeBSODProcessingApp Crashing on Certain Set of Dump Files

blueelvis

blueelvis

BSOD Kernel Dump Senior Analyst
Joined
Apr 14, 2014
Posts
970
Location
India
Hi Mike ^_^,

I am trying to analyze 3 dump files using the SysnativeBSODProcessingApps but the application is crashing. Below is a screenshot of the crash so that you know the exact moment of the crash -
Untitled.png

Also, these 3 dump files are opening properly with WinDBG/BlueScreenView and are also attached with this thread.

@Everyone else - Could you guys also check this so that I could confirm if it is a local problem or not.

EDIT :- I forgot mentioning one point though. The app reaches the parsing point very quickly. This is strange for me because for the rest of the dump files, the app seems to run the kd.exe for quite some time.


Thanks!

-Pranav

View attachment 051915-25718-01.zip
 
Last edited:
I was unable to reproduce the crash on my end. It may be your options for the user options section.

Can you please save a .zdn file through Change Settings->File->Save As->crash.zdn and upload the crash.zdn file in your next response?
 
Last edited:
writhziden said:
blueelvis said:
Here you go Mike :)


View attachment 13118


-Pranav
Click to expand...
Thanks. Oddly, I can now reproduce it with both your settings and mine, but it happens randomly. It will likely take me some time to track down. Random crashes are the worst to debug. :-{
Click to expand...
Well that is strange. If you don't mind, could you tell me how would you be trying to debug this situation? Configuring ProcDump to capture the crash?

I already tried running the app for like 4 times and it failed every single time. Seems like it is not random for me or I do have a very bad coincidence.


@Richard - You seem to like them :p


-Pranav
 
blueelvis said:
Read More:
Well that is strange. If you don't mind, could you tell me how would you be trying to debug this situation? Configuring ProcDump to capture the crash?

I already tried running the app for like 4 times and it failed every single time. Seems like it is not random for me or I do have a very bad coincidence.


@Richard - You seem to like them :p


-Pranav
Click to expand...

There appear to be two crashes associated with the .dmps. Yours should be reproducible once I can sit down and dig into it. Your settings result in a very consistent crash as you mention. There is a more subtle crash that happens very rarely during the 2nd kd.exe .dmp run, and I am not sure what is causing that one.

Depending on the type of crash, I do two things: I run in debug mode through Visual C++ when random crashes occur so I can track clobbered memory, or I have a logfile I generate to track crashes that are easily reproducible.
 
Just FYI - I find crashes frequently in the version of the app that you last posted for Pranav.
Some of them will work in the version that you last posted for me.
If not, then they all work in the last released version.
 
usasma said:
Just FYI - I find crashes frequently in the version of the app that you last posted for Pranav.
Some of them will work in the version that you last posted for me.
If not, then they all work in the last released version.
Click to expand...

Thanks. That may be very helpful. I added in a check for the missing DRT files in the unofficial releases. I will have to check my logic there and see if I might have a mistake somewhere.

I will also check the logic for the baseboard info that I added.


I have a lot of family time going on right now, I am in the process of getting ready to move, and I have some training to take to prepare for looking for a job. Things should free up considerably in August, which may mean the apps are a little behind with the Windows 10 release date. I was not anticipating such an early release of Windows 10 since early projections placed it toward the end of the year.
 
jcgriff2 said:
@ Pranav - go to the Reliability Monitor & grab the crash info. Doubtful there is much, if anything, helpful, but never know.

https://www.sysnative.com/forums/wi...ability-monitor-windows-10-8-1-8-7-vista.html
Click to expand...
WOA!
I was always wondering as to why VLC wouldn't launch immediately after closing one video and it seems that it has been crashing silently and the reports are here in the Reliability Monitor. These VLC Problems account to like 100's of reports :O

For Mike's app, below is the data present -
Code: 
SourceSysnative BSOD Analysis Software


Summary
Stopped working


Date
‎12-‎06-‎2015 01:11


Status
Not reported


Description
Faulting Application Path:	C:\SysnativeBSODApps\SysnativeBSODApps.exe


Problem signature
Problem Event Name:	APPCRASH
Application Name:	SysnativeBSODApps.exe
Application Version:	2.16.0.0
Application Timestamp:	54d56443
Fault Module Name:	KERNELBASE.dll
Fault Module Version:	6.3.9600.17415
Fault Module Timestamp:	54504ade
Exception Code:	e06d7363
Exception Offset:	00014598
OS Version:	6.3.9600.2.0.0.256.89
Locale ID:	16393
Additional Information 1:	5861
Additional Information 2:	5861822e1919d7c014bbb064c64908b2
Additional Information 3:	a10f
Additional Information 4:	a10ff7d2bb2516fdc753f9c34fc3b069

Thanks a lot JC! Need to find a fix for these VLC crashes since that is the only way to increase my reliability score :p


-Pranav
 
blueelvis said:
Read More:
Click to expand...

Installed the apps on the laptop I have with me for my family trip. I am unable to reproduce the crash using any settings now. This is very confusing...

Are you using the most recent version of the kernel debugger? That is the only real difference between this system and my test system at home: I have the most recent version of the kernel debugger installed on this system.

I'm thinking it's a version issue with the kernel debugger. One version outputs slightly different information that the apps parse and causes a crash. Other versions may or may not cause the parsing to fail. I really wish there was an archive of previous Windbg/kd.exe versions. I need 6.2.9200.16384 but have 6.12.0002.633 instead.
 
Last edited:
writhziden said:
Installed the apps on the laptop I have with me for my family trip. I am unable to reproduce the crash using any settings now. This is very confusing...

Are you using the most recent version of the kernel debugger? That is the only real difference between this system and my test system at home: I have the most recent version of the kernel debugger installed on this system.

I'm thinking it's a version issue with the kernel debugger. One version outputs slightly different information that the apps parse and causes a crash. Other versions may or may not cause the parsing to fail. I really wish there was an archive of previous Windbg/kd.exe versions. I need 6.2.9200.16384 but have 6.12.0002.633 instead.
Click to expand...
I am able to reproduce the crash as of now.

The version installed on my system of WinDBG is - 6.3.9600.17298

Also, I have got Windows 8.1 Embedded Industry Pro installed on this laptop. Now, that you mention different versions of kd.exe , I remember that when I asked Jared to analyze a dump file, he got a completely different stack than me. He was on a different version than me. I confirmed with Patrick as well and he got the stack which was similar to Jared's. Below is a small quote from the PM which I sent to Patrick for confirmation -
I am working on a case on Eightforums with Jared. Here is the link -
http://www.eightforums.com/bsod-cras...x0000004e.html

And here is the ZIP file -
Microsoft services

Now, the problem me and Jared facing is that we both are getting different stacks even though we are analysing the same dumps, same symbols and same 64 bit version of WinDBG (We both tried 32 Bit version as well).

I am using Version - 6.3.9600.17298
Jared is using version - 6.3.9600.17029

Below is Jared's stack of the latest dump files (012515-7940-01.dmp) & (012515-8985-01.dmp) -
Code: 
Code:
0: kd> kC
Call Site
nt!KeBugCheckEx
nt! ?? ::FNODOBFM::`string'
nt!KiPageFault
win32k!VertCrossings
win32k!DoVertDropout
win32k!LookForDropouts
win32k!fsc_FillGlyph
win32k!fs_ContourScan
win32k!lGetGlyphBitmap
win32k!ttfdQueryFontData
win32k!ttfdSemQueryFontData
win32k!PDEVOBJ::QueryFontData
win32k!xInsertGlyphbitsRFONTOBJ
win32k!RFONTOBJ::bGetGlyphMetricsPlus
win32k!ESTROBJ::vCharPos_H3
win32k!ESTROBJ::vInit
win32k!GreExtTextOutWLocked
win32k!GreExtTextOutWInternal
win32k!GreExtTextOutW
&
Code: 
Code:
2: kd> kC
Call Site
nt!KeBugCheckEx
nt! ?? ::FNODOBFM::`string'
nt!KiPageFault
win32k!BltLnk
win32k!EngBitBlt
win32k!NtGdiBitBltInternal
win32k!NtGdiBitBlt
nt!KiSystemServiceCopyEnd
0x0
And now, here is my stack -
Code: 
Code:
2: kd> kC
Call Site
nt!KeBugCheckEx
nt! ?? ::FNODOBFM::`string'
nt!KiPageFault
win32k!XLATEOBJ_cGetPalette
win32k!EngBitBlt
win32k!XLATEOBJ_cGetPalette
win32k!XLATEOBJ_iXlate
nt!KiSystemServiceCopyEnd
0x0
&
Code: 
Code:
0: kd> kC
Call Site
nt!KeBugCheckEx
nt! ?? ::FNODOBFM::`string'
nt!KiPageFault
win32k!EngBitBlt
win32k!EngBitBlt
win32k!EngBitBlt
win32k!EngBitBlt
win32k!EngBitBlt
win32k!EngBitBlt
win32k!EngBitBlt
win32k!EngBitBlt
win32k!XFORMOBJ_iGetFloatObjXform
win32k!EngBitBlt
win32k!EngBitBlt
win32k!EngBitBlt
win32k!EngBitBlt
win32k!XFORMOBJ_iGetFloatObjXform
win32k!XFORMOBJ_iGetFloatObjXform
win32k!XFORMOBJ_iGetFloatObjXform
Now, could you please crosscheck which stack are you getting? Also, any idea why we might be getting different stacks?
Click to expand...


Any chance these 2 problems could be related?



Thanks a lot Mike ^_^


-Pranav
 
Last edited:
blueelvis said:
Any chance these 2 problems could be related?



Thanks a lot Mike ^_^


-Pranav
Click to expand...
No idea, but it's possible. I'll have to check my drives I brought with me and see if I can find some other versions of the debugger.

EDIT: Ugh, more inconsistency. Found 6.2.9200.16384 and installed it, but I still cannot get it to crash on this system using your crash.zdn settings.

EDIT2: Finally reproduced it with 6.3.9600.17336 and will try to track down what is causing the crashes.
 
Last edited:
usasma said:
Sweet!!! Thanks Mike!!!
Click to expand...

You will note that there is a new button under Old Driver After for Windows 8.1 and Windows 10, but there is currently no actual functionality for the window that opens using that button. The button was not meant to be in the updated version today, but I hope to add functionality to its window in the next week or two.
 
writhziden said:
This problem should now be resolved in the official update: 2.16.7

Let me know if you encounter further bugs with the latest version.
Click to expand...
So, what was the problem with the App?

I will test them soon and report them back to you. Also, as soon as I opened the app right now, I got the update notification that there might be an update. After I opened it again, I got a notification again. This is going on since like 5-6 times now. Any idea what might be happening here?



Thanks a lot Mike! Now, enjoy the vacation ;)


-Pranav
 
blueelvis said:
So, what was the problem with the App?

I will test them soon and report them back to you. Also, as soon as I opened the app right now, I got the update notification that there might be an update. After I opened it again, I got a notification again. This is going on since like 5-6 times now. Any idea what might be happening here?



Thanks a lot Mike! Now, enjoy the vacation ;)


-Pranav
Click to expand...
The problem was that I was reading 10 lines in advance to find the Baseboard information you wanted. That resulted in reading beyond the end of the file at times.


As to the notification of the update occurring multiple times, that is due to one of three things:
  1. A DNS issue on your end due to your ISP.
  2. A poor internet connection on your end.
  3. The server being down, resulting in your system not being able to check the current version of the apps
 

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

Back
Top