Warning this is a mind blower, enter at your own risk!

xSv

Member
Nov 15, 1999
42
0
0
Soooooooo, I am running win2k on a MSI6163pro
and I get the new Celeron2 566 thinking I will give it a try. Well I plug it in and Blank screen. So I take it out and replace it with the original Celeron 300a that was in it but it wont post. Next day I turn it on for fun and it posts no problem everythings back to normal, great.
THe next day I turn it on and it posts up to entering Windows and then goes black. Same result on repeated attempts. It will start up in safe mode but not normal. I then reload Win2k and choose "Repair" but still end up with the same black screen upon entering Windows.

(Here is where it get fun) So I format the hard drive and put Win98 back on and it all works. I then load Win2k and DOES THE EXACT SAME THING! Black screen upon entering Windows2k.

I keep thinking I have seen it all but am constantly amazed at this stuff. Anybody have any ideas at all? Thanks in advance.

 

xSv

Member
Nov 15, 1999
42
0
0
It was but I put it back to the defaults and it still does the same.
Here is what I have tried:

Flashed to latest BIOS.
Removed all other cards besides the graphics card.
Tried a different Monitor.
Reloaded Win2k
Formatted Hard Drive
Fresh load of Win98 and Win2k.

What is strange is that this system has run nearly flawless for several months prior. (With the TNT2 card )

 

xSv

Member
Nov 15, 1999
42
0
0
Ok after replacing the CPU with another 300a and then a C2/566 the only logical thing left to do was change the TNT2 for a Velocity 100 video card and Voila! Problem solved. Go figure, the card works fine everywhere else it just selctively rejected Win2k after several months of operating perfectly normal. NARF!
 

MrCookie

Senior member
Apr 27, 2000
729
0
76
I had a similar problem not too long ago with a mobo and vid card not being happy together. I just had to get a different vid card.
FYI it was a PCI viper 330 (that didn't work)in an older(pre-agp) socket 7 mobo with a P200mmx. I got a Matrox Millenium, and the problem was instantly better :)
 

Genius

Member
Aug 8, 2000
186
0
0
Pull out all unnecessary hardware and replace the memory chips, then try it, etc, etc.