• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Strawhat12

  1. Ever since Win 7 has been installed on the machine it's had this problem. I haven't done a clean install since first installing it though and tbh I'd rather not.
  2. So there's a problem on one of my PCs where the system either hangs/crashes or loads up really slow from resuming in sleep mode. I've had a look at the 'power' options under 'control panel' and have made sure the HDD is set to 'never' spin down as I've read that has usually been the culprit. I've also run a chkdsk to make sure everything is in working order yet the problem persists. Any ideas?
  3. Also one more question; I checked and my processor is within the 3 year warranty period that Intel offer. If I was to contact them would it be best not to tell them it was overclocked? Does that void warranty? Even if I don't mention about the OC can they still find out somehow? Also, if I mention I get the BSOD randomly telling me its a hardware error they may say it could be to do with other components when I actually know its the processor via the minidump. Do I mention this to them?
  4. Thanks for the response. I suspected the CPU would be the problem. You said that the file I provided wasn't a Kernel dump but a minidump. Well is there a different way of selecting a Kernel dump that I'm not aware of? I right-clicked 'My Computer' then 'Properties' and then 'Advanced Settings'. From there I selected 'Startup and Recovery' and from the drop down box there are three options; 'Small memory dump 256kb', Kernel dump', 'complete memory dump'. I obviously selected 'Kernel dump'. Is this not the way I should be doing it?
  5. So had the PC BSOD on me again but I managed to upload a Kernel Dump of it. I did have a look at the dump myself using Windbg but I'd like to know what it all means.
  6. Do you want me to upload the minidump?
  7. Hi, For some reason I get the BSOD stop 0x00000124 error message randomly whether my PC is idle or its nearing 100% usage. From the BSOD this is the full error; stop 0x00000124 (0x0000000000000000, 0xfffffa8002a8f038, 0x00000000b2000040, 0x0000000000000800 I've gathered that this means its a hardware related error. I did have my CPU overclocked recently and I think I must have first got the message then but now everything is back at default, stock, auto and yet I still get the error. I ran memtest and memtest86+ for 7 passes each with no errors. So what could it be?
  8. I've tried my best and I've decided to RMA the drive and get a replacement. Before I do that though how do I erase my drive securely without it giving me errors. I tried that Secure Erase program but it just seems baffling in running it from DOS.
  9. Once I unbricked the drive and backed up everything I upgraded the firmware from SD15 to SD1A if that helps.
  10. Yes I also cleared the S.M.A.R.T I don't want to give up on the drive yet as its still recognised and I can see it in my other machine. I'm still going to see if I can fix it somehow before I give up on it completely. Still any other suggestions would be welcome in the slightest chance that it may fix the problem.
  11. Ok, I also did the second step cleared the G-List and still the same thing. Any other ideas? Would zeroing the drive completely fix the problem?
  12. Right, I've run Seatools on both Windows and in DOS and this is what I got. S.M.A.R.T check - failed Short test which also failed And then I did the long test in DOS and it failed with this message; 'LBA 2627 99 errors detected, read scan failed, error on identify command 71:04' I'll now try the the second option you mentioned and see how that goes.
  13. Seems like you have a lot of bad sectors. Try running Seatools and see what it says. Next options are: 1) throw away the stoopid thingy 2) re-do the "unbricking thing" this time clearing the G-list and SMART Then, run seatools again. jaclaz Thanks for the response. I'll save the throwing away option as a last resort I'll run Seatools now and post back what it says and then I'll try the BSY unbricking thing again.
  14. I have a ST350032AS Seagate HDD. The drive had the dreaded BSY problem which I've corrected but after fixing one problem I've been presented with another. So here goes; After getting rid of the BSY error state I put the HDD back into its PC, I start it up all well and good and see the Windows loading screen, so I'm thinking so far so good. However straight after I see a BSOD screen which appears for a fraction of a second which then restarts itself again and does this continuously. I then connect the HDD to another PC which has its own HDD, OS etc. I boot up to Windows Vista albeit slowly as the problem HDD is making the PC run slow for some reason. I can see the HDD on my other machine and manage to backup my important files. Next step I completely reformat the problem HDD and tried to install a fresh copy of Vista on it again but I get errors and it won't let me install! So then I connect it up to my other machine and I can see the HDD there (465GB out of 465GB) I run HDTune and I see this particular error 'Reallocated Sector Count, Current - 13, Worst - 13, Threshold - 36, Data - 1788, Status - Failed' I don't know whats wrong with it, I can access the HDD when connected to another machine albeit it opens slowly and sometimes I hear the disc spin up and down if idle for some time but I can't seem to install Vista or do anything else with it.
  15. I was hoping I wouldn't have any more problems but here goes; As I said in my previous post, I managed to recover my HDD and its seen in the bios and everything but for some reason I can't seem to boot it up to Windows. I get up to the Windows loading bar then after that for a fraction of a second I see a blue screen and it restarts my PC again, it does this everytime. However if I have another HDD connected as a main I can boot up into Windows and see the recovered HDD but the whole system seems very slow due to the recovered HDD. I managed to backup my important files and flashed to the latest firmware but just wanted to know what may be up with my HDD. Any ideas?