Hi,
I was working with some of you over on the DashNation slack about this, it was suggested that I post here about it.
I am trying to run the Windows 64bit dash-qt in testnet for 12.1 on my VPS.
In the current build (#676), I am getting an APPCRASH when launching dash-qt.
- It only happens when I use -testnet=1 parameter in the command line or dash.conf. The wallet loads fine in the live environment without testnet=1.
- The crash happens immediately -- the splash screen does not come up, there is no debug.log and the testnet3 folder does not get created.
- I can run the current 12.0.58 client with testnet=1 with no problem. I can also run the 12.0.59 release #32 (
https://dashpay.atlassian.net/builds/browse/DASHW-REL-32) with testnet=1
- I tried some earlier 12.1 builds going back to #660 from Nov. 24, but they all crash immediately, and only when testnet=1
- using -splash=0 does not resolve the issue
- The 32-bit version has the same problem
- It is an older OS but is up to date with the latest windows updates and .NET framework version
- Yes, I tried rebooting
splawik21 and bertlebbert were helping me to make sure my folder structure was correct, was getting a fresh start and was using the correct command line parameters,...etc, but we weren't able to find the problem.
It is a *very* generic error message. From error details:
Code:
Application Version: 0.12.1.0
Application Timestamp: 5685c180
Fault Module Name: StackHash_e42b
Fault Module Version: 6.1.7601.23572
Fault Module Timestamp: 57fd0651
Exception Code: c0000374
Exception Offset: 00000000000bf3e2
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 1033
Additional Information 1: e42b
Additional Information 2: e42ba80f0e604413c03a7cab4669ab96
Additional Information 3: 0cea
Additional Information 4: 0cea4eb8f33588e87b8b09234cac6d38
From event log:
Code:
Faulting application name: dash-qt.exe, version: 0.12.1.0, time stamp: 0x5685c180
Faulting module name: ntdll.dll, version: 6.1.7601.23572, time stamp: 0x57fd0651
Exception code: 0xc0000374
Fault offset: 0x00000000000bf3e2
Faulting process id: 0x94c
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
System info:
Code:
Host Name: WIN-BOFMD33PJ3R
OS Name: Microsoft Windows Server 2008 R2 Standard
OS Version: 6.1.7601 Service Pack 1 Build 7601
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Server
OS Build Type: Multiprocessor Free
Registered Owner: Windows User
Registered Organization:
Product ID: 55041-013-1647746-84951
Original Install Date: 5/22/2015, 9:00:56 PM
System Boot Time: 12/4/2016, 5:45:20 PM
System Manufacturer: Red Hat
System Model: KVM
System Type: x64-based PC
Processor(s): 2 Processor(s) Installed.
[01]: Intel64 Family 6 Model 13 Stepping 3 GenuineInt
el ~2000 Mhz
[02]: Intel64 Family 6 Model 13 Stepping 3 GenuineInt
el ~2000 Mhz
BIOS Version: Seabios 0.5.1, 1/1/2007
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: (UTC-05:00) Eastern Time (US & Canada)
Total Physical Memory: 2,048 MB
Available Physical Memory: 1,578 MB
Virtual Memory: Max Size: 4,095 MB
Virtual Memory: Available: 3,589 MB
Virtual Memory: In Use: 506 MB
Page File Location(s): C:\pagefile.sys
Domain: WORKGROUP
Logon Server: \\WIN-BOFMD33PJ3R
Hotfix(s): 206 Hotfix(s) Installed.
[01]: KB981391
[02]: KB981392
[03]: KB977236
[04]: KB981111
[05]: KB977238
[06]: KB2849697
[07]: KB2849696
[08]: KB2841134
[09]: KB977239
[10]: KB2670838
[11]: KB2830477
[12]: KB2592687
[13]: KB981390
[14]: KB2506014
[15]: KB2506212
[16]: KB2506928
[17]: KB2509553
[18]: KB2533623
[19]: KB2545698
[20]: KB2547666
[21]: KB2552343
[22]: KB2560656
[23]: KB2563227
[24]: KB2564958
[25]: KB2574819
[26]: KB2585542
[27]: KB2603229
[28]: KB2604115
[29]: KB2607047
[30]: KB2608658
[31]: KB2620704
[32]: KB2621440
[33]: KB2636573
[34]: KB2639308
[35]: KB2640148
[36]: KB2643719
[37]: KB2653956
[38]: KB2654428
[39]: KB2660075
[40]: KB2667402
[41]: KB2676562
[42]: KB2685811
[43]: KB2685813
[44]: KB2690533
[45]: KB2698365
[46]: KB2705219
[47]: KB2719857
[48]: KB2726535
[49]: KB2729094
[50]: KB2729452
[51]: KB2731771
[52]: KB2732059
[53]: KB2742599
[54]: KB2750841
[55]: KB2758857
[56]: KB2761217
[57]: KB2763523
[58]: KB2765809
[59]: KB2770660
[60]: KB2786081
[61]: KB2791765
[62]: KB2798162
[63]: KB2800095
[64]: KB2807986
[65]: KB2808679
[66]: KB2813430
[67]: KB2834140
[68]: KB2836943
[69]: KB2840149
[70]: KB2843630
[71]: KB2852386
[72]: KB2853952
[73]: KB2857650
[74]: KB2862152
[75]: KB2862330
[76]: KB2862335
[77]: KB2864202
[78]: KB2868038
[79]: KB2868116
[80]: KB2871997
[81]: KB2882822
[82]: KB2884256
[83]: KB2888049
[84]: KB2891804
[85]: KB2892074
[86]: KB2893294
[87]: KB2893519
[88]: KB2894844
[89]: KB2900986
[90]: KB2908783
[91]: KB2911501
[92]: KB2912390
[93]: KB2919469
[94]: KB2929733
[95]: KB2931356
[96]: KB2937610
[97]: KB2957189
[98]: KB2966583
[99]: KB2968294
[100]: KB2970228
[101]: KB2972100
[102]: KB2972211
[103]: KB2973201
[104]: KB2973351
[105]: KB2977292
[106]: KB2978120
[107]: KB2984972
[108]: KB2985461
[109]: KB2991963
[110]: KB2992611
[111]: KB2993651
[112]: KB3003743
[113]: KB3004361
[114]: KB3004375
[115]: KB3006137
[116]: KB3010788
[117]: KB3011780
[118]: KB3018238
[119]: KB3019978
[120]: KB3020370
[121]: KB3021674
[122]: KB3022777
[123]: KB3023215
[124]: KB3030377
[125]: KB3033889
[126]: KB3035126
[127]: KB3035132
[128]: KB3037574
[129]: KB3042553
[130]: KB3045685
[131]: KB3046017
[132]: KB3046269
[133]: KB3054205
[134]: KB3054476
[135]: KB3055642
[136]: KB3059317
[137]: KB3060716
[138]: KB3068457
[139]: KB3068708
[140]: KB3071756
[141]: KB3072630
[142]: KB3074543
[143]: KB3075220
[144]: KB3076895
[145]: KB3078601
[146]: KB3078667
[147]: KB3080079
[148]: KB3080149
[149]: KB3080446
[150]: KB3084135
[151]: KB3086255
[152]: KB3092601
[153]: KB3092627
[154]: KB3097989
[155]: KB3101722
[156]: KB3102429
[157]: KB3107998
[158]: KB3108371
[159]: KB3108381
[160]: KB3108664
[161]: KB3108670
[162]: KB3109094
[163]: KB3109103
[164]: KB3109560
[165]: KB3110329
[166]: KB3118401
[167]: KB3121255
[168]: KB3122648
[169]: KB3123479
[170]: KB3124275
[171]: KB3126587
[172]: KB3127220
[173]: KB3133043
[174]: KB3133977
[175]: KB3135983
[176]: KB3137061
[177]: KB3138612
[178]: KB3138901
[179]: KB3139398
[180]: KB3139914
[181]: KB3139923
[182]: KB3139940
[183]: KB3140245
[184]: KB3142024
[185]: KB3146706
[186]: KB3146963
[187]: KB3147071
[188]: KB3149090
[189]: KB3156016
[190]: KB3156017
[191]: KB3156019
[192]: KB3159398
[193]: KB3161561
[194]: KB3161949
[195]: KB3161958
[196]: KB3163245
[197]: KB3164035
[198]: KB3170455
[199]: KB3177186
[200]: KB3177467
[201]: KB3179573
[202]: KB3185911
[203]: KB3195789
[204]: KB976902
[205]: KB982018
[206]: KB3197869
Anyone have any ideas?
Also, is there a way to find earlier versions of 12.1 builds? I'd like to see if there is a build earlier than 12.1 #660, but after the 12.0.59 release 32 that works, to maybe pinpoint when the problem starts.
Thx --
