| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 129904 | 2013-03-19 08:39:00 | Not too sure what the problem is actually... | skeptile2 (16539) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1333349 | 2013-03-24 23:09:00 | You're not trying to run single and double sided ram together are you? Many systems don't like that and cause all sorts of faults. Also as your OS is only 32bit, any more than 4Gb ram is a waste anyway so don't even bother putting more than 4 in it. Either go for 2x2Gb or 4x1Gb. Also don't try running mixed mode ram ie: 1 stick of DDR 800 and 3 sticks of DDR667 for example. HP mummyboards can be a pain for memory upgrades. | Iantech (16386) | ||
| 1333350 | 2013-03-24 23:28:00 | ??? It doesnt matter where the RAM came from, or what brand the RAM is, or doesnt matter if the RAM worked in another PC. Some motherboards can be a bit fussy about the ram you put in it. Some motherboards dont like certain mixtures of RAM (eg double & single sided). Some dont even like RAM with different speed/timing ratings. Some motherboards will only work with a max of 2G or 4G, stupid yes, but they are out there. Check the Kingston website to see exactly what RAM will work in you MB. As someone else mentioned, sometimes a RAM slot can get a bit dodgy as well. |
1101 (13337) | ||
| 1333351 | 2013-03-25 01:01:00 | And every now and then you find a system with 4 totally mismatched Ram chips working just fine, it's a bit random. The best thing is to use matched sets of RAM from the motherboard manufacturers list of compatible types, failing that you just have to try it and see. Even on my previous gaming machine I bought corsair DDR3-1600 1.5v dual channel RAM that should have worked but didn't and replaced it with gskill ripjaws at the same rating which did. ( might have just been faulty though) |
dugimodo (138) | ||
| 1333352 | 2013-04-07 00:05:00 | ok so for | skeptile2 (16539) | ||
| 1333353 | 2013-04-07 00:28:00 | ok so I finally got round to testing the ram, (many other things were happening so no spare time) and it seems as though I have somehow managed to ruin the 2gb stick aswell. through testing every possible configuration of ram, somewhere along the line the stick died. so now I have no ram. at the start of testing, it worked om every slot without fault. at the end of testing, it works in no slots. | skeptile2 (16539) | ||
| 1333354 | 2013-04-08 09:37:00 | ok so after a lot of experimentation, I have come to the conclusion that it is actually the hard drive, or something on it. I know this because I am able to install vista on a spare hdd, and have no problems running it. I stick in the vista install disk, and go repair, however it can't find any problems on the drive. I am able to get into cmd so if there's any thing I could use that for it would be great. my question is: is there any way to repair this? I would quite like to keep my hdd and not have to do a fresh install but atm it looks likely. |
skeptile2 (16539) | ||
| 1333355 | 2013-04-08 09:40:00 | oh btw, the new problem diagnosis is that on the vista load screen(little green bars going across) it freezes after 2 times going across consistently. | skeptile2 (16539) | ||
| 1333356 | 2013-04-09 01:38:00 | ?? I one post you say the RAM is faulty, then the next post you say the HD is the cause of the issues?? Save yourself alot of grief. Wipe Windows & reload. The really is no generic fix for Corrupt windows, just a matter of elimination & at the end may you have to reload regardless. Download a Hard Drive test tool from WesternDigital or Seagate & run it across the 'suspect' hard drive. DO a FULL hard drive test/scan. It could of course still very easily be a hardware issue giving the issues described in your last post. |
1101 (13337) | ||
| 1 2 | |||||