Reinstalled OS on ASUS laptop but BSOD still persists. Help! - Windows 8 x64

Y

Yancey

Member
Joined
Sep 29, 2014
Posts
5
Windows 8 x64
Original OS Windows 8 OEM
Purchased Summer 2013
Age of OS - 1 day, reinstalled multiple times.

· CPU - Intel® Core™ i7 3517U Processor
· Video Card - NVIDIA® GeForce® GT 620M

· System Manufacturer - ASUS
· Exact model number - ux32v
· Laptop

Hope this is all the information you need.

This laptop has been acting up in the past few months, but yesterday it just all of a sudden just died. I met with a friend to go study and closed my laptop and put it on sleep mode. When I opened it back up, it would not start. I could turn it off and on again, but most of the time it would hang up at the login screen, or I would manage to get to the desktop, but inevitably, it would freeze and I would get a bluescreen.

It got so bad to the point that I could not even reach the necessary avenues to refresh or restart the system.

My friend did a bit of troubleshooting and found what he thought may have been the source of the problem - I had replaced the 4gig ram stick with an 8 gig a few weeks after I bought it. According to the ASUS site, that particular slot only allows up to 4 gigs. However, I've seen multiple guides indicate that an 8gig stick could work anyways, and it worked fine for most of the year. It just starting acting up in the last few months.


So after we open up the laptop and I replace the ram stick with the original, we thought it would fix everything, but the freezing and blue screening persisted. Afterwards, we attempted to reset the PC and reinstall the OS. What followed is something I found very strange. If you are aware of the steps that it takes to reset OS, there was freezing after each step. Eventually, I was able to go through the re-install process. Literally every step I took it would end up freezing, but when I turn the laptop on and off again, it would move on to the next step.

So here I am now, the laptop is useable, but when I try to restart, it blue screens. It's always the same blue screen too - Driver Power State Failure (or something along those lines).

If someone can help me fix this and save me $200 for a repair fee, I will be forever grateful!

Thanks for your time

View attachment 9422
View attachment SysnativeFileCollectionApp.zip



 
Hi,

For the bug check that you're having, a kernel dump will be required.

Kernel-dumps are located at C:\Windows and named MEMORY.DMP. If there is nothing there, you may need to enable generation of them - Creating a Kernel-Mode Dump File (Windows Debuggers)

Note that this file we be too large to attach here, so you'll have to upload it to a site such as Onedrive, Mediafire, Filedropper, etc.

Regards,

Patrick
 
Thanks.

DRIVER_POWER_STATE_FAILURE (9f)

This bug check indicates that the driver is in an inconsistent or invalid power state.

Code: 
3: kd> !locks
**** DUMP OF ALL RESOURCE OBJECTS ****
KD: Scanning for held locks..

