pc keeps crashing motherboard i think please help

Associate
Joined
25 Jul 2009
Posts
9
pc keeps crashing when using convert x or nero7 (just copying disc) been inside tower when i wobble the ram on slots 1 and 3 it crashes all the time i have 4 slots all ram passes mem test so is this my motherboard spec below any advice would be greatly received thanks.


motherborad: dti lan party jr p45 t2rs lga775 ddr2
cpu: q6600 quad core 2.4ghz overclocked to 3.4ghz
ram: ddr2 800mghz 4x1gb
heatsink: Thermalright 120 with noctua fan
hard drives: 2x500gb
optical drives: samsung dvd speed plus super ritemaster and hitachi dvd multi recorder
pcu: galaxy enermax ega1000ewl quad pci express extreme
graphics card: ati radeon hd 4600 gddr512
running windows 7 32bit

standing temperture 44c on all cores
voltage: 1.264
passes intel burn test v2.2 but not 1.9 under stress level 1? not sure if compatible with windows 7
all running on sata
mini port lan
running in mini atx case any help would be great.
 
I'm not surprised it crashes if you are wobbling the ram sticks while it's on lol :D

But seriously, if it's just nero thats not working then it's probably just a fault with the software and nothing to do with your machine.

You need to explain what you mean by crash as in what you actually see and what kinda error pops up, IE does it blue screen ? Does your PC reboot ect.. Did you overclock it using unstable settings ?
 
I'm not surprised it crashes if you are wobbling the ram sticks while it's on lol :D

But seriously, if it's just nero thats not working then it's probably just a fault with the software and nothing to do with your machine.

You need to explain what you mean by crash as in what you actually see and what kinda error pops up, IE does it blue scree scree screen ? Does your PC reboot ect.. Did you overclock it using unstable settings ?
Thanks
for fast reply. Yeah its a stable overclock passes intel burn test stress level 1 5 passes. When it crashes it freezes and there is a rainbow effect on screen then pc reboots but no screen no beep so restart it and it comes up with boot messenger missing press ctrl alt del and get stuck on this so have to repair windows. Or get A disc missing and have to do the same. But it only does this with nero 7 or convert x. So looked to see if there was a cable loose and you only have to knock the ram and the same happens or get blue screen and it counts this memory thing and does the same. Not sure why it will not pass on intel burn test v1.9 anymore but will on v2.2 is this windows 7? Have tried new ram just does the same but nero and convert x did work before but its all the time on both. Thanks again. Just to add have tried running at stock speed 2.4ghz with same out come thanks.
 
Last edited:
:eek: Why would you wobble the RAM? :eek:

If the retatining clips are in place the RAM wont be moving.
Thanks
for reply the ram is clipped in right you just knock it on top or slightly push it left or right and it crashes but only on slots 1 and 3 running it on sticks 2 and 4 and no problems. Have tried new ram same outcome? Thanks again.
 
Not very convinced this is real. no one I've ever met thinks pushing the ram about while the machine is on is a sensible idea, and your definition of stability looks carefully chosen to provoke.

You don't know if the overclock is stable. You're pulling the ram about with the machine on. Software is crashing. I reckon this is user error.

Run memtest at stock cpu clock to try to judge if you've damaged the ram. If it passes, reinstall windows. Then put the overclock back on and stability test it (5 runs is not sufficient, the program itself tells you this). If you pass this and nero is the only thing that crashes, stop using nero.

I think you've damaged the ram slots on the motherboard. If you rma it having treated it like this I hope they laugh in your face.
 
Hehe, you missed your vocation in diplomacy Jon ;)

As candid as JonJ’s reply was he’s right. I’m afraid, by no stretch of the imagination, can you pass your clock as stable. You need to do at least double that amount of passes, coupled with a minimum of 8rs – 12hrs prime, a few hrs of ORTHOS (small and large FFTs) or OCCT and a few passes of memtest. All combined with general use and abuse in which it should remain 100% solid to be classed as stable. (And my methods are very conservative to some).

Basically, you need to assure yourself that your system is as stable as it can be - and sustained stress testing of different apps is a crucial part of this process. For example if you planned to do an 12hr blend test of prime and it failed on the fifty-ninth minute of the twelfth hour it would still indicate that the system was unstable.

There are very few occasions for justifying 'physically' poking around the insides of the case when the system is powered without the risk of causing damage – and nearly all of them involve a voltmeter or similar...

With the above in mind, I would follow Jonj’s advice (perhaps overlooking his more succinct summarizations as he’s a pussy cat really) – reset the CMOS and load optimised defaults ‘or similar’ and then run memtest from a bootable ISO.

If the system passes memest, reinstall windows. Stress test at stock (refer to above recommendations) just to make sure that you haven’t induced some quirky fault with your penchant for wiggling components fully juiced and, if it passes, then install NERO and test to see if the app will run without crashing (obvioulsy making sure windows and said app are all patched and upto date).

If it achieves this milestone, you can then begin to integrate the clock, gradually, but making sure that you stress test comprehensively as you go. These things take time and patience but it’s ultimately worth it as you will be rewarded with a system that doesn’t flag up immediate doubts or awkward threads about the credibility of your clock whenever you experience a minor problem.

