Hello all,
The crashes finally have done my nut in, so I'm going to ask some of you here to have your say in what could be going on.
Circumstances of the crash (usually during 3D applications)
1. All working fine
2. Audio cracking creeps in
3. Audio cracking progresses and video STUTTERING enters the mix
4. Problem 3 continues to worsen over time
5. Eventual system HALT
Doesn't usually BSOD, it just hangs and sometimes there isn't response to the power button (makes me think MOBO maybe?).
Of the BSODs I have had, it has been "KERNAL DATA INPAGE ERROR", quick googling revealed not much.
System is in the SIG, 2 4890s have recently been replaced with a 5850 due to one 4890 failing.
New hardware as of late - Corsair HS1 headset
Other Information: ESATA stopped working on my external drive recently (doesn't detect in bios)... yet USB works fine (again screaming MOTHERBOARD at me?). On top of this my motherboard overclock failed after been stable for nearly a year which I found a bit odd, this problem occurs WITH and WITHOUT the overclock btw so I've ruled that out.
Let me know what you think.
Thanks in advance,
Rob
The crashes finally have done my nut in, so I'm going to ask some of you here to have your say in what could be going on.
Circumstances of the crash (usually during 3D applications)
1. All working fine
2. Audio cracking creeps in
3. Audio cracking progresses and video STUTTERING enters the mix
4. Problem 3 continues to worsen over time
5. Eventual system HALT
Doesn't usually BSOD, it just hangs and sometimes there isn't response to the power button (makes me think MOBO maybe?).
Of the BSODs I have had, it has been "KERNAL DATA INPAGE ERROR", quick googling revealed not much.
System is in the SIG, 2 4890s have recently been replaced with a 5850 due to one 4890 failing.
New hardware as of late - Corsair HS1 headset
Other Information: ESATA stopped working on my external drive recently (doesn't detect in bios)... yet USB works fine (again screaming MOTHERBOARD at me?). On top of this my motherboard overclock failed after been stable for nearly a year which I found a bit odd, this problem occurs WITH and WITHOUT the overclock btw so I've ruled that out.
Let me know what you think.
Thanks in advance,
Rob
Last edited: