This issue just recently started to happen, and I cannot for the love of god troubleshoot it or fix it.
Most games run just fine, but so far the games that I've tried that cause this bsod are Sleeping Dogs and Dishonored. It can happen from anywhere from 15 minutes to 45 minutes into gameplay. It is a 0x0000001e error code. I would post a dump file, hell I would look at it myself, but for some reason Windows just refuses to generate one after bluescreening, and yes I [I]have[/I] enabled dumps. I'm also running Windows 7 home premium 64-bit, if that helps. I did a memory check on startup and there were no issues, so it's not a RAM problem.
I tried updating to the newest nvidia beta drivers, but the problem still persists. And why would it only happen in specific games?
[url]http://www.nirsoft.net/utils/blue_screen_view.html[/url]
Download, run, it's safe. If you're getting a BSOD, it'll be here. The topmost is most recent.
Does it mention a file name, or just 0x0000001E?
I've already tried that. Nothing shows up, there's nothing in the Minidump folder (hell I even had to make the folder myself).
And no file name, just 0x0000001E with some assorted other 0x00000 whatever numbers.
when you reboot after a bsod, a window should popup saying it had a bsod, scroll down till it says additional details, and go to the 2 directories
I would go back to stable Nvidia drivers (you may need to go a few versions back as apparently Nvidia recently shipped a real shit build). Also, monitor your GPU and CPU temps; overheating shouldn't cause BSODs (those say fuck you and shut right [I]off[/I]), but it might give you an idea.
Does it give any sort of error message in plain English? e.g.
[code]STOP: 0x0000001E (0xC0000005, 0xFCA733B9, 0x00000000, 0x00000000)
KMODE_EXCEPTION_NOT_HANDLED 0xC0000005 from 0xFCA733B9 (0x0, 0x0)Address FCA733B9 has base at FCA70000 - SRV.SYS[/code]
I'm more focusing on the "KMODE_EXCEPTION_NOT_HANDLED" part than the filename at the end (since you've already said there isn't one).
I don't get a window after rebooting. I just login like normal.
When I BSOD'd during Dishonored, I got that bootmgr is missing shit, but I managed to repair it with my Windows 7 disc. Hasn't happened since, but I haven't tried Dishonored again. I've only been replicating the bsod with Sleeping Dogs.
[editline]3rd August 2013[/editline]
[QUOTE=elixwhitetail;41704478]I would go back to stable Nvidia drivers (you may need to go a few versions back as apparently Nvidia recently shipped a real shit build). Also, monitor your GPU and CPU temps; overheating shouldn't cause BSODs (those say fuck you and shut right [I]off[/I]), but it might give you an idea.
Does it give any sort of error message in plain English? e.g.
[code]STOP: 0x0000001E (0xC0000005, 0xFCA733B9, 0x00000000, 0x00000000)
KMODE_EXCEPTION_NOT_HANDLED 0xC0000005 from 0xFCA733B9 (0x0, 0x0)Address FCA733B9 has base at FCA70000 - SRV.SYS[/code]
I'm more focusing on the "KMODE_EXCEPTION_NOT_HANDLED" part than the filename at the end (since you've already said there isn't one).[/QUOTE]
no plain english. All it gives me are the number codes. At first I thought maybe my CPU didn't have enough power for the GTX 780 I just installed, but these issues were happening before on my old graphics card, so that's definitely not the case. 750w should be enough for anything, anyway.
Bootmgr is missing is a different sort of brain damage. I'd see if there are updates for your other drivers, like sound, keyboard, mouse, etc, if it isn't happy with any Nvidia driver versions you switch to. I'd also run malware scans and stuff just in case.
I tried uninstalling that Razer Synapse shit, since I heard it caused BSODs for some people, but that didn't do anything. Didn't bother with keyboard drivers since I've had the same ones forever and things have been just fine, and I use onboard sound so that should be fine too. I might do an Avast scan and see if it's some nasty virus or something (man do viruses even still exist?)
Viruses do, but mostly as spyware and shit. I'd suggest giving MalwareBytes Anti-Malware a try (the free version of MBAM is sufficient), and you might also want to give Gmer a run. Gmer checks for rootkits, and for our purposes, if you open Gmer and 5 minutes later none of the text in the main window (if there is any at all) is red, you're good.
I really dunno, though, with that little to go on with the BSOD. It could be a number of things and if the computer's not saving dumps, it's pretty hard to figure out what.
Do you recommend running those in safe mode, or is normal windows fine?
Normal, but if you get even a single suspicious hit, you might want to run scans in safe mode to try and dig up everything if something's gotten into your system.
Obviously, hits excluding things like tracking cookies and shit. :v:
I should probably also mention that my processor is an i5 2500k that is overclocked to 4.5 GHz. I have a good cooler to help, and games worked just fine a few months ago even with it overclocked. Could it have something to do with this?
I would [I]definitely[/I] put it back to stock clock timings to see if the BSODs stop. If they do, try overclocking to 4 even. The games might've gotten updates that, as a purely unintended side effect, don't like your particular system's unique alchemy when you're oc'd to 4.5GHz. Or... something.
I really am throwing darts at the board here, because a single, pretty generic-ass BSOD error code (0x1E is basically "shit fucked up") isn't giving us much, so I apologize for not being able to give more precise suggestions or instructions.
okay, so I didn't get any hits with those scans (which I guess is good!). I decided to play some Sleeping Dogs again to try and bsod.
I decided to check my temps while I was playing, and apparently my CPU was pushing upwards to 130F degrees. I'm guessing that's [I]not exactly good[/I], right? Could high temps cause BSODs? And if so, why only in specific games? Or am I just going on a tangent.
When running a reasonably intensive game like Sleeping Dogs, 130F is prooooobably about where you want to be sitting at to be comfortable, so that's not as much to worry about -- especially if you're still clocked at 4.5GHz. In other words, if you didn't change the clocking at all, your cooling is doing its job. You'd have reason for concern if you start pushing past 140-145F and there isn't some other reason (it's like 700F in the house because of a once-in-a-century heat wave, for example).
Okay, so that means my OC should be okay.
I'm gonna try completely cleaning my Nvidia drivers with driver sweeper and the whole lot, and see if a fresh driver install will change things.
I would take it back to the default timings anyway, just to eliminate it as a possible source of problems.
Not for any overheating issues, but just for the actual running of the program. I'm speculating pretty hard here, but unless it's just Nvidia drivers/Sleeping Dogs and Dishonored just hate your face, the big overclock might be interacting in some bizarre way that ultimately makes the machine shit itself.
To give you an analogy to explain what I mean, consider a standard SUV. It's rated for safety based on its stock configuration. Now replace the motor with a really bitchin' powerful motor taken from a Bugatti Veyron or something ridiculous like that. Ignoring problems like how would that even work properly, the extra speed and acceleration that this new motor is capable of putting out means that you're probably going to be rolling this thing all over the place if you try and actually [I]use[/I] even some of that new power. Under ordinary circumstances (with a stock engine), the SUV is safe, but shit turns catastrophic at random if you change the engine up dramatically.
I'd pin my money on the graphics drivers, but downclocking is fairly painless and less invasive than ripping drivers out.
Well, driver sweeper + re installation didn't do jack. Same shit. Took a picture of the screen this time. Notice how it says it makes a log, yet the minidumps folder remains empty.
[img]https://dl.dropboxusercontent.com/u/16550652/fucking%20windows.jpg[/img]
Huh. Two things:
1) Make sure the permissions on c:\windows\Minidump are set to give both Administrators (the user rights group) and SYSTEM [B]Full Control[/B]. I imagine this shouldn't be a problem, but there's a slim chance the permissions are set up wrong and Windows can't write dumps to the folder because it doesn't have the perms. Not likely, but easy to check.
2) Open a Command Prompt window as Admin and run this: sfc /scannow
Scan didn't find any problems.
I did some more thorough memory tests with memtest last night, and no errors came up. If it's not the RAM or anything else, I'm thinking it has to be some sort of device driver. I'm gonna go through device manager and try disabling things I don't need.
Try running some of the really intensive benchmarks on looping mode to see if you can get those to trigger a BSOD the way the games do?
any benchmarks you could recommend?
[URL="www.ozone3d.net/benchmarks/fur/"]FurMark[/URL] is apparently rather punishing and specifically tries to overheat the GPU by pushing it to its limits. Your cooling should be fine, and we're not trying to trigger an overheat, but we're trying to trigger load.
However, I do suggest monitoring the GPU and CPU temps while you run. The temperature should stay normal, but we want to eliminiate overheating from the equation. There are plenty of things that could go wrong when the machine's under heavy load (like, a game), and the more we can narrow it down, the better.
Probably not malware.
Probably not the temperature.
Probably not faulty ram or other hardware.
Could be the overclock if you haven't tried it without (you haven't said anything either way)
Changing Nvidia drivers didn't help, but it might be other drivers.
If your machine has a RAID array of any sort, make sure the RAID controller's drivers are up to date. I really don't understand why a consumer PC would have a RAID these days, but I've seen weirder.
Don't have a RAID array, and I haven't tried downclocking yet (mostly because I kinda forgot how to change it on my bios).
[editline]4th August 2013[/editline]
Ran the benchmark a few times at 1080p, seemed to run just fine. Highest temp the GPU went was 69C.
Well...I think I fixed it. I just went through an entire hour or more of Sleeping Dogs without a BSOD.
I went through device manager and uninstalled any devices that weren't being used, mostly human interface ones. I also uninstalled Geforce Experience, if that had anything to do with it. I updated daemon tools, but I really doubt that did anything either. Must've been uninstalling one of those devices.
Weird, but, sounds like it did ultimately come down to drivers, just random-as-fuck ones. Computers, y u gotta make our lives so difficult while making our lives better?
Sorry, you need to Log In to post a reply to this thread.
