ntoskrnl.exe BSOD

The dump file reads

Code:

nvlddmkm
start             end                 module name
fffff880`130f9000 fffff880`13dd5000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Oct 16 07:31:28 2014 (543FBAA0)
    CheckSum:         00C97F5B 
    ImageSize:        00CDC000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0

Which is your graphics driver. Please reinstall the graphics driver using these instructions
NVIDIA Drivers - Avoid Problems when finished

Open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

The event log is full of events like these...

Code:

Event[57312]:
  Log Name: System
  Source: Microsoft-Windows-DriverFrameworks-UserMode
  Date: 2014-11-01T10:08:37.083
  Event ID: 10114
  Task: Startup of the UMDF reflector
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Ethan-PC
  Description: 
The UMDF reflector was unable to complete startup because the WUDFPf service was not found.  This service may be started later during boot, at which point Windows will attempt to start the device again.
 
Event[57313]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-PnP
  Date: 2014-11-01T10:08:37.083
  Event ID: 219
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Ethan-PC
  Description: 
The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&2&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC-&PROD_COMPACT_FLASH&REV_1.01#058F63626420&1#.

Please open an Elevated Command Prompt, and run the following commands....

SC QC WUDFPf
DIR C:\Windows\System32\WUDFPf.* /S

post the results.

Here are some instructions to make life easier :)
1) To open an Elevated Command Prompt Window (the ECP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.
2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Window, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.
3) To copy the results... click on the Black/White icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>SC QC WUDFPf
[SC] QueryServiceConfig SUCCESS

SERVICE_NAME: WUDFPf
TYPE : 1 KERNEL_DRIVER
START_TYPE : 3 DEMAND_START
ERROR_CONTROL : 1 NORMAL
BINARY_PATH_NAME : system32\drivers\WudfPf.sys
LOAD_ORDER_GROUP : base
TAG : 0
DISPLAY_NAME : User Mode Driver Frameworks Platform Driver
DEPENDENCIES :
SERVICE_START_NAME :

C:\Windows\system32>DIR C:\Windows\System32\WUDFPf.* /S
Volume in drive C is WIN7
Volume Serial Number is 70BC-C401

Directory of C:\Windows\System32\drivers

07/25/2012 09:26 PM 87,040 WUDFPf.sys
1 File(s) 87,040 bytes

Total Files Listed:
1 File(s) 87,040 bytes
0 Dir(s) 194,337,775,616 bytes free

C:\Windows\system32>

That looks normal enough.

Let's check the other driver now...

Open an Elevated Command Prompt, and run the following commands.
SC QC WUDFRd
SC QUERYEX WUDFRd
SC QUERYEX WUDFPf
SC START WUDFPf
SC START WUDFRd

post the results.

OK - end of red herring
Those results are as expected (surprisingly!).

I'll hand you back to the BSOD specialists now

moieu, Your dump files say the same thing every other dump file you have uploaded that I can remember.

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, d8ab3, 2, d8ab2}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner

We are more than likely going to have to run memtest86+ again, but first I'd like to try something. Follow the tutorial exactly.

First If you don't have it or the installation disk, create a repair disk System Repair Disc - Create

Next, create a restore point System Restore Point - Create

Enable driver Verifier Driver Verifier - Enable and Disable
Be sure and select all drivers NOT provided with Microsoft,