Frequent BSOD 0x0000007A and 0x000000F4

[Zs7879]

Hi guys,

I've been trying to solve this issue for a while: cleaning up, updating the drivers, checking the windows hot fixes and updates, chkdsk, but to no avail as the BSOD now crashes within an hour my Lenovo Ideapad S300.
I had the laptop for about a year, worked like a charm until about a month ago. I'm not so sure what triggered the BSODs.
Chkdsk /f seemed to fix the issue for a short while, then they started again and became more frequent.
I really appreciate any help. Could it be some sort of hardware problem, as I read suggested on some websites?
I've used the SF Diagnostic Tool, please check out attached the report and please let me know if you need additional info.

 

[HarriePateman]

Can you attach an english file

 

[HarriePateman]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8800ad89000, 2, 0, fffff88004ef985a}

*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : [COLOR="Red"]igdkmd64.sys ( igdkmd64+c885a )[/COLOR]

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8800ad89000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88004ef985a, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003905100
GetUlongFromAddress: unable to read from fffff800039051c0
 fffff8800ad89000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
igdkmd64+c885a
fffff880`04ef985a 8b0407          mov     eax,dword ptr [rdi+rax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  [COLOR="red"]WIN7_DRIVER_FAULT[/COLOR]

BUGCHECK_STR:  [COLOR="red"]0xD1
[/COLOR]
PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre

TRAP_FRAME:  fffff880095dcdb0 -- (.trap 0xfffff880095dcdb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000ffe rbx=0000000000000000 rcx=0000000000000ffe
rdx=fffff8a013c11b89 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004ef985a rsp=fffff880095dcf40 rbp=fffff880095dd080
 r8=fffff880095dce88  r9=0000000000000002 r10=000000001b324000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
igdkmd64+0xc885a:
fffff880`04ef985a 8b0407          mov     eax,dword ptr [rdi+rax] ds:00000000`00000ffe=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800036cd169 to fffff800036cdbc0

STACK_TEXT:  
fffff880`095dcc68 fffff800`036cd169 : 00000000`0000000a fffff880`0ad89000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`095dcc70 fffff800`036cbde0 : fffff880`00000027 fffff880`05155c88 fffff880`095dce80 fffff8a0`1379b7a0 : nt!KiBugCheckDispatch+0x69
fffff880`095dcdb0 fffff880`04ef985a : fffffa80`08acd000 00000000`1b324ffa fffff880`0000ad88 fffff6fc`40056c40 : nt!KiPageFault+0x260
fffff880`095dcf40 fffffa80`08acd000 : 00000000`1b324ffa fffff880`0000ad88 fffff6fc`40056c40 00000000`00000000 : igdkmd64+0xc885a
fffff880`095dcf48 00000000`1b324ffa : fffff880`0000ad88 fffff6fc`40056c40 00000000`00000000 00000001`095dd168 : 0xfffffa80`08acd000
fffff880`095dcf50 fffff880`0000ad88 : fffff6fc`40056c40 00000000`00000000 00000001`095dd168 fffff801`00000ffe : 0x1b324ffa
fffff880`095dcf58 fffff6fc`40056c40 : 00000000`00000000 00000001`095dd168 fffff801`00000ffe 00000002`00000ffe : 0xfffff880`0000ad88
fffff880`095dcf60 00000000`00000000 : 00000001`095dd168 fffff801`00000ffe 00000002`00000ffe 00000000`00000001 : 0xfffff6fc`40056c40


STACK_COMMAND:  kb

FOLLOWUP_IP: 
igdkmd64+c885a
fffff880`04ef985a 8b0407          mov     eax,dword ptr [rdi+rax]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  [COLOR="red"]igdkmd64+c885a[/COLOR]

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME:  igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51cc552e

FAILURE_BUCKET_ID:  X64_0xD1_igdkmd64+c885a

BUCKET_ID:  X64_0xD1_igdkmd64+c885a

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd1_igdkmd64+c885a

FAILURE_ID_HASH:  {f9d90cee-43d2-e514-b08c-011422728a3a}

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

Cause by you Intel Graphics Driver, Try updating it. And let me know how it goes.

https://downloadcenter.intel.com/Default.aspx

 

[Zs7879]

wow, HarriePateman, that was so quick!

I upgraded the Graphics Driver and so far so good, I'll let you know how it goes through the day!

but many thanks already!

 

[HarriePateman]

No worries, welcome to sevenforums stay active.

Let me know how it goes.

 

[Zs7879]

well. it worked like a charm the whole day, until I tried in the evening to send from my gmail in Opera an image as attachment.
it then froze and a few seconds later I got the BSOD with the F4 error.
the same happened after I tried to simply open the image from Explorer with IrfanView - and it was a small JPG, not a big file at all. it froze then BSOD, same error.
I checked and the driver is updated: Intel (R) HD Graphics 3000, 1/29/2014, version 9.17.10.3347. Maybe I should try with another driver?

 

[HarriePateman]

Can you attach new Dmp files please.

 

[Zs7879]

here attached the dump file.
It worked again just fine until I copied a few files (including images) from a folder to a USB stick.

 

[Zs7879]

couple of days later - the worse has clearly passed.
thanks once again for helping so swiftly.

 

[HarriePateman]

No worries Glad i could help you.

Stay Active