HALP! BTP won't open anymore!

Found a problem? Post details on BeerTools Pro errors and how they are caused.
Post Reply
BeefySS65
Posts: 9
Joined: Sat Sep 12, 2009 8:49 pm
Location: Sammamish, WA

HALP! BTP won't open anymore!

Post by BeefySS65 »

I re-downloaded, even copied my recipe folder to a backup and re-installed. Did a clean uninstall as well. BTP just won't run anymore!

:(

Running Vista...here's the crash detail report:

Problem signature:
Problem Event Name: APPCRASH
Application Name: BeerTools Pro.exe
Application Version: 1.5.3.218
Application Timestamp: 49da13f6
Fault Module Name: StackHash_d359
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 02897975
OS Version: 6.0.6002.2.2.0.256.6
Locale ID: 1033
Additional Information 1: d359
Additional Information 2: 3aea869f71000792dff2eab077f75b0b
Additional Information 3: ea33
Additional Information 4: cd7920d108a0a373b5f3da963056f37b

:(
User avatar
jeff
Imperial Stout
Imperial Stout
Posts: 1602
Joined: Sun Jan 09, 2000 8:16 pm
Location: Hollywood, SC
Contact:

Has anyone else experienced a crash on Vista?

Post by jeff »

BeefySS65 wrote:I re-downloaded, even copied my recipe folder to a backup and re-installed. Did a clean uninstall as well. BTP just won't run anymore!

:(

Running Vista...here's the crash detail report:

Problem signature:
Problem Event Name: APPCRASH
Application Name: BeerTools Pro.exe
Application Version: 1.5.3.218
Application Timestamp: 49da13f6
Fault Module Name: StackHash_d359
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 02897975
OS Version: 6.0.6002.2.2.0.256.6
Locale ID: 1033
Additional Information 1: d359
Additional Information 2: 3aea869f71000792dff2eab077f75b0b
Additional Information 3: ea33
Additional Information 4: cd7920d108a0a373b5f3da963056f37b

:(
Hmm. This is the first report I have heard of this issue. Has anyone else reading this topic experienced a crash similar to this?
Jeff
BeerTools.com Staff
BeefySS65
Posts: 9
Joined: Sat Sep 12, 2009 8:49 pm
Location: Sammamish, WA

Post by BeefySS65 »

I tried looking for any potential remnants leftover in the registry after an uninstall as well. I looked for 'obvious' candidates but didn't see any. Perhaps I have a corrupt shared dll? It was working fine 3 days ago. I'm really surprised a clean install didn't remedy the problem. Is there any tests I could do to provide you info? What happens is the windows opens and is white <aka no contents>. Then the Windows alert pops up saying "BeerToolPro.exe has stopped working. Windows can check for an online solution to the problem'
User avatar
jeff
Imperial Stout
Imperial Stout
Posts: 1602
Joined: Sun Jan 09, 2000 8:16 pm
Location: Hollywood, SC
Contact:

Post by jeff »

Does the app launch if you turn off your internet connection?
Jeff
BeerTools.com Staff
BeefySS65
Posts: 9
Joined: Sat Sep 12, 2009 8:49 pm
Location: Sammamish, WA

Post by BeefySS65 »

Unfortunately, no. I unplugged my ethernet cable and the same result happens.
BeefySS65
Posts: 9
Joined: Sat Sep 12, 2009 8:49 pm
Location: Sammamish, WA

Post by BeefySS65 »

OK, I installed Windwos Debugger and opened the exe. Here's what it spewed:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

CommandLine: "C:\Program Files\BeerTools Pro 1.5\BeerTools Pro.exe"
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
ModLoad: 00400000 00649000 X86RunHoudini.exe
ModLoad: 771d0000 772f7000 ntdll.dll
ModLoad: 76890000 7696c000 C:\Windows\system32\kernel32.dll
ModLoad: 74b70000 74b78000 C:\Windows\system32\VERSION.dll
ModLoad: 76710000 767ba000 C:\Windows\system32\msvcrt.dll
ModLoad: 747e0000 7497e000 C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6002.18005_none_5cb72f96088b0de0\COMCTL32.dll
ModLoad: 75b30000 75bf6000 C:\Windows\system32\ADVAPI32.dll
ModLoad: 767c0000 76883000 C:\Windows\system32\RPCRT4.dll
ModLoad: 76d70000 76dbb000 C:\Windows\system32\GDI32.dll
ModLoad: 76cd0000 76d6d000 C:\Windows\system32\USER32.dll
ModLoad: 76fe0000 77039000 C:\Windows\system32\SHLWAPI.dll
ModLoad: 740c0000 740f2000 C:\Windows\system32\WINMM.dll
ModLoad: 76dc0000 76f05000 C:\Windows\system32\ole32.dll
ModLoad: 76970000 769fd000 C:\Windows\system32\OLEAUT32.dll
ModLoad: 74080000 740bd000 C:\Windows\system32\OLEACC.dll
ModLoad: 75110000 75129000 C:\Windows\system32\iphlpapi.dll
ModLoad: 750d0000 75105000 C:\Windows\system32\dhcpcsvc.DLL
ModLoad: 75350000 7537c000 C:\Windows\system32\DNSAPI.dll
ModLoad: 76c10000 76c3d000 C:\Windows\system32\WS2_32.dll
ModLoad: 75b20000 75b26000 C:\Windows\system32\NSI.dll
ModLoad: 75710000 75724000 C:\Windows\system32\Secur32.dll
ModLoad: 750c0000 750c7000 C:\Windows\system32\WINNSI.DLL
ModLoad: 75090000 750b2000 C:\Windows\system32\dhcpcsvc6.DLL
ModLoad: 76f10000 76f83000 C:\Windows\system32\comdlg32.dll
ModLoad: 75c00000 76710000 C:\Windows\system32\SHELL32.dll
(19c0.235c): Break instruction exception - code 80000003 (first chance)
eax=00000000 ebx=00000000 ecx=0012faf8 edx=77235e74 esi=fffffffe edi=7721c19e
eip=77218b2e esp=0012fb10 ebp=0012fb40 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
ntdll!DbgBreakPoint:
77218b2e cc int 3


I'm no programmer...any clues what this means?
User avatar
jeff
Imperial Stout
Imperial Stout
Posts: 1602
Joined: Sun Jan 09, 2000 8:16 pm
Location: Hollywood, SC
Contact:

Debugger

Post by jeff »

Honestly, I don't know what that means. However, if I were trying to use the debugger I would probably repair the symbols problem first. Some resources including symbols packages are here:

http://www.microsoft.com/whdc/devtools/ ... fault.mspx

The output you provided above seems to stop short of anything connected with running BTP since all of the libraries loaded up to the error point are system related. I have never used the utility so I don't have much insight on its use. Perhaps its output will reveal whether the problem exists on your system or in BTP itself once the symbols thing is resolved. Like I said, though, this is outside my realm of experience so proceed at your own risk :?
Jeff
BeerTools.com Staff
BeefySS65
Posts: 9
Joined: Sat Sep 12, 2009 8:49 pm
Location: Sammamish, WA

Post by BeefySS65 »

OK, repaired the symbols, reran, pointed to the beer tool pro exe and got:

ModLoad: 76850000 7686e000 C:\Windows\system32\IMM32.DLL
ModLoad: 76fd0000 77098000 C:\Windows\system32\MSCTF.dll
ModLoad: 773c0000 773c9000 C:\Windows\system32\LPK.DLL
ModLoad: 76af0000 76b6d000 C:\Windows\system32\USP10.dll
ModLoad: 001d0000 001eb000 C:\Program Files\Common Files\Logishrd\LVMVFM\LVPrcInj.dll
ModLoad: 74600000 7463f000 C:\Windows\system32\uxtheme.dll
ModLoad: 734f0000 73550000 C:\Program Files\Common Files\microsoft shared\ink\tiptsf.dll
ModLoad: 72390000 72397000 C:\Windows\system32\wsock32.dll
ModLoad: 76df0000 76e74000 C:\Windows\system32\CLBCatQ.DLL
ModLoad: 10000000 10023000 C:\Program Files\BeerTools Pro 1.5\BeerTools Pro Libs\Appearance Pak.dll
ModLoad: 00a00000 00a1a000 C:\Program Files\BeerTools Pro 1.5\BeerTools Pro Libs\Browser Plugin.dll
ModLoad: 00a70000 00a82000 C:\Program Files\BeerTools Pro 1.5\BeerTools Pro Libs\Internet Encodings.dll
ModLoad: 00aa0000 00aba000 C:\Program Files\BeerTools Pro 1.5\BeerTools Pro Libs\MD5.dll
ModLoad: 01850000 018c0000 C:\Program Files\BeerTools Pro 1.5\BeerTools Pro Libs\REALSQLDatabase.dll
ModLoad: 01d60000 01d85000 C:\Program Files\BeerTools Pro 1.5\BeerTools Pro Libs\RegEx.dll
ModLoad: 038c0000 0399e000 C:\Program Files\BeerTools Pro 1.5\BeerTools Pro Libs\RBScript.dll
ModLoad: 03a40000 03b34000 C:\Program Files\BeerTools Pro 1.5\BeerTools Pro Libs\SSLSocket.dll
ModLoad: 03750000 03813000 C:\Program Files\BeerTools Pro 1.5\BeerTools Pro Libs\XML.dll
ModLoad: 01db0000 01dc1000 C:\Program Files\BeerTools Pro 1.5\BeerTools Pro Libs\EHObjectArray4801.dll
ModLoad: 01de0000 01df7000 C:\Program Files\BeerTools Pro 1.5\BeerTools Pro Libs\EHObjectCollection4801.dll
ModLoad: 01e10000 01e20000 C:\Program Files\BeerTools Pro 1.5\BeerTools Pro Libs\EHDateCtrl3601.dll
ModLoad: 61a40000 61af8000 C:\Program Files\BeerTools Pro 1.5\BeerTools Pro Libs\libExtended.DLL
ModLoad: 02000000 0201e000 C:\Program Files\BeerTools Pro 1.5\BeerTools Pro Libs\EHTreeView4101.DLL
ModLoad: 03830000 03846000 C:\Program Files\BeerTools Pro 1.5\BeerTools Pro Libs\EHWindowSplitter7201.dll
ModLoad: 03850000 03861000 C:\Program Files\BeerTools Pro 1.5\BeerTools Pro Libs\EHInterfaces4801.dll
ModLoad: 75b50000 75cda000 C:\Windows\system32\SETUPAPI.dll
ModLoad: 757f0000 7580e000 C:\Windows\system32\USERENV.dll
ModLoad: 73fb0000 7406b000 C:\Windows\system32\PROPSYS.dll
ModLoad: 74f90000 74fcb000 C:\Windows\system32\mswsock.dll
ModLoad: 74c10000 74c15000 C:\Windows\System32\wshtcpip.dll
ModLoad: 73f20000 73f2f000 C:\Windows\system32\NLAapi.dll
ModLoad: 6edb0000 6edbf000 C:\Windows\system32\napinsp.dll
ModLoad: 6ed70000 6ed82000 C:\Windows\system32\pnrpnsp.dll
ModLoad: 6eda0000 6eda8000 C:\Windows\System32\winrnr.dll
ModLoad: 769b0000 769f9000 C:\Windows\system32\WLDAP32.dll
ModLoad: 758a0000 758a7000 C:\Windows\system32\PSAPI.DLL
ModLoad: 16080000 160a5000 C:\Program Files\Bonjour\mdnsNSP.dll
ModLoad: 74a70000 74a76000 C:\Windows\system32\rasadhlp.dll
ModLoad: 75630000 756a6000 C:\Windows\system32\NETAPI32.DLL
ModLoad: 74d10000 74d4b000 C:\Windows\system32\rsaenh.dll
ModLoad: 71d10000 71d16000 C:\Windows\system32\RICHED32.DLL
ModLoad: 719e0000 71a54000 C:\Windows\system32\RICHED20.dll
ModLoad: 73310000 7339c000 C:\Windows\system32\msftedit.dll
(1370.d44): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000000 edi=034892c0
eip=027a7975 esp=0012dd18 ebp=0012f2e0 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
027a7975 8b4000 mov eax,dword ptr [eax] ds:0023:00000000=????????


...then it halted...any clues?
BeefySS65
Posts: 9
Joined: Sat Sep 12, 2009 8:49 pm
Location: Sammamish, WA

Post by BeefySS65 »

Perhaps some more info from the Event Viewer:

Version=1
EventType=APPCRASH
EventTime=129048921060534938
ReportType=2
Consent=1
UploadTime=129048921195799718
Response.BucketId=1598407925
Response.BucketTable=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=BeerTools Pro.exe
Sig[1].Name=Application Version
Sig[1].Value=1.5.3.218
Sig[2].Name=Application Timestamp
Sig[2].Value=49da13f6
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_d359
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=00000000
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=02667975
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.0.6002.2.2.0.256.6
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=d359
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=3aea869f71000792dff2eab077f75b0b
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=ea33
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=cd7920d108a0a373b5f3da963056f37b
UI[2]=C:\Program Files\BeerTools Pro 1.5\BeerTools Pro.exe
UI[3]=BeerTools Pro.exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=1598407925/nBucketTable=1/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=BeerTools Pro.exe
AppPath=C:\Program Files\BeerTools Pro 1.5\BeerTools Pro.exe
User avatar
jeff
Imperial Stout
Imperial Stout
Posts: 1602
Joined: Sun Jan 09, 2000 8:16 pm
Location: Hollywood, SC
Contact:

Post by jeff »

I have been searching the web for clues for what all of that means but have found nothing useful so far. I have a feeling that the only way I would be able to locate the problem is to use my own remote debugging program. However, the logistics of setting that up are a little tricky.

You mentioned that you tried a clean install. Perhaps you can try renaming your preferences files too. Look for this directory:

C:\Documents and Settings\<your username>\Application Data\BeerTools Pro

There are a few files in there that you might rename such as:

Prefs.xml
RecentItems
license

Renaming the files essentially forces BTP to recreate them. If you rename each file individually and check if BTP runs after each one, we will have a good chance of figuring out what is causing the problem.
Jeff
BeerTools.com Staff
BeefySS65
Posts: 9
Joined: Sat Sep 12, 2009 8:49 pm
Location: Sammamish, WA

Post by BeefySS65 »

WOOHOO! SUCCESS! Thx for the point to the prefs. Didn't even think to look there! Problem solved!
User avatar
jeff
Imperial Stout
Imperial Stout
Posts: 1602
Joined: Sun Jan 09, 2000 8:16 pm
Location: Hollywood, SC
Contact:

Post by jeff »

BeefySS65 wrote:WOOHOO! SUCCESS! Thx for the point to the prefs. Didn't even think to look there! Problem solved!
Awesome! So, was it the Prefs.xml file or one of the others?
Jeff
BeerTools.com Staff
youngster9
Posts: 4
Joined: Mon Jan 26, 2009 11:17 pm

Beertools Update Pro 1.5 Update

Post by youngster9 »

I too can't get the program to run after installing the update and was going to brew this coming weekend. Dowload 2 (maybe 3) times and installed on 11 Se at 5PM Pacific. HELP!!!
youngster9
Posts: 4
Joined: Mon Jan 26, 2009 11:17 pm

BTP 1.5 Update

Post by youngster9 »

Disregard last post ... looks like I'm back in business after a couple reboots.
Post Reply