• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Weird problem with a HDD BSOD'ing XP, suggestions?

N

Necromancyr

n00b
Joined
Mar 29, 2004
Messages
5
Ok, I'm completely baffled by the problem I am having. I have a Western Digital 200gb hard drive on my system that has been working fine since I got it for christmas. All of a suddent it's causing windows to BSOD.

I started getting some weird issues with McAfee Virus Scan autoupdate and I decided I wanted to reinstall XP. So, when I attempted to do so setup started BSOD'ing. So, I unplugged all drives except for my system HDD and my CD-ROM drive that I would install from. Installation went without a hitch. Completed ALL Windows Updates, then began plugging back in drives.

I plug back in the drives, and wind up getting a BSOD (error code STOP 0x0000007f - all of the rest of the line is 0x00000000's) and an instant reboot. (The only way I could get the error code was to try to reinstall XP and see what code came up when that BSOD'd and didnt force a reboot instantly).

My system is an ABit BX-133, and the I've updated the HPT370 controller to 3.351 (the newest version available) so it can recognize the WDD 200gb as a 200gb hard drive. I have a Tualatin (w/adaptor) 1.1ghz celeron in there, NON-OC'd.

Now, what I've done to try to pinpoint the issue is the following:
- Remove drive, XP boots fine. No issues.
- WDD Diagnostics on the drive. No issues reported in both quick and long tests.
- Memtested the computer, no issues.
- Swapped out all memory with drive connected to see if it was some faulty RAM. No alterations.
- Changed IDE cables. No change.
- Put the drive on the primary slave, secondary master, and secondary slave configurations - problem still occurs no matter where it is.
- Disconnected EVERY other drive except for the system drive and this drive. Still BSOD's.
- Tried Cable selected jumper settings. Doesn't even get recognized by the HPT bios when I do this. (BTW, the jumper settings have been correct for each config I've tested).

Any suggestions/ideas would be great. I'd prefer not to RMA, for one big reason: I can't get at the drive. The Abit BX133 can only get at a 200gb HDD through the HPT370 and I've yet to find a way to access the HPT370 via any DOS methods. Add into it that the drive is NTFS, and getting anything off it seems impossible considering I can't get into Windows.

So, after discussing with people in #hardocp for a bit of last nite I put this up as a plea for help to the forums :).

(Oh, and last thing, I don't have another PC I can put this into to access the entire drive.)
 
It's a 350W Enermax PSU (I'm fairly certain right off the top of my head). Also, having JUST the two HDD's connected causes it. So I have been assuming that it's not that.


(If anyone has any ideas on getting the info off the drive that would be great too as WD didn't seem to have ANY problem giving me an RMA...even though the drive is reporting no error codes. Which kind of bothers me....)
 
Go System Properties -> Advanced -> Startup and Recovery and uncheck the Auto restart box.
That way it wont restart from a BSOD.That way you can check that you get the same stop code each time.

Are you overclocking.

Info on Stop 0x0000007f Here.

Luck........:D
 
I read up on the info code - and no OCing at the moment. The processor is running at FSB 100, Mult. of 11 - well within the ABit BX133 specs. Also, the memory all tested out fine. And swapping it out didn't do anything.

And, strangely enough, I tried doing that (turning off autorestart)...and it's still doing it. I have to go back into windows to check and make sure it actually got changed however.
 
Well, after calling WD I figuered out the problem.

Stupidly enough, it seems that attempting to start a Highpoint 370 without updating the drivers ONLY crashes when you try to use a drive larger then 137gb.

So...My 120, 80 and 40 drives all were fine. The 200 freaked it out and I guess had it using the wrong type of variable or something for HDD usage.

Strange, one would think I would have at least got an error about driver failure...not a general stop error.
 
You must log in or register to reply here.
Back
Top