well like i said i'll just drop it off at the place and if the bill's too high i may be biting the bullet and building myself a new one
i've had this one for about 3.5 years now anyway
i've had this one for about 3.5 years now anyway
Just thinking back to last year at College where we had to create an OS fault to fix, and I ended up purposely corrupting my hal.dll file so Windows wouldn't boot and then replacing it with the one on the Windows disc. Sorted the problem, so naturally, I've related the two, but I'm not exactly certain on whether it'd sort the problem, was just a suggestion.burnzz wrote:
technically you can't - you could replace the file "hal.dll" which is a dynamic link library, the hardware abstraction layer itself is created each time you boot. it's part of the process. that's why it's important to have the correct drivers for your hardware.FFLink wrote:
You can replace the hal.dll file with one that's on your Windows disc, see if it sorts it.
Or any Linux live CD.Flaming_Maniac wrote:
or a bootable cd/usb stick
Last edited by tazz. (2010-03-23 18:08:49)
Leave it turned off, its not necessary for machines nowadays, because devices operate through drivers, not the BIOS.Bevo wrote:
KB arrived. Looks like memtest needs to be written to a CD as I have no floppy drive and USB boot only works on linux?
also I was sifting through the options on my MB setup and I see "System BIOS cacheable" set to disabled. The description says "enable this item to allow the system to cache this RAM to increases performance" (lol grammar error). Should I turn this on? What does it do?
the memtest site says the USB bootable is installable on linux onlymenzo wrote:
when in BIOS turn USB devices on, so you can use your normal KB. make a boot able usb with memtest86. so waste of cds
i lost you after linuxFinray wrote:
You could download a Linux distro, run a VM machine and use Memtest that comes with that?
Last edited by Bevo (2010-04-03 15:50:16)
Motherboards die in mysterious ways. Alright, take one stick, check each slot. If nothing comes up, which it probably will come to think of it, then you try each stick in each slot.Bevo wrote:
Wouldn't checking each stick in each slot be redundant? Like if I check them all in slot 1 and they all pass a-ok and one of them fails in another slot it has to be the slots fault?
Ed: That's also... 24 different combos assuming you have each slot filled at all times (ignoring the 5th and 6th slot)
well putting a single stick in slot 2 gives me no output at all, so I don't think it's quite that simple. Putting a stick in 1+3 and 1+2 also lead to failures, sooo if all the sticks check out individually the mobo is toast, yes?Finray wrote:
Motherboards die in mysterious ways. Alright, take one stick, check each slot. If nothing comes up, which it probably will come to think of it, then you try each stick in each slot.Bevo wrote:
Wouldn't checking each stick in each slot be redundant? Like if I check them all in slot 1 and they all pass a-ok and one of them fails in another slot it has to be the slots fault?
Ed: That's also... 24 different combos assuming you have each slot filled at all times (ignoring the 5th and 6th slot)
Last edited by Bevo (2010-04-03 22:31:17)