Driver power state failure BSOD

#5 Broni

The Coolest BC Computer

BC Advisor
42,772 posts
OFFLINE

Gender:Male
Location:Daly City, CA
Local time:07:49 AM

Posted 13 February 2011 - 11:27 AM

Also, since Windows files are involved in your crashes, I always recommend new topic in "Am I Infected?" forum to make sure, your computer is clean.

My Website

My help doesn't cost a penny, but if you'd like to consider a donation, click DONATE

#6 kerryboy

Topic Starter

Members
82 posts
OFFLINE

Local time:10:49 AM

Posted 14 February 2011 - 09:59 AM

Thanks guys but looking at the posts in that link doesn't really provide much help as they all refer to windows 7 and I am using Vista, Plus they refer to updating a symantec driver and I don't think I have any symantec hardware/software on my computer. Any other ideas?

I haven't had a chance to scan with malwarebytes/spybot yet but will do so as soon as I get a chance, depending on the outcome I might begin an 'am I infected' thread.

#7 hamluis

Moderator

Moderator
56,573 posts
ONLINE

Gender:Male
Location:Killeen, TX
Local time:09:49 AM

Posted 14 February 2011 - 01:30 PM

FWIW: Chances are that...any fix that applies to Vista regarding BSODs...may also apply to Win 7.

Win 7 is said to be an updated/improved version of Vista, while Vista was a serious departure (IMO) from XP and preceding systems.

In many cases, drivers which work or were developed for Vista...may work where there are no specific drivers developed for Win 7.

The generic causes of certain BSODs...do not tend to vary in nature. The error you reflect...is what I would consider unusual and the only clues to resolving it...must be found where they lie.

http://social.answers.microsoft.com/Forums/en-US/w7hardware/thread/7705222b-3ab4-4fae-87c2-566ba9a5e3ce

I also agree with Broni about the pattern of BSODs reflected...as possibly indicating malware.

Louis

Edited by hamluis, 14 February 2011 - 01:54 PM.

#8 kerryboy

Topic Starter

Members
82 posts
OFFLINE

Local time:10:49 AM

Posted 20 February 2011 - 12:13 PM

Having read the post in the links given I am a little confused, they specify multiple different drivers to update. How do I know which one I need to update to solve my problem?

#9 hamluis

Moderator

Moderator
56,573 posts
ONLINE

Gender:Male
Location:Killeen, TX
Local time:09:49 AM

Posted 20 February 2011 - 04:50 PM

Any link provided...is done so with the intent of providing a pertinent reference that is similar to a member's problem.

The links are not intended to convey that what worked for one...will work for you. They are only references that seem to relate to your situation.

Louis

#10 kerryboy

Topic Starter

Members
82 posts
OFFLINE

Local time:10:49 AM

Posted 21 February 2011 - 10:36 AM

thanks hamluis, I am just struggling a little bit with which drivers to update and there are a lot of suggestions in the links provided

#11 hamluis

Moderator

Moderator
56,573 posts
ONLINE

Gender:Male
Location:Killeen, TX
Local time:09:49 AM

Posted 21 February 2011 - 03:21 PM

The reason (IMO) for a lot of suggestions when it comes to drivers...are simply the fact that there are so many different drivers which could be problematical...and there is really no reliable way to isolate/determine what drivers are responsible for problems which affect the heart of the Windows system.

Any BSOD which reflects ntkrnlpa.exe as the culprit...is patently inaccurate, IMO. That's merely the scene of the crime, the point at which Windows reached breaking point and called attention to the fact that something is wrong.

Such being the case...you will find a wide variety of suggested fixes and methods to proceed...because the nature of the BSOD doesn't yield itself to a nice, tidy suspect and resolution.

I've personally never received that particular BSOD message...but I would suspect the PSU since it is such an unusual error and it's easy enough for me to swap out PSUs to refute/affirm the PSU as a suspect.

Louis