News Forum Phone database

> New Topic
> Reply
< Esato Forum Index > Sony Ericsson / Sony > Software, Firmware and Drivers > MS Duo corruption problem with R1N035 Bookmark topic

Well, I tried once more to transfer a bunch of MP3's. Sure enough, it failed. But I discovered something interesting:

How you disconnect, eject or whatever doesnt matter!

I found the following log entry in the system event log:

Event Type: Warning
Event Source: Disk
Event Category: None
Event ID: 51
Date: 24.10.2005
Time: 01:29:16
User: N/A
Computer: *****
Description:
An error was detected on device DeviceHarddisk2D during a paging operation.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
(snipped)


There were 2 additional event 51's later, but it is the first that messes up the transfer.

All files copied before the event shows up fine in the phone, but the file being copied at the time of the event is gone, just the filename shows up in the phone. When trying to play this file, the next file(s) transfered after this file is played instead for the same duration as the vanished file would have played.

The rest of the files are unaccessible, but I'm sure they're there since parts of hidden files were played.

These id-51 events began to show up right after I upgraded to R1N035.

--
Posted: 2005-10-24 02:18:12
Edit : Quote


http://support.microsoft.com/?id=244780#top
--
Posted: 2005-10-24 02:44:09
Edit : Quote


Do those with problems by any chance run VIA chipsets/usb controllers ? Or are anyone with problems running Intel Chipsets ?

There are known problems between XP SP2 usb drivers and VIA chipsets/usb controllers, which could lead to event ID 51's, and possible transferproblems.



--
Posted: 2005-10-24 02:55:36
Edit : Quote


I'm on VIA and I've got the problem...I'm gonna take a look at the MS link above.
--
Posted: 2005-10-24 07:09:15
Edit : Quote


just formatted by memory stick. is it normal to only have 467mb out of 512mb of available memory after formatting? that sounds like an awful lot of system files. Mine is SanDisk. a check on the memory stick properties says it has 490mb capacity, with 467 available memory. i loaded 233mb of songs, and 234 still available.

[ This Message was edited by: stelvio on 2005-10-24 08:47 ]
--
Posted: 2005-10-24 08:51:07
Edit : Quote


Quote:
On 2005-10-24 02:55:36, numb wrote:
Do those with problems by any chance run VIA chipsets/usb controllers ? Or are anyone with problems running Intel Chipsets ?

There are known problems between XP SP2 usb drivers and VIA chipsets/usb controllers, which could lead to event ID 51's, and possible transferproblems.

numb is correct - VIA's implementation of USB has always given me problems. I'm now using nVidia's nForce 4 chipset and it's 100% fine. I'm still on R1L, and staying thay way until a better firmware is released!
--
Posted: 2005-10-24 10:45:25
Edit : Quote


Quote:
On 2005-10-24 02:55:36, numb wrote:
Do those with problems by any chance run VIA chipsets/usb controllers ? Or are anyone with problems running Intel Chipsets ?


Running updated intel 925X chipset drivers here and still have problems. I will try to use my other PC which currently has no SE software later.

--
Posted: 2005-10-24 14:27:43
Edit : Quote


just out of curiosoty how many of you guys are using PC's that you look after?

defrag, use 3rd party reliable backup/imaging software and keep updated to the very latest, wilst having a failed update?
--
Posted: 2005-10-24 22:21:22
Edit : Quote


Update my anti-spyware, anti-virus and WinXP every month or so. Firmware on most of my PC hardware are current as well along with their drivers. Don't really check these often.

I don't see how these affect a firmware update on a handphone. I say this because I updated to R1N035 without a hitch. Updated to R1NA005 and I was smacked with the corruption bug. Ouch.

Like everyone else here, I will like to know the real cause of this.


--
Posted: 2005-10-24 22:49:29
Edit : Quote


This is certainly one of the strangest most irregular bugs we've seen so far.

Some dont have it at all, others were hit with it on R1N035, and burn-x didnt get it untill R1NA005

And still we havent been able to find a commom denominator.

With that kind of irregularity, its no wonder that S//E technicians have not been able to post a fix yet.


--
Posted: 2005-10-24 23:47:14
Edit : Quote

---

New Topic   Reply

Forum Index