So I just played Skyrim with 22 mods installed, mostly graphical enhancements, for two hours and no issues. So I guess it's starting to seem like it's a Saints Row IV issue. I'm going to play some Team Fortress 2 again and see if that will BSoD again and try and figure out what the issue really is.
Ok, so I have Saints Row IV installed on the 1 TB HDD. The game will typically have some kind of audio error, be it a dialog not being audible or just completely skipped during a cut scene, or just a buzzing noise. Then trying to open a menu of any kind will typically speed up the complete lock up or BSoD. I just ctrl alt del at the point where I thought the error was going to occure and when I got to the desk top Intel Rapid Share had notified me that a drive had been removed. I had noticed this at one point one other time but the drive instantly reconnected and was up and running again. This is what had lead me to install the game on the SSD to see what would happen, although the game did BSoD on me again. I was just testing the game again, it's on the HDD again, and this time Intel Rapid Share had notified me a drive was removed but this time it did not connect. So I am going to assume this is probably part of my issue. Now I just need to get another HDD and make sure. I'll keep you updated.
EDIT: I restarted and it's back, is the HDD disconnecting because of the kernel that's stopping in Windows or a HDD issue?
EDIT Again: I found a recommendation to download AMD Catalyst if having issues with any crashing and I just played two straight missions successfully, so we'll see how that goes.
Last edited by vinone; 11 Sep 2013 at 19:50.
I know very little about Rapid Share technology. You can run check disk on the drive to answer part of your question.
Disk Check
If it it a form of raid, Western Digital does not recommend their desktop drives to be used in any kind of raid. They want you to buy their commercial drives for that.
Says the hard drive doesn't have any errors. I'm not using a raid, just a simple one SSD, one HDD set up. I also redid my Nvidia drivers and to no avail. Also downloading the AMD Catalyst software didn't work either. Although now I seem to be at a point in the game where it's not random. The last two time the same exact instance has triggered the audio to get glitchy and cause a BSoD. So I'm going to test it one more time and probably get in contact with Volition (Saints Row developer) and see what they think.
I'm pretty sure this has to be a driver issue somewhere though.
Okay
First, we want to make sure the computer is saving your dump files. Go to Control Panel -> System -> Advanced System Settings -> Startup and Recovery [Settings] Make sure that "Write Debugging Information" is set to Small Memory Dump (256kb) if it is not already.
Next, make sure that the folder C:\Windows\Minidump exists. If not, create it (allow permission if asked). Make sure any dumps you want to analyze, whether yours or others', are in this folder. You can ZIP/RAR the files and send them to someone else to analyze as well.
I'm not sure what you mean by the AMD catalyst software with an Nvidia card. AMD and Nvidia do not get along well on the same system. But, something is causing the hard drive to drop out. Try replacing the Sata data cable and checking your connections of both cables on both ends. Also, try to download and run the Western Digital diagnostic program on the drive. Use the Data lifeguard for DOS and run the short and long test. Upload the SF diagnostic software for Koolkat to look at to see if there is a driver problem. But, a driver problem should not cause a hard drive to disappear, I don't believe.
I read on a forum post on a Saints Row website that for Nvidia GPUs downloading the AMD catalyst software could help for crashes. I know Saints Row is part of AMD's gaming evolved thing or whatever it's called, so I thought maybe it would help, I knew it was a long shot. I tested the drive many times through Windows, Seagate, WD, and nothing has come up any time; and it doesn't do that ANY other time, even with different games, and it also BSoD when I had the game on the SSD. I don't think it's the HDD it's self or the SATA cable. That's just an observation I had when I catch the game causing problems fast enough and am able to ctrl alt del and get the game to stop running..
Also, I have all of that stuff already on the first post from the many times it crashed previously. I'm about to force the BSoD again so I can get you another minidump to see if anything has changed.
And, after getting a BSoD three straight times in the same spot, this time I don't get one at all for a sold 40 minutes of play time, weird. I'm sure one will show up again eventually and I'll attach it on here.
Quote