Anybody else had this happen?

keogh

keogh

keogh

Soldato
Joined
22 Jun 2004
Posts
2,756
Location
Bangkok, Thailand (formally London)
Howdy,

I managed to get my C2D to 3.4ghz yesterday, and I ran orthos for 19hrs without any problems. This to me would have suggested that it was stable.

Anyway I was playing STALKER earlier, and bout 15mins in my PC rebooted... I thought strange, maybe it was a random thing. So I booted it back up, I played it for about 30-40mins this time and it crashed, then done the same and rebooted my PC.

Just before it rebooted I saw on of those Windows Blue Screens too... from what I could see the same blue screen I was getting on my first install of XP on this new PC the other day. I described that problem in this thread: http://forums.overclockers.co.uk/showthread.php?t=17714839 please read that if you can, cos it could detail the problem more?

Anyway, I just wanted to know if anyone else had ran orthos for many hours without fail, and then get probs playing games?

If I never got the problem I described on the thread I have linked to above, I would just simply think that the clock was unstable and think nothing of it and lower my overclock... but because I had that problem I am wondering if I have issues with my RAM? I am running memtest86 atm and will run it all night to see what it says.

For now though I have put my RAM to its default or 4-4-4-12 800mhz and I have knicked my E6600 back to 3.0ghz which I can live with.

I have been playing STALKER/HL2 Ep1 and Oblivion for a bit since I put my clock back and havent had a problem... but I dont think I have played them long enough to know. I need to play STALKER for at least an hour to be a bit more sue, but I am getting my arse whooped in it at the moment so dont want to play it :)

Incase needed, my spec is:

ASUS P5N-E SLi
C2D E6600 :: 3.4ghz
GeIL 2GB PC6400C4 DDR2 800mhz :: 4-4-4-12 800mhz
Corsair HX 620W PSU
2xSeagate Barracuda7200.10 250GB SATA-II 16mb Cache
BFG 8800GTX OC 768mb

Anyone have any ideas? Or had this problem before?

Also, if I run memtest all night and it says no fails, would that pretty much mean that I DO NOT have a problem (hardware wise) with my RAM? Or could it still mean I have probs with it?
 
Last edited:
run the memtest without overclock-everithing at default- (7/8 hours) and ran it again with the overclock you had before-3400 mhz

ram timmings at 400mhz (DDR800) 12-4-4-4 at 2.1V

these BSOD seems memory related problems,me thinks :)
 
netby said:
run the memtest without overclock-everithing at default- (7/8 hours) and ran it again with the overclock you had before-3400 mhz

ram timmings at 400mhz (DDR800) 12-4-4-4 at 2.1V

these BSOD seems memory related problems,me thinks :)
Click to expand...

When I got the BSOD on the first day when installing XP detailed in that other thread, I hadn't changed any settings at that point... It was at auto everything. I then changed the settings to 4-4-4-12 2.1v and I was still getting that error. Thats when I removed 1 of the sticks and booted and it worked? Put it back and it worked still and XP boots without a problem since!

Ill put my setting back to the "faulty" 3.4ghz clock and try memtest again.

ta
 
Just so I know though, if running memtest all night on both overclock 3.4ghz settings and default/stock, if memtest doesn't find any problems would that mean my RAM is fine?

I've already run long self test on my two Seagate HDDs and they passed. Im also 99% sure its not them, as when I was having this problem I installed windows on both HDDs and the error occured on both, so the chances of both HDDs being screwed are very slim!

Just the fact that removing the RAM when I was gettin gthis problem allowed me to boot leads me to believe its the RAM... either that or the mobo?

I'll see what memtest does? Just wanna know that if memtest finds nothing, shall I rule the RAM out? I'm gonna give STALKER a good going over tomorrow evening, so if it dont crash then chances are it was the clock and all will be well!
 
yes run the memtes86 , for a few hours first ( sistem overclocked and non overclocked)
if no errors are found ,you could rule out of equation your mems

and if with everithing at default( board timmings,cpu at default ,ram at default,etc) you could play the game without lock-ups or reboots then ,most for sure, your cpu does not like to run overclocked at all :)
 
