yet another BSOD attack

[sakilo]

Greetings, i have recently purchased a custom built pc and installed a firewire pcie card (PEX 1394b) to use in conjunction with my presonus firebox audio interface. I seem to be getting BSOD at random times (sometimes within a few minutes, other times a few hours). I have uploaded the minidump file as i am not sure how to analyse and gather the information from it myself, help in this regard would be greatly appreciated.

Should further information be required on my part feel free to ask me and i will reply as soon as possible.

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 36198f, 2, 36050e}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

You need to test your RAM DIMM's/motherboard RAM slots for errors.

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Use this tutorial to help you use MemTest86+:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[sakilo]

thank you, i will do that and post results, i have since then suffered two more BSOD, i have attached the new data in case they provide more information

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR="Red"]BugCheck 50[/COLOR], {ffffffffffffff86, 1, fffff800031837ff, 0}


Could not read faulting driver name
Probably caused by : hardware ( nt!ObOpenObjectByName+20f )

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

One of them is inconclusive, but the other again points to memory -- MemTest86+ is the test to run. A minimum of 8 passes is required to adequately test the RAM, but more is better - I recommend running it overnight.

 

[sakilo]

I have successfully ran MemTest86+ for 8 passes without errors. I have attached a picture of the process for reference.

 

[sakilo]

I have let memtest run for a few more passed overnight just to e sure. Still no errors have been reported.

 

[Golden]

OK, time to attempt to force a BSOD to dump something more useful.

Please do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

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:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[sakilo]

Here is the collected data after running driver verifier and having a BSOD. I will continue to run verifier for now to try and capture more data should it be needed.

 

[Golden]

Excellent, driver verifier did its job perfectly!

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C1, {fffff98025976fd0, fffff980259764e5, 59402c, 32}

*** WARNING: Unable to verify timestamp for klflt.sys
*** ERROR: Module load completed but symbols could not be loaded for klflt.sys
Probably caused by : [COLOR="Red"]klflt.sys[/COLOR] ( klflt+4671 )

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

fffff880`09a5b228  fffff880`020faec4*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for [COLOR="red"]klif.sys[/COLOR]
 klif+0x34ec4

Kaspersky isn't playing nicely with Windows 7 - this is a very common occurrence on some systems. There are many, many instances of BSOD's being solved by uninstalling Kaspersky completely. You can replace it with free MSE.

 

[sakilo]

Thank you very much! As i have paid for they're service i will try to contact them and see if there is a solution but i will uninstall in the meantime and post if the issue is solved. I had another BSOD before posting this message and uninstalling karspersky and just wanted to verify if it also draws the same conclusion.

Kind Regards

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, afd4001, 665b, fffff70001080000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ad3 )

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

This one is inconclusive. It doesn't point to Kaspersky directly, but it could be triggered by the earlier Kaspersky problem.

I understand your reluctance to abandon a paid product. Kaspersky isn't alone in triggering BSOD's - I have seen the same issue with AVG, Avast (very common here because its so widely used), Symantec (Norton), Bitdefender and even Avira. There are many systems that have one of these and never experience BSOD's - why that is, I cannot say.

I think because anti-malware products tend to be intrusive by nature, the Windows system files tend to be sensitive to that behaviour. Perhaps if 3rd party anti-malware products can be set-up less 'aggressively' they may not trigger BSOD's.

The only product that we have never seen cause BSOD's here, is MSE, but that makes sense because both it and the OS are products of the same company.

 

[sakilo]

that makes perfect sense actually. Thanks again for the help! Will wait for a day or two to see if any more BSOD occur and mark as solved if not.

 

[Golden]

No worries. If you experience BSOD's in that time, just post them here and we'll have a look.

 

[sakilo]

I've unfortunitly just encountered another BSOD attack and attached the new .dmp file. I will re-activate verifier to try and get more data once again.

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffffffffffff8f, 6, 1, fffff8800f1ccf70}

*** WARNING: Unable to verify timestamp for [COLOR="Red"]nvlddmkm.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : hardware ( nvlddmkm+103f70 )

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

Try updating the Nvidia display driver from here:
Drivers - Download NVIDIA Drivers

 

[sakilo]

I seem to already be on the latest version of the driver. I will try various older versions and see if it fixes the problem.

 

[sakilo]

I have tried an older version of the driver and still received several BSOD attacks. I have uploaded the new .dmp files to make sure that they also point to the same error.

 

[Golden]

fffff880`03046718  fffff800`02ed1c84 nt!KeBugCheckEx+0x104
fffff880`03046720  fffff880`050bc000*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x85e000

Yes, it looks like the same problem. Lets back out to the last known stable driver.

Lets revert to the 314.22 WHQL driver only. Uninstall the following Nvidia items in Control Panel > Programs and Features:

- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- Nvidia Update

Now follow http://www.sevenforums.com/tutorial...over-files-after-uninstalling.html#post726559
Reboot. Go to http://www.nvidia.in/Download/index.aspx?lang=en-in, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Reboot. Use system as normal.

 

[sakilo]

I have the GTX 770 which was released after the 314.22 driver therefore it is not available for it unless modifying the .inf file from what i have gathered. I have tried the 320.18 driver and got a BSOD error but i was still running driver verifier when that occured.

 

[Golden]

OK. Try running with verifier off for now please. Monitor temperatures closely and report on those please. You can use Speccy for that.

Speccy - System Information - Free Download