BSOD ntoskrnl.exe+404e92 , error 0X000000f4

Apparently the discs are in good condition.

Will wait for the memtest result. Take your time with it.

Next, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

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

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

NT Kernel Resources - Windows Packet Filter Kit

Either update it or uninstall it, depending on your necessity.

Code:

ndisrd    WinpkFilter LightWeight Filter    c:\windows\system32\drivers\ndisrd.sys    Kernel Driver    Yes    System    Running    OK    Normal    No    Yes

Code:

BugCheck C4, {40, 0, fffff9800d052c10, 0}

*** WARNING: Unable to verify timestamp for ndisrd.sys
*** ERROR: Module load completed but symbols could not be loaded for ndisrd.sys
Probably caused by : ndisrd.sys ( ndisrd+272e )

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

Code:

    Image name: ndisrd.sys
    Timestamp:        Thu Feb 07 13:56:48 2013 (51136548)

IMHO it might be needed to continue with verifier to see if it catches anything else.

Good news.