|
|
#11
6th Sep 2009, 13:40
| ||||||||||||
| ||||||||||||
| Try another date, that is shown in System Restore.
__________________
My System: Home Build
|
|
#12
6th Sep 2009, 16:35
| |||
| |||
| I tried an earlier date, that was in bold, 3 weeks ago, and I got the same message, but I was off on what the message said before. It actually says that the restore was Incomplete because no changes have been made to the system since then anyway. |
|
#13
6th Sep 2009, 21:34
| |||
| |||
| I just got another BSOD (the 4th or 5th so far, I think) and it looks different this time! A photo: http://i212.photobucket.com/albums/c...A/100_5755.jpg Also, another important piece of info may be that I think the BSODs only happen upon rebooting, like maybe after that "Windows" loading screen appears (I have Windows XP). The other times I saw the BSOD, they probably happened after a sudden reboot, when I wasn't in the room at the time, and then I come back to a BSOD that shows up at the start of a reboot, and stays on the screen until I manually restart the computer, and then it reboots correctly, without a BSOD. But the BSOD can appear even after an intentional and normal Restart. Anyway, does any of this help narrow it down now? |
|
#14
7th Sep 2009, 02:20
| |||
| |||
| Hmmmmmm. I think you are going to need to look closer at your Ram ....... try removing a stick of Ram (assuming more than one is fitted), running with just one .... if no better swap them over, if a stick has gone bad, this will help you identify which one. Also, when you cleaned the PC, did you get all the gunk/dust out of the fins of the heatsink ? |
|
#15
7th Sep 2009, 09:08
| |||
| |||
| Hmm, I am so unknowledgeable about the inside of the computer, and am afraid to touch anything that's already installed, which is why I was hoping that my BSOD photo or my other clues may pinpoint an exact cause first, that I could then act on. Is there anything that pinpoints RAM, first off? Second, I don't know what the fins or the heatsink are. |
|
#16
7th Sep 2009, 11:47
| |||
| |||
| Well .... you are either going to take it in somewhere, or bite the bullet and have a go yourself. Removing a stick of Ram is pretty simple, as long as you ground yourself (touch a radiator or the PC Case), before touching internal parts, you should be fine. This gets rid of any jarmful static. The Heatsink is normally a large metal block, with a fan on top something similar to this. In this pic the Ram slots are the blue sockets, with 2 black ones to the left. To remove a stick, you push the grey lugs outwards, at each end and this will release it. Replacing is the opposite, but when you push the Ram back in, the grey lugs should lock by themselves. HTH  Sometimes it's nececary to remove the fan (often just 4 screws), to clean it thoroughly. |
|
#17
7th Sep 2009, 12:24
| |||
| |||
| <post removed> |
|
#18
7th Sep 2009, 12:26
| ||||||||||||
| ||||||||||||
| It's spam phil, deleted and banned. Thanks again.
__________________
My System: Hybr!d
|
|
#19
8th Sep 2009, 09:56
| |||
| |||
| Ah, a BSOD happened just a few minutes ago, at 12:37 my time, and I have new information from the Event Viewer that I'm guessing may show what causes it: http://i212.photobucket.com/albums/c...09124625PM.jpg http://i212.photobucket.com/albums/c...09124652PM.jpg But how do I get rid of those bad processes from happening? |
|
#20
9th Sep 2009, 01:46
| |||
| |||
| Check your Ram first .... if the Ram is bad, this will cause all sorts of spurious unrelated messages, which will be meaningless. You need to follow a process of elimination, to pinpoint where your problem lies, otherwise you will be going round in circles and down "blind alleyways" Ram is probably the cause and is one of the easist things to check, without spending time or cash ...... if this proves not to be the answer, we can then look at other possibilities  |
