Solved BSOD random while idling or during light tasks.

[darkronin619]

Just put together a hardly used E5-2680 Xeon workstation. CPU and Intel DX79SI MB had been used for 1 week in a test rig. I had noticed that in the mornings the computer was at the login screen. On login, there would be an error report and to "check for solutions."

I have actually seen 5 BSOD happen...once 5 minutes after completing 8 hours of Prime95, others when the computer is at idle.

I have booted MemtextX86+ and ran 2 full passes with no errors. Temps all seem to be completely in specs.
Since I just put the machine together, havn't tried removing parts yet. The only change from when the computer was first built back on June 1st, was an upgrade from an older Geforce 560 to a Geforce 970.

All drivers are up to date as far as I can tell. Have removed AVG, and am trying Avast...same issues.

BSOD Error Code is 0x0000001E, last crash.

System Specs:
Intel E5-2680 XEON
Intel DX79SI Motherboard
16 GB ram - 4 channel
Vertex2 SSD - 120 Gb system drive
2 x Western Digital 1 TB drives (data and archive)
PC Power & Cooling Silencer 750w

Attached are the dump files. I need my machine to be available at night....rendering, cad design, etc. Thanks in advance for any and all help.
Kit

 

[Arc]

Hi darkronin619.

Sorry to say, but your issue is not determined, and I cannot guide you to a specific way till now. Because there is only one dump included in the zip, and that one is having symbol error while loading with windbg.

I would suggest you to wait for a few more time, and let the PC BSOD for a couple more time. Dont run any disc cleanup program like CCleaner etc within this time, to make it sure that the dumps are not being deleted.

Hopefully we will be able to have a solution here.

In the mean time, you free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs. And you have a lot unnecessary things there.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

 

[darkronin619]

Thanks for the quick tips regarding the Startup Processes. Now do you intend I disable all to narrow down possible causes of the BSOD, or just as a common practice?

I'll keep collecting and submitting Dumps as they (unfortunately) happen.

Thank you again for the help!

Kit

 

[Arc]

Now do you intend I disable all to narrow down possible causes of the BSOD, or just as a common practice?

Both.

 

[darkronin619]

Here's 2 more dumps. One the previous night, computer was at idle, and the next happened 7 minutes ago while browsing the web. Looks like the same stop error.

 

[Arc]

Good job.

The issue is the Intel(R) C600 series chipset SATA AHCI Controller, the Intel Rapid Storage driver.

Update it from Intel Download Center. The Driver Update Utility will be helpful there.

Let us know the situation after doing it.
________________________________________________________________

BugCheck D1, {0, 2, 0, fffff880017470d2}

*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by : iaStorA.sys ( iaStorA+64024 )

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

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fc100
GetUlongFromAddress: unable to read from fffff800032fc1c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
storport!StorPortNotification+22
fffff880`017470d2 488b18          mov     rbx,qword ptr [rax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  linpack_xeon64

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

DPC_STACK_BASE:  FFFFF880038F8FB0

TRAP_FRAME:  fffff880038f8c20 -- (.trap 0xfffff880038f8c20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000001003
rdx=fffffa801c7d4000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880017470d2 rsp=fffff880038f8db0 rbp=fffffa800d4343d0
 r8=0000000000000002  r9=0000000000000000 r10=fffffa801c7d4000
r11=00000000000dac00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
storport!StorPortNotification+0x22:
fffff880`017470d2 488b18          mov     rbx,qword ptr [rax] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030bee69 to fffff800030bf8c0

