PDA

View Full Version : G53SW blue screen when put to sleep problem.



Hoplite01
01-26-2012, 02:52 PM
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?

dstrakele
01-26-2012, 03:11 PM
Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE (http://msdn.microsoft.com/en-us/library/windows/hardware/hh406232(v=vs.85).aspx) indicates a problem with Power Management. The 4 Parameters displayed after the STOP 0x9F can provide more information as to the specific cause. What parameters are displayed in your BSOD?

What file does the BSOD indicate is causing the problem?

Are you running a clean Windows 7 installation or the ASUS Factory OS?

Power4Gear is the ASUS utility that manages power on the ASUS Factory OS installation. If you disable it or uninstall it does the behavior change?

What Antivirus, AntiMalware, Firewall, or Remote Access software do you have installed to your G53SW?

Hoplite01
01-26-2012, 03:32 PM
I tried uninstalling the POwer4Gear and it did help. And it seems like the issue happens after installing new drivers.

dstrakele
01-26-2012, 03:40 PM
I've found the Windows 7 driver stack to be somewhat fragile. I've seen 2 posts in this forum of users installing a bluetooth driver which results in corruption of their entire clean Windows 7 OS installation. I have also experienced increased video problems after installing a beta audio driver on my clean Windows 7 installation. As a result, I now unintall and install drivers after booting into Safe Mode. Safe Mode disables other running drivers that can potentially interfere with your driver installations or uninstallations.

Hoplite01
01-26-2012, 09:35 PM
Here is all the extra info i can provide. Any ideas what is causing that?

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

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA800785A060
BCP3: FFFFF80000B9C3D8
BCP4: FFFFFA8006E55010
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\012612-17503-01.dmp
C:\Users\Kacper\AppData\Local\Temp\WER-77033-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
01-26-2012, 10:23 PM
Here's what the MSDN Bugcheck Code Reference (http://msdn.microsoft.com/en-us/library/windows/hardware/hh406232(v=vs.85).aspx) says for STOP 0x9F
For Parm 1 = 0x3 (Windows XP and later)
Param 2: The physical device object (PDO) of the stack
Param 3:The functional device object (FDO) of the stack. In Windows 7, this parameter points to the nt!TRIAGE_9F_POWER structure.
Param 4:The blocked IRP

CAUSE: A device object has been blocking an IRP for too long a time.

You report the issue appears after installing new drivers. I've seen reports of driver installation causing problems with other installed drivers. I encountered video problems after installing a new version of the Realtek Audio driver. For this reason, I now install and uninstall drivers from within Safe Mode. Safe Mode disables running drivers that may potentially interfere with your driver installations.

I suspect a driver installation may have corrupted the Power4Gear driver(s). Since Windows can provide everything in the way of power management that P4G provides, I would NOT reinstall it. It is one less thing to worry about.

Hoplite01
01-27-2012, 08:09 PM
I deleted Power4Gear and everything worked fine. Until now, the BlueScreen returned. Could someone give me a step by step instructions how I can get rid of it?

dstrakele
01-27-2012, 08:48 PM
Let's make sure it is the same STOP 0x9F Bugcheck. Please report the Bugcheck number and 4 parameters of this most recent BSOD.

The BugCheck event details may also list a filename that was involved. What is that filename?

What Antivirus, AntiMalware, Firewall, or Remote Access software have you installed to your system?

What other applications have you installed?

I think it may be useful to get output from BlueScreenView by Nirsoft. This will examine the Mini-Dumps on your system and give us a history of the bugchecks.

Hoplite01
01-29-2012, 11:33 AM
Exactly the same error. I use ESET Nod32 as the antivirus. What do you mean by getting output from Nirsoft?

dstrakele
01-30-2012, 02:46 AM
ESET Nod32 is one you don't hear about often which makes me suspicious that it may be involved in your BSOD. See http://www.google.com/#pq=bluescreenview&hl=en&sugexp=pfwl&cp=15&gs_id=23&xhr=t&q=eset+nod32+BSOD&pf=p&sclient=psy-ab&pbx=1&oq=eset+nod32+BSOD&aq=0v&aqi=g-v1&aql=&gs_sm=&gs_upl=&bav=on.2,or.r_gc.r_pw.r_qf.,cf.osb&fp=e8db89ab90c5d414&biw=982&bih=841

I would attempt to disable it by setting all its Services in the SERVICES applet to "Disabled" and then reboot the system. It's the only way to be sure if it's drivers are unloaded. Of course it would be much better to uninstall it for the reproduction test.

My G74SX came with a running trial of Trend Micro pre-installed. Did your G53SW come with this trial? If so, did you uninstall it prior to installing ESET Nod32?

I mean downloading BlueScreenView from http://www.nirsoft.net/utils/blue_screen_view.html and running it. Then posting a screenshot of the results so the history of each Bugcheck Code and Parameters 1-4 on your system is revealed. It also gives filenames that are involved in the BSOD (either the cause or a victim) and that can help troubleshoot your issue.

Hoplite01
01-30-2012, 10:35 AM
5653Here is the Nirsoft file. I used Microsoft security essentials before so I will try to investigate the Nod32. It is hard to find out if the issue is fixed because it happens so randomly.

dstrakele
01-30-2012, 03:42 PM
It looks like your latest BSOD is a STOP 0x9F, just like the other recent ones. They list NTOSKRNL.EXE as the problem. NTOSKRNL.EXE is the main Windows 7 process. It is either a victim or your Windows 7 instance is corrupt.

1) Have you run CHKDSK C: /F /R ? It would be worthwhile to confirm your file system is sound.

