G53SW blue screen when put to sleep problem.

[Hoplite01]

I have an issue with sleep mode on my G53. I set the lid closing action to sleep. Sometimes instead of sleeping it stays on for long time and then displays the blue screen (9f). I've heard that it can have something to do with the ATK package and I re installed it. It helped for some time but now the problem is back. Anyone else who experienced this and maybe knows how to fix it?

[PILGRIM]

You might want to try Microsoft Security Essentials.
It's light, free and, of course, a Windows component.

EDIT: Oh. I didn't see in your previous post you used MSE before.

[Hoplite01]

the CHKDSK was all correct. and it seems as if the Nod32 was causing the issue all the time.

[dstrakele]

Very good, @Hoplite01. Microsoft Security Essentials is very light on resource usage, plus I think it has a better chance of being included in Mocrosoft's Q/A testing of Windows Updates, meaning less chance of a blowup when they get installed.

I've also used MalwareBytes AntiMalware for some time, initially because I saw it recommended just about every time someone was worried about malware. I've never had a issue with it and like MSE, the price is right.

[Hoplite01]

Ok sorry to bother again but now a new blue screen just popped out... I did not change anything since the last one no programs installed nothing removed.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 50
BCP1: FFFFF6FC4005A000
BCP2: 0000000000000001
BCP3: FFFFF8000346B504
BCP4: 0000000000000009
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\020312-22822-01.dmp
C:\Users\Kacper\AppData\Local\Temp\WER-109091-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

[dstrakele]

Bugcheck code 0x50 is a generic error for memory corruption. It can indicate faulty RAM, a faulty device, or a problematic driver - in other words, just about anything. In your case, you report no new hardware or software was added, so the idea that the last change made is usually involved in the fault does not apply.

Do any Errors or Warnings in the Windows System or Application Event Log point to some troubleshooting direction?

If I encountered this error, I'd run memtest86 to confirm my memory is sound. I'd follow @fostert's post for the memory testing strategy: http://rog.asus.com/forum/showthread.php?10312-Asus-G74sx-and-Ram-Dimm-problem&p=70636&viewfull=1#po...

If memory passed, I might try a registry cleaner such as CCleaner.

If that failed, I'd restore my last stable Windows System Image from backup or perform a clean Windows 7 installation.