STACK_TEXT:  
fffff880`038f8ad8 fffff800`030bee69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`038f8ae0 fffff800`030bdae0 : 00000000`00000007 fffff880`0604b0a4 fffffa80`13355608 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`038f8c20 fffff880`017470d2 : fffffa80`00000007 fffff880`06048b34 fffffa80`133541a0 00000000`ffffffff : nt!KiPageFault+0x260
fffff880`038f8db0 fffff880`01124024 : 00000000`ffffff00 fffffa80`1c7d4000 00000000`00000002 00000000`00000000 : storport!StorPortNotification+0x22
fffff880`038f8e30 00000000`ffffff00 : fffffa80`1c7d4000 00000000`00000002 00000000`00000000 fffff880`038f8ea8 : iaStorA+0x64024
fffff880`038f8e38 fffffa80`1c7d4000 : 00000000`00000002 00000000`00000000 fffff880`038f8ea8 ffffcc99`e86e89b4 : 0xffffff00
fffff880`038f8e40 00000000`00000002 : 00000000`00000000 fffff880`038f8ea8 ffffcc99`e86e89b4 00000000`00001800 : 0xfffffa80`1c7d4000
fffff880`038f8e48 00000000`00000000 : fffff880`038f8ea8 ffffcc99`e86e89b4 00000000`00001800 fffff880`0112b168 : 0x2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
iaStorA+64024
fffff880`01124024 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  iaStorA+64024

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStorA

IMAGE_NAME:  iaStorA.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  507ffd86

FAILURE_BUCKET_ID:  X64_0xD1_iaStorA+64024

BUCKET_ID:  X64_0xD1_iaStorA+64024

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd1_iastora+64024

FAILURE_ID_HASH:  {aa4ca8db-dda5-1253-44e8-a5b3d19be9ef}

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

10: kd> lmvm iaStorA
start             end                 module name
fffff880`010c0000 fffff880`01746000   iaStorA  T (no symbols)           
    Loaded symbol image file: iaStorA.sys
    Image path: \SystemRoot\system32\DRIVERS\iaStorA.sys
    Image name: iaStorA.sys
    Timestamp:        Thu Oct 18 18:30:54 2012 (507FFD86)
    CheckSum:         0008D6BD
    ImageSize:        00686000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[darkronin619]

Used the Intel update utility. Swore I had installed everything manually from Intel, but the utility didn't even "detect" any of the already installed Intel drivers.

Went ahead and installed everything, minus the Infrared Driver (I have this disabled in BIOS cause I don't have a sensor, yet)
Chipset Driver and Storage Driver both install fine, but Intel utility says they failed and do not record the current installed version being installed. So for no BSOD's yet.

Gonna give it through the weekend, and if I don't get a crash by Tuesday morning, I think it's been licked.

 

[Arc]

Went ahead and installed everything, minus the Infrared Driver (I have this disabled in BIOS cause I don't have a sensor, yet)

Now that is a better decision. Check which driver is active now.

1. Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
2. Double click to expand "IDE ATA/ATAPI Conreoller".
3. Right click the Items below it and click properties > Deiver > Driver deatils". Is it showing msahci.sys there?

Let us know.

 

[darkronin619]

The listings are a tad different in the Device Manager than you describe. Originally, I believe when Windows7 was first, brand new installed without any of the Intel updates, that the IDE/ATAPI listed was present, but after the Intel Storage Controller install, it disappeared and was replaced with the Disk Drives category, and the Storage Controllers category popped up.

Attached is a screenshot with the instructions and what is actually available.

 

[Arc]

It seems to be SCSI to me. And as it is SCSI, it should be the iastor driver still now, not msahci.

Let us check it. Right click on the highlighted item in your disc management ....

View attachment 365752
​

Then select "properties > Deiver > Driver details". Which driver does it show there?

EDIT: I consulted with my guru essenbe who says this is common for RAID setup. Are you aware of the fact that which Intel IRST driver you have installed? There is a RAID mode driver there, too, of the same name. So that is a big possibility. Boot into the BIOS and see which Storage Controller mode is set there .... IDE, or AHCI or RAID. Let us know.

I will also wait to know the driver shown under driver details.

 

[darkronin619]

The BIOS mode is set to AHCI.

While the symbol is SCSI, everything in the machine is SATA.

It shows 2 instances, iaStorA.sys & iaStorF.sys

C:\Windows\system32\DRIVERS\isStorA.sys

&

C:\Windows\system32\DRIVERS\isStorF.sys

It seems I have been getting crashes again, but there is no message about the crash after bootup.

 

[Arc]

There are no crash dumps in both the zip.

But as it is continuing to crash, and the IRST drivers, the crashers for your case, are still present there, I would suggest you to go for some deeper troubleshooting.

When The AHCI (or IDE) storage controller is applied, it should come under IDE ATA/ATAPI Controllers. When it comes under a Storage controller, it is SCSI, the RAID mode driver for IRST.

Boot into the BIOS. Disable anything saying Intel Rapid Storage and/or Intel Smart Response. Double check to make it sure that the storage controller mode is set to AHCI, and nothing else.
If needed, reset the BIOS to default (clear CMOS) and apply those settings, to make it sure that the SCSI mode IRST driver is not applicable there at all.

Then perform a clean reinstall, without installing the Intel Rapid Storage drivers.

As far as I can say, that is the only way to make your computer free from this particular issue in the long run.

 

[darkronin619]

So I started digging around the web for anything IAstor and Intel Rapid Storage related. Apparently...there have been longstanding issues with the Intel driver over multiple revisions causing the BSODs'.

https://communities.intel.com/message/160599#160599

Anybody having problems with Intel's Rapid Storage Technology enterprise drivers on X79 ?

I thought I had previously installed the updated Intel driver, but when I compared what the Intel RST software said it was, and the actual Driver Details Windows was reporting, the old version was still being reported by Windows.

I am even tried reverting to the Windows native driver and installed the "new" version only to have it do the same thing.

I am going to revert to the native Windows 7 Driver and see how that works out. Most if not all of the folks who rolled back to the Windows driver cleared up their problems.

Some people did say reduced performance, but I am not running a RAID, and am not using UEFI.

Seem like a good course of action?

 

[darkronin619]

No crashes so far.