Power driver state failure -Blue Screen ERROR in DELL XPS i5.

I am always blamed!

The Intel display driver is failing there.

Code:

fffff880`0bfc81e8  fffff880`04d73562Unable to load image igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0x340562

And it seems to be too old.

Code:

    Image name: igdkmd64.sys
    Timestamp:        Mon Nov 29 10:53:11 2010 (4CF338BF)

I see your Laptop is running with a Second Generation i5 processor.

Code:

Processor    Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz, 2501 Mhz, 2 Core(s), 4 Logical Processor(s)

So this one should be applicable for you. Intel® HD Graphics Driver for Windows* 7/8/8.1 64-bit

But, the interesting thing is that the BSOD occurred when MBAM was running.

Code:

PROCESS_NAME:  mbamservice.ex

Better you boot into Safe Mode and scan the entire system with MBAM. Kill any threat it detects.

And, dont forget to remove the startup entries. Dont let anything run there other than the MSC.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

BTW, have you performed a system restore by any chance? You already disabled startup items and updated the intel Graphics driver! There should be a reason behind this reversal.

Let us know how the computer is running after doing these.
_______________________________________________

Code:

............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa8009fd6430, fffffa8009fd6450, 4020015}

GetPointerFromAddress: unable to read from fffff80002f110e8
GetUlongFromAddress: unable to read from fffff80002f11198
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8009fd6430, The pool entry we were looking for within the page.
Arg3: fffffa8009fd6450, The next pool entry.
Arg4: 0000000004020015, (reserved)

Debugging Details:
------------------


BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  fffffa8009fd6430 Nonpaged pool

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  mbamservice.ex

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

STACK_TEXT:  
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

BUCKET_ID:  INVALID_KERNEL_CONTEXT

FAILURE_BUCKET_ID:  INVALID_KERNEL_CONTEXT

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:invalid_kernel_context

FAILURE_ID_HASH:  {ef5f68ed-c19c-e34b-48ec-8a37cd6f3937}

Followup: MachineOwner
---------

OK, Good to know that there is no threat.

So update the display driver, disable the startup items and continue monitoring. Let us know for any further BSOD. :)