Annoying computer troubles...

[DyslexicHobo]

Ok, so I have this computer:


M7NCD
Socket A Mobile 2500+ Barton
Samsung 40GB HDD
512 Mushkin memory
Generic PSU 480 Watt (keep in mind that I've tested this system with an Antec True 380 with the same problems)
XFX GeForce 6600GT



The problems:
-Windows is freezing during boot. I've reformatted a total of 4 times with the same results each time.

-The CPU speed is detected as 800 MHz, and the motherboard does not have the multiplier unlocked in the BIOS.




I've got no clue what to do to fix either problem.

There was a point with this computer that I got into Windows and updated the BIOS to the latest version, but then Windows froze whenever I opened an Explorer window (stuff like AIM worked fine).

 

[Biggerhammer]

I presume that you've removed and reseated CPU, vidcard and memory.

Freezing on startup can be a heat issue. Mobile makes that less likely, but even so- how's your CPU temp?

 

[DyslexicHobo]

CPU temps are very low.

 

[airfoil]

Looks like your BIOS has kicked in and restricted the CPU until things can be sorted out. I'd say this is probably a power issue.

 

[dhoytw]

Yeah I would think it's a power issue. I have seen this before a few times with the Barton Cores, I don't remember what I did to fix the computer.

 

[airfoil]

Try going to the BIOS and loading the default settings, the first thing to try to get the CPU to be identified correctly.

 

[Fern]

Originally posted by: DyslexicHobo
Ok, so I have this computer:


M7NCD
Socket A Mobile 2500+ Barton
Samsung 40GB HDD
512 Mushkin memory
Generic PSU 480 Watt (keep in mind that I've tested this system with an Antec True 380 with the same problems)
XFX GeForce 6600GT



The problems:
-Windows is freezing during boot. I've reformatted a total of 4 times with the same results each time.

Have you run Memtest86 to check the ram?

-The CPU speed is detected as 800 MHz, and the motherboard does not have the multiplier unlocked in the BIOS.

Weird, I expected you to say 600mhz (FSB 100 x 6 multi). HERE'S a link that you may find helpful. The last post, although drastic, may be whats called for. Although since this is an NF2 mobo I would've expected you to have no problem with changing the multi. Maybe something specific to Biostar?




I've got no clue what to do to fix either problem.

There was a point with this computer that I got into Windows and updated the BIOS to the latest version, but then Windows froze whenever I opened an Explorer window (stuff like AIM worked fine).

Try going to the BIOS and loading the default settings, the first thing to try to get the CPU to be identified correctly.

Since the mobile chip is not intended for use in desktops, very few will recognize it. So you must set it up manually (FSB, multi and vcore). But, there are some mobos which with newer BIOS will recognize the mobiles. DFI does IIRC. Don't know about this Biostar. Just don't be alarmed if it doesn't, its normal.

Fern

 

[DyslexicHobo]

Ok, looks like I'm going to be doing the wire thing with my CPU. Any other thoughts about Windows not working?

I'm going to try installing Win2K, then upgrading to WinXP instead of doing a clean install with XP.

 

[DyslexicHobo]

Oh, by the way, I've tried a stick of RAM that I'm using in my computer now... so that's not the problem.

 

[Fern]

Originally posted by: DyslexicHobo
Oh, by the way, I've tried a stick of RAM that I'm using in my computer now... so that's not the problem.

If I understand, the ram works in your 64bit rig. Still might not be a bad idea to memtest the ram on that Biostar mobo. Sometimes seems mobo are picky about ram. I recommend memtest cuz it just sounds like ram problem to me.

Good Luck with it.

Fern

 

[DyslexicHobo]

Alright thanks, I'll try that.

 

[mechBgon]

"the wire thing?" :Q Try the BIOS menus.

What exact kind of Mushkin memory is that, what speed and model? What bus speed, timings and voltage are you using? If you need a suggestion: 1) lock it to run at the same bus speed as the CPU, async = evil; and 2) bring up the memory voltage to 2.7 volts and see how that does for stability. Undervolted, out-of-sync RAM isn't going to help your stability.

 

[overclock]

Originally posted by: DyslexicHobo
I'm going to try installing Win2K, then upgrading to WinXP instead of doing a clean install with XP.

Definately do not do this. It will not help. The upgrade process is rough from OS to OS.

Does it do this under Win2k?

 

[VirtualLarry]

Originally posted by: mechBgon
"the wire thing?" :Q Try the BIOS menus.

That's the problem. The "M7NCD" model is extremely limited. Not just in terms of not being allowed to select higher "overclocking" settings, but crippled to limit user control over those options at all. Meaning, looks like the wire-mod is likely the only way to fix this. (I tried to set up on of those boards once. The initial installation was a breeze, and I highly recommend those boards as budget NF2 boards, but there were nearly no adjustment options. I had to use NVidia's system utils 1.0 to overclock the system from within Windows'.) I can't help but think that there shouldn't be some 3rd-party hacked bios for those particular boards out there somewhere, that might add back in some of those options, that are present in the "Pro" (overclocking) model, but missing on the non-Pro.

 

[DyslexicHobo]

Ok, I downloaded Memtest and got an IMG file along with a "security catalog", what do I do with that...?