[SOLVED] BSOD - DRIVER POWER STATE FAILURE (ACPI.sys)

Deek said:
They may be related, can you try to get it to BSOD now?

First thing I would try would be a bios update for the power state BSOD, If you don't know what I am talking about, you could first try going into setup (Bios) during post and disabling APM (Advanced Power Management)

Let me know if I need to elaborate, you seem to know your way around a PC pretty well.

For a bios update, go to the manufacture web site of your laptop, then support, look up you service tag or model and download the firmware/bios update...they will provide instructions, but these days it's just a windows program you fire off.
Click to expand...

I updated my BIOS a few weeks ago trying to solve the problem. It is safe to update again?
 
no need to do a second update, has it crashed again since the work we did last night? Like I said, those BSODs are probably related.

But you could still try disabling APM in bios if it is still crashing, it will decrease your battery runtime, but at least we can see if the issue goes away.
 
Deek said:
no need to do a second update, has it crashed again since the work we did last night? Like I said, those BSODs are probably related.

But you could still try disabling APM in bios if it is still crashing, it will decrease your battery runtime, but at least we can see if the issue goes away.
Click to expand...

My computer is freezing some times, but no blue screen.
 
I think i solved my problem. Someone know a good stress test software? I just want to make sure that wont happen again
 
Deek said:
Fardarkside said:
I think i solved my problem. Someone know a good stress test software? I just want to make sure that wont happen again
Click to expand...

What fixed it? We like to document solutions for those Googlers out there.
Click to expand...

I updated my graphic card driver to 327.23 version. But it seems that im getting another BSOD. Here it is the verifier enabled dump file
 

Attachments

Hi,

The attached DMP file is of the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) bugcheck.

This indicates that a system thread generated an exception which the error handler did not catch.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005

^^ access violation

Code: 
3: kd> .exr 0xfffff88007faf328
ExceptionAddress: fffff880057c085f ([COLOR=#ff0000][U][I][B]nvlddmkm[/B][/I][/U][/COLOR]+0x00000000000ed85f)
   ExceptionCode: [COLOR=#ff0000][I][B]c0000005 (Access violation)[/B][/I][/COLOR]
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 000000000000008c
Attempt to read from address 000000000000008c

It's being caused by nvlddmkm.sys which is the nVidia video driver.

Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

------------------------------------------------------------------------------------------------------------------------------

Remove and replace avast! with Windows 8's built-in Windows Defender for temporary troubleshooting purposes:

avast! removal tool - avast! Uninstall Utility | Download aswClear for avast! Removal

If you're still crashing after the removal of avast! and if you've experimented with multiple driver versions, do you have access to integrated graphics? If so I would recommend uninstalling your video card drivers, shutting down and removing video card, installing integrated graphics drivers, and use the system as you would regularly. This is to rule out the video card as the issue.

Regards,

Patrick
 
A bit of a late reply, but I just noticed you mentioned you're using a notebook. My apologies, you don't need to refer to my video card recommendation, but refer to the rest.

Regards,

Patrick
 
You may want to try driver version 314.22

It seems there are lots of this type of problem.


Maybe even see what the latest the laptop manufacture has for the device. Sometime laptop drivers are customized by the manufacturer to prevent this sort of thing.
 
Hi,

Have you removed and replaced avast! as well? If so, this is likely a hardware issue. I'd recommend running Memtest for NO LESS than ~8 passes (several hours):

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

Regards,

Patrick
 
I finally managed to fix the BSOD. For real now.
I downgraded my graphic card driver to 314.07, and updated the intel HD graphics to the latest driver. Dont know which one fixed my problem, but its all runing just fine.
Thanks for everyone who supported me
 
Good to hear, thanks for letting us know. I imagined it was an issue between the nVidia drivers somewhere or possible hardware. Glad to hear it was the former. Navigate to Thread Tools > Mark as Solved at the top when you are ready.

Regards,

Patrick
 

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

Back
Top