I'm sure my colleagues will look into this for you tomorrow.
I'm sure my colleagues will look into this for you tomorrow.
Mako,
PM me the following information and I shall look into this further for you tomorrow:
Original Invoice Number:
RMA Number(s)
Once I have this I shall see if I can talk to the returns team to see how the goods were tested in a working configuration to see if this resolves any issues.
Regards,
Thanks guys - will do
'Speak softly and carry a big stick'
I had a similar prob to yours on my Asus P5WD2. I tried installing a few times, and everytime it looked fine, went through loading drivers etc, then BSOD. Took me a few attempts to get it resolved, and the solution may sound silly, but it did the trick for me.
The MB didn't like the DVD-RW (installation drive) being on the ITE IDE controller as master. After fiddling with the SATA to ATA mapping in the BIOS, and moving the cable to the other IDE controller, everything installed perfectly.
I know, it sounds like a long shot (and assumes you have another ide controller), but its worth a shot.. what you got to lose..
Thanks for the sugestion
No joy, i'm afraid - tried that as well!
'Speak softly and carry a big stick'
Hi Mako,
Im very sorry to hear of the problem you are still having, The only reason that the goods were returned as No Fault Found was simply because we found them to be without fault in respect to the fault report given - Your Mainboard Cpu and Memory were used along with a SATA Hard drive, optical drive, tagen PSU and a 6600GT, Windows installed perfectly first time we then run various benchmarks and the system was completly stable,
I will however raise a returns number for the entire system we can then test the full system and find the faulty part and get it swapped out ASAP,
Ill email all the details across via OLQ,
Best Regards
Mako,
Please keep in touch with myself as this RMA progresses by PM message, i would personally like to monitor this RMA through to its conclusion to make sure everything is swiftly resolved for you.
Kind Regards
Wesley Aldred
Operations Manager
I have an A8N-SLI (premium) and had a problem with BSOD when installing Windows XP. I found that if I used the most recent SATA drivers it didn't work, because of the BIOS revision, you have to use a > 1006 version for it to work properly with the sata drivers (dunno if they use the same version numbering if it's not a premium board?)
I also had a load of problems trying to use the floppy drive to load the Sata drivers for the Windows Install (the Hit F6 to load Scsi drivers bit) so I created my own windows xp cd using my orignal silver disk and this tool called nLite. ( http://www.nliteos.com ) It's really quite cool, it allows you to integrate service packs / hotfixes etc, but I'd just concentrate on getting the SATA drivers loaded onto the CD, then burn a copy and use it for the install.
Anyway, I think it's to do with this BIOS version thing. Basically go here: http://support.asus.com/download/dow...Language=en-us it's the ASUS download site, go to Motherboads -> S939 -> A8N-SLI and have a look at the BIOS versions, all the newer ones have this warning about:
NVidia NForce Drivers v6.66 ( http://www.nvidia.com/object/nforce_..._amd_6.66.html )To avoid crashing file system, please do update the chipset driver to below version prior to this Bios.
For WinXP 32bit system, please download and update chipset drivers V6.65 or later
Older v6.39 ( http://www.nvidia.com/object/nforce_nf4_winxp_6.39.html
So update ur BIOS or use the older drivers, I know it cured it for me, gl.
Firstly, i would like to make it clear that i am a complete plank....
I have managed to fix it at long last! The problem was that i had both the CD/RW & DEV players on the same IDE...
AAAARRRGGGHH
Hats of to the guys at scan for having the patience to deal with a complete plank!
Also thanks to everyone else for their suggestions - I am off to cry for a bit
Thanks again
'Speak softly and carry a big stick'
No worries
Glad it's all sorted.
I know how frustrating these things can be.
Wesley
Mate you have just made me day with that post good to hear its all sorted! dont cry ^ ^ it happens to every single one of us at times.. IIRC the last system I build i couldnt figure out why the system wouldnt boot small problem of connecting the power button to the board.. it was the most obvious thing ever but i still sat there.. wondering and gettin very angryOriginally Posted by Mako159th
then after figuring it out... cracked up laughin for a good half hour realising what a prat i am
Originally Posted by Noni
You aren't the only person to do this either Kaine
Yea it makes it that bit worse when you figure out you can turn the system on for the power on the board but not the switch and STILL didnt realise it was that connection
Originally Posted by Noni
Lol. Glad you got it sorted though man.i do stuff like that all the time. personal favourite is thinking ive blown my pc up when it screeches every time i have the graphics card out cos i forgot to plug the power back into it.
Hey I had one the other day with my mouse, bought a Logitech G5 Laser mouse, suddenly it stopped working "oh no methinks, 4 days old and already its fubar!" turns out the laser won't read an 'ICEMat' (its black glass). My old MX510 reads it fine (L.E.D) and I never twigged that I'd just started using this new mouse-mat when the G5 stopped working. Doh! did my nut trying to get it to work
Lasers are supposed to track on glass. my mx1000 tracks on a window
There are currently 1 users browsing this thread. (0 members and 1 guests)