Solved Random BSOD's during Start up or running - 0x000000d1, 0x0000005, etc

[hy2vieira]

Hello.

I am having several BSOD's during start ups or running in a random manner, Please Help.
Next are the some components that appear in the BSOD's:
iaStor.sys
ntoskrnl.exe
win32k.sys

Attached are the minidump files.

Thanks in advance.

Best Regards.

 

[Arc]

Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions

BugCheck D1, {9e, 2, 0, fffff880014d6ce6}

*** 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+49ce6 )

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

4: 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: 000000000000009e, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880014d6ce6, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c8100
GetUlongFromAddress: unable to read from fffff800030c81c0
 000000000000009e Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
iaStor+49ce6
fffff880`014d6ce6 418b4918        mov     ecx,dword ptr [r9+18h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

TRAP_FRAME:  fffff88002d64890 -- (.trap 0xfffff88002d64890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800afeb7c8 rbx=0000000000000000 rcx=000000000ace6cb8
rdx=fffffa800b36a6c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880014d6ce6 rsp=fffff88002d64a28 rbp=fffffa800ace6000
 r8=0000000013e38608  r9=0000000000000086 r10=0000000000010000
r11=0000000013e38608 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
iaStor+0x49ce6:
fffff880`014d6ce6 418b4918        mov     ecx,dword ptr [r9+18h] ds:00000000`0000009e=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8ae69 to fffff80002e8b8c0

STACK_TEXT:  
fffff880`02d64748 fffff800`02e8ae69 : 00000000`0000000a 00000000`0000009e 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02d64750 fffff800`02e89ae0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`09d0e100 : nt!KiBugCheckDispatch+0x69
fffff880`02d64890 fffff880`014d6ce6 : fffff880`014d72da fffffa80`09d0e100 fffff880`014e383f 00000000`00000000 : nt!KiPageFault+0x260
fffff880`02d64a28 fffff880`014d72da : fffffa80`09d0e100 fffff880`014e383f 00000000`00000000 fffffa80`09d0e1a0 : iaStor+0x49ce6
fffff880`02d64a30 fffffa80`09d0e100 : fffff880`014e383f 00000000`00000000 fffffa80`09d0e1a0 fffffa80`09db4010 : iaStor+0x4a2da
fffff880`02d64a38 fffff880`014e383f : 00000000`00000000 fffffa80`09d0e1a0 fffffa80`09db4010 fffffa80`09d0e1a0 : 0xfffffa80`09d0e100
fffff880`02d64a40 00000000`00000000 : fffffa80`09d0e1a0 fffffa80`09db4010 fffffa80`09d0e1a0 fffffa80`0afeb7c8 : iaStor+0x5683f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
iaStor+49ce6
fffff880`014d6ce6 418b4918        mov     ecx,dword ptr [r9+18h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  iaStor+49ce6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME:  iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a287aa4

FAILURE_BUCKET_ID:  X64_0xD1_iaStor+49ce6

BUCKET_ID:  X64_0xD1_iaStor+49ce6

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd1_iastor+49ce6

FAILURE_ID_HASH:  {09672e37-b69d-a08b-3243-97e71bcb11a8}

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

4: kd> lmvm iaStor
start             end                 module name
fffff880`0148d000 fffff880`015a9000   iaStor   T (no symbols)           
    Loaded symbol image file: iaStor.sys
    Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
    Image name: iaStor.sys
    Timestamp:        Fri Jun 05 07:23:40 2009 (4A287AA4)
    CheckSum:         000640D7
    ImageSize:        0011C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[hy2vieira]

Thank you Arc.
I tried to follow the instructions but the Norton Suite does not permit to run the dm log collector. Norton said, the file is a kind of malware, so I uploaded the minidumps files. I will try to reinstall the Intel Matrix Software. Thank you very much.

 

[Arc]

We need the files to help you. If you connot provide those, that is your loss.

If norton says the DM Log collector is a malware, norton is a liar. And there is no doubt that norton is a crapware. Check the BSOD threads and see how many BSODs are caused by only Norton.

 

[hy2vieira]

Hello

I reinstall the Intel Matrix Software but the problem persist. The PC is running stable just in safe mode. I run the dm log collector in safe mode. Atthached are the zip file generated by dm log collector. Please help.

Thanks in advance.

Best Regards.

 

[Arc]

It is the same thing causing the BSOD. The Intel RAID driver.

Name    Intel(R) ICH8R/ICH9R/ICH10R/DO/PCH [COLOR=Red]SATA RAID Controller[/COLOR]
Driver    c:\windows\system32\drivers\[COLOR=Red]iastor.sys[/COLOR] (8.9.0.1023, 399.02 KB (408,600 bytes), 3/20/2010 4:54 PM)

BugCheck D1, {ffffef8021af3ec0, 2, 1, fffff8800148608a}

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

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

The same grandfather driver, prior to windows 7 era.

    Image name: iaStor.sys
[COLOR=Red]    Timestamp:        Fri Jun 05 07:23:40 2009[/COLOR] (4A287AA4)

And ASUS does not have a feasible update to it. Motherboards | P6T Deluxe V2 | ASUS Global

In this condition, you have two things to try.

First option, try to update the driver from Intel Download Center. https://downloadcenter.intel.com/
Intel might have an update o it, as expected. If you can have a proper update, the computer is expected to run stable for next six months at most, as expected. Then it will continue to fail again. Because RAID is problematic by its own virtue. If RAID is not a must for you, you should not use it at all. And if it is a must for you, you have to adjust with those ongoing troubles. So if you go for the update way, leave this thread open after the issue is solved for the time being.

Second option, to not use iaStor. That will not be very easy in your case, as it is used as RAID. If you uninstall the driver, the RAID setup will automatically install the driver via windows update on the next restart. So, to stop using iaStor, you need to de-RAID the system.

And here comes the problem. Windows can boot only with the native storage controller mode on which it is installed. So de-RAIDing the system will make the computer unbootable at all.

So, if you want to de-RAID, first get prepared for a clean reinstall, back up the user data elsewhere. Then de-RAID the system, and perform a clean reinstall.

I explained the issue as far as I can, you have both the options open .... decide which one will suit your needs and do accordingly.

Let us know your decision, and the results.

EDIT: Virtual CloneDrive is also another problematic element. It is better to not use such programs those install a SCSI to emaluate hardware.