BSOD again even after restoring to a previous system image 0xC4 0x24

Raveiyn · 06 Mar 2014

Original Help Thread Here

I didn't want to re-open the previous BSOD thread because it is brand new errors. Either I am a complete idiot and forgot something or I have a hardware issue as this is a continued problem after restoring to a 3 day old system image on a brand new custom built PC.

I flashed the BIOS via Bios control panel and a flash drive with Bios Update after first BSOD.
http://us.msi.com/product/mb/Z87GD65....html#download Version 1.9

I have installed the stable 314.22 WHQL Nvidia driver after Who Crashed mentioning Nvidia driver.
http://www.nvidia.com/object/win8-wi...ql-driver.html

I have updated the Realtek driver.
http://us.msi.com/product/mb/Z87GD65....html#download

I have updated the Killer Ethernet drivers.
http://us.msi.com/product/mb/Z87GD65....html#download

I don't know what I am forgetting or doing wrong. This is so frustrating.

Arc · 09 Mar 2014

Four BSODs. Three first.

Code:

BugCheck 44, {fffffa800bd90090, 1d7b, 0, 0}

*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
Probably caused by : luafv.sys ( luafv!LuafvGenerateFileName+6d )

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

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff8800182304a, fffff880031ee358, fffff880031edbb0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

Code:

BugCheck 24, {1904fb, fffff8800935f218, fffff8800935ea70, fffff80002e94cde}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

And three of them are all different.

Then you applied driver verifier, and got it .....

Code:

BugCheck C4, {62, fffffa800a217d38, fffffa800a213240, 1}

*** WARNING: Unable to verify timestamp for mbam.sys
*** ERROR: Module load completed but symbols could not be loaded for mbam.sys
Probably caused by : mbam.sys

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

MBAM does not cause a BSOD. And this post nullifies the possibility of a virus infection.

Now, such an all different series of BSODs can be caused by some hardware error only. RAM/CPU/GPU/PSU/MOBO.

You said you ran memtest. Though you did not say the results.

Test the other hardware .....

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Unfortunately I cannot test PSU and MOBO.

So let us know the results. (Expecting no issue will be obtained).

Raveiyn · 09 Mar 2014

Thank you for the response Arc. I broke down and stayed up all night testing the RAM ... again. 12 passes this time and tested each one

(I only have two thankfully). Both came back as failed. These were brand new so I guess I just got a bad set of sticks. I will be sending them back for replacement, and using the 2 gig sticks from my old machine in the meantime.

This is the 3rd time I have tested the sticks.. but I didn't think to test them individually until reading one of the seven guides a few days ago. I have gone 3 days with no problems at all. Thank you for your time and patience.

Arc · 09 Mar 2014

No problem mate.

Let us know for any further issue. :)