I have finished reading the HWINFO64 log, it doesn't give any clues to extraordinary loads comparing the first few lines with the last (right before crash). It will be more useful if you still have the freeze error after the iastora issue is solved. Here's a cleaned up excel sheet if you want it: https://drive.google.com/file/d/0B1KaSmm1I4TecnZxLTlNTjdCcGs/view?usp=sharing Could be. I've read about twenty different help threads now from MS on this type of error. I can't find anyone who has this exact bug code: iastora.sys 0xD1 (0x70, 0x2, 0x0, 0xFFFFF880012A9195) The most common remedy is to update drivers (primarily the Intel RST) and hope it is not a hardware failure as the root cause. http://www.sevenforums.com/general-discussion/276161-bsod-irql_not_less_or_equal-storport-sys.html
I was reading that doing a flash update on the BIOS is the easiest way to update the iastora.sys "thing" (technical term, shut up), and I grabbed the latest flash update for my chipset, but was having issues getting the computer to recognize it from the flash drive, and had to come to work. I'll get it updated sometime tomorrow when I get home, and then leave it going to see if the BSOD stuff stops. As such, I've updated the title of this thread to "Upgrading my video card and general PC clusterf*^%" This was supposed to be such a simple thing, and it's exploded into so many random problems. This is why I hate looking at my components, I'm cursed!
Had this happen to me with one of my older systems. It was a RAM issue with mine causing corrupt files even though everything checked fine. If you have some spare RAM laying around I would switch out and see if that stabilizes things. If it works at least you know where your problem is.
Feeling that pain mate, I had a years worth of issues with my tri-crossfire setup. Hope I can help a bit at least. True, this can be a hardware failure but it's a good idea to try the drivers first before pulling apart the PC. Eliminate the possible software issues first, then do hardware (since it's also potentially more expensive).
To test ram, use memtest86+: http://www.memtest.org/ To test CPU, use prime95's torture test overnight: http://www.mersenne.org/ To test video memory, use VMT: http://mikelab.kiev.ua/index_en.php?page=PROGRAMS/vmt_en To test GPU, use Furmark: http://www.majorgeeks.com/files/details/furmark.html Other things are harder to test through software.
Well, I went to bed hopeful today, but woke up to disappointment Flashed my BIOS and updated them, but it still blue screened while I was asleep...seems to happen after about 113 or so minutes, give or take, each time...just wish there was a way for the computer to tell me exactly what it was doing when the problem occurred, and what caused it in detail. But computers, so no. It did give me a new dump and log file at least >< http://www.filehosting.org/file/details/469266/011015-43898-01.dmp http://www.filehosting.org/file/details/469267/Log 7.CSV
Grrr...so ran the verifier.exe program to check all my drivers, and that caused a BSOD on startup instead, and had to rollback repair the system to get it to come back on at all, so that didn't work It said it created a .dmp file, but nothing was there when I got back since it did the rollback, so shit. Durandal is getting upset. At least my laptop still works nicely...
Memtest, VMT, and Furmark all came up empty...will try the torture test when I go to bed, but seeing as it blue screens every couple hours, I don't know if it will be able to run long enough before it reboots itself. Been experimenting with different things to no avail...can't figure out what's going on
Hmm...I will check the two files after work tonight, but from the pic - it's a new one. Durandal, if I recall correctly, HWINFO64 can also output a massive HTML report on your system. If you are willing to send it to me I can get more info from it, component names, driver versions etc. I can check for known component failures or issues. Be warned though, it contains your IP and a LOT of info on your hardware so do a email to [email protected] and not a open link. Sure, it can be the PSU causing quite a few different errors. But I'm not convinced it's just one thing. At this point, I hope Durandal has saved data externally..
I do have an external HD where I tend to keep anything important. In the worst case scenario, if the whole PC dies, that'll save everything except for game installs/saves that aren't on my steam cloud Didn't smell anything burning inside the case, so that's nice. Popped off an email of the report to you.
Well, I did some windows updates, ran a disk check on my C drive, and did some other things...and it seems good. 5+ hours with no BSOD. Here's hoping...
Uninstall your Intel rapid storage driver and any other RST stuff. I'm not sure what it does other than muck everything up. Seen it on a half dozen computers before (source: I am a certified hardware tech) If you don't want to do that, swap in a spare hard drive and do a fresh install of windows with JUST chipset video and sound drivers and see if the game still crashes. The game is also CryEngine which uses a lot of tessellation and other tech, could always try reverting a factory overclock on your GPU (if it has one).
I'll wait a bit with searching for data on your hardware until we see if you've manage to solve things.
Never did get a BSOD yesterday. Will see if anything happens today If not...I can get back to wanting greedy video cards!
But I can only get 498 porn videos running at the same time before they start ending! I mean...wait, what?
Figured I'd pop an update in, I'm starting to think that whatever was causing the blue screen problem must have been related to something that Windows auto-updated on my system. Since the 13th, I haven't had a single blue screen (despite doing a lot of stress tests), and several things were updated since then, so it's been the likely culprit. Since the problem went away, I'm just hoping that it sticks Now I can go back to wanting expensive upgrades, mwahahaha!!!
Sounds like it could have been a driver thing, as was suspected with the first error. Strange you had others which now is gone by themselves, sometimes errors are linked but give the appearance of other issues I suppose. I'd hang onto all the logs and software, just to be safe.