FancyCache for Disk 0.7 error only @ first run

[jotte]

Hi, I have installed FancyCache 0.7 on Windows 7 x64 (fresh install ASP.NET developer machine) Intel Core2 Duo E8400 @ 3GHz, 8Gb RAM.
It looks like it is working fine, but after a reset, after login, the very first launch of FancyCcD will result in an error/crash, so I chose close program and attempting to run it again will work just fine.
Here's the application error log:
Faulting application name: FancyCcD.exe, version: 0.7.0.0, time stamp: 0x4e5b3ed6
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e21213c
Exception code: 0xc0000005
Fault offset: 0x00000000000036a8
Faulting process id: 0x270
Faulting application start time: 0x01cc82b4af215d09
Faulting application path: C:\Program Files\FancyCache For Disk (Beta)\FancyCcD.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: eddb21c9-eea7-11e0-8967-005056c00008

Please let me know if you need more details.

Guess I should add this:

FC settings

FancyCacheD.PNG (47.62 KiB) Viewed 5494 times

[Support]

Hi jotte,

Thank you for the bug report.

It is an application-level bug which may happen in 0.70 version. I think the Disk 1 "R:" is a ramdisk, right? The issue is possibly related to it. Can you tell us what software created this ramdisk?

[jotte]

Hi,

sure, that was created using Dataram Ramdisk.
And as a side note, on another machine (using different hardware but still same Windows 7 x64), using same dataram and similar settings for FancyCcD works without a hitch.
On this machine, it will occur only at first launch attempt after a reboot or a log out for the current user, so basically at first launch, then it will run fine. Also, at that time the ramdisk is already created and running.
Please let me know if you need more info.

Odd, I just did a log out... log back in, and this time no error!!! (yesterday was different)
I will update at next reboot...

UPDATE: after reboot got the same error at first attempt to launch FancyCcD... second attempt will run just fine!

[jotte]

Ok, here's another update: I used to launch FancyCcD pretty fast after booting into windows, but if I wait a little bit and launch it afterwards, no error will be thrown.
So, I guess it is related to one service that is starting delayed in my Win 7...

[Support]

Hi jotte,

The issue may happen while application tries to query disks but encounters some improper data. In previous versions, we did a very strict check on disk query data. However a user reported that he cannot list the disks correctly. So in version 0.70, we loosened restrictions a little, which cause this issue. If you go back to the version 0.62, you'll find that the ramdisk R will not be listed at all.

We'll try to fix this bug soon.