New
#11
Hmm weird. I've had a few bluescreens.
RE posting SF tool logs again. Could you please look over again. Thanks a lot.
This should solve the issue. Hope it's not ram related.
Hmm weird. I've had a few bluescreens.
RE posting SF tool logs again. Could you please look over again. Thanks a lot.
This should solve the issue. Hope it's not ram related.
Whoops double post.
In the mean time I actually got a Tcpip.sys BSOD.
Last edited by Mushroom; 17 Nov 2013 at 00:04.
Thanks for the update :) .
The last three bug checks are quite similar to the first, and all seem to have a driver misbehaving
so we need to turn to Driver verifier to hopefully help in uncovering the culprit(s).
Follow this post to enable Driver Verifier:
Also the MSinfo32 file is empty again,
Please confirm you have these services running and active:
Security Center, IP Helper, Windows Management Instrumentation.
> Services.msc > hit enter.
Then follow,
Please upload the MSINFO32 file:
Start → Run → type MSINFO32 then hit Enter.
In MSINFO32 go to, File → Save → name it your user-name.
Once the file is saved right click it and choose Send to → Compressed (zipped) folder.
Attach the file in your next post.
Ok. did driver Verifier. Was getting BSOD C4 message which was NVLDDKM.sys, constantly and wouldn't log on to windows.
Hi thanks for the update :) ,
the new dumps aren't in the file uploaded please manually check the minidump folder.
If dump files are present in that folder copy them to the Desktop, zip and upload in your next post.Code:C:\Windows\minidump
NoteBefore proceeding with the installation of the new driver DISBALE DRIVER VERIFIER.
Follow this post to disable Driver Verifier:
After a couple of complete restarts to the PC enable it again.
Follow this post to enable Driver Verifier:
Good job on catching what the the code and accused driver were :) .
nvlddmkm.sys is an nVidia driver for that reason please try the latest WHQL
driver, installation in the manner detailed in the quote below.
Let us know how it went.
Ok did the Nvidia thingy. Hope all goes well. Here are my Dmp's.
Ok. Ran into a bit of an error. I did everything you said with the Nvidia driver thingy.
turns out if I do anything with the Nvidia Geforce experience (opening the program). Will result in a BSOD. the once I described before.
So ignore my old DUMPS.. Please check these ones out.
Yep Driver Verifier doesn't like nvlddmkm.sys trying to corrupt the system, especially using
nvspcaps64.exe which is GeForce Experience.
In your next post, follow the posting instructions instead of posting only the dumps.
Did you follow the settings detailed in the linked post completely?
Please verify the drivers selected for DV to stress.
Run an elevated command prompt and type in verifier /query.Start Menu> CMD - right click and Run as administrator.Disable DV and uninstall the nVidia drivers.
Type verifier /query hit Enter and post a screenshot of the window.
Use the integrated graphics then enable DV the same manner as before, keep it for a couple
of days and post back with any new dumps or reporting a stable system.
Ok it appears that it's not the only error occurring. Audio some times cut out etc.
Check out these new logs please .
Hope it all makes sense.
Hi :) .
Please disable DV now. - Driver Verifier - Enable and Disable
Driver Verifier consistently found nvlddmkm.sys performing illegal calls which comes down to a driver
issues which needs to get patched with the next update from nVidia, since you're using the latest
(at the time of typing this) WHQL release there's not much you can about that
at the moment unfortunately :\ .
Code:DRIVER_VERIFIER_DETECTED_VIOLATION (c4) A device driver attempting to corrupt the system has been caught. This is because the driver was specified in the registry as being suspect (by the administrator) and the kernel has enabled substantial checking of this driver. If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will be among the most commonly seen crashes. Arguments: Arg1: 00000000000000f6, Referencing user handle as KernelMode. Arg2: 00000000000001b8, Handle value being referenced. Arg3: fffffa801789c8d0, Address of the current process. Arg4: fffff8800f158a6d, Address inside the driver that is performing the incorrect reference.The other driver that DV found to be offensive is one mentioned in my post in this thread,Code:4: kd> k # Child-SP RetAddr Call Site 00 fffff880`0e735908 fffff800`033514ec nt!KeBugCheckEx 01 fffff880`0e735910 fffff800`03366bf4 nt!VerifierBugCheckIfAppropriate+0x3c 02 fffff880`0e735950 fffff800`0311e890 nt!VfCheckUserHandle+0x1b4 03 fffff880`0e735a30 fffff800`031781a5 nt! ?? ::NNGAKEGL::`string'+0x2027e 04 fffff880`0e735b00 fffff800`02ec3e53 nt!NtSetValueKey+0xe1 05 fffff880`0e735c30 fffff800`02ec0410 nt!KiSystemServiceCopyEnd+0x13 06 fffff880`0e735e38 fffff800`033554db nt!KiServiceLinkage 07 fffff880`0e735e40 fffff880`0f158a6d nt!VfZwSetValueKey+0x6b 08 fffff880`0e735e90 00000000`00000008 nvlddmkm+0x9aa6d
It's doing so even after the update.Code:BugCheck 50, {fffff6fc40c5db58, 0, fffff80002f8f565, 2} *** WARNING: Unable to verify timestamp for Ak27x64.sys *** ERROR: Module load completed but symbols could not be loaded for Ak27x64.sys Could not read faulting driver name Probably caused by : Ak27x64.sys ( Ak27x64+1a11a5 )
A new offender that DV found was your Razer Naga try not to use it for the coming days and see how things are going.Code:lmvm Ak27x64 Browse full module list start end module name fffff880`0482d000 fffff880`04c3b000 Ak27x64 T (no symbols) Loaded symbol image file: Ak27x64.sys Image path: \SystemRoot\system32\DRIVERS\Ak27x64.sys Image name: Ak27x64.sys Browse all global symbols functions data Timestamp: Wed Sep 04 22:37:23 2013
On top of that please update your USB host controller.
Please clean your start up, - Troubleshoot Application Conflicts by Performing a Clean Startup
Please test your RAM:
Testing the RAM:
When done with the testing procedure take a picture and upload it here.
Let us know :) .