Think my secondary HD has been fried??

SmoochyTX

Lifer
Apr 19, 2003
13,615
0
0
OK, I was surfing along and reading quite fine while one of southeast Texas' finest thunderstorms reared its ugly head.

Lightning strikes started happening just a few minutes apart so I figured I had better shut my comp down. Was about to start shutting things down when all of a sudden I saw the cable lights go out on my cable modem. No blinking lights. Nothing. Never seen that before.

Went ahead and shut down by Start, Turn Off Computer, Turn Off. (XP Home BTW)

Then I decided to turn it back on to see if the modem would come back on. (I had planned on turning it back off if the modem did come back on after that. If the modem didn't come back on, was going to call Time Warner.) Well, the modem came back on but I had an ugly error screen that I'd never seen before accompany it.

"A problem has been detected and Windows has been shut down to prevent damage to your computer. If this is the first time you've seen this Stop error screen, restart your computer." yada yada yada It gave the Stop error code and also named my GoBack2K.sys file.

So I restarted my computer. I got the same message.

So I'm sitting here thinking and saying *@@#@*! Turned it off again for about 5 minutes hoping and praying that this incident was just a dream.

It wasn't. Got the same error code message again.

Anyway, to make a long story shorter, I switched to onboard video (thinking my video card was fried). OK so far. Tried to boot again and got the same error message as before. So I disconnected my secondary HD (a 120G Seagate 2MB) and put the primary HD (a 120 Seagate 8MB) all by itself on the cable.

System booted fine into Safe Mode. Shut down and switched back over to my video card. Restarted and everything's fine now. (minus the secondary HD)

Soooooooo, is my backup HD fried? If not, what else could have caused this problem?
 

OdiN

Banned
Mar 1, 2000
16,430
3
0
Hrmm...you have goback installed? That I would remove personally...System Restore would be a better option than that software.

As for the drive being dead...try it in another computer. I'm assuming the second HD presumed dead was on the same chain as the primary...that would cause the boot problem. Try disconnecting a CD device temporarily and attaching the presumed dead drive there and booting. If you get in, maybe you can get some data...or at least confirm that the drive is in fact dead. Also, try hooking it back up and see if you still get that error. Does the drive still spin? Any clicking noises? Any burn marks on the PCB?
 

al5

Junior Member
Jun 12, 2004
3
0
0
I have the same problem.
I am running Windows XP pro.
My Hard drives are all fine because I can read all the data on them in DOS and performed a scandisk which showed no problems.
But this file "GoBack2k.sys" is preventing me to boot to windows in normal or safe mode.
I can only boot to a DOS prompt using a boot floppy.

The Blue Screen says:

"A problem has been detected and windows has been shut down to prevent damage to your computer"

"Technical information:"
*** STOP: 0X0000007E (0XC0000005,0XF7860343,0XF789E0E4,0XF789DDE4)
*** GoBack2k.sys - address F7860343 base at F785E000, DateStamp 3dbd6b29

I have disabled goback and that did not help.
I deleted the goback directory on the drive using DOS and that did not help.
I ran scandisk on all drives and it found no errors.

Do I need to format the main drive to get rid of this ??
I would appreciate any help.
 

al5

Junior Member
Jun 12, 2004
3
0
0
OK, I made a little progress.
I finally found the file GoBack2k.sys
I still get the blue screen and cannot boot to windows, but the reference to GoBack is gone.

The Blue Screen says to use CHKDSK to check my drives, but I can't find a version of CHKDSK that will run from my Boot floppy. The 2 versions I have tried say that they cannot be run from DOS.

So now the blue screen says:
"Technical information:"
*** STOP: 0X0000007B (0XF789E63C,0XC0000034,0X00000000,0X00000000)

Any suggestions what to do next?
 
Jan 31, 2002
40,819
2
0
Anyone see the common thread here?

Two systems that are pooched.
Two systems that use GoBack.

Uninstall that MBR-hijacking piece of crap.

Ctrl-Alt-G on bootload to force-unhook it from the MBR - also, try booting to your GoBack recovery disk (you DID make one, right?) and doing goback /r (IIRC)

- M4H
 

al5

Junior Member
Jun 12, 2004
3
0
0
Thanks MercenaryForHire

I tried both of those things without any luck.
I finally decided to reinstall Windows XP and things seem to be working again.
I have used GoBack for several years and this is the first problem I have had.
GoBack has saved my butt on many an occasion when the kids mess up the computer or when an installation doesn't go well.
I think I would feel pretty vulnerable without it now.

I appreciate the help.
Take care,
Al