Solved BSOD at seemingly random times, typical refer to ntoskrnl.exe

[hdt80]

Hey there, I've been trying to solve a BSOD problem I've been having for quite a while, and decided to ask here for some help. The BSODs as far as I can tell, happen randomly. I could be watching a YouTube video and I get a BSOD, I could be talking to people on TeamSpeak and I get a BSOD, I could be playing League of Legends and I get a BSOD.

I've ran memory test over night, getting 9 passes in with no errors. I've reinstalled my graphics driver follow this. I've also ran Furmark following this tutorial for 30 minutes without the temperature ever raising above 80°C.

While trying to figure out why I have been receiving BSODs I noticed something odd about my memory usage. If I total up my total memory usage using tasklist I get that about 3GB of RAM is being used, but if I check physical memory in Task Manager it says 29% of memory is being used, and with 16GB of RAM installed, 29% is about 4GB. I don't know if this extra GB could be a problem or even the cause of my BSODs, or it isn't an issue at all, but I thought it wouldn't hurt to mention this.

Attached is the DM Log Collector. If you have any ideas, or things that I should do, please let me know. I'm getting mildly frustrated with these BSODs and would really appreciate any amount of help.

 

[Arc]

Hi hdt80.

A lot of different errors are showing up. A good proportion of that lot is pointing to the Mad Katz R.A.T.5. Mouse and the Keyboard.

fffff880`0313f568  fffff880`05fae514Unable to load image \SystemRoot\system32\DRIVERS\SaiK1705.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SaiK1705.sys
*** ERROR: Module load completed but symbols could not be loaded for SaiK1705.sys
 SaiK1705+0x2514

I would suggest you to use any other Keyboard-mouse to see how it goes .... as least it stops the keyboard-mouse related issue (as reported in the logs) or not.

It may needed much more further actions.

 

[hdt80]

Hey Arc, thanks for the response.

I purchased the R.A.T 5 mouse about a week ago, and BSODs occur well before that. That could fix this one issue, but I don't know if the same error occurs before last week.

I will try using a new keyboard and my old mouse and if I get BSODs using that, I'll try a new keyboard and a new mouse. If I continue to receive BSODs after using the new keyboard and mouse I'll run the log collector again and report back to you.

I also have a little bit more information that might be helpful, or not. While trying my hand at reading .dmp files following this post I noticed in some .dmp files on my computer it says that the cause is something to do with ownership locks. For a while now, rarely, when trying to delete files or folders I am shown this dialog and cannot delete the folder, even after providing an admin's password. In this instance I am trying to delete a folder on my thumbdrive with this as it's contents. When I click "Continue" I receive this dialog. Clicking "Try Again" will keep showing this dialog over and over again so I decide to come back later and try again. Although the folder I'm attempting to delete is different when I click "Continue", the dialog is the same for all folders/files I'm trying to delete. Typically some time later, in this case with TI-Connect ~3 minutes, when I attempt to delete the folder/file again the folder/file has been deleted and is in my recycle bin.
Although the example I provided used a file on my thumbdrive, this also occurs on both my C: and D: drive, both of which are hard drives. I don't get this issue when attempting to delete files off my thumbdrive on any other computer, regardless of the OS running or the port the thumbdrive is plugged into. I believe it might have to do with my Anti-virus, Microsoft Security Essentials, but other then that I have no clue.

I really appreciate your help, and keep being awesome .

 

[Arc]

Hey Arc, thanks for the response.

I purchased the R.A.T 5 mouse about a week ago, and BSODs occur well before that. That could fix this one issue, but I don't know if the same error occurs before last week.

I will try using a new keyboard and my old mouse and if I get BSODs using that, I'll try a new keyboard and a new mouse. If I continue to receive BSODs after using the new keyboard and mouse I'll run the log collector again and report back to you.

That will be very good, mate. It will eliminate a lot of noise in the reported issues and will help to find us the exact root of the issue.

 

[hdt80]

I went back to my old mouse that was laying around, and removed any driver related it this. BSOD
Double checked for all drivers, found none, and found a different keyboard laying around. BSOD
Since then I have had 4 more BSODs, on the 20th-22nd. All with different mouses and keyboards I found laying around.

