Problem, possibly memory related?
I’ve spent the better part of the day putting together a computer for the g/f and keep coming to a halt, which I’m pretty sure, is due to the same recurring problem.
Everything is pieced together and running, I start to install Windows (Xp, Pro, Home, Hax0red and legit copies), the HDD formats without a problem, then setup starts listing/installing files but gets to a point where it can’t install some of the files (none specific, no recurring pattern). I skip the files and obviously it doesn’t work, instead I get the blue screen and a message saying something like “IRQL input same as output” or something like that, and “Memory Management”.
When I first switched it on there was a bios message saying CMOS Settings Wrong and CMOS Memory Size Wrong, I just pressed F2 and loaded the default values or something :unsure: when I didin't boot from disk there was an ntldr error, but that only happened once :ermm:
Here’s the specs for all this:
Mobo - PcChips M848ALU SKT A SIS 748 400 DDR AGPx8 ATA133
AMD Sempron 2200
2 sticks of Ebuyer 256MB DDR PC2700 333MHz 184pin Extra Value Ram
Western Digital Caviar 80Gb 7200rpm
Hightech ATI Radeon 7000 64MB DDR Memory
Liteon SOHC-5235 52x32x52x16x Internal IDE Combo
Re: Problem, possibly memory related?
I've never gotten that error, so I dunno' what's wrong.
Try setting "PnP OS installed" (or something similar) to "no" or "disabled", and see what happens. If it's already set to that, try turning it on :unsure:
EDit: also, try with just one stick of ram installed and see what happens.
Wild stabs in the dark here :unsure:
Re: Problem, possibly memory related?
i see two options...
No.1 do as snny said...
No.2 Get your gf to do it herself and go down the pub with her money.
Not sure if any of that helps...
Just messin
Re: Problem, possibly memory related?
The only things with "PnP" are DMA and IRQ Channels which can only be changed to ISA/EISA? :unsure:
Doesn't seem to be a "PnP OS installed" option :cry:
edit: tried it with one stick, still no luck :ermm:
Quote:
No.2 Get your gf to do it herself and go down the pub with her money.
Hmmm, interesting :unsure:
Re: Problem, possibly memory related?
Meh, pretty sure it hadn't helped.
All it does is let your bios handle the IRQ assignments on it's own, I think. Which might possibly help with weird hardware conflicts, if you are lucky.
It's also good for linux.
Try with just the one stick of ram since it says something about memory though.
I'll check some stuff and see if I can find anything.
EDit: meanwhile, try putting in as little stuff as you can, ie mobo, cpu, ram and graphics, and see if this does any difference.
Re: Problem, possibly memory related?
Quote:
Originally Posted by SnnY
EDit: meanwhile, try putting in as little stuff as you can, ie mobo, cpu, ram and graphics, and see if this does any difference.
just tried it out, got the same fecking message :frusty:
CMOS Settings Wrong
CMOS Memory Size Wrong
:pinch:
Re: Problem, possibly memory related?
we're guessing it's the ebuyer extra value ram, maybe the wrong sort? :ermm:
Re: Problem, possibly memory related?
Quote:
CMOS Settings Wrong
CMOS Memory Size Wrong
Not to alarm you or anything, but if that error persists like it appears to do, it might be your bios/cmos chip/bios battery that's buggered. I thought it happened just when you started it up the first time.
I just remembered that when the caps blew on my kid brother's mobo we'd get that error or something like it a lot.
Does your bios keep any settings you save? :unsure:
Re: Problem, possibly memory related?
Clear your CMOS.
Unplug the power cord, remove the battery and set the jumper to "clear".
Wait.
Perhaps now would be a good time to hit the pub.
Stumble home.
Replace jumper to running position, insert battery and power up machine.
Enter BIOS and "Load optimised settings".
If it works, you get laid.
If not, return to pub.
Re: Problem, possibly memory related?
now you mention it the very first time i switched it on i got a low battery warning but then it went away :ermm: yeah it's saving stuff though :unsure: