Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: multiple BSOD caused by ntoskrnl.exe


15 Aug 2011   #1

Windows 7 Ultimate x64
 
 
multiple BSOD caused by ntoskrnl.exe

Hello, a month or so ago (just couple of months after I bought a new PC, pretty decent\expensive for my country) I started to experience a lot of BSODs, only at the time I started any game or any video file. Sometimes I could play for 3-4 hours or watch a video, sometimes it crashes 1-2minutes after I start a game. It works fine while I keep browsing internet in Mozilla though. First I thought my main drive - SSD crashed - we unplugged it and tried to work on my older HDDs (which I kept from my old PC). Same problem. We re-installed Windows multiple times, it kept showing the problem. Usually it does not start right after some new action was taken - like If I change HDD and install a new windows here, a day, two, maybe 3 it works ok with no BSODs at all. BlueScreenView shows mostly always (cant recon a different result) a problem with ntoskrnl.exe.
Once I thought my memory was an issue, but 4-5 circles of Memtest86 didn't show any problems at all.
I run the latest drivers for my graphics card (nvidia geforce gtx 560 ti) and I don't know wheter my video card can cause the problem. What I know is thats its definetely not the HDD or probably my memory, so I can only think about motherboard or graphics card problems.
And to be clear at first my PC just got stuck in games and I had to reboot it, sometimes graphics in games crashed (like flashing, or everything was very smooth(blur), sorry for my english), and a week or two after it started to give me BSOD all the time in games\videos. I used Windows 7 driver verifier and as expected everything was clear.
I'm not good at technical side of the issue but getting a little bit desperate to find a solution I decided to ask for help from the pro's, here are my dumps of BlueScreenView:



==================================================
Dump File : 081711-11372-01.dmp
Crash Time : 17.08.2011 1:59:32
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000088
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`03055ece
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\081711-11372-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 262 192
==================================================

==================================================
Dump File : 081711-10935-01.dmp
Crash Time : 17.08.2011 1:32:10
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000088
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`03063ece
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\081711-10935-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 286 664
==================================================

==================================================
Dump File : 081711-11700-01.dmp
Crash Time : 17.08.2011 1:21:20
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`001eb2ae
Parameter 3 : 00000000`00000001
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\081711-11700-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 286 656
==================================================

==================================================
Dump File : 081711-24835-01.dmp
Crash Time : 17.08.2011 1:09:38
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000088
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`030abece
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\081711-24835-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 290 808
==================================================

==================================================
Dump File : 081711-54475-01.dmp
Crash Time : 17.08.2011 0:43:28
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`00022d37
Parameter 3 : 00000000`00000001
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\081711-54475-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 286 632
==================================================

==================================================
Dump File : 081711-22058-01.dmp
Crash Time : 17.08.2011 0:24:02
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000088
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`0305dece
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\081711-22058-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 286 656
==================================================

