What Driver is Crashing My Pc

EpiclesOf4wesome

Reputable
Aug 31, 2014
17
0
4,510
When I play games, my pc crashes randomly. I have tried a thousand things to fix it, but I can't manage to get it. Bluescreenview shows that it is almost always ntoskrnl.exe +142940 as the crash address, so i'm almost certain its a driver that it causing the crashes. I have tried to use windbg, but i can't understand that thing. here are the dumps:

http://www.mediafire.com/download/25pj7zm9w5cgp1i/Dump.zip

As long as this crashing thing is hanging over my head, I can't play games for risk of losing stuff.
Thanks
 
Solution
You only get POST beeps if the case you are using has a speaker (which is connected with the Front Panel Connector Header). So unless you had something plugged into the speaker output on the FP connector, then no POST beeps.

So it's likely that the HDMI problem was your actual problem and not your brothers motherboard. However it's not in the realm of impossibility since his parts are new and untested.

Rosewill PSU's in general aren't quality PSU's. There are exceptions (such as the HIVE series) but in general they are garbage. EVGA on the otherhand has some very good PSU's, though it's model dependent. Some of their best models are the Supernova G2, P2, GS, GQ, B2 series. Their first B series PSU's are too good as well as the...
If you are certain that a driver is the issue, have a look at this link:

Driver Verifier - Windows 10, 8.1, 8, 7 & Vista (BSOD-related)

Please be aware that you may need to make an adjustment to your system if you are running Windows 8 or 10 as F8 by default won't work to get into Safe Mode so you can disable Driver Verifier. This will return F8 functionality for Safe Mode in Windows 8 and 10, it must be run from an elevated command prompt:

bcdedit /set {current} bootmenupolicy Legacy

Then to return it to the way it was:

bcdedit /set {current} bootmenupolicy Standard


 
Search for reliability history in windows search. It will show you what crashed crashed your PC corresponding to the date. Check the data of at least one week so you have a definite idea of what's causing it. It can be a faulty PSU, since it only crashes under heavy load.
 
Okay, so I had already ran the verifier before, and it ultimately caused me to have to reset windows, but I'm out of options so i tried it and it actually succeded, i think? It came up with this dump:
http://www.mediafire.com/download/7w6zaa6sr3i9z4v/dump2.zip
it shows a logitech driver, which would make sense since it would see more use in games.
As for the reliability thing, it only said things like "windows shut down unexpectedly", so I don't think its going to be useful
Thanks for the speedy replies

edit:
I'm also going to run verifier again, after renaming the lgbusenum.sys to .old
 
Your second dump file points to dxgkrnl.sys which is almost certainly graphics card related.

You haven't give system specs, that might help. Also are you running the latest graphics driver? When did these crashes start or have you always had them? If you are running the latest graphics drivers, you may need to go back a driver version or two to see if that sorts you out.

Make sure you run DDU between driver installs to remove any leftovers after the uninstall. I don't normally recommend using DDU every time, but I definitely recommend it when there is a possible graphics driver issue.
 

My pc specs from the system info panel:
OS Name Microsoft Windows 10 Home
Version 10.0.10586 Build 10586
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name JACOBSPC
System Manufacturer To be filled by O.E.M.
System Model To be filled by O.E.M.
System Type x64-based PC
System SKU SKU
Processor AMD FX(tm)-4350 Quad-Core Processor, 4200 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 2301, 1/6/2014
SMBIOS Version 2.7
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.10586.420"
User Name JacobsPC\smith_000
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.90 GB
Available Physical Memory 5.26 GB
Total Virtual Memory 9.15 GB
Available Virtual Memory 6.26 GB
Page File Space 1.25 GB
Page File C:\pagefile.sys
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
also, I have an r9 270 gpu. I don't know why it doesn't include that in the info


