[harry-bee]

I've posted about this problem previously, however it seems nothing i do can solve this problem.

It seems that when I start my laptop, 90% of the time I get a resource conflict error relating to my network devices, both the ethernet and wireless. Once this error occurs, then none of network hardware can start. On the occasion that it does work, my laptop still has a tendancy to bluescreen or crash. I've updated the BIOS, from which I am unable to edit the resource allocation settings, and I can't fix the problem within windows. I have a feeling the hardware itself is damaged.

It would be a shame to have to scrap a £500 machine that Ive had just three years out of. Any ideas?

Acer Aspire 5102 WLMi
Phoenix Bios v 3.13
Windows XP Home Edition (SP2)
AMD Turion 64 TL-50 1.6 GHz Processor
ATI Mobility Radeon X1300
1024 MB DDRII-533MHz SDRAM
Broadcom BCM4381 802.11g -Fails to start
Realteck Gigabit Ethernet LAN -Fails to start

Cheers,

Harry

[-Fabez-]

Have you changed any settings, installed any programs or changed your hardware recently ?

[harry-bee]

Well I did completely wipe the hard drive and did a fresh install of XP. I installed all the correct drivers from the Acer website, which, when the hardware starts, all work fine. I even flashed the BIOS. but the problem started about 6 months ago, but has only recently been causing certain hardware to fail to start.

The laptop has all the original hardware it came with, apart from a new CD Drive which again I only installed a few weeks ago along with another GB of RAM.

Thanks

Harry

[-Fabez-]

If the problem started after adding new hardware, remove the hardware to see if it resolves your problem. Does the hardware manager report any problems ?

[harry-bee]

No, I dont think that any hardware was installed before the problem started. I have just found a way of disabling ACPI, and after reinstalling some drivers, the conflict seems to have stopped.

[-Fabez-]

Glad to hear you got it sorted

[Elvandil]

I was going to suggest that if you only use one of them, try disabling the other, either in BIOS, if that option is there, or in Device Manager. It may well be a hardware problem with just one of the cards themselves and not the whole "system".