The first scan found corrupted files, rebooted, second scan said it didn't find any integrity violation. Not sure if its related, but after the reboot a custom windows theme I had was removed entirely.
Blue screened again, 0x0000007a, this time I decided to try launching a game.
Last edited by Isley; 11 Nov 2015 at 14:26.
Just to note, I am and have suggested a few things that are usually causing the crashes.
This because the 0xF4 and 0x7A you have had, usually doesn't reveal much for me to really pinpoint the cause.
Diagnostics Test
Malware scan
Please run a threat scan with Malwarebytes*, a full scan with your AV, scan your system with Adwcleaner, Kaspersky TTDSKiller, ESET Online Scanner and SuperAntiSpyware
Note*(Uncheck trial version in the installation process)
Diagnostic Test
RAM TEST
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums
Note
MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
Right, I was just saying what the stop error was incase it would help. I've removed everything you noted was a potential cause minus the drivers installed via Tweakbits since I have no idea which it updated outside one audio, which I removed. At this point do you think it'd work to just replace my ssd/hd/ram?
I think it would be worth it as a rush choice that could be a waste of money.
No, I don't think it would be worth it to replace them. What if the crashes persist after replacing them? Replacing the motherboard, PSU and everything else?
My point: please don't (yet) replace anything that is not for sure the cause, because the risk that it is a waste of money would be great.
I am only suggesting things out of my experience with debugging, but I have no other lead.
Please try running the tests and see how it goes.
Its more just in case it keeps persisting assuming the above tests don't show anything at fault. I'll post back once the memtest is done.
If the above tests don't give any results, there are other things to tryBut it would depend mainly on what stop codes you get.
When you get another BSOD, it is requested to run the DM Log Collector tool and upload the zip file. Also please give some description of what you were doing and what happened
Alright so I ran all the cleaners, restarted after they finished and tried to launch a game. I didn't blue screen but it closed followed by everything I had open giving me an error box until it was all closed. Then I ran the memtest, 8 passes with no errors. I restarted and tried launching a different game, and the same happened followed by a bluescreen that didn't provide a dump, but was 0x0000007a. I had to unplug my HD again and decided to leave it unplugged and haven't had any crashes of any kind since.
Also prior to this, my blue screens have happened while in a game, idling, and even a few times logging into windows.
Yeah I don't know. Before when I tried this I didn't have much on my ssd to try while I had it unplugged. This time I moved the game that was causing me crashes to my ssd. I'll post again in a day or so depending on if I crash at all.
With just the ssd plugged in roughly 4 minutes after launching fallout 4 I blue screened. Same 7a as before, no dump was produced. After restarting, my computer said I didn't have a boot device enabled even after started. I had to plug my hd back, restart, then reset and unplug the hd for the ssd to be recognized again.
Tried running it with the hd plugged in. I got an error after it crashed and everything else froze instead of blue screening. 'The exception integer division by zero. 0x0000094 occured in the application at location 0x0077ab2233'. I know it isn't a blue screen but if I don't blue screen that's what shows up.
edit a third time: This time upon crashing with no games open, I got a disk read error trying to restart. After restarting, I was brought to a screen from my mobo saying S.M.A.R.T status bad, backup next to my SSD.
Last edited by Isley; 12 Nov 2015 at 14:50.
Quote