Resource @ nt!IopDeviceTreeLock (0xfffff803c1349640)    Shared 1 owning threads
     Threads: [COLOR=#ff0000]fffffa800a24f500[/COLOR]-01<*> 
KD: Scanning for held locks.

Resource @ nt!PiEngineLock (0xfffff803c1349740)    Exclusively owned
    Contention Count = 22
    NumberOfExclusiveWaiters = 2
     Threads: fffffa800a24f500-01<*> 
     Threads Waiting On Exclusive Access:
              fffffa800a127b00       fffffa8009e1e5c0

Code: 
3: kd> !thread fffffa800a24f500
Base [COLOR=#0000cd]fffff8801e4bc000 [/COLOR]Limit [COLOR=#006400]fffff8801e4b6000 [/COLOR]Call 0
Priority 15 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`1e4bac60 fffff803`c111799c : fffffa80`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x76
fffff880`1e4bada0 fffff803`c1113c1f : fffffa80`05bff410 ffffc300`3a4b0c42 00000000`00000000 fffff880`1e4bb100 : nt!KiCommitThreadWait+0x23c
fffff880`1e4bae60 fffff880`0141d009 : fffff880`1e4baf20 fffff880`00000000 fffffa80`12178100 00000000`00004000 : nt!KeWaitForSingleObject+0x1cf
fffff880`1e4baef0 fffff880`0140e1f2 : fffffa80`11f204b0 fffffa80`12178100 fffff6fc`00000001 fffffa80`05bff410 : storport!RaSendIrpSynchronous+0x71
fffff880`1e4baf50 fffff880`0140d6a0 : fffff880`1e4bb420 fffff880`00000000 fffff880`1e4bb460 fffff880`01407aa0 : storport!RaidBusEnumeratorIssueSynchronousRequest+0x16a
fffff880`1e4bb120 fffff880`0140d7d4 : fffffa80`12178130 fffff880`00000001 00000000`00000001 00000000`00000001 : storport!RaidBusEnumeratorIssueReportLuns+0x68
fffff880`1e4bb180 fffff880`0140f4fb : 00000000`00000001 00000000`00000001 fffff880`1e4bb2c0 fffff880`1e4bb420 : storport!RaidBusEnumeratorGetLunListFromTarget+0xac
fffff880`1e4bb200 fffff880`014086e8 : 00000000`00fe0200 fffffa80`00000001 00000000`00000000 00000000`00000000 : storport!RaidBusEnumeratorGetLunList+0x5b
fffff880`1e4bb290 fffff880`01408319 : 00000000`00000000 00000000`00000000 fffff880`1e4bb500 00000000`00000000 : storport!RaidAdapterEnumerateBus+0x94
fffff880`1e4bb400 fffff880`0140b190 : fffffa80`1136e210 fffff880`1e4bb560 fffffa80`1136e210 fffffa80`0a2a7010 : storport!RaidAdapterRescanBus+0xcd
fffff880`1e4bb4e0 fffff880`0140b537 : 00000000`00000000 00000000`00000000 fffffa80`1136e210 00000000`00000000 : storport!RaidAdapterQueryDeviceRelationsIrp+0x114
fffff880`1e4bb5a0 fffff880`0140ff68 : fffff880`1e4bb6f0 fffff803`c11787ec fffffa80`1136e210 fffffa80`053c9880 : storport!RaidAdapterPnpIrp+0x1f7
fffff880`1e4bb640 fffff803`c14f7706 : fffffa80`1136e210 fffffa80`11d46e50 fffffa80`05f39050 fffff803`c1369180 : storport!RaDriverPnpIrp+0x94
fffff880`1e4bb680 fffff803`c14f8884 : 00000000`00000000 fffff880`1e4bb719 fffff803`c11787ec 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`1e4bb6c0 fffff803`c14f877f : fffffa80`11d46e50 fffffa80`11d46e50 fffffa80`051eaeb0 fffff803`c14fb118 : nt!PnpQueryDeviceRelations+0x88
fffff880`1e4bb780 fffff803`c14f6fb8 : fffffa80`125185a0 fffffa80`053dc770 00000000`00000002 00000000`00000000 : nt!PipEnumerateDevice+0x12f
fffff880`1e4bb800 fffff803`c14fe9e1 : fffffa80`125185a0 00000000`00000001 00000000`00000000 fffff803`c13f1512 : nt!PipProcessDevNodeTree+0x19c
fffff880`1e4bba80 fffff803`c117930a : 00000001`00000003 00000000`00000000 00000000`00000000 fffffa80`053eaf28 : nt!PiProcessReenumeration+0x89
fffff880`1e4bbad0 fffff803`c1126591 : fffffa80`0a24f500 fffff803`c11791a0 fffff803`c13466e0 fffff803`c10f7400 : nt!PnpDeviceActionWorker+0x16a
fffff880`1e4bbb80 fffff803`c1095535 : fffffa80`11780102 00000000`00000080 fffff803`c1126450 fffffa80`0a24f500 : nt!ExpWorkerThread+0x142
fffff880`1e4bbc10 fffff803`c10d3e16 : fffff880`03065180 fffffa80`0a24f500 fffffa80`0516eb00 fffffa80`0521c040 : nt!PspSystemThreadStartup+0x59
fffff880`1e4bbc60 00000000`00000000 : fffff880`1e4bc000 fffff880`1e4b6000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

Something 3rd party is causing file system conflicts. Let's dump the raw stack:

Code: 
fffff880`1e4b9478  fffff880`02343eb9 mfewfpk+0x5eb9
fffff880`1e4b9480  fffff880`1e4b94a0
fffff880`1e4b9488  fffff880`0235d037 mfewfpk!DEVICEDISPATCH::DispatchPassThrough+0xec7
fffff880`1e4b94a0  00000001`ffffffff
fffff880`1e4b94a8  fffff880`0234aa30 mfewfpk+0xca30
fffff880`1e4b94e0  fffffa80`0734fae8
fffff880`1e4b94e8  fffff803`c102d2a1 hal!HalpApicRequestInterrupt+0x1e5

A lot of McAfee calls, I wouldn't be surprised if it's causing problems.


1. AiCharger.sys is listed and loaded in the modules list which is the Asus Charger driver. It's included in many Asus bloatware, which you appear to have installed. Please go ahead and uninstall any and all Asus software as it's unnecessary bloatware.

2. Remove and replace McAfee with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it's very likely causing conflicts with Diskeeper's ExpressCache:

McAfee removal - How to uninstall or reinstall supported McAfee products using the Consumer Products Removal tool (MCPR)

Windows Defender (how to turn on after removal)

A.Navigate to Control Panel (with icons). You can do this by hitting Start > Search > Control Panel. Once in Control Panel, change the drop-down from Category to Large and/or Small icons.

B.Among the list of icons, find and click Action Center.

C.Assuming the removal of your prior antivirus software went properly, you will notice for both Spyware and unwated software protection (important) and Virus protection (important), it'll have a button labeled Turn on now. Click this button (it doesn't matter which, as Windows Defender serves as both in Windows 8/8.1).

Windows Defender (turn on) Windows 8:

1. Navigate to Control Panel (with icons). You can do this by hitting Start > Search > Control Panel. Once in Control Panel, change the drop-down from Category to Large and/or Small icons.


2. Among the list of icons, find and click Windows Defender.


3. Once the Windows Defender window pops up, select the Settings tab. As soon as you're in Settings, on the left-hand side, select Administrator (below MAPS), and then un-check Turn on this app. If UAC (User Account Control) notes this is an administrative privilege and requires you to prompt it, select yes.

Regards,

Patrick
 
Hi Patrick,

Removing the extra programs and McAfee have got rid of the blue screen problem. But there is still a lot of freezing that occurs when I open up programs right after start-up and also, it takes a long time to shut down and when I turn it back on again for some reason I get the "a problem has occurred that required windows to shut down" window when I get to the desktop.
 
Patrick has just gone offline.

Can you check your temperatures?
Is the computer getting hot at all?

I would suggest Driver Verifier if your computer is freezing.

What is Driver Verifier?

Driver Verifier monitors Windows kernel-mode drivers, graphics drivers, and even 3rd party drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject the Windows drivers to a variety of stresses and tests to find improper behavior.

Essentially, if there's a 3rd party driver believed to be causing the issues at hand, enabling Driver Verifier will help us see which specific driver is causing the problem.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8/8.1)
- DDI compliance checking (Windows 8/8.1)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled per my instructions above, it is monitoring all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
Restart and boot into normal Windows.

If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.

-- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1

How long should I keep Driver Verifier enabled for?

I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.

My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?

- If you have the system set to generate Small Memory Dumps, they will be located in %systemroot%\Minidump.

- If you have the system set to generate Kernel-Memory Dumps, it will be located in %systemroot% and labeled MEMORY.DMP.
 
Hi Jared,

I'm trying to create a system restore point but it's been idling for quite some time. Would you recommend that I just go ahead?
 
You don't really need one as it's rare to not boot into safe mode, unless you check any microsoft drivers, Macrovision drivers or unknown drivers.
It's just a recaution really.
 
Hey,

sorry it took so long. I'm not sure if the driver verifier went through fully, whenever I try to restart I get a BSOD Driver_Power_State error. I can't even turn off my computer properly, I have to do a hard shut down. Here's my latest Memory.dmp: MEMORY
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top