While looking at other users who had issues with nt!KxWaitForLockOwnerShip I ran across another thread that talked about memory voltage, and I remembered that I have two different timings on my RAM. Could this be an issue? If it is, is there any instructions I should follow? I don't want to mess this up.

I've attached the DM files again, and thank you so much for you help.

 

[Arc]

Yes, memory can be the issue, and it is not to use two different sets of RAM at the same time. You should remove either tow to see how it goes.

Out of interest I took a look at this page ..... 970 Extreme3 Memory Support List. None of these models are listed there as supported.

 

[hdt80]

I tried testing each set of RAM individually over night using MemTest86 each getting in more then 8 passes with no errors. When I first built my computer I used this set (pair?) with no problems. The first BSOD according to event viewer is from 4/11/2014, however I don't seem to have a .dmp file from there, and then there is a two month gap between the next one, at 6/24/2014, and after that date BSODs occur every couple of days. I installed the second set of RAM on 12/19/2013, 5 months before any BSODs and 7 months before I received repeated BSODs. If that could cause any issues 7 months later, I would be very surprised.

If you have any other things you'd like me to try, I'd happily try them. Thank you for your help

 

[Arc]

I tried testing each set of RAM individually over night using MemTest86 each getting in more then 8 passes with no errors.

That is an inferior tool to test RAM, and not trustworthy.

If you want to test the RAM, follow http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run memtest86+ for 8 consecutive passes with all the RAM modules .... that will be a meaningful result. If errors are found, then and only then try to test individual sticks.

 

[hdt80]

Alright, I'll try that one tonight, and let you know if any errors occur. Thank you so much for your help.

 

[hdt80]

Sorry for the delay.

I'm having difficult creating a bootable USB as the first one I got my hands on isn't working with any version and I cannot find another USB lying around. I'm still trying to get back to you and haven't forgotten about getting back to you. I'll get back to you once I find a USB that works.

 

[hdt80]

I have gotten more BSODs, and tried my own hand at reading them, and want to get an experts second opinion on them. From what I can see, the latest one (11/7/14) was caused by dxdmms1. From the module list I'm told that dxgmms1 was installed April 9th 2013, which sounds about the time my BSODs started occurring.

I don't know if I have read the .dmp correctly, so I'd like a second opinion on it. If it is dxdmm1 causing the BSODs what steps should I take from here?

I also ran the superior RAM test, getting 31 passes over 7 nights, all with no errors.

Sorry for the delay, and thank you so much for your help

 

[Arc]

BugCheck 1000007E, {ffffffffc0000005, fffff800032ff622, fffff880021fa2e8, fffff880021f9b40}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31 )

Followup: MachineOwner
---------

This BSOD means there is something wrong with the graphics environment. The first two suspects are the display driver and the graphics card (not DirectX).

You are using 344.11 WHQL which causes BSODs of the same nature in a number of systems. Uninstall the installed display driver using Display Driver Uninstaller.
Then download and install 340.52 WHQL.
Follow NVIDIA Drivers - Avoid Problems to have a perfect and clean driver installation.

When the suggest driver is applied, stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Also, as you are having various different BSODs with varying probable causes, and you confirm that the RAM is free of errors, update the BIOS to version 1.80 (the applied version is 1.70). Get teh BIOS update from ASRock > 970 Extreme3

Let us know the results.

Scope is gradually minimizing, and the situation is not feeling very good to me.

 

[hdt80]

Alright, I've uninstalled 344.11 using the link you provided, and installed 340.52.

I ran Furmark, with the tempature peaking at about 77°C. I've attached the screenshot right before closing. I also checked log GPU data, but I don't know where that is located.

I updated my BIOS from the link you provided, and installed perfectly.

Thank you so much for you help

 

[Arc]

OK, let us know For any further BSOD.

 

[hdt80]

I haven't gotten any BSODs this past week doing anything that normally gets me a BSOD, so I'd say the problem was fixed.

Thank you so much for your help, I really appreciate it.

 

[Arc]

You are welcome.