Snake05
New Member
- Joined
- Oct 17, 2005
- Messages
- 530 (0.08/day)
- Location
- Little Rock, AR
Processor | Intel Core 2 Quad Q6600 Kentsfield 2.4GHz G0 @3.6GHz |
---|---|
Motherboard | MSI P35 Neo2 FR |
Cooling | Thermalright Ultra-120 Extreme w/Scythe S-FLEX 1600rpm |
Memory | 4 x G.SKILL 2GB DDR2 1066 |
Video Card(s) | SAPPHIRE Radeon HD 6870 |
Storage | OCZ Vertex 2 3.5" 90GB SSD/Seagate Barracuda LP 2TB/750GB WD Caviar |
Display(s) | Samsung 24" LCD/Samsung 941BW |
Case | Thermaltake Soprano DX |
Audio Device(s) | Creative X-Fi XtremeMusic w/ Logitech Z-5300e |
Power Supply | Mushkin NANOPOINT 550W |
Software | Windows 7 Ultimate x64 |
Benchmark Scores | 3DMark06 - 15647 |
I have been away for what seems like years, but I am back and in need of grave assistance. I need help trying to establish the culprit of my BSOD issues. I recently upgraded GPU (October) and then HDD and RAM (November) (see hardware in specs). Around Christmas time, was surfing along my Netflix queue, then BAM.... Death from Microsoft (at least I like using them as my scapegoat). After much manipulation, I run Mem test and find errors with the RAM (an issue I will ask for assistance in the short term). Needless to say, I replace it with my good ole 4x 2Gb OCZ Platinum (800) and get back to life.... at least until last Wednesday. By this time, I have finagled with my RAM voltages and had success with everything I threw at it.... until my casual interweb surfing Wednesday. Similar error (don't recall the original BSOD message). So I turn back to my OCZ once more, and it hits me again, and again, and again with all configurations, including different GPUs. I am assuming at this point it is my newly installed SSD, or possibly my mobo biting the dust after a long hard run.
From what I gather, the code seems to be pointing at a hardware, whether it be driver or the component. I will be on after work today provide any more information needed. I have been limited to time to try and fix my poor baby, so any and all help is much appreciated.
p.s. It's good to be home....
From what I gather, the code seems to be pointing at a hardware, whether it be driver or the component. I will be on after work today provide any more information needed. I have been limited to time to try and fix my poor baby, so any and all help is much appreciated.
p.s. It's good to be home....