borschtBomber[SS]
04-18-2008, 05:14 PM
I posted this elsewhere..and this is I think separate of my last BSOD...the BSOD gods seem to hate me right now. :frown:
I think something is amiss but I just don't know what is causing this issue as of yet. I ran memtest and the memory passed fine so its not that. So I'm just not sure if its the hard drive or the motherboard causing these problems. Here is what has happened over the last few days leading up to this.
Tuesday - Installed Enemy Territory to give it a try for old times sake and played for a bit, then the next day my wife started the pc up and after getting into XP and everything is loading up, BSOD with no error code. After a reboot CHKDSK runs and starts cleaning stuff up, one file I noticed was the patch for ET. So after we got back into Windows I uninstalled ET. No problems
Thursday - No issues until I decide to try and overclock the HD 3650 I have installed, but ATI Tool won't run and Rivatuner refuses to let me. I click on auto detect, but nothing happens and it won't allow me to adjust anything. So I then choose the reboot option and after reboot about 2 seconds after the XP splash screen I the BSOD with 'process1_initialization_failure' error code. Tried booting into Safe Mode, Last Known Good Config and still get BSOD.
Searching around seems to point to it being a messed up XP install. I ran out of time last night but I'm worried that it might be a HD issue so I'm gonna run the Seatools diagnostics on it tonight. This scares me because the drive is OEM (thats what Seagate sent from the Christmas contest) and it was a royal PITA trying to get it replaced when it was DOA when I first got it. Is it possible the motherboard could be screwing things up or does this really look like only a HD issue?
5000+ Black Edition
Foxconn NF570Sli
2x2Gb G.Skill DDR2 800
Diamond HD 3650
Seagate 1Tb SATA
I think something is amiss but I just don't know what is causing this issue as of yet. I ran memtest and the memory passed fine so its not that. So I'm just not sure if its the hard drive or the motherboard causing these problems. Here is what has happened over the last few days leading up to this.
Tuesday - Installed Enemy Territory to give it a try for old times sake and played for a bit, then the next day my wife started the pc up and after getting into XP and everything is loading up, BSOD with no error code. After a reboot CHKDSK runs and starts cleaning stuff up, one file I noticed was the patch for ET. So after we got back into Windows I uninstalled ET. No problems
Thursday - No issues until I decide to try and overclock the HD 3650 I have installed, but ATI Tool won't run and Rivatuner refuses to let me. I click on auto detect, but nothing happens and it won't allow me to adjust anything. So I then choose the reboot option and after reboot about 2 seconds after the XP splash screen I the BSOD with 'process1_initialization_failure' error code. Tried booting into Safe Mode, Last Known Good Config and still get BSOD.
Searching around seems to point to it being a messed up XP install. I ran out of time last night but I'm worried that it might be a HD issue so I'm gonna run the Seatools diagnostics on it tonight. This scares me because the drive is OEM (thats what Seagate sent from the Christmas contest) and it was a royal PITA trying to get it replaced when it was DOA when I first got it. Is it possible the motherboard could be screwing things up or does this really look like only a HD issue?
5000+ Black Edition
Foxconn NF570Sli
2x2Gb G.Skill DDR2 800
Diamond HD 3650
Seagate 1Tb SATA