First of all, Gaius (my desktop) BSODs all the bloody time, usually because of a page fault or an access violation
Page faults themselves are usually reserved for page file violations that result from the HD (as that's where you page file resides), not necessarily from the RAM itself. RAM, in my experience, is incredibly difficult to break unless you are over/under-volting it (ie giving it more power from the PSU than it can handle with the timings you have set) and mobos are also hard to trip up (again, unless you are over/under-volting the North or South Bridges). ...Do I still have you?
If you want to be sure it isn't your ram, check out Memtest86, something I've used in the past and it stresses your RAM prior to OS boot-up. You burn it to a CD and make sure that your BIOS is set to start from CD instead of a HD. If all goes well after, oh, a night's worth of stressing, your RAM is fine. If you've replaced your PSU recently, that could be a problem but, again, unlikely. What GPU (video card) do you have? Do you
( ... )
Ram timings --> Ah...hard to understand/explain. Basically how fast the RAM runs.
North/South Bridges --> I'm pretty sure it's how the CPU communicates with the mobo, but I could be wrong. Still, vital pieces that are usually under heatsinks.
print --> Python programming language way of saying "show on screen." It also is in a ton of other languages as well.
POST --> that beep you hear when the computer gives an early "all clear" for essential components to run a computer.
...And sorry for my long answers. I get excited when computers have problems. ...And that also sounded very, very wrong. *facepalm*
And sorry for the edits. And sorry for saying sorry all the time. Heh.
Comments 5
Reply
Reply
First of all, Gaius (my desktop) BSODs all the bloody time, usually because of a page fault or an access violation
Page faults themselves are usually reserved for page file violations that result from the HD (as that's where you page file resides), not necessarily from the RAM itself. RAM, in my experience, is incredibly difficult to break unless you are over/under-volting it (ie giving it more power from the PSU than it can handle with the timings you have set) and mobos are also hard to trip up (again, unless you are over/under-volting the North or South Bridges). ...Do I still have you?
If you want to be sure it isn't your ram, check out Memtest86, something I've used in the past and it stresses your RAM prior to OS boot-up. You burn it to a CD and make sure that your BIOS is set to start from CD instead of a HD. If all goes well after, oh, a night's worth of stressing, your RAM is fine. If you've replaced your PSU recently, that could be a problem but, again, unlikely. What GPU (video card) do you have? Do you ( ... )
Reply
RAM --> You know this.
CPU --> You know this too
Mobo --> motherboard
GPU --> graphics card (graphics processing unit)
PSU --> Power Supply Unit
Ram timings --> Ah...hard to understand/explain. Basically how fast the RAM runs.
North/South Bridges --> I'm pretty sure it's how the CPU communicates with the mobo, but I could be wrong. Still, vital pieces that are usually under heatsinks.
print --> Python programming language way of saying "show on screen." It also is in a ton of other languages as well.
POST --> that beep you hear when the computer gives an early "all clear" for essential components to run a computer.
...And sorry for my long answers. I get excited when computers have problems. ...And that also sounded very, very wrong. *facepalm*
And sorry for the edits. And sorry for saying sorry all the time. Heh.
Reply
Reply
Leave a comment