ChatterBank5 mins ago
BSOD problem
5 Answers
I have experienced this problem on my desktop computer for some time now and have learned to live with it. I've done the usual tests such as memtest, hard drive tests and driver updates to name but a few. I am now considering replacing the motherboard as this is the oldest part of the machine. Before I do I would like to know if anyone as any further ideas. I run Windows 7 Ultimate with 4mb of ram, 3.2ghz processor with 2 500gb hard drives.
Answers
Best Answer
No best answer has yet been selected by spider32. Once a best answer has been selected, it will be shown here.
For more on marking an answer as the "Best Answer", please visit our FAQ.Some of the initial things I would check are:
1) Is the power supply powerful enough? If so, it may be faulty.
2) Check your processor - is it fitted correctly? It could be overheating.
3) Have you got enough ventilation in your case? The cooler the better.
4) Have you got any older hardware fitted, such as sound card, graphics card, TV card? They could cause some problems. Try removing any you can.
It might not be any of these, but it should give you something to look at.
1) Is the power supply powerful enough? If so, it may be faulty.
2) Check your processor - is it fitted correctly? It could be overheating.
3) Have you got enough ventilation in your case? The cooler the better.
4) Have you got any older hardware fitted, such as sound card, graphics card, TV card? They could cause some problems. Try removing any you can.
It might not be any of these, but it should give you something to look at.
-- answer removed --
Aquariel, 1 to 3 could be a possibility because all are a good 8 years old now. I have however checked the ventilation which seems fine. 4 I have no cards fitted I use on board graphics and sound.
SlackAlice I will check the error code next time, I have looked at the crash dump all of which makes no sense to me. I remember that each time the possible cause mentioned is ntoskrnl.exe though.
SlackAlice I will check the error code next time, I have looked at the crash dump all of which makes no sense to me. I remember that each time the possible cause mentioned is ntoskrnl.exe though.