Been having random blue screens, minidumps attached.

I've been having a few bluescreens the last few days, it seems to happen at random but it was about 2 days apart. So far both of these bluescreens have happened while watching streams on twitch and not when playing games like League of Legends which I find odd or largely a coincidence. Both the bluescreens have been caused by ntoskrnl.exe+75169

Either way any help would be greatly appreciated. Here is the two mimidumps of the bsod's.

Please run memtest and enable Driver Verifier
Using Driver Verifier to identify issues with Drivers
RAM - Test with Memtest86+

Golden said:

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

Here you go.

Golden said:

Code:

fffff880`03567010  0000007f`fffffff8
fffff880`03567018  fffff880`0fbd94caUnable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x9754ca
fffff880`03567020  fffffa80`092dd000
fffff880`03567028  fffff880`0014b825

1. Uninstall your video card drivers and software, then follow this
Drivers - Clean Left over Files after Uninstalling

2. Downlaod and reinstall your video card drivers using this
NVIDIA Drivers - Avoid Problems

Ok did that. Anything else or should I now wait to see if it happens again?

Either way thank you for the assistance thus far.

Golden said:

Try this to see if we can get a quick BSOD - follow carefully:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode

Was not able to boot with verifier as the PC would not boot, could not get it to boot into safe mode either. I had to system restore back to the point I made before attempting. I however did just get another BSOD while in a game of League, attached the dump.

Golden said:

Code:

0: kd> !thread
GetPointerFromAddress: unable to read from fffff800030b6000
THREAD fffffa800a42db50  Cid 0194.091c  Teb: 000007fffff32000 Win32Thread: 0000000000000000 RUNNING on processor 0
Not impersonating
GetUlongFromAddress: unable to read from fffff80002ff5ba8
Owning Process            fffffa80093f8060       Image:         avgrsa.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      116715       
Context Switch Count      162692         IdealProcessor: 0             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x000007feff1f4f90
Stack Init fffff88005898c70 Current fffff88005897f30
Base fffff88005899000 Limit fffff88005893000 Call 0

Mmmm....lets test my theory, uninstall AVG completely, replace it with MSE.

Monitor for further BSOD.

Removed AVG and installed MSE. However not long after that my PC completely froze, no bluescreen or dumps it just completely locked up and I had to power it down with the power button because it was hung.