JohnW

Member
Joined
Apr 8, 2016
Messages
32
Hello, recently I've getting getting numerous errors with my PC, and at first I thought it was hard drive related, however now I am not so sure. I will list problems in order from when they started happening to what's happening now (after a clean system restore)
C:120G D: 1TB
(SSDSC2CT120 120G SSD)paired with (WDC WD10EZEX-OOBN 1TB) < Possibly failing?

Problem 1. When playing games that boot from my secondary hard drive, they would run fine for a given time (anywhere from 30 minutes to a few hours) then I they would freeze, and a error box would pop up saying Microsoft Windows has stopped responding would you like to close? And it would either A. Resolve itself after a period of time in witch I would return to my computer with my D: drive would be disconnected. (A computer restart would usually resolve this).
Or B. End in a BSOD.
Games that caused it (that I played that were on my D: drive) Rocket League, The Division, Dying Light, World of Warcraft.

Problem 2. In addition to problem 1. I was also getting the occasional blue screen caused by this issue that was either Critical Process Died (being the rarer one) or something to the extent of a kernal impage error. (both of witch seemed to happen randomly in conjunction with the freezes however random in witch BSOD I received.

Problem 3.Eventually I was able to do a clean reformat of my PC (the long one) and get everything re downloaded and reinstalled. However I was still having issues, only now the only BSOD I seem to get is Critical Process Died. I decided to move my Rocket League over to my C: drive so that I could play it without issues (because I can play CS:GO and LoL, without any problems both being on my C: Drive. However even with it moved it still causes the BSOD, while the other games do not. I would also like to note that I replaced the sata cables on both my disks as I believed that to be the issue originally.

I have tried Memory Diag, checked my disks for errors, and done general diagnosing to the best of my ability, I can normally fix these kind of things myself With the help of google of course, however there seems to be a unlimited number of possibilities witch are caused by this BSOD as well as the other issues.

I have included a SystemReport file below that I created using PowerShell any help would be greatly appreciated.
 

Attachments

Solution
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C5, {100000000, 2, 0, fffff80113ab9840}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a0 )

Followup: Pool_corruption
Hi,
the above bugcheck is usually caused by a driver corrupting the system pool. Unfortunately the dump file doesn't say which driver...
That's great John! Glad to hear your issues are resolved... :)
 

Yes, but what of my secondary hard drive? Is it safe to plug it back in now?
 

Yes it should be fine.
 

So, in my bios under the sata cotroller settings, I have it changed to AHCI and under that is an option for sata 4/5 controller types witch is IDE, apparently this whole time I thought my D: drive was disconnected it was actually plugged it, but windows wasn't recognizing it. I plugged it in to the appropriate port and can't find it in my bios or inside of windows. However I'm pretty sure I can hear is spin up when I turn on my computer. Is it possible the hard drive was the issue, and once I used the recovery stick to "format it" it gave out? And maybe that's why I haven't been having problems? If not any ideas on getting it working?
 

Try unplugging the HDD, boot the system a couple of times and then attach the D drive again. If you have the SSD on port 1 try popping the HDD onto port 2 and then boot up. See if you can find the drive in the bios first. If you can, boot into Windows, open the control panel, click admin tools, computer management and finally disk management. If the drive is there you may need to format it to NTFS by simply right clicking on the volume.
 

Tried what you stated above to no avail, won't recognize hdd in windows. And depending on the sata ports I use, I can't find my ssd or my dvd burner in bios either (atleast the way I have them plugged in right now) there's 4 slots in the bios, and 6 on my motherboard. Both are there however. I tried plugging my hdd into many different slots, still not recognizing it under disk management. Should I attempt switching back to IDE and see if it recognizes it?
 

Should I attempt switching back to IDE and see if it recognizes it?
I guess you could give it a try just to see if the drive still runs under IDE. When you formatted the drive was it for NTFS or FAT32?
 

NTFS. Would switching it back to IDE possibly cause any problems? And would I be able to switch back easily? Or would I need to follow the guide I used to switch it in the first place. Or is it just the drive being done.
 

Would switching it back to IDE possibly cause any problems?
Normally no and it's usually just a case of making a change in the bios. I know you had to use a guide but i think that's because the os was originally installed under IDE. I guess at this point you'll just have to see what happens if you switch it back but ideally you should have both drives on the AHCI enabled ports and the DVD-ROM drive could be inserted into the ports which are still IDE.
 

Welp, tried multiple ports, as well as switching between modes (switched back to ACHI with no problems) and no luck. Only other explanation is drive failure. And after reviewing abunch of different internal HDD lately I can't say I even trust a brand anymore. Both Seagate and WD seem to be getting all kinds of hate lately for there quality in drives. I don't suppose you have any recommendations? I barley even filled half of this drive, but I plan on using my new one for a bit more storage. So anything in the 1-2 tb range should do.
 

I know a lot of people don't like Toshiba HDD's but I have had mine now for 4 years and no problems. It is a 2tb 7200rpm drive. You might want to try that if your looking for a new drive.
 

Last edited:
So something like this? Toshiba DT01ACA200 2TB 7200 RPM 64MB SATA3 6GB/s 3.5" Desktop Hard Drive - NEW Cheapest price I could find. How do you feel about SSHHD. Hybrid drives?
 

All honesty I don't know much about the Hybrid drives. I will have to look in to it. Never gave it much thought.
 

This is the one I have Toshiba DT01ACA200. I am trying to remember what I paid for it. I think it was $90. Wasn't over a $100. It might be higher now than it was 4 years ago. It is a 2tb HDD.
 

 

Your site is cheaper than what I looked at.
 

Welp, tried multiple ports, as well as switching between modes (switched back to ACHI with no problems) and no luck. Only other explanation is drive failure. And after reviewing abunch of different internal HDD lately I can't say I even trust a brand anymore. Both Seagate and WD seem to be getting all kinds of hate lately for there quality in drives. I don't suppose you have any recommendations? I barley even filled half of this drive, but I plan on using my new one for a bit more storage. So anything in the 1-2 tb range should do.
Can you test the drive in a different machine?

As for Disk brand, I go for Samsung but that's their SSD's. Actual Hard disk drives I always used Seagate. Their hybrid drives are supposed to be pretty decent too but if I'm interested in anything I simply google for a review.
Exactly how old is the hard drive which fails to be detected?
 

I'd say about 4 years, I believe we built this pc back in 2012.
 

Did you try installing those chipset/AHCI drivers we discussed in post #38?
 

There were no chipset drivers. All it did was install AMD control panel, witch was useless for me. There were no drivers associated with it, or I already had them. Either way it's working fine on ACHI mode now.
 

Back
Top