I'm out of suggestions atm I`m afraid as the problem only happens with the one game and the substantial (and excellent) work carried out by BrianDrab and yourself has not resolved the issue I suggest that you post here to see if anyone at the steam community has encountered this issue and more importantly if there is a fix, I will keep pondering on this in case I have overlooked something but tbh I feel that the MGS software is the problem.
Blue screens, many 'seems to be caused by ... ntoskrnl.exe'.
#61
Posted 07 October 2015 - 04:26 PM
#62
Posted 08 October 2015 - 09:12 AM
Thanks very much. Both Brian and yourself have been great. At this point, I don't care nearly as much if I have to restart before I play this game, because now it takes a couple of minutes and the PC will be completely booted and usable if I walk away after turning it on. My system generally feels smoother now, so even if the problem isn't totally sorted, I'm really glad that we've done all this.
I've posted on the Steam forum and searched through all the MGSV threads for a similar problem but no-one seems to have the same trouble.
I honestly don't think it's MGS as much as it's MGS finding the thing that's wrong with my system, because I believe more people would be having this trouble otherwise. I have one more thing to try later. I remember someone complaining that Resident Evil 5 was causing blue screens for them, and we went through all his drivers and such looking for problems and I gave up for a couple of days. When I talked to him again, he said it was a wireless gamepad dongle of all things, and that if he played without that, there were no blue screens.
I have an iLok for a lot of my music software licences, and iLoks are notoriously both invasive and faultily coded. Perhaps in some way that's the problem. It's related to the sound, and my sound card was totally removed (aside: just played for a couple of hours with the sound card back in, so that wasn't the problem) for several sound-related blue screens if I recall, and I remember one of the earliest blue screens was a 'USB bug code check' or something similar. Over the next couple of days I'll run some tests.
Thanks again, both of ye.
Edited by For the love of sod., 08 October 2015 - 09:12 AM.
#63
Posted 08 October 2015 - 07:53 PM
So, new dump file. Looks like more of the same to me but you can make sure if you like. This time the game went for over three hour after being woken from sleep. It never would have done that before some of the stuff I did as per Brian's instructions, which means we've made significant improvements, and I hate to say it but I think that makes it prey on my mind more.
Earlier I started the PC like normal but with the sound card back in (restarted a couple of times for proper driver installations and such), and at some point later I played the game for a couple of hours with no trouble. Later, both physically and via the taskbar I removed the iLok, which is always in, and I put the PC to sleep. I came back several hours later, and eventually started the game. That was my test.
I suppose I could try putting it to sleep now that the iLok wasn't in during the boot process, and then try to play the game. If it works, that test only helps to narrow down which of my components is laughing at my strife as for practical purposes, if I have to start the game only if the iLok was never in, that sort of defeats the purpose.
Another weird thing about my arrangement is it's a Mac keyboard and mouse I do use on my Windows PC. Never been a problem before but that hardly means it isn't now.
Unfortunately, the most likely culprit if it's a piece of hardware, is my GPU, and I can't test the game without that, nor have I access to any others.
Cheers.
Attached Files
#64
Posted 11 October 2015 - 02:43 AM
Apologies for the delay getting back to you
Nothing specifically identified in the latest crash dump but there are two instances of iLok drivers failing to load;
#65
Posted 11 October 2015 - 06:45 AM
Thanks. Here's the screen shot: http://prntscr.com/8q2i98
Interesting findings with the iLok but as the game's crashed with no iLok in, I would think it's not that, yeah? Another thing I thought of is what if something weird happens to the memory when I put it to sleep? Maybe I should run that MemTest again both before and after the PC's been put to sleep. Remember, this is that other MemTest that runs from the desktop, not the one that boots from a CD or USB drive before Windows boots.
#66
Posted 11 October 2015 - 10:48 AM
#67
Posted 11 October 2015 - 11:00 AM
Ah yeah sorry, that's my external drive that WD one is. Don't be keeping it plugged in however. The Seagate is a 3TB one, which Asus for whatever reason (the motherboard I assume) automatically instally software to read all 3TB. It said 2TB was its maximum and installed Disk Unlocker to partition it automatically. Seems a bit dodgy to me but it's worked so far. I keep my Steam games on that partition and back up the other one, as I can just download my Steam games from the cloud if needed at any point.
#68
Posted 11 October 2015 - 12:03 PM
As I suspected but had to check because of the presence of the USB Sandisk Cruzer device.
I keep my Steam games on that partition and back up the other one
To which partitions are you referring please.
For best performance and security it is best to have Windows on its own partition out of harms way and data such as games ect on their own partition, one of the suggestions that I was going to make was to try installing MGS V on a partition away from Windows, you could try bringing the unallocated space into use and after ensuring that it has been allocated a drive letter install MGS V there and test.
Tip
While troubleshooting be sure to disconnect all USB storage devices from a computer.
#69
Posted 11 October 2015 - 01:04 PM
Ah right, the E drive is the partition with my games, which is the partition Disk Unlocker made automatically. Not long ago I moved all my Steam stuff to that previously unused partition, but definitely a good while before I got MGSV. No other games have had any problems. That partition is of course not the same one as Windows.
Thanks for the tip. That USB device was only there as I was trying to run thebootable MemTest as opposed to the HCI one that's run from the OS. Generally, I don't have one in, but I probaby wouldn't have thought to remove it for a bit so thanks for that. This time, I remembered and it hasn't been in there for a few day at least, but usually I'd have forgotten.
I've considered dual-booting a Windows 10 upgrade to see what does and doesn't work. Would you advise that and how would you go about it?
Thanks.
#70
Posted 11 October 2015 - 01:42 PM
Not long ago I moved all my Steam stuff to that previously unused partition
Not sure if I am understanding correctly here as unallocated space on a HDD cannot be used until it has been formatted and allocated a drive letter.
Excuse the title of the tutorial, a step by step guide here, please note that you will need to use all of the unallocated space as one partition, this because Windows will not boot with any more than four partitions on a single storage device, you could try installing Windows 10 and nothing else to the new partition and then test out MGS V.
#71
Posted 11 October 2015 - 01:50 PM
Sorry, knew I'd forgotten something. That unallocated space appears to be the E partition. My motherboard is an Asus M5A97 R2.0 (Socket 942), and for whatever reason it has trouble with a HDD over 2TB. So, it seems to recognise that that space is there but be unable to do any thing with it I suppose, and it installs Disk Unlocker (this is all a while ago, so it's from memory and may be slightly inaccurate) which partitions whatever's over 2TB so you can use it. I think the confusion is it somehow virtually treats it as a separate drive entirely, for some purposes, and for other purposes it remembers it's a partition. A bit confusing to me but I've gone with the flow so far and not had any problems.
#72
Posted 12 October 2015 - 06:42 AM
That is messy and small wonder that you have had problems with slow boot times
No easy way of trying out Windows 10 then unless you install it to your WD external drive and set the BIOS to boot from USB then load MGS V from the internal drive, alternatively, upgrade Windows 7 to 10 and if you dont like it roll it back to Windows 7, see article here
#73
Posted 16 October 2015 - 07:51 AM
Been trying to research the purpose of Disk Unlocker and it seems that my motherboard and Windows 64-bit both are capable of handling over 2TB HDDs, so I'm really confused. I probably won't bother with Windows 10 in that case. Thanks.
#74
Posted 17 October 2015 - 11:48 AM
Aye most odd as Disk Unlocker was an optional download from way back in 2012, it should not have been installed on your computer without your knowledge.
#75
Posted 17 October 2015 - 11:55 AM
Well, it didn't do it without prompting me, but the prompt said that either Windows or the motherboard couldn't read HDDs over 2TB and would I like to install this to do it a different way, so I allowed it thinking I had to if I wanted to use my whole drive. Is there something I can try to remove it and maybe it will read all 3TB anyway?
Similar Topics
Also tagged with one or more of these keywords: blue screen, bsod
Software →
Applications →
Atikmdag BSOD upon AMD driver installStarted by anujsingapore , 11 Dec 2020 ATIKMDAG.SYS, BSOD, BLUE SCREEN and 2 more... |
|
|
||
|
Security →
Virus, Spyware, Malware Removal →
Random ShutdownStarted by Sirius Black , 01 Mar 2019 Windows 7, blue screen, shutdown and 2 more... |
|
|
|
Retired Forums →
Windows Vista and Windows 7 →
Frequent BSOD shut downsStarted by ColtsFan18 , 08 Feb 2018 BSOD, Crash, Shutdown |
|
|
||
Retired Forums →
Windows Vista and Windows 7 →
blue error screenStarted by jc0987 , 07 Feb 2018 blue screen, blue error screen and 5 more... |
|
|
||
Retired Forums →
Windows Vista and Windows 7 →
[HELP] Blue screen random shutdown (tcpip.sys problem)Started by Hatsumo , 20 Nov 2017 bsod, tcpip.sys |
|
|
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users