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: Fairly frequent BSOD


18 Jul 2010   #1

Windows 7
 
 
Fairly frequent BSOD

Win 7 64, fully updated. Rest of specs you can see in my signature.

about a week ago my computer has been BSOD'ing. It's been running perfectly for more than a year. Haven't installed any new hardware or new drivers that i can think of. Tried to analyze the dmp file myself and the only culprit I noticed was tcpip so i went ahead and updated my ethernet drivers via windows update (probably not the smartest but the easiest). =)

I attached all the crash info as per the sticky

thanks for any help!


My System SpecsSystem Spec
.

18 Jul 2010   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium SP1, clean install, upgrade disc
 
 

Your Dump Report

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Code:
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_BSOD%20analyze[1].zip\Windows7_BSOD_jcgriff2\071310-10250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c11000 PsLoadedModuleList = 0xfffff800`02e4ee50
Debug session time: Tue Jul 13 21:57:50.355 2010 (GMT-4)
System Uptime: 11 days 9:00:04.000
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {88, 2, 1, fffff80002c60ea2}
Unable to load image \SystemRoot\system32\DRIVERS\iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : iaStor.sys ( iaStor+2d990 )
Followup: MachineOwner
---------
0: 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: fffff80002c60ea2, address which referenced memory
Debugging Details:
------------------
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb90e0
0000000000000088 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!KeInsertQueueApc+42
fffff800`02c60ea2 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:  fffff800041f7790 -- (.trap 0xfffff800041f7790)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8008c80208
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c60ea2 rsp=fffff800041f7920 rbp=0000000000000002
r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KeInsertQueueApc+0x42:
fffff800`02c60ea2 f0480fbaab8800000000 lock bts qword ptr [rbx+88h],0 ds:43a8:00000000`00000088=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002c80b69 to fffff80002c81600
STACK_TEXT:  
fffff800`041f7648 fffff800`02c80b69 : 00000000`0000000a 00000000`00000088 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`041f7650 fffff800`02c7f7e0 : 00000000`0000c000 00000000`00000000 00000000`00011031 fffff880`05a56000 : nt!KiBugCheckDispatch+0x69
fffff800`041f7790 fffff800`02c60ea2 : fffffa80`08d94340 fffffa80`07252000 fffffa80`0780f001 00000000`00000000 : nt!KiPageFault+0x260
fffff800`041f7920 fffff800`02c8445b : 00000000`00000000 00000000`a000000c 00000000`00000000 00000000`00000000 : nt!KeInsertQueueApc+0x42
fffff800`041f7980 fffff880`0110a990 : fffffa80`09164280 fffffa80`08c80100 fffffa80`08369b70 00000000`00000000 : nt!IopfCompleteRequest+0xbdb
fffff800`041f7a60 fffffa80`09164280 : fffffa80`08c80100 fffffa80`08369b70 00000000`00000000 00000000`00000000 : iaStor+0x2d990
fffff800`041f7a68 fffffa80`08c80100 : fffffa80`08369b70 00000000`00000000 00000000`00000000 fffff880`010e6e7d : 0xfffffa80`09164280
fffff800`041f7a70 fffffa80`08369b70 : 00000000`00000000 00000000`00000000 fffff880`010e6e7d fffffa80`04b84458 : 0xfffffa80`08c80100
fffff800`041f7a78 00000000`00000000 : 00000000`00000000 fffff880`010e6e7d fffffa80`04b84458 fffff800`041f7b40 : 0xfffffa80`08369b70
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
iaStor+2d990
fffff880`0110a990 ??              ???
SYMBOL_STACK_INDEX:  5
SYMBOL_NAME:  iaStor+2d990
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: iaStor
IMAGE_NAME:  iaStor.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4b2a7b77
FAILURE_BUCKET_ID:  X64_0xA_iaStor+2d990
BUCKET_ID:  X64_0xA_iaStor+2d990
Followup: MachineOwner
You have given us two reports, both indicate the same problem.

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Probably Caused by iastor.sys.
Iastor.sys

Intel Matrix Storage Manager driver - Intel Matrix Storage Manager driver - Intel Corporation

Iastor.sys file description
Productname: Intel Matrix Storage manager Driver
Description: Intel Matrix Storage Manager driver
Company: Intel Corporation

Conclusions
Uninstall and replace iastor.sys, with an updated driver. Update from Intel Website.

Virus Scan
SFC /scannow

www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

If the BSOD continue, after uninstalling the above driver, replace your AntiVirus with Microsoft Security Essentials, and Malwarebytes, use the Windows Firewall
My System SpecsSystem Spec
18 Jul 2010   #3

Windows 7
 
 

hmm...ok, so I believe I have intel's updated RST driver package for my intel SSD drive. Should I still uninstall and replace iastor/Intel Matrix Storage Manager?
My System SpecsSystem Spec
.


18 Jul 2010   #4

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium SP1, clean install, upgrade disc
 
 

Yes, I would uninstall and then install again. You have two reports with the same indication. This BC report, usually points toward a driver. We have to be able to rule out the driver as the cause. If replacement does not work, install the new AntiVirus as suggested. If new BSOD reports are made post, and they will be analyzed.

These reports are not definitive, but merely point the way. We have to follow the trail until we reach our destination.
My System SpecsSystem Spec
18 Jul 2010   #5

Windows 7
 
 

ok, well i uninstalled and reinstalled lastest RST drivers...we'll see

thanks for the help!
My System SpecsSystem Spec
18 Jul 2010   #6

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium SP1, clean install, upgrade disc
 
 

Enjoy the computer.

If it happens again, change your antivirus as indicated in my post, above.

If it still continues, just post and the new BSOD will be analyzed. Based upon the reports submitted, it was caused by the Driver, but it could been caused by the interaction of the driver and memory. If it does happen again, and the report is the same, I will give you an easy memory diagnositic to check the memory.
My System SpecsSystem Spec
Reply

 Fairly frequent BSOD




Thread Tools



Similar help and support threads for2: Fairly frequent BSOD
Thread Forum
BSOD fairly random 0x0000000a IRQL_NOT_LESS_OR_EQUAL BSOD Help and Support
BSODs fairly frequent, 0xf4, no dump created BSOD Help and Support
BSOD Fairly New PC, error 0x50 BSOD Help and Support
Solved BSOD - son's computer so activity at time unknown. Fairly frequent. BSOD Help and Support
Solved Daily BSOD on a fairly recent install BSOD Help and Support
Random BSOD's....though fairly often BSOD Help and Support
Fairly regular BSOD after a few hours. 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 01:31 PM.
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