A7V333 Athlon 3000XP upgrade
|
Original Message
|
Name: mikeydude
Date: June 16, 2006 at 03:15:07 Pacific
Subject: A7V333 Athlon 3000XP upgradeOS: Win XPCPU/Ram: Approx 600Model/Manufacturer: ASUS |
Comment: Hello all, looking for ASUS experts. Just trying to upgrade my A7v333 (PCB 2.0!!!) to AThlon XP 2000. ASUS website says that you just need to update the BIOS to 1016 or above for 333FSB. Upgraded the BIOS fine to 1017 but when I put in my new chip (previous 2000XP), nothing comes up on screen. Do I have to set the MB to 333FSB manually? The motherboard only covers manual settings up to 230 I think so I'm a bit stuck here. Anyone know what's going on? Any help appreciated!!
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: jam
Date: June 16, 2006 at 05:04:06 Pacific
Subject: A7V333 Athlon 3000XP upgrade |
Reply: (edit)The correct setting for 333FSB is 166MHz. If your CPU is a 3000+ (not sure cuz you keep calling it XP 2000), the correct settings are 13 x 166MHz @ 1.65v...it runs at 2167MHz.
Report Offensive Follow Up For Removal
|
|
Response Number 2
|
Name: mikeydude
Date: June 16, 2006 at 08:21:14 Pacific
Subject: A7V333 Athlon 3000XP upgrade |
Reply: (edit)yes... sorry about the 2000 thing. Ummm.. is there a possibility that the processor is bust? I mean.. nothing comes up on screen even when i used jumperless setting which i thot would auto detect something righT? surely even if the speed settings were incorrect there would be a BIOS at least!
Report Offensive Follow Up For Removal
|
|
Response Number 3
|
Name: jam
Date: June 16, 2006 at 09:06:06 Pacific
Subject: A7V333 Athlon 3000XP upgrade |
Reply: (edit)Is the CPU brand new or used? If you installed the heatsink improperly (backwards, not properly seated, no thermal paste, etc) & then tried to fire it up, it wouldn't take long for the CPU to fry. If you tried to test fire it without a heatsink installed (someone recently did this), the CPU would fry almost instantly. Try resetting the BIOS (use the ClearCMOS jumper) & try again.
Report Offensive Follow Up For Removal
|
Use following form to reply to current message: