Solved BSOD ntoskrnl.exe+404e92 , error 0X000000f4

[VodoBaas1]

I keep getting this BSOD and can't figure out exactly what the problem is. I have blue screen view, is there a better program to see what might be wrong and if anyone has any ideas into why it might be doing this? Thank you for the help.

 

[Arc]

Click on button below ....

​

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[VodoBaas1]

Here is the file that was requested. Thank you for the help.

 

[Arc]

OK, make it sure that the SSD is having the latest firmware.

How to Upgrade Samsung SSD Firmware | StorageReview.com - Storage Reviews
​

Let us know the result.

 

[VodoBaas1]

I didn't have the latest firmware. I was apparently behind by one. I am now up to date. I will monitor for the next day. Is there anything else I should check in the mean time?

 

[Arc]

Is there anything else I should check in the mean time?

Apparently not.

Stop 0xF4 is a storage related BSOD, and a SSD not having the latest firmware may cause it for sure.

Observe the situation now. Let us know for any further BSOD. If (and only if) the BSODs continue, we will go for some further steps.

 

[VodoBaas1]

Ok, thank you for your help.

 

[VodoBaas1]

Didn't have to wait long. It crashed again. I enclosed the new dump file with the old.

 

[Arc]

    ReadMemory error: Cannot get nt!KeMaximumIncrement value.

Post a screenshot of your discs using CrystalDiskInfo - Software - Crystal Dew World

Also test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.

 

[VodoBaas1]

Here are the hard drives, i will run Memtest and post next.

[/ATTACH]

 

[Arc]

Apparently the discs are in good condition.

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

 

[VodoBaas1]

So I ran MemTest and had 10 passes with no errors.

 

[Arc]

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.

 

[VodoBaas1]

View attachment 351195 With verifier on.

 

[Arc]

NT Kernel Resources - Windows Packet Filter Kit

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

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

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
[COLOR=Red]Probably caused by : ndisrd.sys ( ndisrd+272e )[/COLOR]

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

    Image name: ndisrd.sys
[COLOR=Red]    Timestamp:        Thu Feb 07 13:56:48 2013[/COLOR] (51136548)

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

 

[VodoBaas1]

Thank you for all the help. I tried to update it and it still was crashing, so I deleted the file and cleaned up my registry and it hasn't crashed since. I will report back in a coulpe days.

 

[VodoBaas1]

So i still haven't had another BSOD, so i think that this has been solved. Thank you very much for all the help.

 

[Arc]

Good news.