Im getting blue screens when i try to load my OS from the cd. I cant install windows xp pr or window 2000 pro. All i get are blues screens during the setup.
For 2000 i get all the way to the first boot to where it finishes its set up, then it crashes
I do not have a USB hub connected to my computer. My ram is set to autoclock, the processor runs 266, so ill set it there and see what happens. Ill underclock it too. Thanks and ill get back to you on this.
"If youre paddling upstream in a canoe and a
wheel falls off, how many pancakes fit in a doghouse? None! Icecream doesn't have bones!!!"
Ok. I underclocked my ram. I reased the CAS latency. I even under clocked the processor and buss. I either got a restart when it trys to boot windows for the setup, it asks for the CD in the middle inepecting the hardware before setup, or is just does the same crap again with the blue screen.
Is this bad ramchips? Sucky VIA chipset? Im realy gettting ticked off at this thing.
Any ideas?
"If youre paddling upstream in a canoe and a
wheel falls off, how many pancakes fit in a doghouse? None! Icecream doesn't have bones!!!"
definitely some hardware problem. What about trying one stick of RAM at a time, to see if one has a problem? Maybe there's a problem with the IDE bus/cable too.
ive tryed both chips at once, same ordeal. i toggled my ide cables.. same thing..
"If youre paddling upstream in a canoe and a
wheel falls off, how many pancakes fit in a doghouse? None! Icecream doesn't have bones!!!"
<P ID="edit"><FONT SIZE=-1><EM>Edited by clob on 03/23/04 06:11 PM.</EM></FONT></P>
Well, I heard VIA word somewhere in there, do you do, or do you not do have a K6 processir? If you do do, then you are in the no go to the nowhere at all.
PS: next time (or even this one) sistema spex would be more helpfull to us (and so to you).
..this is very useful and helpful place for information...
my bad, anyway, it is not a PS, he has mem problem with HD or Memory itself. Installation cant read/write into something. Hey, have you used different CD for install, I mean Win2k, ME, 98x, Lin/ux, whateva? If any of those can be installed, CD is the issue here, don't bother us with stuff that can be troubleshooted easy on the spot ;>
..this is very useful and helpful place for information...
I've seen that same thing happen three times now, One time it was a memory error with the memory they were using, another time they said it was a mobo(not confirmed), and the last time i saw it happening to a new system the CPU was effed up.
This was with a 2400xp. The last time.
The only one I can understand is the memory, i have no clue of how the other two factored into anything. Since you aren't getting beeps, then i'd suggest swapping memory first. If at all possible swap out cpu for [-peep-]'s and giggles.
If it was a hard drive, the only thing i could say is try and do a format again, if that doesn't work possibly a bad low level format? Maybe it's trying to write info to a couple of bad sectors...
Those were all brand new OS install's with XP. All three of the people tried multiple OS disks of XP, and 98.
<A HREF="http://arc.aquamark3.com/arc/arc_view.php?run=277124623" target="_new">http://arc.aquamark3.com/arc/arc_view.php?run=277124623</A>
46,510 , movin on up. 48k new goal. Maybe not..
Interesting.. im just going by some new ram. The HD is fine and if the new ram wont work ill just buy a new board.
It says in the manuel for the mobo that a processor with 333 bus wont work on 400mhz ram chips, but 266 will. It says i have to have 333 for the processor to work at 333, and nothing else. I think this is garbage. The 400 should automaticaly clock down to 333. Am i right on this?
"If youre paddling upstream in a canoe and a
wheel falls off, how many pancakes fit in a doghouse? None! Icecream doesn't have bones!!!"
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.