- ago
Greetings,
I am running WL8 Build 32. Since updating I have noticed an increase in the number of Wealth-Lab crashes. Most of the time the crash occurs when saving a strategy to Wealth-Lab.com, but there have also been a few evenings when I left Wealth-Lab running over nite to get the data updates, and when I come back in the morning Wealth-Lab is gone. Is anyone else having this problem? Or is it something environmental on my end?
Thank you
-sifty
0
643
Solved
7 Replies

Reply

Bookmark

Sort
Cone8
 ( 6.17% )
- ago
#1
Which data providers are schedule to update overnight?
0
- ago
#2
-WealthData
-Q-Data
-Yahoo! Finance
0
Cone8
 ( 6.17% )
- ago
#3
Only Daily providers. If you were updating highly granular intraday data, there's a potential for a memory issue .

This is a tough guess from our vantage point without more information. Maybe you can find some crash information in the Windows Event Viewer to help isolate it.
0
- ago
#4
Thank you for the tip. Found the following two. This was when I saved the strategy to disk and Wealth-Lab.com.

System

- Provider

[ Name] Application Error
[ Guid] {a0e9b465-b939-57d7-b27d-95d8e925ff57}

EventID 1000

Version 0

Level 2

Task 100

Opcode 0

Keywords 0x8000000000000000

- TimeCreated

[ SystemTime] 2023-03-08T21:33:25.2427912Z

EventRecordID 13680

Correlation

- Execution

[ ProcessID] 9736
[ ThreadID] 35100

Channel Application

Computer LAPTOP-0B54II2U

- Security

[ UserID] S-1-5-21-91988198-2477983528-856112534-1001


- EventData

AppName WealthLab8.exe
AppVersion 8.0.32.0
AppTimeStamp 63558578
ModuleName ntdll.dll
ModuleVersion 10.0.22621.900
ModuleTimeStamp a97a9ed6
ExceptionCode c0000409
FaultingOffset 000000000008eadf
ProcessId 0x360
ProcessCreationTime 0x1d95131d76e2f2c
AppPath C:\Program Files\Quantacula, LLC\WealthLab 8\WealthLab8.exe
ModulePath C:\WINDOWS\SYSTEM32\ntdll.dll
IntegratorReportId a8245f28-31e3-411a-ab09-cdc6fc27297b
PackageFullName
PackageRelativeAppId

Faulting application name: WealthLab8.exe, version: 8.0.32.0, time stamp: 0x63558578
Faulting module name: ntdll.dll, version: 10.0.22621.900, time stamp: 0xa97a9ed6
Exception code: 0xc0000409
Fault offset: 0x000000000008eadf
Faulting process id: 0x0x360
Faulting application start time: 0x0x1D95131D76E2F2C
Faulting application path: C:\Program Files\Quantacula, LLC\WealthLab 8\WealthLab8.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: a8245f28-31e3-411a-ab09-cdc6fc27297b
Faulting package full name:
Faulting package-relative application ID:

which was followed 4 seconds later by:
System

- Provider

[ Name] Windows Error Reporting
[ Guid] {0ead09bd-2157-539a-8d6d-c87f95b64d70}

EventID 1001

Version 0

Level 4

Task 0

Opcode 0

Keywords 0x8000000000000000

- TimeCreated

[ SystemTime] 2023-03-08T21:33:29.5808258Z

EventRecordID 13681

Correlation

- Execution

[ ProcessID] 9736
[ ThreadID] 35100

Channel Application

Computer LAPTOP-0B54II2U

- Security

[ UserID] S-1-5-21-91988198-2477983528-856112534-1001


- EventData

Bucket 1312103773709310758
BucketType 5
EventName BEX64
Response Not available
CabId 0
P1 WealthLab8.exe
P2 8.0.32.0
P3 63558578
P4 ntdll.dll
P5 10.0.22621.900
P6 a97a9ed6
P7 000000000008eadf
P8 c0000409
P9 000000000000000a
P10
AttachedFiles \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.80f22f7d-edf3-4f8c-a1d2-e5c9cbe2ba30.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9e2751be-f00f-4746-8d8e-cad4d1b58de4.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4d8381a4-e74b-4393-a3b7-26b8ffc524bc.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.3850408c-1a8b-461d-8002-44bfaead3862.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.2134e1a0-a57f-4016-90f1-c24e6f031a08.tmp.xml
StorePath \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_WealthLab8.exe_54c978f87728b9d647f6e74899f9a43877fbc4a_3e999f31_7386a586-946d-4132-b154-f0ad62391c7f
AnalysisSymbol
Rechecking 0
ReportId a8245f28-31e3-411a-ab09-cdc6fc27297b
ReportStatus 268435456
HashedBucket 6f7029c7344df677d235876e2c649b26
CabGuid 0

Fault bucket 1312103773709310758, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: WealthLab8.exe
P2: 8.0.32.0
P3: 63558578
P4: ntdll.dll
P5: 10.0.22621.900
P6: a97a9ed6
P7: 000000000008eadf
P8: c0000409
P9: 000000000000000a
P10:


0
Glitch8
 ( 12.53% )
- ago
#5
Some research on this 409 indicates it might be related to some system or NET framework corruption:

https://answers.microsoft.com/en-us/outlook_com/forum/all/outlook-2019-random-crash-for-random-users/220322db-e9ea-4aeb-9a96-8b582d53ec55

Does this happen consistent?
0
- ago
#6
No. It is sporadic. Today I have been editing and saving several strategies with no application crashes. Yesterday it crashed three times (prompting my original post). The overnight crashes have occurred ~4 times over the last 3-4 weeks.
0
- ago
#7
After experimenting with a few different instance types on Amazon EC2, I think I have narrowed the cause on this issue to a "Low Virtual Memory" condition in Windows. I have since doubled the amount of physical memory in my local machine to 32Gb and am only using "Large" instance types and above for virtual machines. No crashes in the last month or so. I failed to mention in the earlier posts that I was using a dataset with ~4k symbols, and a daily time series of 25 years. Now, as to how an OS in this day and age can run low on virtual memory with adequate disc space is beyond me. Cheers,
-sifty
1
Best Answer

Reply

Bookmark

Sort