Tweet
Reset Problems - (AMD) GA-MA78G-DS3H
Hi guys, this is my first post on this forum so I'll quickly intoduce myself as Kris, 23 from the South West of U.K 
I spend the majority of my spare time producing progressive house music and recording live edits from various sources.
So, on to my problem! Pretty plain and simple, but more annoying because it doesnt give an indication why;
My computer will reset itself randomly. I've turned off the system reset protection in order to get some kind of answer from the blue screen of death, but it doesnt come up with one! Just resets to black every time.
This problem has been non-existant since I first built in in November 2008, and then appeared over the last 3 weeks.
Time scales are completely random. This morning the computer had been running for 25 minutes then just reset itself. Last night it had been on for several hours before deciding to give up. As I type now it's been on for about 3 hours with no problems.
As you can imagine this is having a big impact on my workflow because I am constantly saving musical projects and am petrified of losing all the hard work!
So far I have done/checked the following:
I checked around for hot areas inside and found that the Hard Drive was rather hot, So purchased a front case fan and ran it with it on, but still had the same issue, although the hard drive was then only luke warm. So I guess I can count the HD out.
However the NorthBridge is hot to the touch - is this perfectly normal?
Other points to note:
I used Si Soft to get my system details a few moments ago and it came up with two notices - could anyone shed any light as to whether these are likely to be related, and how they could be resolved?;
<link rel="stylesheet" type="text/css" href="../style/OFFICE10.CSS"> Tip T100 - Large memory systems (1GB or greater) should use Registered/Buffered memory, especially if more than 2 are installed on the same channel. This improves signal quality by reducing the load on the chipset channel. While these modules add an extra clock delay due to the on-board buffers (thus CL2 effectively becomes CL3), the stability will be worth it. Server chipsets with many memory slots generally require Registered memory.
Fix: If you plan on adding more memory, consider replacing the modules with Registered/Buffered modules. Do note that you cannot mix Unbuffered and Registered/Buffered modules on the same channel, but you may be able to if the chipset has multiple memory channels.
<link rel="stylesheet" type="text/css" href="../style/OFFICE10.CSS"> Tip T2546 - Large memory modules (512 or greater) should be ECC/Parity. Since the probability that a bit will be corrupt is the same or increases with module density, the bigger the module, the bigger the overall probability that you will get one or more corrupted bits. While these modules add an extra delay on partial writes (e.g. less than data width) as parity for the whole line must be re-calculated, the stability will be worth it.
Fix: If you plan on adding more memory, consider replacing the modules with ECC/Parity modules. Do note that running plain and ECC/Parity modules will turn off ECC/Parity for the whole memory array.
Any help would be greatly appreciated! I'm a little stumped, but am leaning towards RAM issues.....
Kris
I spend the majority of my spare time producing progressive house music and recording live edits from various sources.
So, on to my problem! Pretty plain and simple, but more annoying because it doesnt give an indication why;
My computer will reset itself randomly. I've turned off the system reset protection in order to get some kind of answer from the blue screen of death, but it doesnt come up with one! Just resets to black every time.
This problem has been non-existant since I first built in in November 2008, and then appeared over the last 3 weeks.
Time scales are completely random. This morning the computer had been running for 25 minutes then just reset itself. Last night it had been on for several hours before deciding to give up. As I type now it's been on for about 3 hours with no problems.
As you can imagine this is having a big impact on my workflow because I am constantly saving musical projects and am petrified of losing all the hard work!
So far I have done/checked the following:
- Driver Updates (All)
- Hard drive format/ fresh install of Vista x64
- Temperature checks of CPU/Graphics Card
- BIOS update to F8
I checked around for hot areas inside and found that the Hard Drive was rather hot, So purchased a front case fan and ran it with it on, but still had the same issue, although the hard drive was then only luke warm. So I guess I can count the HD out.
However the NorthBridge is hot to the touch - is this perfectly normal?
Other points to note:
I used Si Soft to get my system details a few moments ago and it came up with two notices - could anyone shed any light as to whether these are likely to be related, and how they could be resolved?;
<link rel="stylesheet" type="text/css" href="../style/OFFICE10.CSS"> Tip T100 - Large memory systems (1GB or greater) should use Registered/Buffered memory, especially if more than 2 are installed on the same channel. This improves signal quality by reducing the load on the chipset channel. While these modules add an extra clock delay due to the on-board buffers (thus CL2 effectively becomes CL3), the stability will be worth it. Server chipsets with many memory slots generally require Registered memory.
Fix: If you plan on adding more memory, consider replacing the modules with Registered/Buffered modules. Do note that you cannot mix Unbuffered and Registered/Buffered modules on the same channel, but you may be able to if the chipset has multiple memory channels.
<link rel="stylesheet" type="text/css" href="../style/OFFICE10.CSS"> Tip T2546 - Large memory modules (512 or greater) should be ECC/Parity. Since the probability that a bit will be corrupt is the same or increases with module density, the bigger the module, the bigger the overall probability that you will get one or more corrupted bits. While these modules add an extra delay on partial writes (e.g. less than data width) as parity for the whole line must be re-calculated, the stability will be worth it.
Fix: If you plan on adding more memory, consider replacing the modules with ECC/Parity modules. Do note that running plain and ECC/Parity modules will turn off ECC/Parity for the whole memory array.
Any help would be greatly appreciated! I'm a little stumped, but am leaning towards RAM issues.....
Kris
PLEASE
Comment