Issue with the HDMI-IN

I have a MX17 Alienware laptop which comes with an HDMI-IN port. I connected a PS3 to it and the screen automatically switched to display the PS3 game. I did not have to press anything. Then when I unplugged the HDMI cable the computer gave me a blue screen of death with error "POWER_STATE_FAILURE" ever since then and its been months, I have been getting blue screens of death randomly, sometimes weeks apart sometimes hours apart usually when I am watching a movie or using the computer to play some PC games. I tried updating all the graphics card drivers etc but nothing seems to work. Now I am wondering if there was some driver I needed to download for the HDMI-IN port, but I can't find any. I would really appreciate any help with this issue.

 

I don't think the issues are related. I think you are getting blue screens because something is awry with your Windows install at this point, or you have an unstable machine (perhaps a bad overclock?)

 

Please link your system specs. Use my signature as an example of what to tell.

 

Your problem is a bad driver. A "POWER_STATE_FAILURE" basically occurs when a driver does not handle resuming from hibernation/standby correctly. I'm guessing that when you plug your PS3 into your M17x, it goes into standby or even hibernates due to inactivity.

A possible solution would be to prevent the computer from going to sleep by changing the settings in your Power Management. However, if you're getting BSOD with "power_state_failure" then you've almost certainly got a bad driver somewhere.

Did you install any software recently? or update any drivers recently? Just doing a quick google search, I'm finding a lot of people are associating these errors with antivirus software. What kind of antivirus are you running?

 

We'll find out when we find out his specs.

Please not an nvidia 460m...please.

 

Why not a 460m?

 

M17xR3 Intel(R) Core (TM) i7-2720QM @ 2.20Ghz(8 CPUs), 8gb, NVIDIA GeForce GTX 460M, 750gb, 1600x900.
I am sorry if I am missing anything. Why is it bad that its 460m?
Thanks for the responses though.

 

Well the 460m causes bsods due to optimus.

Check this out.
http://forum.notebookreview.com/alienware-m17x/628575-guide-nvidia-460m-users-experiencing-bsod.html

And a "Just in case"
NVIDIA DRIVERS 1.00.00.59 WHQL

 

And I don't think its the anti-virus software, I tried two different ones and nothing changed, also I ran it for a while without any and it still happened. I have updated some drivers, I tried to update everything, but its been doing the same thing. I don't know about it being over clocking. The software support people were useless but they did install a program called WhoCrashed that analyzes what went wrong. But they didn't fix the problem. Here is the report for the past five crashes:

On Mon 12/12/2011 7:05:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121211-30934-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8009898A10, 0xFFFFF80000B9C3D8, 0xFFFFFA800E3ECE10)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 12/12/2011 7:05:06 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8009898A10, 0xFFFFF80000B9C3D8, 0xFFFFFA800E3ECE10)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 12/8/2011 9:16:04 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120811-30576-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8009876A10, 0xFFFFF80000BA2748, 0xFFFFFA8007587E10)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 11/27/2011 11:31:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112711-35771-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800987AA10, 0xFFFFF80000B9C3D8, 0xFFFFFA800BCCA010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 11/26/2011 6:49:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112611-31761-01.dmp
This was probably caused by the following module: igdkmd64.sys (igdkmd64+0x288451)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88004E88451)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\igdkmd64.sys
product: Intel Graphics Accelerator Drivers for Windows 7(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: igdkmd64.sys Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

 

I would highly recommend the method I posted. I've had all these same problems with my old 460m.

 

I think mine is a 3D system, will your method still work or are there adjustments to be made? I don't mind losing 3D capability if it will stop the BSOD.

 

Well, check first if it is 3D or not. It only works if its not 3D.

 

And if it is? No solution? Will the issue be resolved if I replace the video card? If so is there one that people can recommend?

 

If you could verify if its 3D or not first, it would help quite a bit.

 

The reason I am confused is because I have options which say enable 3D vision but my actual monitor does not support 3D viewing. So you understand my confusion. Is there a specific way I could verify whether I have a 3D system or not?

 

Cause I remember when buying the computer it said something like, it is 3D capable but I don't think I chose one with 3D enabled. Sorry about the confusion.

 

yup you don't have the model with the 3d screen which means you are having to deal with opti-mess (optimus). This can cause issues but idk if it has to do with the HDMI-In or not. I could test in a bit though and see what driver version works.