Notes |
|
(0002955)
|
u294
|
2008-09-21 02:24
|
|
This is probably bug in Windows Vista ;). Crashing into blue screen on file access is surely OS fault. Regardless of anything else. System should be robust when dealing with file systems since file systems MAY get corrupted anyhow sometimes. If system crashes on file access, there is bug in system. I bet aMule team can't do anything with errors which happen in Windows Vista. You should ask Microsoft instead.
Hint: you may also want to check your disk for errors. |
|
|
(0002965)
|
yelo3
|
2008-09-24 01:13
|
|
well... this would be correct if amule wasn't the cause of the crash...
or maybe this is a ntfs-3g bug... |
|
|
(0002966)
|
yelo3
|
2008-09-24 01:14
|
|
ok, I will address it to ntfs-3g, maybe is their fault |
|
|
(0002967)
|
u294
|
2008-09-24 13:49
|
|
Surely Windows bug can be triggered by someone else error (like ntfs-3g or just by occasional filesystem corruption). But BSDO due to (possibly incorrect) filesystem data is surely Windows fault.
Generally, in such scenario OS should just return "read error" status of operation to application or something like this. Crashing to BSOD is a bug.
So, really you probably should file bug to "Windows Vista" OS selecting component "NTFS driver" with description "NTFS driver could crash in specific scenario" but unfortunately it does not looks like MS provides bug tracker. |
|