Well I have just found out on the official P5N-E SLi board thread in the mobo board, that some people where having problems with using the yellow slots for their dimms. Slot A1 and B1 are yellow, and A2 and B2 are black.

I've put my DIMMS in the black slts now as that may have been the problem? Thinking about it now, trying to get to 3.5ghz overclock was VERY hard, yet orthos thrw random errors also... so it may have been the memory screwing it up.

So I have put my PC back to the 3.4ghz overclock and the sticks in the black slots, Im gonna run memtest all night now and see what happens. If its all good tomorrow morn, ill give STALKER a good going over for at least 1 hr tomo evening and Ill see if I get any locks.

Thanks for ya help so far!
 
Ran memtest on the oveclocked "crashable" settings for 9hrs 20mins and it passed 14 times and failed 0... rule out faulty memory you reckon?

As I say, I'm gonna give stalker a go for at least an hour later, see what happens then! If it crashes, Ill go back to 3ghz and play it then!
 
Have you had the blue screen when playing a game other than Stalker?

Reason I ask is that Stalker gave me my first blue screen under Vista and I guarantee it was due to the one of the games assortment of bugs. Everything else I play is problem free.
 
Oh no I'm 99% sure its not the game, as I had been playing stalker on my previous rig for hours on end on XP (the same as what I am running now) and it never gave me any problems.

I would have thought that would have been the problem too... but as it played so well on my last rig I have ruled that out!

I feel like playing oblivion actually, so I might play that instead as I know thats is a game that can cause overclocks to die!
 
Im going back to 3ghz now, just in windows and my PC just decided to reboot... and I wasnt even doing anything :)
 
keogh said:
Oh no I'm 99% sure its not the game, as I had been playing stalker on my previous rig for hours on end on XP (the same as what I am running now) and it never gave me any problems.

I would have thought that would have been the problem too... but as it played so well on my last rig I have ruled that out!

I feel like playing oblivion actually, so I might play that instead as I know thats is a game that can cause overclocks to die!
Click to expand...

Until you get the blue screen in another game I'm convinced the problem is Stalker.

The fact that your stable in all your tests and the issue only crops up in one game that's well known as being bug ridden sugests to me that your chasing a phantom hardware issue.
 
Yeah well not anymore though, as I said above, windows just rebooted for no reason so that was definitely not stalker. Im gonna see how it goes at 3ghz now.
 
Tell a lie I have put it back to 3.4ghz, and uped the vcore a notch... im doing my everyday thing whilst running orthos in the background.

I understand where your coming from about STALKER though, as it is strange that orthos ran on priority 9 for 19hrs without fail, and stalker keeps killing it. But the earlier reboot whilst doing NOTHING in windows was a problem, that did not involve STALKER.

I'll give Oblivion a go later for a while and Ill see if I get reboots in that? If not, I'll try STALKER again... but I never had one lockup on STALKER on my last PC???

Although, I did read somewhere that STALKER had problems with the 8800GTX's... is this true? Could be that? Cos I was on a 7800GTX last time?
 
I know its a silly question as orthos should stress ram/cpu but are you having a heat problem? Probably with the gfx card as this is not stressed when running memtest or orthos! The 8800's are known to be hot little buggers and 'venting' improvements like an extraction fan under the card or blocking those venting holes that allow the hot air out of the card inside the case!

Just a thought.
 
Phunky Phish said:
I know its a silly question as orthos should stress ram/cpu but are you having a heat problem? Probably with the gfx card as this is not stressed when running memtest or orthos! The 8800's are known to be hot little buggers and 'venting' improvements like an extraction fan under the card or blocking those venting holes that allow the hot air out of the card inside the case!

Just a thought.
Click to expand...

Must admit that did cross my mind... but the temps of my 8800 seem to stay quite stable, and until the random windows desktop crash i recently had, there would have been some truth to that, but I really dont think its that

Ive ran 3dmark06 bout 15 times non stop too and it was fine? Its annoying!
 
You must log in or register to reply here.
Back
Top Bottom