Yeah, I updated graphic drivers, and am updating windows. I've been updating those two every chance I get for the past week. However, I don't know if doing that stuff reinstalls directx, and google is no help in figuring that one out.
I want to say that these crashes began when overwatch came out. As well, i just crashed today while not gaming and it was showing to be caused by ntoskrnl.exe +142940, just like it is when I AM gaming so... idk anymore. I'm considering backing up all my programs and data and just clean wiping my drive and reinstalling EVERYTHING. I'm about to that point. Also, I tried running verifier some more, but it keeps breaking and making a startup-bsod loop with error 0xc000021a, or something like that. I have to go back to a restore point to fix it. I'm gonna keep playing with things and seeing what happens. Is there some way I can just reinstall every single driver in my system cause they all seem to hate me.
Thanks for helping.
 
The start up BSODing is why I suggested the editing of the boot mode. This give the Safe Mode via F8 back to you, this is the only way to turn off Driver Verifier before it has a chance to BSOD again.

As for nuking your OS install from orbit, that is one option, though I am inclined to think that it might not solve your problem. At least for the dxgkrnl.sys BSOD, it's very possible you could have a hardware issue with your graphics card. Though it still could be a driver issue. The driver dxgkrnl.sys isn't part of your drivers and won't be re-installed as part of the driver install.

There is a possibility something in Windows (or even more directly Direct X) has been corrupted. You could try running the System File Checker. It's just a matter of running the following command from an elevated Command Prompt:

sfc /scannow

If it reports back that it didn't find any corruption, then your issue isn't related to a corrupt file. If it returns saying it found some corrupt files and it successfully fixed them, then it may have fixed your issue. If it comes back that it found corruption, but wasn't able to correct them, they try running this command from an elevated Command Prompt:

Dism /Online /Cleanup-Image /RestoreHealth

Make sure you have an internet connection for this command as it uses Windows Update to download replacements for the corrupted files it replaces.
 


Actually, i had it set to f8 safe mode, but it still went blue when I tried. I think it may be because I renamed the directx krnl driver to .old. I'll experiment late.
I'll run sfc and let windows download its anniversary update while im at school.
How could I tell if I have broken hardware? I'm going to be upgrading almost everything by the end of the year, so that would fix that problem, but right now, is there some command, or some way to conclude that it's not software?
Also, my pc occasionally freezes, like stops all output, video and sound, and I can only hard restart it. This mostly happens in games, so I thought that maybe the game overloaded my 8gb ram? However, it has just now froze twice while watching videos online, so maybe not. Might that be a sign of hardware failure?
P.S., "nuking the os from orbit" is now the coolest phrase I have ever heard. I want to put that on a shirt.
 
Yeah, you can't rename dxgkrnl.sys, its a system file. Windows isn't smart enough to attempt downloading it if it finds it missing, just crashes. If you can, try getting to a command prompt and naming dxgkrnl.old back to dxgkrnl.sys. I'm thinking this should stop the BSOD loop. This file is an integral part of the OS and works in conjunction with your graphics hardware. I'm betting that when Windows attempt to take control over of your graphics hardware and initialize the driver, with this file missing, everything goes sideways.

As for testing if it's a hardware issue, the very easiest is testing the questionable component (in your case the graphics card) in a known working system.

As for the freezing, it's possble that the issue may actually be your PSU. Again testing would require you use a known good working PSU in your system to see if it fixes your issues. Unfortunately unless a component out and out dies, it usually requires swapping until you find the culprit. There are certain problems (such as this one) that could have a few different solutions. A borderline PSU could cause all sorts of issues. These types of issues seem to be accelerated / exasperated when under load. So gaming or some CPU have task. Whilst GPU's would tend to crash most often when loaded like gaming. Though failing graphics cards can also act up even on the desktop, or watching videos or Flash content. It really depends on what part of the graphics card is failing.

Failing RAM can cause similar issues, but usually they result in a BSOD. Failing storage can cause all sorts of odd behavior, from long pauses to BSODs, though not usually crashing / freezing until a hard reset.
 

