BSOD while computer was locked

bebopkid · 27 Jan 2014

It's been over a month since I've had a lot of BSOD problems, but they seem to be back.

Any help is appreciated.

peebee · 27 Jan 2014

You've got hardware memory issues. Are you overclocking your rig? Make sure you're running at spec, do some memory stress testing (there are a ton of tools out there for this) and see what turns up. If you've recently added memory, then consider removing it and testing one module at a time until you find which is the culprit.

YoYo155 · 27 Jan 2014

Hi bebopkid :) .

Just to elaborate on peebee's post testing the RAM won't hurt, this will help you accomplish that.

Testing the RAM:

koolkat77 said:

Test and Diagnose RAM Issues with Memtest86+:

RAM - Test with Memtest86+

Tip

Pay close attention to part 3 of the tutorial "If you have errors"
Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

When done with the testing procedure take a picture and upload it here.

This will help you to determine where the issue is origination from (if any):

Arc said:

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

If MEMTEST86+ reports a clean bill of health I recommend scanning for possible infections,
but the main issue appears to be EagleX64.sys, the thing is I don't see HackShield installed
or any mention of AhnLab in your MSinfo32 file yet it appears in all of the dumps.
Do you know anything about it?

Please scan for possible infection and file corruption.

Download TDSS-Killer and scan for rootkits.
Download Kaspersky Rescue CD and scan for other types of infections. (a how-to tutorial)
Download Malwarebytes and DON'T activate the trail (uncheck the box at the end of the installation)
Follow this tutorial on how to use the SFC/ SCANNOW tool in Windows.

(*Kaspersky Rescue CD from a USB thumbdrive)

Let us know the results.