2) Is this the ASUS Factory version of windows or a clean Windows 7 installation that you have done?

3) Have you had any problems installing any Windows Updates?

The first BSOD recorded is different. It is a STOP 0x1000007E with MijXfilt.sys listed as the cause. This is a driver from Motion in Joy.

4) Is Motion in Joy still running on your system?

5) If you perform a Windows System Restore to a date prior to 27/12/20011, does it resolve your BSOD issues?

Hoplite01
01-30-2012, 05:55 PM
I deleted the motion in joy long ago. THe windows is a clean install cause i had issues with installing SP1 a while ago. I had a problem a while ago where my computer would freeze after wake up but i resolved that using restore.

dstrakele
01-30-2012, 05:58 PM
If you perform a Windows System Restore to a date prior to 27/12/20011, does it resolve your BSOD issues?

Hoplite01
01-30-2012, 06:08 PM
no. it still exists.

dstrakele
01-30-2012, 06:37 PM
Have you run CHKDSK C: /F /R ? It would be worthwhile to confirm your file system is sound. A corrupt file system could also be why you lost CinePlayer after the update.

Hoplite01
01-30-2012, 07:19 PM
How do I run it?

dstrakele
01-30-2012, 07:28 PM
Right-click on Command Prompt and choose "Run as Administrator" from the popup menu. After it launches, enter CHKDSK C: /F /R
It'll then tell you to REBOOT and it will run on Startup. Report if it detects any errors or bad blocks.

dstrakele
01-30-2012, 07:59 PM
Sleep puts your open documents and other work into memory, keeping it alive with a small charge. Bad RAM could also be responsible for your BSOD's when attempting to put your laptop to sleep. I think it would also be worthwhile to extensively test your laptop's memory with memtest86.

Hoplite01
01-31-2012, 09:37 AM
Ok I will perform the CHKDSK soon and report if anythign happens. But I tried removing the Nod32 program and so far I have not experienced a single crash. I've put my pc to sleep 5 or 6 times so far. Any suggestions as to what antivirus to use after the trend Microsecurity runs out?

PILGRIM
01-31-2012, 09:46 AM
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
01-31-2012, 01:41 PM
the CHKDSK was all correct. and it seems as if the Nod32 was causing the issue all the time.

dstrakele
01-31-2012, 02:40 PM
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
02-03-2012, 12:47 AM
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
02-03-2012, 01:09 AM
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#post70636

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.