Good luck.
 
Last edited:
That's weird. I've wobbled memory before and its not crashed the pc...

Actually speaking truthfully there. I didn't do it to an overclocked pc, or even to my own pc.... It was at work. Luckily the PC was already broken before that.. random bsod's from hardware faults. But the wobbling of the RAM didn't actually make a difference.


Moral of this Thread: Turn your PC Off before wobbling memories.
 
Hehe, you missed your vocation in diplomacy Jon ;)

As candid as JonJ’s reply was he’s right. I’m afraid, by no stretch of the imagination, can you pass your clock as stable. You need to do at least double that amount of passes, coupled with a minimum of 8rs – 12hrs prime, a few hrs of ORTHOS (small and large FFTs) or OCCT and a few passes of memtest. All combined with general use and abuse in which it should remain 100% solid to be classed as stable. (And my methods are very conservative to some).

Basically, you need to assure yourself that your system is as stable as it can be - and sustained stress testing of different apps is a crucial part of this process. For example if you planned to do an 12hr blend test of prime and it failed on the fifty-ninth minute of the twelfth hour it would still indicate that the system was unstable.

There are very few occasions for justifying 'physically' poking around the insides of the case when the system is powered without the risk of causing damage – and nearly all of them involve a voltmeter or similar...

With the above in mind, I would follow Jonj’s advice (perhaps overlooking his more succinct summarizations as he’s a pussy cat really) – reset the CMOS and load optimised defaults ‘or similar’ and then run memtest from a bootable ISO.

If the system passes memest, reinstall windows. Stress test at stock (refer to above recommendations) just to make sure that you haven’t induced some quirky fault with your penchant for wiggling components fully juiced and, if it passes, then install NERO and test to see if the app will run without crashing (obvioulsy making sure windows and said app are all patched and upto date).

If it achieves this milestone, you can then begin to integrate the clock, gradually, but making sure that you stress test comprehensively as you go. These things take time and patience but it’s ultimately worth it as you will be rewarded with a system that doesn’t flag up immediate doubts or awkward threads about the credibility of your clock whenever you experience a minor problem.

Good luck.

thanks for your FRIENDLY advice pc was built for me by somebody who knows a lot about pc i.e his is running on water cooling and over clocking but i always bother him with problems. But since it crashe once it seems to be getting more frequent. the overclock is stable can pass 20 passes on intel burn test and all ram can pass mem test but i am a novice (stupid one at that) that will play inside when turned on we all have to start somewhere thank you again for your advice will do as you said cheers.
 
That's weird. I've wobbled memory before and its not crashed the pc...

Actually speaking truthfully there. I didn't do it to an overclocked pc, or even to my own pc.... It was at work. Luckily the PC was already broken before that.. random bsod's from hardware faults. But the wobbling of the RAM didn't actually make a difference.


Moral of this Thread: Turn your PC Off before wobbling memories.

thanks for your comment lesson learned cheers.
 
Not very convinced this is real. no one I've ever met thinks pushing the ram about while the machine is on is a sensible idea, and your definition of stability looks carefully chosen to provoke.

You don't know if the overclock is stable. You're pulling the ram about with the machine on. Software is crashing. I reckon this is user error.

Run memtest at stock cpu clock to try to judge if you've damaged the ram. If it passes, reinstall windows. Then put the overclock back on and stability test it (5 runs is not sufficient, the program itself tells you this). If you pass this and nero is the only thing that crashes, stop using nero.

I think you've damaged the ram slots on the motherboard. If you rma it having treated it like this I hope they laugh in your face.

thanks for your advice harsh it may of seemed but i am a service engineer and work with tv's dvd players and stereo's etc and i was looking for something called dry joints ie solder on the borad i am new to the whole pc world and overclocking and windows 7. hope you never get a job with the smaratans as i would have killed myself. but thanks for the advice in your massage which i will be trying thank you.
 
thanks for your FRIENDLY advice pc was built for me by somebody who knows a lot about pc i.e his is running on water cooling and over clocking but i always bother him with problems. But since it crashe once it seems to be getting more frequent. the overclock is stable can pass 20 passes on intel burn test and all ram can pass mem test but i am a novice (stupid one at that) that will play inside when turned on we all have to start somewhere thank you again for your advice will do as you said cheers.

Intel burn test isn't a stability test. It just heats up the CPU to see if you can induce thermal throttling. If you want to do a stability test try OCCT or Orthos and run it for a LONG time (8-24 hours).

As for waggling the RAM while it's running. It's not a known IT diagnostic methodology as far as I'm aware.
 
Plec has a point, I'm not diplomatic. It's hard to find an engineer with people skills :D

If you were looking for dry solder joints you should have been testing for electrical continuity with the ram modules removed. As it happens I'm inclined to agree, the contact between plastic slot and board is probably the issue, not the contact between the ram and the socket. eflowing the solder may well help, but waggling the ram about definitely wont, and would damage the inside of the socket and the contacts on the ram.

Good luck with the (probably time consuming) testing process.

@Plec, you write far better posts than me. I could learn things from you :)
 
Back
Top Bottom