Oh, I already stopped the loop by going back to a restore point.
As for testing harware, I have no other system to test it in currently, but I think my brother is (finally) finishing his rig soonish, so that will probably be my closest opportunity to test everything. However, how much risk would there be in testing in his pc? I'd imagine that the only risk would be the psu, as it could fry his things if it's broken. If I end up using his, what would be the fastest way to test the parts? just play games and see if it crashes?
I would't think that it'd be hardware though, since I never oc, and I use a surge protector that still has some use left in it. However, my room can get a little hot, so maybe a part that just doesnt get cooled enough ended up being fried one day, which would make sense, since it all started when the weather started heating up and I went back to heavy gaming.
Lastly, windows did its anniversary update today, although it sorta broke, and I had to hard restart, but it had already made a save point at 75% install? Anyway, perhaps, since it seemed like a big update to download, it may have updated some core windows drivers. here's to hoping, anyway.
In the mean time, I'm going to run verifier a bit more, and just uncheck any driver it calls out, instead of renaming it. I'll make a list and put it on here.
Thanks
 
If you are testing if it's a PSU problem, you would put a known good working one in you system, don't test yours in his.

As for testing if it's a graphics card problem, you would test yours in another system to see if it displays the same symptoms. Checking your card in his system shouldn't cause his system and problems if the card is faulty.

Unfortunately you can treat your hardware respectfully and it's still might fail. Nearly every product if you were to scrutinize it close enough has some sort of defect. Whether the defect is serious enough to degrade as the product is used or not determines if it will fail. There is always a lemon in every batch.
 


Wow that was a fast reply. Any way. I forgot to say that sfc came back with nothing. also, i just ran verifier a bit more, and it got stuck on iorate.sys, even when I told it not to check that driver. I suppose that means the end of me using verifier to check things. I also think that, since I've gotten about 5 different drivers called out by verifier, all of them almost totally unrelated, this is probably a hardware issue. Windows HAS to be smart enough to make finding a bad driver easier than this. It should be more consistent in the errors if its a driver issue, shouldn't it? I'm going to try to play a few games to see if, perhaps, by the favor of god, lucifer, bhuda, the emperor, my local polterghiest, lord gaben, and every possible holy or unholy being in the universe, my issue has miraculously gone away. if not, I certainly hope my bro can hurry up and by his parts.
Also, i imagine that wattage is fine for my rig, with a 600 watt psu, 4350 cpu, r9 270 gpu, fans, 8gb ddr3, hard drive, and few odds and ends? I certainly hope that my issue is as simple as a crap psu. ALSO, my hard drive is sorta almost broken at the sata connector, but it has been taped together very securely and reliably for 2 years before this issue. Could it randomly be disconnecting that is doing this?
Thanks, again
 
Okay, so I played more overwatch, and for a while it didn't crash. Then, it froze once and crashed the next game. I give up. My brother should get his parts sometime in the next month, hopefully, and i'm planning to get the am4 generation of amd mobo and cpu, which will be in january. In the meantime, i think i'm going to 'nuke the os from orbit', as you say. It's my only choice, now, and I'm sorta desperate to just be able too play. Although, I HAVE only tested with overwatch, but I assume that, if it were OW, it would just crash the game, or freeze. Maybe i'll test with something else.
Thanks for the help, I at least now know what my options are.
 
Okay, so I think i've found the issue, more or less. I did some stress testing on my gpu, using unigine's valley benchmark. That brought no warning after about an hour or two of using it and watching videos. I then used prime95 to test the cpu, and that thing made errors in 12 minutes, and about 30 minutes on the second test. My thought was that it would be the cpu being broken, so I swapped it with the cpu my bro bought, which happens to be the same model. I tested with it, and it still broke, so I thought it'd be ram. I ran memtest86, and it got errors. I switched my two 4gb sticks to be in the secondary set of dimm slots. I ran prime95, as its easier than memtest, and it still did it. I tested both sticks individually, and they both still broke prime95. At this point, i think that its the mobo. My bro also bought his mobo already, so i'll test with that tomorrow, as I'm currently dead tired.
Am I right in my thinking that its the mobo? Could it still be the gpu, even though there were errors in memtest? could it still be my psu? I'll report back with the result of the mobo switch.
Thanks
 
Well now since we are looking at a possible hardware issue, maybe we should have some detailed specs on your system. CPU, RAM, motherboard, etc, and Windows version.

It's difficult to say, but since you didn't seem to have any issues running Unigine Valley, it's likely that your GPU is OK.

As to the Prime 95 errors, what sort of errors are you getting. Do all the threads error? Or just one?

