BSOD while watching streams/videos and playing games, Error 0x000000d1

[arcazua]

Hi, recently i started getting BSOD's when i play games and start watching a stream/video at the same time.

They happen within 10 to 15 minutes of playing and watching at the same time.

if you need any more information ill do my best to provide it, I'm not that good with computers

thanks in advance

 

[koolkat77]

Hi arcazua and welcome to the forum.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff8800172c0d2}

*** 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+63aa8 )

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

5: 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: fffff8800172c0d2, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f7100
GetUlongFromAddress: unable to read from fffff800032f71c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF880036BFFB0

TRAP_FRAME:  fffff880036b88b0 -- (.trap 0xfffff880036b88b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000001003
rdx=fffffa8012487000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800172c0d2 rsp=fffff880036b8a40 rbp=fffffa80085fe1d0
 r8=0000000000000002  r9=0000000000000000 r10=fffffa8012487000
r11=fffff880036b8b30 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
storport!StorPortNotification+0x22:
fffff880`0172c0d2 488b18          mov     rbx,qword ptr [rax] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030bf1a9 to fffff800030bfc00

STACK_TEXT:  
fffff880`036b8768 fffff800`030bf1a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`036b8770 fffff800`030bde20 : 00000000`00000007 fffff880`080270a4 fffffa80`0eb56608 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`036b88b0 fffff880`0172c0d2 : fffffa80`086841db fffff880`0110a0de 00000000`00000000 fffffa80`0866aad8 : nt!KiPageFault+0x260
fffff880`036b8a40 fffff880`01108aa8 : fffffa80`08844e40 fffffa80`12487000 00000000`00000002 00000000`00000000 : storport!StorPortNotification+0x22
fffff880`036b8ac0 fffffa80`08844e40 : fffffa80`12487000 00000000`00000002 00000000`00000000 fffff880`036b8b38 : iaStorA+0x63aa8
fffff880`036b8ac8 fffffa80`12487000 : 00000000`00000002 00000000`00000000 fffff880`036b8b38 00000000`00000002 : 0xfffffa80`08844e40
fffff880`036b8ad0 00000000`00000002 : 00000000`00000000 fffff880`036b8b38 00000000`00000002 00000000`00000000 : 0xfffffa80`12487000
fffff880`036b8ad8 00000000`00000000 : fffff880`036b8b38 00000000`00000002 00000000`00000000 fffff880`0110fbec : 0x2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
iaStorA+63aa8
fffff880`01108aa8 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  iaStorA+63aa8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStorA

IMAGE_NAME:  iaStorA.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5021378e

FAILURE_BUCKET_ID:  X64_0xD1_iaStorA+63aa8

BUCKET_ID:  X64_0xD1_iaStorA+63aa8

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

5: kd> lmvm iaStorA
start             end                 module name
fffff880`010a5000 fffff880`0172b000   iaStorA  T (no symbols)           
    Loaded symbol image file: iaStorA.sys
    Image path: \SystemRoot\system32\DRIVERS\iaStorA.sys
    Image name: iaStorA.sys
    Timestamp:        Tue Aug 07 21:43:10 2012 (5021378E)
    CheckSum:         0008E07D
    ImageSize:        00686000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

There appears to be a problem with your Intel RST (Rapid Storage Technology) driver which is causing the BSOD's for you. I would recommend that you either uninstall it or install the latest version available.

Daemon Tools/Alcohol %

• Start Menu\Programs\DAEMON Tools Lite

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

As an alternative, many people recommend the use of Total Mounter or Magic ISO

Hard Drive/Storage

Post disk summary using CrystalDiskInfo software: CrystalDiskInfo Standard Edition

• :info: For how to upload a screenshot or file, read here

Make a hard drive test from the hard drive manufacturers website: Hard Drive Diagnostic Procedure

For errors on your Hard drive(s): How to Run Disk Check in Windows 7

From a senior analyst:

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:
There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website). Be sure to update ALL controllers on the motherboard! I STRONGLY suggest not using controller drivers older than mid-2012 with SSD's.
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: Solved Win8 x64 PC reboots when waking from sleep
27 Feb 2013 - I'm starting to see much better reliability with SSD's using current (mid-2012 and later) storage drivers. I have withdrawn my objections to using these devices in everyday systems.

SFC /scannow to check windows for corruption:

How to Repair Windows 7 System Files with System File Checker
1. Click Start

2. In the search box, type Command Prompt
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type

sfc /scannow

and hit enter.

Start up

Keep less stuff at the start-up. Only anti-virus, this helps avoid driver conflicts and improves time to log in to windows.
Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista
How to Change, Add, or Remove Startup Programs in Windows 7

Memtest86+

Run Memtest86+ for at least 8-10 passes. It may take up to 20 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. How to Test and Diagnose RAM Issues with Memtest86+

   Note

Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.

   Tip

Do this test overnight.