Vista keeps on crashing...

Shame dude, I seriously cannot believe you're still having problems with this rig. I'm so surprised you've not given up yet.
Keep us posted! :)
 
I would have given up Rob, but I can't afford to.

ByteJuggler, I won't be able to get onto MSN tonight due to too much coursework, I shouldn't really be posting this.

But the RAM Guy on the Corsair forums suggest upping the ram volts to 2.1v, so I did, and now I can't get an install at all. I tryed twice I got the following errors, on each go respectively...

SS851380.jpg


SS851391.jpg


I tryed a 3rd time and I got a BSOD
 
Last edited:
Try installing windows with just 1 stick in, not 2 and keep the 2nd stick out for awhile. If windows fails to install again swap the sticks just keep 1 stick in (1gb ram) in at all times. Wana see what happens.

As usual do a full format not quick format when retrying install of os. Also up the cpu volts by 0.025 perhasp just as a test.

Btw u said xxxx replaced ** hdd as they found it faulty. Can u do some scans to see if theres any problems with the sectors on ** new hdd. Just to rule out another dodgy hdd.
 
SkeeterPSA said:
Try installing windows with just 1 stick in, not 2 and keep the 2nd stick out for awhile. If windows fails to install again swap the sticks just keep 1 stick in (1gb ram) in at all times. Wana see what happens.

As usual do a full format not quick format when retrying install of os. Also up the cpu volts by 0.025 perhasp just as a test.

Btw u said xxxx replaced ** hdd as they found it faulty. Can u do some scans to see if theres any problems with the sectors on ** new hdd. Just to rule out another dodgy hdd.
Click to expand...

yep I'll try the hard drive test again.

the bios only allows a pd increase of 0.1v, unless there's another way of doing it that allows a smaller increase.

anyway I managed to get an install of windows first time with the ram at 2.0v, but I havn't got around to installing drivers yet.

I may try installing vista again first with only one ram stick etc...

hopefully if bytejuggler comes we'll be able to diagnose a problem.

cheers
 
I ran the HDD and it passed

but I tryed doing what you said on msn skeeter, that is running memtest with individual sticks etc...

and I can't get the PC to boot anything now. not even with two sticks, it won't boot any CD's and it won't boot aff the Hard Drive.

It bleeps when i first turn the PC on which in never used to, and then it get's to the screen just after the bios, and it bleeps again and restarts.
 
You altered some stuff in bios for mem maybe thats it, try clearing cmos. Also the beep sequence is important it has diff beeps to diagnose diff probs so try to be as accurate in description as possible with timing and amount of beeps etc.

I feel bad now if u cant get it to even post to bios. :( sry.

Im on msn if u wana talk more.
 
no need to feel bad, not your fault.

I havn't changed any of the bios settings, there all what they were, ive tryed both sticks on all the slots, get the same prob.

And the bleep sequence is just one bleep just before the bios screen comes up. and that's all it is, just one short bleep.

I'm just leaving to go to my mates house now to test my memory on his machine, I won't be able to test the gpu, as he only has a 300w psu.
 
Just got back from my mates, and testing my ram in his system.

It worked fine, played css fine, then I installed MTW2 on it fine, no errors, played fine.

so it seems unlikely to be the ram, and it was only running at 1.8v aswell on my mates system.
 
hmm it might have been fine but he didnt just install a os with that ram did he and faulty ram and installin a os is a no no i would have thought.if u could test ** ram in his comp why cant u test his ram in ** comp? And maybe other things?
 
he won't let me, because then he'd be without a computer, he only has 512mb aswell, vista's minimum requirements are 1GB I think. (i could be wrong on that)

well if anything it deifinatly rules out the possibility of it being a scratched mtw2 disk, i'm gonna buy crysis this week, see how that goes, as i was going to get crysis anyway.
 
Last edited:
Dont waste ** money yet cos you cant play it really can you till ** comps sorted. And 512mb vista will work fine just be a tad slower than usual.

Can you swap optical drives and cables to see if one of these is the prob, i think i heard u say u tested two liteons, well lets see whatever ** mate has works. I mean u could take ** drive and put in mates and install mtw again and see what happens etc. and test his in urs with vista and mtw one night.
 
Guys, I gather that some (all?) of the P35C DS3R boards overvolt the RAM, so if it's set to e.g. 1.8V in the BIOS it will actually supply e.g 2.0V or whatever. This is second hand information that I've not been able to verify but, that's what is alledgedly the case. Now, this would fit in with yantorsen's experience so far - his RAM working at its proper voltage (in his mates rig) but not liking to be overvolted (accidentally, in his own rig), some/many RAM sticks are as bad when overvolted as when undervolted. I have a feeling if he tries some RAM that can take e.g. 2.0-2.2V, it'll probably work fine at stock settings in his board (with the slight overvolt from stock 1.8V or whatever.) That said, this is all theory. If I go and see this problem rig next Saturday I'll test this theory by trying some more voltage lenient RAM. We shall see...
 
bytejuggler, should i perhaps try undervolting the ram then?

and skeet, I've did what you suggested last night on msn (reseting cmos, using fdisk to delete partition etc..), but the problem still prevails, exact same problem.

one thing I've found out though, apparently, im not sure but, the sata ports have sperate jmmicron drivers to the intel chipset drivers which need to be installed, is this true?

there is a new BIOS out now, would it be worth trying that?

and bytejuggler are you on msn? we could do with aranging a time and stuff for saturday.


thanks guys :)
 
yantorsen said:
bytejuggler, should i perhaps try undervolting the ram then?
Click to expand...

Certainly worth a try. MSN (Live Messenger) is giving me a hard time at the moment (with typical useless error codes.) I'm installing an alternate messenger as we speak - I'll be online a bit more now so catch me when you see me.
 
Install the j drivers if u think it will help, cant hurt anymore than it is already anyhow. Bios update i duno.

You could try undervolting ram but doubt it will do owt, maybe 1.7v?
 
I had that 'corrupted windows files' screen at first when I was clocking my setup. But it was only when the mobo was automatically pushing the RAM way faster than it should have been goin, it seemed to go back to normal when I set everything back to stock (that is until I found out the annoying memory multiplier thing, and when i set that properly it worked fine). Mind you i was running windows xp... so i guess it could be different.

And as for what bytejuggler was saying... that's worrying lol. Because I've got mine set at +0.1v and if this mobo gives the ram too much voltage to begin with, i might be givin my memory more than enough voltage :/
 
memory divider is at 4:5 closerratio, and the J drivers didnt help.

anyways, I guess theres not much other advise or anything you can offer really, seem to have gone thorugh all the possibilities. but hopefully saturday with bytejuggler, we'll get to the bottom of this :)
 
He has fixed his probs with thanks to bytejuggler, it was the ram, it didnt like the volts the board was giving. Bytes ram could take higher volts and his loaned him his ram till he gets it sorted which was nice of him and Yantos comps workin well now.

FINALLY is all i can say lol. :p
 
You must log in or register to reply here.
Back
Top Bottom