• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

My MSI nForce board stopped booting

G

grabadude

Golden Member
System was working fine, except when it got stuck at black screen at times when booting (the problem was usually fixed by rebooting, but it was getting worse and worse). One day i turned on the computer, the system would boot but get stuck when scanning for ide drives, completely failing to detect anything. Rebooting, removing pci cards, removing ide drives did not help. I RMA'ed the board back to Newegg.com and currently deciding if i should get an Asus nForce board. My question is: Should i try another MSI nForce board or get Asus board? Does any1 have any ideas on what went wrong with the board?


Win XP
AMD XP 1.47 proc
300watt Antec PS
256 DDR RAM
WD 30 GIG ATA 100 HD
Maxtor 20 GIG ATA 66 HD
 
I would Try the MSI I have 3 (2/266A and 815)the boards are very good ,you just got a bad one,did you send this board back yet,if not I would try clearing the CMOS it sounds like a bad BIOS setting🙂
 
if you have resetted the CMOS that could have been the error. On early deliverys there has been a wrong jumper setting description in the Handbook Rev. 1.0 & 1.1 which where prited up to Nov.01.

On the MSI homepage you'll find the right handbook (Ver 1.1 Dec.2001)

They have simply changed jumper settings for resetting the BIOS/CMOS. So if you have followed the handbook this could have happened.

I for myself never ever ! had a problem with my MSI K7N420 Pro (MS-6373 v1.0), so you might just have had that portion of luck 😉 to get a damaged one.

There is a thread comparing the MSI Nforce board to the ASUS board, just click

Here ( I know crosslinx suck😉 )

Regards

Funky
 


<< if you have resetted the CMOS that could have been the error. On early deliverys there has been a wrong jumper setting description in the Handbook Rev. 1.0 & 1.1 which where prited up to Nov.01. >>



I knew about the wrong cmos jumper description in the manual, i left the jumper as it was (bottom two pins).

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top