Build 3.15.2 crash
 
Notifications
Clear all

We had a major storm through here recently and we suffered damage to the house roof and ceilings. I just received the quote to repair. I’m hoping that a small fraction of the 80,000 odd people that download SDIO and/or Desktop Info every month won’t mind chipping in a few dollars to help out. Click on the big blue button at the bottom of the page to help us keep a roof over our heads, literally!

Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.

[Closed] Build 3.15.2 crash

5 Posts
3 Users
0 Reactions
1,368 Views
Nathan_K
(@nathan_k)
Estimable Member Registered
Joined: 5 years ago
Posts: 141
Topic starter  

Got up this morning, woke my computer up and no DTI. Restarted DTI and checked the log and found this.

9/6/2024 09:24:30:709 ERROR           STACK DUMP 
9/6/2024 09:24:30:706 DEBUG         [AddDisplayLines] 
9/6/2024 09:24:30:706 DEBUG         [AddDisplayLines] 
9/6/2024 09:24:30:706 DEBUG         [AddDisplayLines] 
9/6/2024 09:24:30:706 DATA          [ProcessData] physicaldrives Generic MassStorageClass USB Device|Size: 0B   Status: OK|Device ID: \.\PHYSICALDRIVE5|Media: <empty>|Model: Generic MassStorageClass USB Device|Serial: 000000001209
9/6/2024 09:24:30:706 DEBUG         [AddDisplayLines] 
9/6/2024 09:24:30:706 DEBUG         [AddDisplayLines] 
9/6/2024 09:24:30:706 DEBUG         [AddDisplayLines] 
9/6/2024 09:24:30:706 DEBUG         [SetUserVariables] KXG60ZNV512G NVMe TOSHIBA 512GB|Size: 512GB   Status: OK|Device ID: \.\PHYSICALDRIVE0|Media: Fixed hard disk media|Model: KXG60ZNV512G NVMe TOSHIBA 512GB|Serial: 0000_0000_0000_0001_8CE3_8E03_001F_A0D4.|TOSHIBA MQ04ABF100 USB Device|Size: 1TB   Status: OK|Device ID: \.\PHYSICALDRIVE2|Media: External hard disk media|Model: TOSHIBA MQ04ABF100 USB Device|Serial: 201103311016|Generic MassStorageClass USB Device|Size: 128GB   Status: OK|Device ID: \.\PHYSICALDRIVE4|Media: Removable Media|Model: Generic MassStorageClass USB Device|Serial: 000000001209|Generic MassStorageClass USB Device|Size: 0B   Status: OK|Device ID: \.\PHYSICALDRIVE6|Media: <empty>|Model: Generic MassStorageClass USB Device|Serial: 000000001209|WDBRPG0010BNC-WRSN|Size: 1TB   Status: OK|Device ID: \.\PHYSICALDRIVE1|Media: Fixed hard disk media|Model: WDBRPG0010BNC-WRSN|Serial: E823_8FA6_BF53_0001_001B_448B_48A4_671E.|Generic MassStorageClass USB Device|Size: 0B   Status: OK|Device ID: \.\PHYSICALDRIVE3|Media: <empty>|Model: Generic MassStorageClass USB Device|Serial: 000000001209|Generic MassStorageClass USB Device|Size: 0B   Status: OK|Device ID: \.\PHYSICALDRIVE5|Media: <empty>|Model: Generic MassStorageClass USB Device|Serial: 000000001209
9/6/2024 09:24:30:706 DEBUG         [SetAlarms2] physicaldrives 0
9/6/2024 09:24:30:708 ERROR         [SetSharedData] physicaldrives [e:EAccessViolation Access violation at address 00000000004096E6 in module 'DesktopInfo64.exe'. Write of address 0000000005B143D7]

9/6/2024 10:15:02:441 INFO          Desktop Info version 3.15.2.4615
9/6/2024 10:15:02:441 INFO          Windows version 10.0.22631 
9/6/2024 10:15:02:441 INFO          Path: C:\Users\xxxxxxx\AppData\Local\DesktopInfo\

9/7/2024 08:35:55:108 ERROR           STACK DUMP 
9/7/2024 08:35:55:091 UI            [UpdateTextEntries] reg
9/7/2024 08:35:55:091 UI            [UpdateTextEntries] text5
9/7/2024 08:35:55:091 UI            [UpdateTextEntries] physicaldrives
9/7/2024 08:35:55:091 UI            [UpdateTextEntries] nav
9/7/2024 08:35:55:091 DEBUG         [SetNav] 
9/7/2024 08:35:55:091 UI            [UpdateTextEntries] nav
9/7/2024 08:35:55:091 DEBUG         [GarbageCollection] 
9/7/2024 08:35:55:091 UI            [TDesktopInfoMainForm.EndUpdate] 
9/7/2024 08:35:55:091 COLLECTOR     [UpdateEntries] Reset collector (16597627)
9/7/2024 08:35:55:091 ERROR         [Application Exception] Sender: TDesktopInfoMainForm [e:EAccessViolation Access violation at address 00000000005E3B24 in module 'DesktopInfo64.exe'. Read of address 0000000000000008]

   
Glenn
(@glenn)
Member Admin
Joined: 7 years ago
Posts: 1778
 

Thanks for the report. I found the second one this week and is fixed. The first one is new. Do you see that one often?


   
Nathan_K
(@nathan_k)
Estimable Member Registered
Joined: 5 years ago
Posts: 141
Topic starter  

@glenn Just upgraded to 3.15.2 yesterday, so really hard to say.


   
(@korbikorb)
Active Member Registered
Joined: 1 year ago
Posts: 12
 

@glenn Is there a new release planned with this fix ?


   
Glenn
(@glenn)
Member Admin
Joined: 7 years ago
Posts: 1778
 

yes 😀 


   
Glenn's Page