Memtest will typically isolate RAM issues, but it can be affected by bad power too. I've never seen it myself, but years ago I was troubleshooting a BSOD issue with a OCZ RAM kit. I was getting BSOD's, and one of the OCZ Reps told me that certain tests failing could point to a bad PSU. However it's my belief that he was stalling on giving me an RMA number (which he ultimately did) but it turned out that it was the RAM. There is the motherboard to consider too, as this provides power to the RAM, and the PCB itself could be faulty (though this would likely cause the board not to POST).

Another thing to consider with RAM issues, assuming you have a newer Intel system (anything released after 2009) or an AMD system, the IMC (Integrated Memory Controller) could play into it. However since you've tried your system with your brother's CPU, that isn't likely it.

So waiting on your system specs. It could be related to your BIOS settings.
 

Okay, so first. I ran more experiments. I switched the mobos, and...nothing. It didn't even post. So, my conclusion was that it was the psu. I ran out today and bought another one, and tried it again with my bro's cpu, ram, and mobo. It still didn't post, or at least i don't think it did, as it never beeped at me, but, when I switched it back to MY mobo and cpu, I had to replace the hdmi cord, because it wasnt working, so his board might have been fine. ANYway, im testing the new psu in prime95, and I'm awaiting results.
As for my pc specs:
vishera 4350 cpu (both mine and bros)
r9 270 gpu
2x4gb 1666 ddr3 ram (mine), 1x8gb 1666 ddr3 ram (bros)
asus m5a97 le r2.0 mobo (mine), msi 970a-g46 mobo (bros)
rosewill rd600 psu (old), evga 600w (new)
windows 10, version 1607, build 14393.187

prime 95 would come back with max number of warnings, various errors, pc freezes, and bsod.

thanks
 
You only get POST beeps if the case you are using has a speaker (which is connected with the Front Panel Connector Header). So unless you had something plugged into the speaker output on the FP connector, then no POST beeps.

So it's likely that the HDMI problem was your actual problem and not your brothers motherboard. However it's not in the realm of impossibility since his parts are new and untested.

Rosewill PSU's in general aren't quality PSU's. There are exceptions (such as the HIVE series) but in general they are garbage. EVGA on the otherhand has some very good PSU's, though it's model dependent. Some of their best models are the Supernova G2, P2, GS, GQ, B2 series. Their first B series PSU's are too good as well as the first G series.

What is the make and model of your RAM? I'm not aware of any DDR3 1666 RAM, only DDR3 1600 or DDR3 1866. Maybe if you could provide a link.
 
Solution


I plugged the little speaker that comes with thee motherboard into the appropriate connector, however, I used the one from my mobo, as I couldn't find his, though i found it today. It could just be that my speaker won't work with his mobo.

Oops, I didn't even look at my ram. The brand is Teamgroup, and its vulcan orange , 4gb 2133. I can't find a page for it anywhere, but this is the closest thing to it: http://www.newegg.com/Product/Product.aspx?Item=N82E16820313353

As for the new psu, it didn't show errors in prime95 after around 45 minutes, and I also played a bunch of overwatch without failure, so I think that might have been the problem, especially if rosewill is as bad as you say.

Thanks
 
I would take a look in your BIOS and make sure that your memory settings are using either DDR3 1600 or DDR3 1333. According to AMD's site the IMC is guaranteed to work up to DDR3 1600 when in single channel mode, and DDR3 1333 in dual channel mode. It's quite possible that it'll work at higher speeds if you motherboard supports it, but if you are having troubles you should start with everything at the nominal values. With a memory speed of 2133, it's most likely that it's an XMP profile, though it could be an AMP profile if it's designed for AMD systems. Either way, you don't want to be using this profile while troubleshooting as it could be what is causing your issues.

That's not to say that it isn't your PSU or motherboard, just one thing that came to mind once you told me that your memory speed supports non-JEDEC standard speeds. I would certainly consider running Memtest again just to be sure. While it's great that it appears to be more stable, since your memory seemed to consistently fail regardless of the memory configuration, it's definitely something you want to check again with the new PSU to see if it's resolved that. The other issues you were seeing seemed more random and may take longer to reappear.