==================================================
Dump File : 081511-33353-01.dmp
Crash Time : 15.08.2011 23:58:01
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000088
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`030b3ece
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\081511-33353-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 290 840
==================================================

==================================================
Dump File : 081511-22058-01.dmp
Crash Time : 15.08.2011 15:51:25
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`0021c126
Parameter 3 : 00000000`00000001
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\081511-22058-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 290 824
==================================================







Thanks in advance


My System SpecsSystem Spec
.

15 Aug 2011   #2

Microsoft Community Contributor Award Recipient

Windows 7 x64
 
 

Minidumps have been created they are referenced in your copy/paste logs there.
Could you follow these.

http://www.sevenforums.com/crashes-d...tructions.html
My System SpecsSystem Spec
16 Aug 2011   #3

Windows 7 Ultimate x64
 
 

Yes, sorry.
I uploaded everything in the *.rar file (bluescreen view dumps report, Windows_NT6_BSOD_jcgriff2 folder,perfmon html report)
My System SpecsSystem Spec
.


16 Aug 2011   #4

Windows 7 Ultimate x64
 
 

mmm, anyone?
My System SpecsSystem Spec
16 Aug 2011   #5

Microsoft Community Contributor Award Recipient

Windows 7 x64
 
 

Sorry I didn't forget you I just keep strange hours these days.
The problem appears to be caused by the intel storage driver.
You can find an update for that driver here.
http://downloadcenter.intel.com/Deta...adType=Drivers

Give that a chance, if you get a bsod after applying that update please upload the new minidump file created by it. (c:\windows\minidump)
As all the current dumps are pointing to the storage driver I can't tell if there are any other problems.
Hopefully once the driver is updated/repaired you will either experience no more crashes or the bug report will change allowing me to see what else is going on.

Code:
Probably caused by : iaStor.sys ( iaStor+2cdb1 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000088, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800030abece, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800033040e0
 0000000000000088 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeInsertQueueApc+42
fffff800`030abece f0480fbaab8800000000 lock bts qword ptr [rbx+88h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88003b1d870 -- (.trap 0xfffff88003b1d870)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8008f98b28
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030abece rsp=fffff88003b1da00 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KeInsertQueueApc+0x42:
fffff800`030abece f0480fbaab8800000000 lock bts qword ptr [rbx+88h],0 ds:2180:00000000`00000088=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030cbb29 to fffff800030cc5c0

STACK_TEXT:  
fffff880`03b1d728 fffff800`030cbb29 : 00000000`0000000a 00000000`00000088 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03b1d730 fffff800`030ca7a0 : 00000000`00000002 00000000`00000000 00000000`00000000 fffffa80`08f98ab0 : nt!KiBugCheckDispatch+0x69
fffff880`03b1d870 fffff800`030abece : fffffa80`0408b1a0 fffffa80`044ce080 fffffa80`044ce790 00000000`00000000 : nt!KiPageFault+0x260
fffff880`03b1da00 fffff800`030cf409 : 00000000`00000000 00000000`a000000c 00000000`00000000 00000000`00000000 : nt!KeInsertQueueApc+0x42
fffff880`03b1da60 fffff880`01085db1 : fffff880`0377df20 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0xb89
fffff880`03b1db50 fffff880`0377df20 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`08ea3cf0 : iaStor+0x2cdb1
fffff880`03b1db58 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`08ea3cf0 fffffa80`044ce6c8 : 0xfffff880`0377df20


STACK_COMMAND:  kb

FOLLOWUP_IP: 
iaStor+2cdb1
fffff880`01085db1 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  iaStor+2cdb1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME:  iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dd69c48

FAILURE_BUCKET_ID:  X64_0xA_iaStor+2cdb1

BUCKET_ID:  X64_0xA_iaStor+2cdb1

Followup: MachineOwner
---------
My System SpecsSystem Spec
18 Aug 2011   #6

Windows 7 Ultimate x64
 
 

Ok, three days it worked close to perfect way. Today I decided to plug my SSD back to my PC(i was working on my old hdd) but I couldnt.. first system didnt see it,than PC didn't load at all..so I unplugged it and decided to work some time more on my old HDD to find solutions.. Later on today the system hardly started (once every five times, other times the window got stuck on "starting windows" picture) and now I get completely new bsod, it was saying something about iastor.sys driver or something like that, so I'm at a loss now.. could this be a total motherboard failure and I'll need to replace it..I'm trying to handle this myself because my vendor says it should take about a week to diagnose my PC.
Here is a dump from bluescreenview (i also attached it).

==================================================
Dump File : 081911-78172-01.dmp
Crash Time : 19.08.2011 21:30:46
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff880`0125d16e
Caused By Driver : iaStor.sys
Caused By Address : iaStor.sys+5116e
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\081911-78172-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 286 640
==================================================
My System SpecsSystem Spec
18 Aug 2011   #7

Microsoft Community Contributor Award Recipient

Windows 7 x64
 
 

iastor.sys is the intel rapid storage drivers.

I would reinstall them, it would appear something went screwy when you plugged in the ssd.
http://downloadcenter.intel.com/Deta...adType=Drivers
My System SpecsSystem Spec
18 Aug 2011   #8

Windows 7 Ultimate x64
 
 

but generally,what could be the problem of the bsod which I'm facing so often.. This PC cost me $1,5k excluding monitor and I can't enjoy using it.. well, its hell a lot for my country and I want this resolved coz I'm very annoyed with my PC and I feel scared when I start using it to see another bsod lol .
Should something be replaced? I'm planning to switch to Win XP 64bit maybe,but as far as I understand the problem is not in Win version but in hardware(motherboard?) ?

P.S. I installed these drivers right after I got your message few days ago, so I got my last bsod (and another one while I was writing my previous post) having these drivers installed on my PC...
My System SpecsSystem Spec
18 Aug 2011   #9

Microsoft Community Contributor Award Recipient

Windows 7 x64
 
 

I don't know what to tell you it's still the named driver in every crash dump you have.
My System SpecsSystem Spec
18 Aug 2011   #10

Windows 7 Ultimate x64
 
 

I updated it, but still get the same crashes, any other opinion on this issue? Please, tell me what else can cause my bsod? :|
My System SpecsSystem Spec
Reply

 multiple BSOD caused by ntoskrnl.exe




Thread Tools



Similar help and support threads for2: multiple BSOD caused by ntoskrnl.exe
Thread Forum
Multiple BSOD - Caused by driver ntoskrnl.exe..please help BSOD Help and Support
BSOD caused by ntoskrnl.exe BSOD Help and Support
Solved BSOD caused by ntoskrnl.exe BSOD Help and Support
BSOD - multiple caused by ntoskrnl.exe BSOD Help and Support
Solved multiple BSOD, almost always caused by ntoskrnl.exe+7cc40 BSOD Help and Support
Please Help I get all my BSoD's are caused by ntoskrnl What can I do? BSOD Help and Support
BSOD being caused by ntoskrnl.exe BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 09:52 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33