yet another BSOD attack

sakilo · 08 Feb 2014

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 · 08 Feb 2014

Code:

*******************************************************************************
*                                                                             *
*                        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+:
RAM - Test with Memtest86+

sakilo · 08 Feb 2014

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 · 08 Feb 2014

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {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 · 09 Feb 2014

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

sakilo · 10 Feb 2014

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

Golden · 10 Feb 2014

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.
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

sakilo · 12 Feb 2014

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 · 12 Feb 2014

Excellent, driver verifier did its job perfectly!

Code:

*******************************************************************************
*                                                                             *
*                        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 : klflt.sys ( klflt+4671 )

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

Code:

fffff880`09a5b228  fffff880`020faec4*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
 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 · 12 Feb 2014

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