BSOD related to Isator/Ntoskrnl

[jaybeebrad]

I set up a virtual machine on my laptop and while installing Windows 2000 onto it my computer crashed. Since then I cannot log into my user account or administrator without getting a BSOD crash. I seem to be able to log into safe mode with networking, but that crashes occasionally too.

I've also noticed two things since the crashes started: when I boot up, NUMLOCK is lit up (it didn't used to be,) and also I can't get Google Chrome to work since the crash.

Attached is my log from the Dump & System File Collection. I did not zip it with another file because when I type perfmon /report at the start menu I get an error message that the system cannot find the path specified.

Here are my system stats:
Windows 7 Home Premium with 64 bit OS, OEM and the original OS on the system.
The laptop is about 3 months old.

 

[zigzag3143]

I set up a virtual machine on my laptop and while installing Windows 2000 onto it my computer crashed. Since then I cannot log into my user account or administrator without getting a BSOD crash. I seem to be able to log into safe mode with networking, but that crashes occasionally too.

I've also noticed two things since the crashes started: when I boot up, NUMLOCK is lit up (it didn't used to be,) and also I can't get Google Chrome to work since the crash.

Attached is my log from the Dump & System File Collection. I did not zip it with another file because when I type perfmon /report at the start menu I get an error message that the system cannot find the path specified.

Here are my system stats:
Windows 7 Home Premium with 64 bit OS, OEM and the original OS on the system.
The laptop is about 3 months old.

These were all caused by your iastor.sys driver. I would re-install the newest copy you can find

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\122810-33493-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a55000 PsLoadedModuleList = 0xfffff800`02c92e50
Debug session time: Tue Dec 28 11:53:33.204 2010 (GMT-5)
System Uptime: 0 days 0:00:58.890
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff80002b0f0f3, 2b0f121, fffff80005abd8c0, a}

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+52533 )

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

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff80002b0f0f3, Virtual address for the attempted write.
Arg2: 0000000002b0f121, PTE contents.
Arg3: fffff80005abd8c0, (reserved)
Arg4: 000000000000000a, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xBE

PROCESS_NAME:  taskhost.exe

CURRENT_IRQL:  2

TRAP_FRAME:  fffff80005abd8c0 -- (.trap 0xfffff80005abd8c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=7fffffffffffffff rbx=0000000000000000 rcx=fffffa80025acec0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880012c8533 rsp=fffff80005abda50 rbp=0000000000000000
 r8=fffffa80025acec0  r9=0000000000000000 r10=fffff8800127b6b8
r11=fffff80002ad0bfc r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
iaStor+0x52533:
fffff880`012c8533 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b44448 to fffff80002ac5740

STACK_TEXT:  
fffff800`05abd758 fffff800`02b44448 : 00000000`000000be fffff800`02b0f0f3 00000000`02b0f121 fffff800`05abd8c0 : nt!KeBugCheckEx
fffff800`05abd760 fffff800`02ac382e : fffffa80`04b30010 fffff880`059db370 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x409b4
fffff800`05abd8c0 fffff880`012c8533 : fffff880`03162020 fffffa80`0500a200 fffffa80`04d2e890 00000000`00000000 : nt!KiPageFault+0x16e
fffff800`05abda50 fffff880`03162020 : fffffa80`0500a200 fffffa80`04d2e890 00000000`00000000 00000000`00000002 : iaStor+0x52533
fffff800`05abda58 fffffa80`0500a200 : fffffa80`04d2e890 00000000`00000000 00000000`00000002 fffffa80`047136f0 : 0xfffff880`03162020
fffff800`05abda60 fffffa80`04d2e890 : 00000000`00000000 00000000`00000002 fffffa80`047136f0 fffffa80`04460010 : 0xfffffa80`0500a200
fffff800`05abda68 00000000`00000000 : 00000000`00000002 fffffa80`047136f0 fffffa80`04460010 fffff880`03d5b376 : 0xfffffa80`04d2e890


STACK_COMMAND:  kb

FOLLOWUP_IP: 
iaStor+52533
fffff880`012c8533 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  iaStor+52533

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME:  iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a7c1cc9

FAILURE_BUCKET_ID:  X64_0xBE_iaStor+52533

BUCKET_ID:  X64_0xBE_iaStor+52533

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

Ken J

 

[jaybeebrad]

Okay. I'd be glad to do that but can you give me some help on where to look? I'm on the intel website and it's all Greek to me in terms of what I need to D/L.

It appears the version I currently have is 8.9.2.1002 - Everything I can find on Intel's site that is a driver download for "Intel Matrix Storage Manager" is a much earlier release.

*note - okay. I went to the official Toshiba website and found the download for version 8.9.2.1002 of Intel Matrix Storage Editor, specifically for my make and model (Satellite c655-s5049.) I ran the EXE file and it went through the installation process, then rebooted and went to the BSOD as soon as I logged into my normal user account. So...that didn't fix it.