• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Major Problem With Biostar 210p

nullzero

Gawd
Joined
Oct 20, 2004
Messages
786
I recently purchased a biostar 210p its a sff with a socket 754 and nforce 3 250gb motherboard. Now my problem is with the motherboard detecting over 256mb of ram. I had the orginal bios and it detected 512mb of my kinston ram fine but when i updated it to the newer bios i lost the ability to go over 256mb i tried everything flashing the bios with the orginal version, reseting the cmos, changing ram slots, nothing seems to work with detecting over 256mb of ram. Im about to rma it but before i do I wanted to know if anyone had a suggestion of what it could be or how to fix it. Im starting to think its the motherboard which is bad. Any help would be appericated. :confused:
 
What are you using to check the ram?

I would try using Everest Home Edition or CPU-Z and see if it detects the correct amount of ram.
 
I used cpu z and check using the bios both said 256mb. I even tried two sticks of 256mb ddr in both slots one in each and then one only in at a time on each slot. it detected 256mb but would not go over with both working sticks of ram. Tried the same with my 512mb module which also only detected at 256mb i tried it in another computer and there was no problem.
 
You said you've tried degrading the bios? Check all ram again (never too many times to check RAM) with MicroScope (my personal favorite program)
 
head over to sudhian forums and search for the 210p. your problem isnt an isolated incident and it seems the people over there have the BIOS update needed to solve your problem.
 
Back
Top